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

Endpoints appearing as unmanaged after SEC 5.2.1 re-install

I recently had to reinstall SEC 5.2.1 after a server failure. I have detected all my endpoints and they all update fine but they appear in SEC as unmanaged, how do i get SEC to start managing them again? I've tried re-installing the client manually but it doesn't seem to make a difference



This thread was automatically locked due to age.
Parents
  • Hello SimonCornish,

    I'm assuming you've started with a fresh OS, haven't you? Did you have a backup and used it during reinstall (in particular the CertAuthStore)? If not, i is a new server in terms of management (RMS) and you have to redirect Windows endpoints to a new management server. Manual reinstall (which is required for non-Windows endpoints) is one of the options and should have changed the endpoint's state to managed though - you did install from the CID created by the new server, didn't you?
    Unlikely but not impossible that just this particular endpoint has troubles so try another one. If the result is the same start Troubleshooting disconnected clients (some steps obviously don't apply but don't foret to check the RMS ports). If you're none the wiser at this point reading the log files would be the next step.  
    Once this has been sorted out redirect your endpoints. Not among the recommended methods is the procedure outlined in this article under B. Configure the central share (the drawback is that if an endpoint is directed to update from a CID without this configuration it will fall back to the useless original).

    Christian   

Reply
  • Hello SimonCornish,

    I'm assuming you've started with a fresh OS, haven't you? Did you have a backup and used it during reinstall (in particular the CertAuthStore)? If not, i is a new server in terms of management (RMS) and you have to redirect Windows endpoints to a new management server. Manual reinstall (which is required for non-Windows endpoints) is one of the options and should have changed the endpoint's state to managed though - you did install from the CID created by the new server, didn't you?
    Unlikely but not impossible that just this particular endpoint has troubles so try another one. If the result is the same start Troubleshooting disconnected clients (some steps obviously don't apply but don't foret to check the RMS ports). If you're none the wiser at this point reading the log files would be the next step.  
    Once this has been sorted out redirect your endpoints. Not among the recommended methods is the procedure outlined in this article under B. Configure the central share (the drawback is that if an endpoint is directed to update from a CID without this configuration it will fall back to the useless original).

    Christian   

Children