WSUS 2012 to WSUS 2016

Would like to replace my 2012R2 WSUS server with a 2016 standard WSUS only role.  My question is there any value in making this a downstream server to get all of the metadata?
I am having so many issues with the 2012 WSUS  that i just want to deploy a new 2016 WSUS and decommission the old 2012 WSUS.  My enviroment is 95% windows 10 Pro with some Windows 7 Pro  that are currently being replace.

any thoughts or best practices are welcome and thanks in advance

Thanks  Alain
Alain LaverdureSystems AdminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ITguy565Commented:
Here is the Microsoft recommended process to migrate from 2012 WSUS to 2016  WSUS :
      Install all Updates
       Copy WSUS folder from previous server.
       Switch off firewall on source WSUS server or open port 7000(TCP and UDP).
       Get parameters from source WSUS:
       Database location: [SQL server].
       Database name (if changed from default): (HKLM\Software\Microsoft\Update service\server\setup{SQL database name}
       IIS settings: WSUS pool user (Network service)
       SMTP server pass:
       Code sign certificate:
        Group membership: (localhost)\WSUS Administrator, (localhost)\WSUS Reporters
       Store: d:\WSUS as example
       On new server install SQL Management studio, , Microsoft Report Viewer 2012 Runtime
       Rename the database to SUSDB (if your database name is customized).
       For WSUS database add permission (SUSDB->Security->Users->add) for user [Domain name]\(new machine name)$ with default schema [dbo]
   On new server in Server manager add role WSUS with Role services: WSUS Service; SQL server Connectivity.
   Content: Store locally. Specify path to WSUS folder with updates from previous server (D:\WSUS as example).
   Specify DB Instance (SQL Database Host)
   After complete reboot new server.
   Stop previous server.
   On new server add to local groups WSUS Administrators and WSUS Reporters user with administration rights (Domain\Your username or admins group)
   Start WSUS console and click RUN.
   When complete run PowerShell:
$updateServer = get-wsusserver
$config = $updateServer.GetConfiguration()
$config.ServerId = [System.Guid]::NewGuid()
$config.Save()
 
When changed GUID run next


%ProgramFiles%\Update Services\Tools\wsusutil.exe postinstall SQL_INSTANCE_NAME=[SQL server Name] CONTENT_DIR=[WSUS content dir d:\WSUS]

   Next if need to change susdb name:
       In IIS stop WSUS Administration site. Stop wsus service
       On new server use regedit for edit the database name \HKLM\Software\Microsoft\Update service\server\setup{SQL database name} (SUSDB_SPB)
       Change in MSSQL susdb name.
       Start wsus service then WSUS Administration web site.

   Set setting for child WSUS servers
       At child WSUS Parameters-Update source-Enter new server name and port. Do it on all child servers
   Set Group policy for new WSUS server. For fast sync with new server use command wuauclt.exe /resetauthorization /detectnow
For start reporting:
 wuauclt.exe /resetauthorization /detectnow
and then
wuauclt.exe /reportnow
   Check workability by Success synchronization server, success reports from computers.
On clients check logs %WinDir%\WindowsUpdate.log

reference  :
https://social.technet.microsoft.com/Forums/windows/en-US/b00c0e00-a870-4b63-91fb-4879ab9642db/wsus-migration-from-2012r2-to-2016?forum=winserverwsus
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alain LaverdureSystems AdminAuthor Commented:
Is it really necessary to save the current WSUS data,  shouldn't the new WSUS server check all the clients for current and missing updates  ?   I really don't want to use any of the data from the old server as it is not working well.
is there any foreseen side effects ?
0
ITguy565Commented:
Alain,

There is really no real side effects you would just need to configure everything from scratch just like you did when you originally setup WSUS.
0
ITguy565Commented:
Keep in mind though from a data perspective the new WSUS server would need to go out and download all the updates and store them once again locally. Where if you go the other route, the updates can just be moved.. Your call there.
0
Alain LaverdureSystems AdminAuthor Commented:
Thanks i appreciate it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.