snapin and batch script

plegrand

@Tom-Elliott In fact i will not use “UpdateInstaller.exe” IRl. I will use a command line with arguments like that :

"call W:\cmd\DoUpdate.cmd /verify /updatecpp /updatetsc /instdotnet4 /autoreboot"

But this command doesnt open a window then for my test i cant see if the command is well launched or not.

But for the moment my problem is : how mount a samba share with snapin which is usable by administrator user

Tom Elliott

@plegrand You can’t. Not with snapins in that sense. It will be mounted by the SYSTEM user only as that’s how snapins run.

Avaryan

@plegrand said in snapin and batch script:

But for the moment my problem is : how mount a samba share with snapin which is usable by administrator user

What version of Windows would this Snapin be run on?

plegrand

@Tom-Elliott may be with psexec tool ?
For the moment i cant make it works syntax problem but with snapin pack ?

plegrand

@Avaryan Windows 7 and Windows 10

Tom Elliott

@plegrand I am pretty sure, no amount of tries (with or without) snapin pack, snapin plain, psexec, powershell, batch, vbscript, or any thing else will get this working for you.

The first step would be to find out if the command is actually needing user input. Snapins cannot operate with the user environment.

Wayne Workman

@Tom-Elliott said in snapin and batch script:

Essentially, the reason why the “red x” happens is because System user is who mounted the point, and the permissions are not available to the user you’re actually logged in under. If you need a “global” mount of a drive, this would be more readily handled using GPO’s, not fog snapins. While I’m sure it “could” be handled via a snapin, i think such a thing is out of scope for the FOG Client.

This is correct, use Group Policy to do this. Either in a startup script or a login script. That’s how I’ve always accomplished it.
Additionally, you don’t even need to script it because Group Policy has native functionality for mapping & mounting remote volumes.

plegrand

@Tom-Elliott as i said before the command i will use will not need user input :

I will use a command line with arguments like that :

"call W:\cmd\DoUpdate.cmd /verify /updatecpp /updatetsc /instdotnet4 /autoreboot"

once share mounted in w:

I would like to update my computer once image deployed, for that i use “WsusOffline”
WsusOffline is located on a samba share, then i have to mount the samba share, in “w:” for example, and then launch this command :

W:\cmd\DoUpdate.cmd /verify /updatecpp /updatetsc /instdotnet4 /autoreboot"

from the samba share

Avaryan

Based on a couple minutes of research, I don’t think you can run UpdateInstaller.exe silently. So this is likely just not going to work.
http://www.wsusoffline.net/docs/

plegrand

@Avaryan said in snapin and batch script:

UpdateInstaller.exe

is only for testing, the command i want to launch is :

"call W:\cmd\DoUpdate.cmd /verify /updatecpp /updatetsc /instdotnet4 /autoreboot"

from the samba share

Tom Elliott

@plegrand Does the “DoUpdate.cmd” script call UpdateInstaller.exe?

plegrand

@Tom-Elliott no
It works alone without waiting something from the user

Tom Elliott

@plegrand So have you tried with using the DoUpdate.cmd instead of trying with UpdateInstaller.exe?

plegrand

@Tom-Elliott @Avaryan
It works !!! with psexec
for the moment from command line, then i need to package my script and psexec ?

here is the command :

psexec \\%computername% -u %computername%\Administrateur -p password -e cmd /c "net use y: \\samba\wsus$ "my'password" /User:samba\Administrateur & y:\wsusoffline\client\UpdateInstaller.exe"

UpdateInstaller.exe open a windows and wait for user input.
For the moment i dont if it will works with snapin

plegrand

@plegrand yes
but for the moment nothing happen
I’m trying snapin pack
with this command :

psexec \\%computername% -u %computername%\Administrateur -p password -e cmd /c "net use y: \\samba\wsus$ "my'password" /User:samba\Administrateur & y:\wsusoffline\client\cmd\DoUpdate.cmd /verify /updatecpp /updatetsc /instdotnet4 /autoreboot"

i made a zip with my batch script (test.bat) and psexec

Snapin Type Snapin Pack
Snapin Pack Template Batch Script
Snapin Pack File cmd.exe
Snapin Pack Arguments /c “[FOG_SNAPIN_PATH]\MyScript.bat”
Snapin File Max Size:1900M test.zip
Snapin Command cmd.exe /c “[FOG_SNAPIN_PATH]\MyScript.bat”

Wayne Workman

@plegrand You know, most people just keep their images updated so they don’t have to worry about this so much. I know some of the community do quarterly images while others do annual images.

You’d probably have better luck just opening an Amazon Web Services account and installing Systems Manager into your image so you can control patching through AWS. This tool is specifically built for this, among a few other things.

Or, just a WSUS server and some group policy to control how updates work.

plegrand

@Tom-Elliott
I cant make it works for the moment with snapinpack, I’ve got an error that i don’t understand :

17/05/2017 08:42 Client-Info Client Version: 0.11.11
17/05/2017 08:42 Client-Info Client OS:      Windows
17/05/2017 08:42 Client-Info Server Version: 1.3.5
17/05/2017 08:42 Middleware::Response Success
17/05/2017 08:42 SnapinClient Snapin Found:
17/05/2017 08:42 SnapinClient     ID: 103
17/05/2017 08:42 SnapinClient     Name: Update Windows 7
17/05/2017 08:42 SnapinClient     Created: 2017-05-17 08:41:24
17/05/2017 08:42 SnapinClient     Action: 
17/05/2017 08:42 SnapinClient     Pack: True
17/05/2017 08:42 SnapinClient     Hide: False
17/05/2017 08:42 SnapinClient     Server: 
17/05/2017 08:42 SnapinClient     TimeOut: 0
17/05/2017 08:42 SnapinClient     SnapinPack File: cmd.exe
17/05/2017 08:42 SnapinClient     SnapinPack Args: /c "[FOG_SNAPIN_PATH]\test.bat" >> %tmp%\test.log 2>&1
17/05/2017 08:42 SnapinClient     File: test.zip
17/05/2017 08:42 Middleware::Communication Download: http://192.168.39.243/fog/service/snapins.file.php?mac=D0:67:E5:0C:6A:1A||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=103
17/05/2017 08:42 SnapinClient C:\Program Files\FOG\tmp\test.zip
17/05/2017 08:42 SnapinClient Processing SnapinPack test.zip
17/05/2017 08:42 SnapinClient Extracting SnapinPack
17/05/2017 08:42 SnapinClient ERROR: Compressed size mismatch between central header(161385) and local header(0)
17/05/2017 08:42 Middleware::Communication URL: http://192.168.39.243/fog/service/snapins.checkin.php?taskid=103&exitcode=-1&mac=D0:67:E5:0C:6A:1A||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json

An idea ?

plegrand

@plegrand
It seams that i have to create the zip file on windows , on linux i have this error.
After that the snapin pack is launched but i think it’s waiting interaction with user and even i use psexec the script is launch by system. Then it doesn’t works.
I have to find an other solution

Quazz

Psexec needs the EULA to be accepted on first use (I’m guessing per user basis even)

So add -accepteula maybe.

edit: But given you only to execute commands on the local system as a different user, runas is likely the easier/better tool for the job.

edit2: Just remembered you can’t pipe passwords to it, nvm

plegrand

@Quazz
I think the problem is that snapin is launched as SYSTEM user, then even i use psexec or runas to run command as local user, snapin is launched as SYSTEM and then it does not works. I try with -accepteula but …

snapin and batch script

168

12.0k

17.3k

155.2k