In addition to Barthax's ideas, there is a problem with the ClientRemote install tool as per Symantec. I had a number of issues with it when we first upgraded to SAV console 10.1.5. The solution we ended up with was to copy the ClientRemote install tool from our old SAV 10.1.4 server, and replace the one that came with 10.1.5. Everything worked fine after that. I usually see the errors your getting when Windows Firewall was enabled without the SAV ports opened, but I can't remember if the faulty ClientRemote install tool gave me the same error. I know the main error I received was "The selected computer %computername% does not have Windows 2000 or higher". You might want to give it a try though.
From Symantec Support:
"I did find out today that your issue is the exact same issue that has already been assigned a defect. There is good news that development has fixed the problem in the code and is slating the fix to be included in the next maintenance release of SAV (10.1.6). I cant confirm at this time if the fix will make the next maintenance release but I will certainly let you know once I have that information. The next build of 10.1.6 is scheduled to be released sometime mid March. Using the workaround provided to deploy out to workstations in the mean time would be my recommendation. The failure with the 10.1.5 tool appears to be when it does a check of the parent server to determine if it is Netware or Windows. There isnt a specific incompatibility between the 10.1.5 client remote tool and Windows 2003 since we have seen this error when the parent server was running Netware."
Main Topics
Browse All Topics





by: BarthaxPosted on 2007-07-11 at 09:20:15ID: 19464138
Check that the Server service is running on these machines - the admin$ share is used to copy the installation files onto the machine first & WMI is then used to start the installer remotely.
ve Templates\Network\Network Connections\Windows Firewall\Domain Profile - the Windows Firewall: Define port exceptions setting. Enable the setting & enter the following line based on version of SAV in use at the workstation (enable both if you have clients with older versions):
c AV Server-Client Interaction
c AV Server-Client Interaction
The SSC talks to already-installed versions via TCP port 2967 (it was UDP port 2967 on earlier versions). The hang you describe is typical of this port being inaccessible by the SSC. You can create a Group Policy Object to force this port open: in the GPO, navigate to Computer Configuration\Administrati
Symantec Anti-Virus v9 and prior:
2967:UDP:*:enabled:Symante
Symantec Anti-Virus v10:
2967:TCP:*:enabled:Symante