WSUS migration to different hardware
- Hi Members,
Which is the best method to migrate WSUS server to different hardware?
Since my server is legacy unit, i would like to move WSUS database, update files and everything to new hardware as a safety measure.
This is the only server i have deployed for update services that delivers updates to client; no complex topology.
I dont want to change server name since all clients are pointed to SUS server via registry settings. Should i name my new server the same name as like the old one to get this accomplished?
What are the data's to be backed up before moving the whole thing to new server?
Please provide with document link as i am new to WSUS.
Thanks,
Kones.S
Answers
- Hi Eric,
Thanks for your reply and sorry about the delay responding to your reply. This method doesnt appear to be migrating computer accounts and approval status.
That just synchronizes the updates and not the rest.
Please advise.
Thanks.
Kones.S- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorFriday, November 13, 2009 6:50 AM
- Two notes.
1. No, it will not replicate computer accounts; however, those will be automatically recreated when the computer registers with the new server right after you change the URL to point to the new server. If you're using client-side targeting, they'll appear in the correct groups; if you're using server-side targeting you'll have to reassign group memberships from "Unassigned Computers" to the correct target group(s).
2. Creating the new server as a *replica* will replicate the approvals. Creating the new server as an autonomous downstream server will not replicate the approvals. Be sure that you have checked the box to "create this server as a replica" when you perform initial setup.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorFriday, November 13, 2009 6:50 AM
- I just recently did what Eric and Lawrence suggest myself and it works fine. What you do it set up the new server as a replica (i.e. "Downstream") server of the old one. Once it synchronizes and gets WSUS all up to date, you simply change it's Update Source to Microsoft instead of the old "Upstream" server and then shut down the old server. After that, you have to make your WSUS Client computers talk to the new server. You could simply change the DNS entry to point to your new server. You could completely change your new server's Name, IP and DNS info to match the old server's info. You could also change your policy to point to the new server's DNS name.
Be patient though, it's not a very speedy process and your WSUS Clients will take a bit to catch up.
There's also a "Update Services 3.0 API Samples and Tools" package that you can get from http://www.microsoft.com/downloads/details.aspx?familyid=805aa009-0c90-4334-a4a1-0c07f9262437&displaylang=en which contains documentation and tools to get a bit more granular in what you want to do with your Migration. With these tools, you don't have to go through the process listed above, you can just Export the old server's Target Groups and Approvals, then import them into your new server.
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorFriday, November 13, 2009 6:50 AM
All Replies
- Hi Kones,
I suggest you install WSUS on the new server and configure it as replica server, synchronize with the old WSUS server.
Make sure all updates has been downloaded to the new server, then shutdown the old WSUS server, rename the new WSUS server, set it synchronize with Microsoft Update. - Hi Eric,
Thanks for your reply and sorry about the delay responding to your reply. This method doesnt appear to be migrating computer accounts and approval status.
That just synchronizes the updates and not the rest.
Please advise.
Thanks.
Kones.S- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorFriday, November 13, 2009 6:50 AM
- Two notes.
1. No, it will not replicate computer accounts; however, those will be automatically recreated when the computer registers with the new server right after you change the URL to point to the new server. If you're using client-side targeting, they'll appear in the correct groups; if you're using server-side targeting you'll have to reassign group memberships from "Unassigned Computers" to the correct target group(s).
2. Creating the new server as a *replica* will replicate the approvals. Creating the new server as an autonomous downstream server will not replicate the approvals. Be sure that you have checked the box to "create this server as a replica" when you perform initial setup.
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorFriday, November 13, 2009 6:50 AM
- I just recently did what Eric and Lawrence suggest myself and it works fine. What you do it set up the new server as a replica (i.e. "Downstream") server of the old one. Once it synchronizes and gets WSUS all up to date, you simply change it's Update Source to Microsoft instead of the old "Upstream" server and then shut down the old server. After that, you have to make your WSUS Client computers talk to the new server. You could simply change the DNS entry to point to your new server. You could completely change your new server's Name, IP and DNS info to match the old server's info. You could also change your policy to point to the new server's DNS name.
Be patient though, it's not a very speedy process and your WSUS Clients will take a bit to catch up.
There's also a "Update Services 3.0 API Samples and Tools" package that you can get from http://www.microsoft.com/downloads/details.aspx?familyid=805aa009-0c90-4334-a4a1-0c07f9262437&displaylang=en which contains documentation and tools to get a bit more granular in what you want to do with your Migration. With these tools, you don't have to go through the process listed above, you can just Export the old server's Target Groups and Approvals, then import them into your new server.
- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorFriday, November 13, 2009 6:50 AM
