![]() For those servers, the CPU utilization (and in some cases the memory) spiked to 100%, especially on the TS servers. 2100 and all seemed fine until we deployed the new SEP client to our database and Terminal Services servers. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ Symantec\ Symantec Endpoint Protection\SMC\ LaunchSmcGui to 0 and then restart the SMC service. For Terminal Servers our best practice doc states you need to set the following registry key: For this kind of test, you add server to the test group and then upgrade them by using AutoUpgrade.Subject: High CPU/Memory on DB and TS after 14.2 upgrade If you do not have a test network, you can create a test group within your production network. However, Test the AutoUpgrade process before you attempt to upgrade on other server in your production network. The primary benefit of side-by-side installation and replace on reboot is that the system continues to be protected by the existing software until the new version is in operation after the reboot.Īuto upgrade is the easiest way to upgrade clients, however make sure to set reboot time during non production hours. Because the two versions are separated from each other, during a migration the older software is left running unchanged until the next reboot. Side-by-side means that new files are written to a new folder, referred to as a silo, isolated from the existing operational folder. SEP 14.0 also employs a side-by-side, replace on reboot installation strategy. Install 14 over 12 can be the best way because machine will remain protected all the time. Thank you for posting in Symantec community.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |