Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 0 subscribers
  • Views 5770 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

Endpoints looking for both old and new server after migration

tlirr

So I recently moved our update manager to a new server. Everything is working as it should except there are about 50 endpoints that are still trying to look at the old server first, failing, then updating from the new server. 

I've tried running the "Protect Computers" wizard from the Enterprise Console on the computer but it didn't change anything. I've also looked at the suggestions here but none of the listed solutions work/are the probelm.

Any suggestions on a way to stop this? It's really annoying to see 50+ errors every day but everything else is at 0.

Oh and we are using 5.3

Thanks!

:57942


This thread was automatically locked due to age.
  • 0

    Hello tlirr,

    without the details of your move it's partly guesswork, I assume your new server has a different name and IP and you've kept the certificates, correct?

    trying to look at the old server first, failing, then updating from the new server

    Where an endpoint looks for updates is determined by its update settings, in case of managed endpoints these have been assigned (assuming the endpoint complies) with the Updating policy. AutoUpdate first tries the Primary location for all products and for each product that can't be synchronized the Secondary (if defined) is tried. Thus on the endpoints in question the Primary must point to the old server and the Secondary to the new.

    Protect Computers uses the Primary Server address (or if defined the Initial Install Source) from the policy to install AutoUpdate which subsequently uses the Primary Server address to download and install the other products. RMS then contacts the server and requests the applicable updating policy. If the computer is in the Unassigned group the policy is sent/supplied after the computer has been moved to a specific group.  

    If you see these endpoints in the new console reporting the error then they have correctly reconfigured RMS and should therefore get their updating policy from the new server. If they still try to download from the old one then either they do not comply with the policy - but after a successful Protect the primary location should be the new server and thus the error no longer occur - or the assigned policy is not correct.

    Christian   

    :57945
Unfiltered HTML