installed as part of image?

Configuring Symantec Endpoint Protection client for deployment as part of a drive image

delete there registry keys and check
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007110510364248

A couple of things.

Try using SylinkWatcher on the Win7 client, and see where the breakdown is happening:
http://service1.symantec.com/support/ent-security....

Also, you might want to try to export a "sylink.xml" directly from the group in the SEPM.
If you are using MR3 or later:

Click (in the SEPM), Clients>Right click the group>export communication settings
Rename the file to "sylink.xml", and import it over to the Win7 client using SylinkDrop.

Maybe run netstat and see if you have any connections to your SEPM box, if I remeber correctly you need port 8014 open for the client to communicate to the SEPM.

Mike

Have tried all of the above and still cant get it to connect to the server, I am going to try reimaging the pc because i think the user may have change a few of the settings

try this before re-imaging

http://service1.symantec.com/support/ent-security.nsf/docid/2008091215040048

First you disable firewall and windows defender then check this also
1. HKCU\SOFTWARE\Microsoft\Windows\Currentversion\Internet settings Click on the internet setting key check for the keys called "ProxyEnable" if it is set to 1 then change it to 0 also check if there is a registry value called "GlobalUserOffline" if it is present change the value of the DWORD to 0
2. Now expand Internet settings key and take a backup of the "Connections" key, Delete the entire key

3. Check HKU\.Default\SOFTWARE\Microsoft\Windows\Currentversion\Internet settings Click on the internet setting key check for the keys called "ProxyEnable" if it is set to 1 then change it to 0 also check if there is a registry value called "GlobalUserOffline" if it is present change the value of the DWORD to 0

4. expand "Internet settings" key in the above said location and take a backup of the "Connections" key, Delete the entire key

5. Reboot the machine.

See whether it is connecting to manager..