Run Script as Administrator

[TSCNUK]

We have received 3 update files in the form of .msp packages. I have written a piece of script to run all three passivly and it works. However it will only run as an administrator. Is there a way either through login scripts or through the loginscript element of group policies to make the script work, either on its own or by forcing it to run as administrator/system?

 

Thanks

 

Tom

[Ric_]

The whole point of a .MSP file is to update an administrative install of a product. If you simply apply the .MSP to the admin install point, your clients (which have installed the app using a .MSI via GPO) will automagically upgrade without needing a script.

[ajbritton]

The whole point of a .MSP file is to update an administrative install of a product. If you simply apply the .MSP to the admin install point, your clients (which have installed the app using a .MSI via GPO) will automagically upgrade without needing a script.

 

Not quite! An MSP can be used to patch an Admin install point, or an installed application. Assuming the application has been installed from an admin installation point and the patch subsequently applied to that install point, then the application would need 're-cacheing' on the PC, using a command like...

 

msiexec /i [path to updated .msi file on the administrative image] REINSTALL=ALL REINSTALLMODE=vomu /qb

 

I suppose this could be done with a Startup Script.

 

It may also be possible to select the 'redeploy application' action on an assigned MSI but I don't know exactly what effect this would have.

[ChrisH]

It may also be possible to select the 'redeploy application' action on an assigned MSI but I don't know exactly what effect this would have.

 

It does what it says it says on the tin!

[ajbritton]

It may also be possible to select the 'redeploy application' action on an assigned MSI but I don't know exactly what effect this would have.

 

It does what it says it says on the tin!

 

OK, so is that an un-install followed by a reinstall, or a repair, or a re-cache? I've seen differing behaviour from this action, depending on the MSI file.

[NetworkGeezer]

We have received 3 update files in the form of .msp packages. I have written a piece of script to run all three passivly and it works. However it will only run as an administrator. Is there a way either through login scripts or through the loginscript element of group policies to make the script work, either on its own or by forcing it to run as administrator/system?

 

Thanks

 

Tom

 

 

If for some reason you can persue the GPO installtion as per ChrisH and ajbritton then your best bet is a startup script. This will have admin privilidges. Alternative you can set a scheduled job on the target computers to run the script. This will aslo be procesed with admin powers.

 

The last option might be to use the EXE packager in AdminScriptEditor to created an encrypted executable. This would allow you to place an explitict run as command in you script with a plain text admin password.

[ajbritton]

The trick with running a seperate script will be to make sure the script only runs once. There are many ways of doing this, but basically what is needed is some kind of 'flag' on the target PCs. The script should check for the presence of the flag before running the update. If the flag is not present, then the update may be run and the flag set to prevent future runs of the script.

 

example CMD script

 

rem Check for flag
if exist C:\AppName_Update_X.txt then goto jExit
rem - add script code here to install Update X for AppName

rem - Add the flag
echo Update X installed at %TIME% on %DATE% > C:\AppName_Update_X.txt
:jExit

[NetworkGeezer]

You could also have markers in the registry using the REG command (or KiX or VBS/JS) but the main problem remains how to how run with elevated privilidges with out having clear text logon details readable by non-tech users.

[ajbritton]

the main problem remains how to how run with elevated privilidges with out having clear text logon details readable by non-tech users.

 

Assuming you have Active Directory, then a Startup Script will do it as you pointed out.