Endpoint Protection

Hi, we've set our installation package to automatically reboot after installation, and when we use the deployment wizard to deploy to more than half a dozen machines, it fails to reboot the machine after the install.  Yet, when we install on 1 client using the same method, the reboot works.  Anyone know why this happens (or doesn't happen)?

Thanks,
Dan

make the modification as per this doc and do a push install
MSI command line reference for Symantec Endpoint Protection 11.0
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101610183248

Wow, that's a lot of technical reading!

I found the setup.ini file for our current install package, and there is a line there that reads:

SuppressReboot=Y

in the [Startup] section.

Should I change this to SuppressReboot=N?

i think that one is for the reboot pop up

Hi Rafeeq, what INI file can you recommend we set to force the reboot?

I have no idea how to do an MSI installation but there should be something to force the reboot after the install.  Can you please check to see whether the setting I mentioned above does what it's supposed to do, or does it do what you suggested in your previous message?

This is critical for us, as we require the machine to be rebooted, without fail.  Otherwise, during our full deployment, we'll be up till the wee hours of the morning rebooting clients manually and checking each one to ensure it was rebooted.

once the installation is doen, it should reboot,
however it reboots if you run it manually
are u running a silent install ?
what are your install settings?

On Edit Client INstall settings:

Installation type:  Silent
Restart after installation
Install to custom folder:  (D:\Program Files\Symantec)
Enable installation logging
Add the program to the start menu
Remove all previous logs & policies

Fairly simple and straightforward.  But not always consistent.

export a package with UI and run the install
since this is in silent mode, it might waiting for an input
lets run the install in unattended, run it on one machine lets see if we get any msg / pop up
that might lead to an solution.

Hi Rafeeq, this method (unattended install) won't work for us, because it prompts the user at the end of the install procedure to reboot his or her computer.  We must have silent install, so that the user is not aware that anything has happened to their computer the next day.