Symantec 10.1 Issues

Moving Symantec AntiVirus Corporate Edition 10.x clients from one parent server to another

Situation: You have installed Symantec AntiVirus Corporate Edition 10.x (Symantec AV) clients as a managed client of a Symantec AV 10.x server, and now you want to move the client or clients to a different parent server. Solution: You can do that by first method but that will give you and your co-worker a big headache, but you can complete your mission without headache and less effort.

1. “Manually move clients to different parent server”
2. “Moving one or more clients to a different parent server"
3. "Moving all clients to a different parent server,"

Manually move clients to different parent server

Uninstall Symantec Client security form your client PC. To uninstall follow below method

• Open Control panel
• Click Add/Remove Programs
• Select Symantec Client Security and click Remove (At the end of uninstall process it will ask for restart PC, but don’t restart now.)
• Select Symantec Live Update and click remove.
• Now restart client PC and login as user or admin.
• Deploy Symantec Client security form the Server.
• Open Symantec System center console
• Select your server group then select your server.
• Click Tools > Client Remote Install (It will open up the Installation wizard)
• Click Next
• In the location select default and click Next
• In the computer selection center from the left panel select your computer (Double click Microsoft windows network, double click your domain)
• From the right panel select the server name then click Add (You will the select client PC shows under select sever)
• Click finish and it will deploy Symantec client security on respective client PC. After finishing deployment click Done and close Symantec System center console

The above process you can use for first time deployment of client. In that you don’t need to uninstall anything just follow the deployment process.

Moving one or more clients to a different parent server

If you want to move a few clients to a different server, then copy the Grc.dat file from the new parent server to all the clients that you want to be managed by the new parent server. This can be done through many distribution methods, the most common being login scripts.Where to find the Grc.dat file on the parent server

• If the parent server is Windows NT or 2000, 2003 then copy the Grc.dat file from the VPHOME shared folder on the parent server. By default, the VPHOME shared folder is pointing to C:\Program Files\SAV on the parent server.
• If the parent server is NetWare, then copy the Grc.dat file from the SYS:SAV folder. Note: If you want to move the clients to a different parent server and also add them to a specific client group, use the Grc.dat file from the directory \SAV\Groups\, where represents the name of the client group. Where to put the Grc.dat file on the clientCopy the Grc.dat file to the appropriate folder for your operating system.

** Windows 98: The default folder location is C:\Program Files\Symantec_Client_Security\Symantec AntiVirus\.

**Windows NT: The default folder location is C:\WinNT\Profiles\All Users\Application Data\Symantec\NortonAntiVirus Corporate Edition\7.5\.

**Windows 2000/XP: The default folder location is C:\Documents and Settings\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\.

Note: On Windows 2000/XP, the directory "Application Data" (C:\Documents and Settings\All Users\Application Data) is hidden.

If you have clients using Norton AntiVirus Corporate Edition 7.5 or 7.6, the appropriate folders are as follows:

**Windows NT: The default folder location is C:\WinNT\Profiles\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\.

**Windows 2000/XP: The default folder location is C:\Documents and Settings\All Users\Application Data\Symantec\Norton AntiVirus Corporate Edition\7.5\.

Note: On Windows 2000/XP, the directory "Application Data" (C:\Documents and Settings\All Users\Application Data) is hidden.

**Windows 95/98/Me: The default location for this version is C:\Program Files\Norton AntiVirus\.

After a few minutes, the Symantec AV client will find the Grc.dat file in this folder. Symantec AV will make the appropriate changes to the registry and will delete the Grc.dat file.

Note: If you do not uninstall the Symantec AV Server software from the original parent server, then client computers may show up in the Symantec System Center (SSC) under both servers for 30 days. The old Symantec AV server retains the client's information in its cache for 30 days after it stops receiving "keepalive packets" from that client. To avoid or solve this problem, see the section “How to remove clients from the Symantec System Center”.

Moving all clients to a different parent server

If you want to move all clients to a different parent server, then changing a specific registry key on the original parent server will automatically direct clients to a new parent server. If the current parent server is no longer functioning, then use Method 2.

WARNING: I strongly recommend that you back up the system registry before making any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Please make sure that you modify only the keys specified.

1. Navigate to the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LanDesk\VirusProtect6\CurrentVersion\ClientConfig\
2. Change the "Parent" name to the computer name of the new parent server.
3. Change "RemoteHomeDirectory" name to the new parent server.
4. If you are migrating clients across server groups, navigate to the following registry subkeys:HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LanDesk\VirusProtect6\CurrentVersion\HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LanDesk\VirusProtect6\CurrentVersion\DomainDataand change "DomainName" to the new server group name in each.
5. Close the Registry Editor.
6. Open Symantec System Center.
7. Right-click the original parent server, point to All Tasks, point to Symantec AntiVirus, and then click Client Realtime Protection Options. Note: If the clients are in client groups, right-click the client group instead of the parent server. You will need to do this for each client group.
8. Click Reset All. This will generate a new copy of the Grc.dat file that refers clients to the new parent server.When the clients check in to the original parent server, they will receive the configuration change and begin communicating with the new parent server. If you stop and then restart the Symantec AV Server service or reboot the original parent server, then the Grc.dat file will again refer clients to the original parent server. Any clients that did not receive the configuration change will still be managed by the original parent server.

Note: If you do not uninstall the Symantec AV Server software from the original parent server, then client computers may show up in the Symantec System Center (SSC) under both servers for 30 days. The old Symantec AV server retains the client's information in its cache for 30 days after it stops receiving "keepalive packets" from that client. To avoid or solve this problem, see the section How to remove clients from the Old Symantec System Center to New Symantec System Center

How to move clients from the old Symantec System Center to New Symantec System Center

If you follow the last two methods may be you will not see the clients computers in SSC. Follow below the steps to see your clients PC under your new parent server SSC. Copy the xxx.xservergroupca.cer from New Parent server’s C:\Program Files\Sav\pki\roots to Client PC’s C:\Program Files\Symantec Client Security\Symantec AntiVirus\pki\roots. If you install Symantec System Center Console in D or E drive of parent server then copy the xxx.xservergroupca.cer file from D:\Program Files\Sav\pki\roots or E:\Program Files\Sav\pki\roots Wait for five to ten minute and you will see your client PC in New Parent server. If not then force the client PC to check with parent server by following steps On the client machine open regedit and goto HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\ProductControl

Change the value from 0 to 1 of ReloadRootCertsNow key Change the value from 0 to 1of ReStartPongEngineNow

If these fields do not exist create a DWORD value and name them accordingly