/build/static/layout/Breadcrumb_cap_w.png

Software install via startup script

Hi all, my first post so please bare with me. GPO and scripts are still new to me ;)

Ok, we currently use McAfee Total Protection on all our workstations. At the moment we either install it locally (by physically going to the workstation) or manually push it out via a web interface, either way it’s a pain in the butt. In an attempt to automate the install process we created a startup script which simply runs the setup.exe with a couple of switches from a network share. Script is as follows:

\\servername\software\vssetup.exe /ck=companylicensekey /email=%computername%

The script works when it’s processed for the first time. However when the workstation is rebooted the script is reprocessed again? Why? I was under the impression a script is ran once unless a change has been made. Anyhow, as it's reprocessed the vssetup.exe automatically forces an uninstall of the existing McAfee and then reinstalls. This in turn forces the machine to reboot and the script is applied yet again. The workstation ends up in a constant loop!

Any ideas or suggestions would be greatly appreciated.

Note - we decided to install via a script (rather than repacking with an msi) as we can specify the /email switch. This allows us to identify each computer as we can see the workstation name with the McAfee web portal. If we simply repackaged and installed the /email switch wouldn’t be applied and the machine we wouldn’t be able to identify the workstation.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: AngelD 16 years ago
Red Belt
0
In your startup script check if it's installed and if not then execute the command.
Startup scripts runs each time the computer starts, hence the name.
Posted by: preecy 16 years ago
Senior Yellow Belt
0
Thanks for the prompt response ;)

Sorry to be dumb but im not sure what you mean by 'In your startup script check if it's installed'?

The startup script works as McAfee does get installed during startup. If we run the gporesult command on the workstation we can also see the script was applied under the computer configuration section. Also, if we run the string/command line (which is in the startup script) in a dos prompt and on a workstation which does not have McAfee already installed, it works fine. The problem is... when a workstation is rebooted the startup script is reapplied for a second time, this forces McAfee to automatically uninstall the current copy and then reinstall it. Once McAfee has been reinstalled the computer then requires a reboot. Upon rebooting the script runs yet again (for a 3rd time) which uninstalls/reinstalls McAfee and reboots. This happens again and again and the workstation ends up in a loop of reboots.

I hope that makes some kinda sense..

My understanding of gpo's were they are only applied once unless you modify them? In other words a computer would apply the gpo the first time, then ignore the gpo unless it has changed. If i am wrong please do correct me. Also, if this is the case is there anyway we can make the startup script run only once on each machine? Or should we be going about this in a different manor?

Again, thanks for your help ;)
Posted by: mehappy 16 years ago
Orange Belt
0
ORIGINAL: preecy

Sorry to be dumb but im not sure what you mean by 'In your startup script check if it's installed'?



IF: Internal MS-DOS command. Performs conditional processing in batch programs.

IF [NOT] EXIST filename command.

IF NOT EXIST filename. (
CALL [pathto]install.cmd
) ELSE (
echo filename. exist.
)

And Vice Versa. IF EXIST filename......
Posted by: AngelD 16 years ago
Red Belt
0
ORIGINAL: preecy
My understanding of gpo's were they are only applied once unless you modify them? In other words a computer would apply the gpo the first time, then ignore the gpo unless it has changed. If i am wrong please do correct me. Also, if this is the case is there anyway we can make the startup script run only once on each machine? Or should we be going about this in a different manor?

No the computer based GPO is applied each time the computer boots-up.

Follow mehappy's example and you should be fine.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ