It will create a system entry in your system tree and will replicate the OU structure if you enable that.
To pull in the systems to the new ePO, use the Transfer Systems function from the old server to the new server. Much easier to track what is happening this way. Once you mark a device to transfer, it will transfer to new servers when it connects to ePO.
It takes minimal setup to do that.
Can you explain what you meant by "create a system entry"? Will a device end up being in both the 4.6 and 5.3 ePO servers? It would seem to me that would not be possible. I just want to make sure that if I enable AD synchronization, I don't want ePO to suck in a whole bunch of devices into 5.3 when I'm not ready to do that. I want to re-create AD in the System Tree and move machines from 4.6 to 5.3 on my own time. When they get moved to 5.3, I want them to get automatically moved to the right spot as a result of AD sync.
I've already set up the ability to transfer systesm from 4.6 to 5.3 and have transferred a handful of systems already.
On AD sync it creates a system object in the system tree, it represents an unmanaged system. When an agent with matching name communicates, the information will merge.
So if you sync, but do not push the agent on sync you will have your unmanaged systems on the new servers but the managed systems will remain on the old server.
Got it. Thanks for the help, Andre!