Client not showing up in protection manager version 12.1
Created: 23 Aug 2012 | 6 comments
Hi all,
We are currently upgrading from endpoint 11.0 to 12.0 and I can remote push the new client just fine to my test boxes. I reboot and it looks like the new client version installed correctly. The problem is, it doesn't show up in protection manager. What gives?
Discussion Filed Under:
Comments 6 Comments • Jump to latest comment
Since these Clients are Cloned / Imaged, a Repair Tool is available for the same -
How to repair duplicate IDs on cloned Symantec Endpoint Protection 12.1 clients
http://www.symantec.com/docs/TECH163349
Thanks In Advance.
Manish
Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.
Hi,
There can be different reasons.
Make sure Firewall exceptions are in placed if windows firewall is used.
Following articles can help you to troubleshoot the issue.
Testing Communication from an Endpoint Protection client to the Endpoint Protection Manager
http://www.symantec.com/docs/TECH102682
Symantec Endpoint Protection Manager 12.1 Communication Troubleshooting
http://www.symantec.com/docs/TECH160964
Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |
Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.&
have you set any filter on SEPM?
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
You might have created domains in your SEPM
open sepm
admin
domains
click on admister the domain u created, you should be able to find client.
first thing to be checked woudl be the windows firewall.turn it off, if its on.
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Check if the machines are in the correct group and that you have the required rights to see them.
Can you check on the client machine the local sylink.xml or the according registry keys to check which server they try to connect(make sure the server name is correct, server certificate is correct and the connection port - port may have changed from 11 to 12 depending on your setup), which domain they use and which group they belong to.
------------------------------------------------------------------
Best regards!
toby
CISSP / MCP
Would you like to reply?
Login or Register to post your comment.