Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 7455 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

Post Server Migration - Machines not reporting to new server

Robert J.C Smith

Hello,

 

I have recently migrated our Enterprise Console onto a new server and have successfully managed to point endpoint machines to the new updating server via the use of OU Containers and Group Policies.

 

The problem is we have some machines (Windows & Macs - Some off the domain) that are still pointing towards the old updating server.

 

The machines that are off the domain obviously will not update automatically as the machines will not be able to pick up the group policy which is fine.

 

My problem is we have some machines that are in the correct OU and appearing on the new Enterprise Console but on the endpoint machine they are still pointing towards the old updating server.

 

 So i will cut to the chase, I am wanting to know if there is an easy to for me to pull off a list of machines from our old server that consists of all machines that are still reporting to it.

 

Thank you..



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

    Hello Robert Smith2,

    do I understand correctly that the old server is still running?
    The connected/disconnected state would be an approximation but I'd rather go the the Computer Details tab, and sort by Last message time.

    Christian

Reply
  • 0

    Hello Robert Smith2,

    do I understand correctly that the old server is still running?
    The connected/disconnected state would be an approximation but I'd rather go the the Computer Details tab, and sort by Last message time.

    Christian

Children
  • 0 in reply to QC

    Hello Christian,

     

    Yes, the old server is still indeed running.

     

    I was thinking that the last message time would be a good place to start but am unsure on its accuracy.

     

    Looking at this information i imagine its safe to assume that any machine with a response earlier then that of the migration date/time is still reporting to it?

  • 0 in reply to Robert J.C Smith

    Hello Robert,

    earlier than that of the migration date/time
    you mean more recent, don't you? A "newer" last message time is indicative that the endpoint is still communicating with the old server (or already in case you look at the new one). The last message time will not get updated though when the endpoint is trying to establish communication but for whatever reason fails. 

    How exactly did you redirect the endpoints, i.e. what are (the contents of) these Group Policies?

    Christian

Unfiltered HTML