I am sure this topic has been addressed somewhat more than a few times here and on the web. IE I have googled this stuff before hand, but I am still unclear and or don't like the solutions that I am seeing.
First I will try to describe what I want to do. I would like to migrate the WSUS role and all of it's approvals and declined updates off of a 2003 Server onto a 2012 Server. I am aware of the following link http://technet.microsoft.com/en-us/library/hh852339.aspx
but this in my opinion is a bit (a lot) ridiculous, way, way too many steps. It's like something an organization with a dedicated WSUS admin would have the time and focus to do.
Alternatively, I was looking at simply firing up a 2012 server, assigning it the WSUS role and setting it as a downstream update server or whatever the terminology is. But, I am wondering if this will "downsteam" everything 100% or just the updates downloaded from the upstream WSUS server? IE I would like it to get all of the historical approvals and declined updates as well as all of the server side targeting setup computer groups and auto approval buckets. I am worried that it will not capture all of this info and that if I re-pointed our AD GPOs to the new server, shut down the old one and changed the new one to the actual main wsus server as opposed to the downstream on, it would start trying to send out all declined Black Tuesday updates that have plagued this year. I would like to know what happens in the scenario above.
Thanks for all of your help.