SEPM Migration to New Domain Question
I am preparing to follow the article below for migrating my production SEP11 system to a new box. We're planning to decommision the SEPM 11.x box after the migration to a new server for SEPM12.x.
http://www.symantec.com/business/support/index?page=content&id=TECH104389
I just thought of a situation that I failed to test in small-scale. I'm wondering if anyone has had it happen and if so, how'd it turn out.
If after you have completed the migration and upgrade you find that some clients are not reporting into the new server, but are still trying to report into the old one, can you remove the old server from the Management Servers List to force the clients to the new box even though the two servers can no longer be replication partners?
I'm envisioning a period where employees with checked-out machines actually decide to turn them on (presumably to do some work... ;-)) and they check in for the first time in a while. Those machines will have not yet recieved the updated managment server list from the old server until now. If I leave the SEPM11 server in operation, but no longer a replication partner with the (now) SEPM12 box, can the Management Servers List still be used to push those long-lost clients to the new server?
I hope I explained this clearly. If not, I'll try to clear it up.
Thanks
Comments
You have a dielmma
Unfortunately, after you decommission (turn off) the server, no more updates will reach the clients.
So any new clients checking in to the old server will not be able to get an updated server list. If, however, as you said, the old server is still online and has an updated management server list, than yes the clients will receive the updated list and the "new" server will be there.
If I may suggest, if you intend to leave the "old" server online, I would place it as secod inthe management server list. That way, when a client that has been off for an extended period of time checks in, it will receive the updated list and move itself over to the server with the highest priority.
If that server (highest priority) is 12.1 and the packages are to be deployed (upgrade from server directly) the clients should also request and receive there updated packages.
I, personally would not remove the replication - until a determined time has passed and you are satisifed that al (or almost all) your clients have migrated.
Hope that helps!
Thank you for your quick
Thank you for your quick reply.
What you describe is exactly what I was planning. However, Murphy's Law dictates that a number of clients will not get the new policy no matter how long I leave the two in replication before the upgrade.
I was just curious if the list would still tell the clients to move even though the two servers are no longer replication partners.
Thanks!
Would you like to reply?
Login or Register to post your comment.