- SYMANTEC ENDPOINT PROTECTION 14 WINDOWS 7 LOCK UP INSTALL
- SYMANTEC ENDPOINT PROTECTION 14 WINDOWS 7 LOCK UP PATCH
> If a PC was newly imaged with a fresh install of SEP 14 the PC login screen will function but a new scenario occurs where the wired and wireless NICs go silent. > If a PC upgraded from 12.1.6 to 14 they will eventually freeze at the login screen requiring a safe mode/clean wipe to remove the SEP client. In my environment I can tell the following is happening: I've begun the slow march to down grading the clients to 12.1.6 as a work around for PCs that are still responding and reimaging the ones that are not. I am having even more computers fail today. any insight from anyone else whould be welcomed.
I have been unable to determine what causing the issue. So far, removing and pushing a fresh copy of the sep 14 client has not seen the issue reoccur in the machines. however, unchecking the box for that client did not allow a normal boot. i still have GEM enabled because on of our tests before removing the sep 14 clients was to disable GEM.
SYMANTEC ENDPOINT PROTECTION 14 WINDOWS 7 LOCK UP PATCH
I am running windows 7 ent 圆4 on sp1 with the most recent MS updates as November's patch tuesday (to my knowledge) the pc was then able to boot successfully. We added a reg key to allow windows installed to start in the safe mode environment and removed the sep 14 client. It is important to know that all clients were upgraded from 12.1.6 to 14.īooting in safemode does work (except for one that we could not get to boot into safe mode) they start, get to the loading screen but never reach the ctrl+alt+del screen. so far only a handful of machines have been affected. Re-imaging the PC with a clean install of version 14 may or may not resolve this problem and requires more testing. Every day I am getting new reports with more and more PCs in this state. With over 2000 PCs, it has become a minefield trying to determine which PCs are broken. I will leave it as support has instructed me to do so for up to 24 hours. Unfortunately despite sitting for about an hour, this PC is still in this locked up state and SEPM does not see that this PC has checked in. I contacted Symantec to create a case report and the phone tech had me create a new default group and place one of the problematic PCs in this group to see if one of our policies was causing the problem. In SEPM you also cannot see that this PC is on. When the computer is in this locked up state it is pingable if you know it's IP but third party VNC remoting utilities (we use Novell) do not work. Going back into Safe Mode and forcefully removing SEP using the clean wipe utility allows the PC to boot properly and login again. Rebooting out of Safe Mode reproduces this problem immediately. Things that we know: When a PC experiences this problem it is possible to sign into the PC in Safe Mode. Our school district PCs were upgraded from version 12.1.6 to 14 on November 16th. This includes clicking the shutdown button. PCs will refuse to login and clicking anything on the login screen causes the computer to completely hang. I am currently having the exact same problem.