Video Screencast Help

Windows XP SP3 SEP Client upgrade took 3 times to working fine ?

Created: 09 Aug 2012 | 5 comments

Hi People,

I have deployed SEP v 12.1 RU1 client into my Windows 7 SP1 64 bit workstation group and it works fine so far with just one reboot needed. However, when my client is Windows XP SP3 32 bit with SEP v 11.0.4 somehow it took 3 times to restart for the upgrade to become normal with green tick ?

Is this normal ? from what I can see is that I have selected the client all of the SEP components required.

 

· First reboot is for previous version app removal

· Second reboot is for app install

· Third reboot is for app install finalisation 

Is there any way to reduce the number of reboot if possible ?

Thanks

Comments 5 CommentsJump to latest comment

Simpson Homer's picture

The number of reboots that it takes is kind of abnormal.

But with the wya ur mentioning the process, it seems to be normal.

Dushan Gomez's picture

That is why I'm asking.

My Quad Core i5 laptop with SSD can boot up in under 10 seconds but for some older workstations and laptop it is very slow, some can take 10 minutes to properly boot.

this number times 3 means productivity lost not to mention if the Execs workstation is rebooted 3 times, then they begin to question this product effectiveness then my career accountability & ability for sure :-|

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP

 

Ashish-Sharma's picture

Hi Dushan,

there's no issue to resolve, in few words SEP is made by drivers and services and Windows needs a reboot to load them.

You may set your installation package to "no restart"so you can control it but it does not mean you can avoid it and the SEPM just reflects it.

 

Migrating the SEPM would not require any reboots. However, when Migrating the SEP clients you may require a reboot of the SEP client machines. Network Threat Protection (firewall) drivers would require a restart of the machines to get themselves activated. However, these could be taken care off by creating custom package and avoiding the restart of machines.

Creating custom client installation packages in the Symantec Endpoint Protection Manager console version 12.1

http://www.symantec.com/docs/TECH165801

NOTE: You may have to restart the machine before the next migration or once the machine is ideal and out of production hours; whichever is earlier.

Thanks In Advance

Ashish Sharma

 

 

Dushan Gomez's picture

Aashish,

"Migrating the SEP clients you may require a reboot of the SEP client machines" --> migrating ? what do you mean ? is it migrating from one OU to another OU in SEPM for applying policy ?

Dushan Gomez
IT Manager
VCP 4 and 5 | MCITP Exchange Server | MCTS SharePoint Server | MCP Windows XP

 

Ashish-Sharma's picture

"Migrating the SEP clients you may require a reboot of the SEP client machines" --> migrating ? what do you mean ? is it migrating from one OU to another OU in SEPM for applying policy ?

No it's means you will be upgrade your sep Client SEP v 11.0.4 to new version...

Thanks In Advance

Ashish Sharma