Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 0 subscribers
  • Views 6207 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enterprise Console wont see endpoint computers

KarenL

So the server running SEC crashed and we didnt have a backup of it. 

I built a new server with the exact same hostname IP and operating system as the failed one. The endpoints are connecting back to the new server and updating but I cannot manage the endpoints from the console.

I discovered all computers using active directory and selected them all and chose Protect Computers. All I see are Orange "downward" arrows on each client and then after about 30 mins this arrow disappears and I get "The installation could not be started. [0x0000002e]"

Can you tell me what is wrong and how to fix it?

Much appreciated.

Thanks.

:57288


This thread was automatically locked due to age.
Parents
  • 0

    Hello KarenL,

    exact same hostname IP and operating system ... I cannot manage the endpoints

    you can work around name/IP and anything else except for the Identity of the server, the CertAuthStore registry key. It's the certificates which identify the server.

    0x0000002e

    did you initially (i.e. with the old server) protect them from the console? Then it should work with the new server as well. If Protect works with a newly installed PC or you don't normally need Protect you could try to redirect Windows endpoints to a new management server instead of troubleshooting the 0x0000002e.

    Christian

    :57293
Reply
  • 0

    Hello KarenL,

    exact same hostname IP and operating system ... I cannot manage the endpoints

    you can work around name/IP and anything else except for the Identity of the server, the CertAuthStore registry key. It's the certificates which identify the server.

    0x0000002e

    did you initially (i.e. with the old server) protect them from the console? Then it should work with the new server as well. If Protect works with a newly installed PC or you don't normally need Protect you could try to redirect Windows endpoints to a new management server instead of troubleshooting the 0x0000002e.

    Christian

    :57293
Children
No Data
Unfiltered HTML