Endpoint Protection

Hello all,

We have installed SEPM on a freshly built Windows 2008 Standard Server 32Bit VIRTUAL machine. The installation seemed to go fine. We started SEPM Console and have configured the install packages, features, install features, etc. We then went to deploy. We tried various techniques, from finding unmanaged computers to using the migration and deployment wizard. At first, everything seemed to go well. A few XP machines were found and deployed to successfully. They should up under the clients tab in the proper group. They were scanning and updating content normally. All seemed well and good.

Then, we tried deploying to our accounting server, a Windows Server 2003 VIRTUAL machine. Epic fail as Remote Desktop Connections seemed to hang. We deployed to our Exchange 2008 Server (Win2008 Server R2 64bit VIRTUAL), again epic fail as mail flow stopped on all accounts. We deployed to the SEPM server itself. Yet another epic fail as all previous clients (the 4 XP machines) ceased ability to connect to the SEPM server and scan or update content.

We uninstalled the client (via client machine) from one of the client machines and attempted redeployment (after uninstalling the client from the SEMP Server), the client machine is seemingly unable to connect to the SEPM server at all. It has not updated or begun to scan.

Not to sure what is going on and hoping someone here can help out. I can say that our Policies for the client machine ONLY include our created policy and a LiveUpdate Policy, we removed the Firewall/Intrusion Prevention/App&Device Control policies from EVERY CLIENT FOLDER (it was defaulted from the My Company down) We have also removed the Inherit Policies from parent group setting.

Any help would be greatly appreciated.

Thanks,
Clay

Disable IPV6  and Windows firewall if it is enabled

If that does not work then paste the sylink.log

https://www-secure.symantec.com/connect/downloads/sylink-toggle

Which components are deployed to the XP machines? The servers?  Which version of SEP? Is the SEPM using the custom site with port 8014?

(I'm not sure what you mean when you say that the client hasn't begun to scan.  The ability to scan is not tied into communication to the SEPM, except to receive a policy setting a schedule.)

I'd recommend using the SEP Support Tool to see if any errors are found.  It's available through the SEP client interface (under Help and Support), or through this page.

Title: 'The Symantec Endpoint Protection Support Tool'
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008071709480648

Thanks,
sandra

Hello ,

Please disable windows firewall on client machines ,also check if client communication port are open . replace sylink.xml by one client machine by stopping service for symantec management client . reboot the machine and then check . On client machine go to HKEYUSER\.DEFAULT\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\INTERNETSETTING\CONNECTION & remove defaultconnectionsettings and savedlegacysettings (Please take registry backup before making any changes to it) ,reboot the machine and then check .

Regards
Swapnil Khare
Symantec Endpoint Protection
 

I think In exchange server, NTP and PTP will create an Issue

Could you elaborate?

sandra