How do I register computers to WSUS?


I am setting up a new WSUS server on windows 2012 R2 (it's a virtual machine.). We currently have in production, a 2003 server running WSUS  V3.2.7600.226 on a physical junker. My goal is to phase out the 2003 server and bring the new one into production,

I am currently in a testing phase. In Active directory, I created a seperate OU called "test OU," and moved a computer to that OU.

In terms of the GPO, in group policy manger, I copied the old WSUS policy and linked/enforced it to the Test OU. The only change I made to the copied WSUS GPO was pointing to the IP of the new WSUS server. I already know that the GPO was applied because i ran the "gpresult command on the testing computer and found the copied WSUS policy listed (I even rebooted.)

I already configured WSUS on the new server according to Microsoft's Technet instructions, and synchronized for the first time.

The problem is that the test computer is not being registered in the Windows Update Service Management Console.

Are there any reasons why this can be happening? Did I miss an important hidden step?

Any help would be greatly appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

David Johnson, CD, MVPOwnerCommented:
When the computer checks for updates it should add itself to WSUS in the unknown and you move it to the category you wnt
Cliff GaliherCommented:
The default configuration for WSUS in 2012 is to use SSL as well. Which usually means you don't want the GPO to have an IP address, but to use the server name. For domain joined WSUS servers, this is usually sufficient to resolve problems that the update agent has when attempting to connect by IP and getting an SSL error.
zito2000Author Commented:
Hi Cliff, David,

I tried both solutions with no luck.

Can it be that I copied the old GPO that was used for the 2003 WSUS server? Do I need to create a GPO from scratch?
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Cliff GaliherCommented:
That shouldn't be a problem. But it won't hurt either. Did you change ports when you switched? If you updated the server, but didn't update the port it uses, that can be a problem too. I've seen instances where the user didn't realize their old install was on a different port.

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
zito2000Author Commented:
How do I check/change the port?
Hector2016Systems Administrator and Solutions ArchitectCommented:
You need to check the file C:\Windows\WindowsUpdate.log on the test computer.

Seek the last lines that include the string "Report " (case-sensitive).

You can force the test computer to report its status by this command in a CMD:

Wuauclt /reportnow

Also you can download this free tool from Microsoft to test WSUS client conectivity and configuration. (Run it as Administrator)
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 Server 2012

From novice to tech pro — start learning today.