Page 1 of 1
[SOLVED] Agent update on a 2003/samba3 server
Published: March 29, 2018 - 3:37 PM
by Raphael
Good morning.
Just in case!
For those still using a 2003 server or a Samba 3 server (yes, it's possible)
), user accounts do not generally have the right to install software.
Following the update to version 1.5, I am using the cpau utility:
http://www.joeware.net/freetools/tools/cpau/index.htm
Below is the script that tests the version on a text file and launches an encrypted "job" to prevent the display of credentials:
Code: Select all
echo off
WMIC DATAFILE WHERE name="c:\\wapt\\wapt-get.exe" get Version /format:Textvaluelist > c:\versionwapt.txt
find "Version=1.5.1.18" c:\versionwapt.txt
if %errorlevel% equ 1 goto pasbon
goto end
:pasbon
echo off
"\\serveur\netlogon\cpau.exe" -dec -file "\\192.168.1.254\serveur\zwapt.job" -lwp
echo off
:end
To create the job:
Code: Select all
- cpau -u domain\user -p pass -ex "\\serveur\netlogon\waptagent" \verysilent -enc -file "\\serveur\netlogon\zwapt.job"
Re: Agent update on a 2003/samba3 server
Published: March 30, 2018 - 5:22 PM
by agauvrit
Hello,
Even though it's documented online, this is a very bad practice for deploying WAPT.
Consider migrating to Windows Server 2012+ and/or Samba4 instead; it will be healthier for everyone.
Regards,
Alexandre
Re: Agent update on a 2003/samba3 server
Published: April 5, 2018 - 7:48 PM
by dcardon
Hello Raphaël,
Thank you Raphaël for your contribution to the forum, but I can't help but react to your post, because I see this mistake made too often.
Raphael wrote: ↑March 29, 2018 - 3:37 PM
For those still using a 2003 server or a Samba 3 server (yes, it's possible
!), user accounts generally don't have the right to install software.
After updating to version 1.5, I'm using the cpau utility:
http://www.joeware.net/freetools/tools/cpau/index.htm
Below is the script that tests the version on a text file and runs an encrypted job to prevent the display of login credentials:
DO NOT USE CPAU.EXE FOR YOUR DEPLOYMENTS!!!!!
It's very easy to recover the password for a CPAU .job file. If you don't believe me, try it with the API Monitor utility [1]. You can refer to the page for guidance
https://micksmix.wordpress.com/2013/03/ ... -software/
In just 2 minutes, we can retrieve the administrator password for your workstations (including tool download)... If you're having trouble following the tutorial above (there's one detail that isn't explained clearly, just to make it a little more advanced than a script kiddie), you can send me your CPAU job file, and I'll send you your password...
And anyway, if we have to resort to using CPAU, IPC$ and ADMIN$ are probably also open, and PSExec will do the job better (even though it's really not recommended at all). There are also some antivirus programs that have basic deployment features. And then (to lighten the mood), while we're at it, check if it's also possible to exploit the EternalBlue vulnerability; sometimes it can be helpful
.
Good evening everyone,
Denis
PS: For Win2k3 users, deployment via GPO works very well!
[1]
http://www.rohitab.com/apimonitor