Product Review: Update on the Zalman ZM-VE300 USB.Toshiba Portege Z830-00P: Some mSATA SSD Testing t.Coffee Reading: Storm Clouds on the Horizon.Moving from Unmanaged or Nonexistent SEP Managemen.Product Review: Update – 120GB OCZ Nocti Died :(.How to Swap the mSATA SSD or RAM on a Toshiba Portege.Fujitsu ScanSnap N1800: User Log On Error Via Acti.Symantec EndPoint Protection CleanWipe Tool: Stuck.RDP: Set up a Monitor Span for Non-Windows 7 Enter.We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.
*Our original iMac was stolen ( previous blog post). Now, hopefully whatever was causing the lockout problem will be gone. Once done we were able to install the SEP v12.x client. The whole process took 3 reboots to complete. The CleanWipe process continued on from there by requesting a restart. In the end we needed to use Task Manager to kill ccSvcHst.exe process and then rename it in Windows Explorer as in the snip above. The last warning indicated 30 minutes or more to run the registry clean-up be we were not getting anywhere after 2 hours. Once we ran the utility we said Yes to all of the options and then waited, and waited, and waited. So, we opened a case with Symantec and obtained a copy of the CleanWipe utility. Removing the Administrator Scan from the management console did not remove the lockout behaviour in this version as it had for v11.x. With the v11.x client we removed the Administrator Scan in the SEP Console on the management server and the problem went away.īut, once we replaced the backend and the client on this machine the lockout behaviour came back. The lockout would happen only after they had plugged into another network to gain access to the Internet.
We were working with a particularly problematic Symantec EndPoint Protection endpoint that always caused the user’s account to lock out when they came back into the office with their laptop.
0 kommentar(er)
