question

Marcus-9726 avatar image
0 Votes"
Marcus-9726 asked RitaHu-MSFT commented

WSUS Migration from 2012 R2 to 2019

My existing WSUS setup on WS2012R2 and the SUSDB is created on a separate SQL 2017 cluster. I would like to migrate it to a new WS2019 Server. I am thinking of configuring the new server as a downstream replica server but wondering how should I cope with the SQL database. Appreciate if anyone could answer the below questions:

  1. Can I configure the new WS2019 server to use WID instead of a database in existing SQL 2017 clustered instance? Will the updates and computer groups replicate to new server's WID?

  2. If I am going to use back the same SQL 2017 cluster for new WSUS server, how should I proceed with that? Just setup a new WSUS 2019 server and point it to the SQL instance? Will I be able to see the existing config after pointing the DB or I will have to do some kind of downstream configuration?


windows-server-update-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered RitaHu-MSFT commented

@Marcus-9726
Here is my test result and I would like to share with you in Server 2012R2:
1) Stop the WSUS Administrator Website in IIS

2)Back the SUSDB database in the SQL server and Delete the SUSDB in the SSMS console
146841-5.png

146816-6.png146777-6.png

3)Reinstall a new WSUS role in the Windows Server 2019 with the SQL server database and finish the post install the New WSUS.
146832-7.png

4)Stop the WSUS Administrator Website in IIS after the installation finished

5) Offline the SUSDB in the SQL Server
146797-8.png

6) Restore the SUSDB by the command:

 RESTORE DATABASE SUSDBFROM DISK = 'C:\backup\SUSDB.bak' WITH REPLACE

7) Start the WSUS Administrator Website in IIS

8) Change the FQDN(Server name and IP address) to the old WSUS. The pointed computers will report to the new WSUS(Server 2019)

Note that there is no such document from MS for reference and this solution is not recommended by MS. So we cannot guarantee that there will be no problems during deployment. I just want to share my test result for your reference.

Hope the above will be helpful.

Regards,
Rita


If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5.png (25.9 KiB)
6.png (15.7 KiB)
6.png (15.7 KiB)
7.png (17.3 KiB)
8.png (23.8 KiB)
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @RitaHu-MSFT

Thanks for the assistance. If I am going for the migration method and need to use WID. What I have to do is to add the new server as a downstream server and cutover it as a upstream when everything is ready will do? Or I need to follow back the existing setup which using separate SQL server instance?

0 Votes 0 ·

In fact, it depend on you :)

Please follow the above steps if you want to use the old SQL server database in the new WSUS server. You can also creat a new WID database in the New WSUS in Windows Server 2019.

Thanks for the assistance. If I am going for the migration method and need to use WID. What I have to do is to add the new server as a downstream server and cutover it as a upstream when everything is ready will do?
If you want to use the WID database in the New WSUS server, please follow it. Note that change the Windows server 2019 's Server name and the IP address to the old WSUS server in Windows Server 2012R2. The clients will scan updates and report to the new WSUS.

Please let me know if you have any questions. Hope the above will be helpful.

Regards,
Rita

0 Votes 0 ·

Hello @RitaHu-MSFT ,

Thanks for the information. For client reporting, I've tested with a lab environment and I found that the client reported to new WSUS server but they are assigned to a computer group called "Unassigned". Even though I've already replicated the computer groups from upstream server previously and the GPO is still applied to the client. Is this a normal behavior that I'll have to manually assign the computer to their respective group manually?

Basically I've came out with the below steps to upgrade the WSUS 2012 R2 server, would you mind to check this for me?

  1. Setup a new Windows Server 2019 VM

  2. Install WSUS role

  3. Configure it as a downstream server and wait for replication done from upstream server (WSUS 2012)

  4. Change the downstream server to upstream server

  5. Reconfigure products & classification, computer group assignment and other features by following the WSUS 2012 configuration

  6. Change GPO pointing to new WSUS 2019 or change the hostname & IP address of WSUS 2019 to WSUS 2012


0 Votes 0 ·
Show more comments
RitaHu-MSFT avatar image
0 Votes"
RitaHu-MSFT answered RitaHu-MSFT edited

@Marcus-9726
Thanks for your posting on Q&A.

I would like to test it in my lab first and I will come back as soon as possible.

Thanks for understanding and cooperation.

Regards,
Rita

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.