Endpoint Protection

Hello all.
My situation is the following:
Last weekend I got into Virtualization, using Hyper-V in a IBM blade system. Well the thing is that I used to have my Symantec Endpoint Protection server installation in my Domain Controller. When moving into hyper-v by using p2v (physical to virtual), everything worked fine. Then i decided to demote the DC Virtual Machine and create a new Domain Controller. Everything went smoothly and right now in that server I have SEP and my Exchange (the rest of the roles were removed, like AD,DCHP,DNS). Then I realised that my clients weren't up to date, at least you can't see the green dot when the client is fully updated and in connection with the server. I opened SEP management console and I first of all I got a message saying

"Unable to communicate with the reporting component", then i got to the admin->servers->"DCserver"->edit server propertied and then I changed the directory servers into the new DC.

Is there anything else that I should do in order to have my clients to synchronize with the SEP server? What do you think that I should do?

Hello

fix the datbase connection and also check if network service is added in your gpo

Follow this doc to get the issue resolved, are you logged in remote ?

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument

Rafeeq

since you changed IP the clients lost communication

please follow the link to get the tool

https://www-secure.symantec.com/connect/forums/sylinkdrop-tool

hope this was helpful

Rafeeq

I will check them out.
And i haven't changed the server's IP

Thanx in advance, that was fast.

If replacing the sylink.xml file on the clients do not re-establish communication then the issue could be with the IUSR account. Make sure the IUSR_Computer Name account used for Anonymous access for the Symantec webserver in IIS is enabled. You may also try resetting the password for this account and then enter the new password for anonymous access.

Thanks :-)

Try to reinstall IIS, I experience this error before reinstalling IIS resolve my concern but I couldnt say this is the solution just give it a try. it works to me. thanks.

Is sepm installed in xp or 2003. because XP have an issue with regard to concurrent connection it can support up 10 connection only so you have to set the client into pull mode for the server to accomodate each clients.In 2003 there is no limitation, If 2003 you can try to reconfigure management server list, to resync the database.

You have mentioned that you have "demoted the DC Virtual Machine and create a new Domain Controller" Can you please let me know did you do an uninstall & reinstal of the SEPM or did you backed up & restored the database?

Gilbert08 has the right query, if u have Xp as anOS the IIS of Xp has the cocurrent user connection limit of 10, so random 10 users can report to SEPM at a time. U can manually increase to 40 but then it is not recommended by Microsoft.

Ajit