SEP RU5 PC(s) keep rebooting post install
Hi,
I've deployed SEP in a 90 users enviroment and out of those, 18 have this issue. Once SEP is installed, if I restart to get the NAC running, it goes into a reboot loop, never coming to the login screen.
Post the 2nd restart you will have the option of using Last known good configuration, which gets me into the machine, but SEP is semi-uninstalled...
Anyone else faced such issue, and what have you done to fix it?
Thank you,
Adrian
Which is the method you are
Which is the method you are used for deploying?
Any similarity between the clients of which the installation failed?
Is it is an up gradation to old version?
Pls give as SEP_INST.log also
I deployed using the find
I deployed using the find unmanaged option - deployed all 90 at the same time...
Have yet to find a similarity, maybe you can point me in the right direction.
SEP_INST.log cannot be provided as it's been removed post "Last known good configuration".
Try to install manually in
Try to install manually in those PCs ans see
If it is not getting installed Pls provide SEP_INST.log
Below doc can help you in this
Creating custom Client Installation packages in the Symantec Endpoint Protection Manager Console
Creating client installation packages
Try in one pc first and see what is the result
One more thing Previously any antivirus was present in those pcs?
I tried this
I tried this yesterday...
Installed manually, opened SEP_INST.log and the last lines where succesfully installed and the 3010 code for needing restart.
..but, after restart same loop thing. I'm guessing it's something these machines have and SEP doesn't like (drivers!?)
initialy SAV 10.1 was installed on all the machines...
I'll try again and send the entire thing...
Sounds like a virus
Sounds like a virus problem
Try by scanning in safe mode with NSS
First you run clenwipe for
First you run clenwipe for both SAV and SEP
Then try to install if not helps try by scanning...
Re
you could also try running on safe mode, and go to your eventvwr.msc filter out the date/time of the restarts, look for the application/system logs for this one.
Would you like to reply?
Login or Register to post your comment.