Configuring WSUS for your clients.

Today I got a call from a friend that was setting up WSUS on Windows Server 2012. He got WSUS setup but the clients were not checking in. After talking on the phone with him for a bit he told me he had not set anything up on the client side yet. 

 Here are the steps to setup your clients via GPO taken from http://technet.microsoft.com/en-us/library/cc720539(v=ws.10).aspx
  1. In Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components, and then click Windows Update.
  2. In the details pane, click Specify Intranet Microsoft update service location.
  3. Click Enabled and type the HTTP(S) URL of the same WSUS server in the Set the intranet update service for detecting updates box and in the Set the intranet statistics server box. For example, type http(s)://servername in both boxes.
  4. Click OK.
This is great in most cases, but to my knowledge WSUS in Windows Server 2003 - 2008 R2 use port 80 as the default port for WSUS synchronization. WSUS in Windows Server 2012 the default port is 8530 and 8531 for SSL.

<edit>
      http://technet.microsoft.com/en-us/library/hh852346.aspx
  • On WSUS 3.2 and earlier, port 80 for HTTP and 443 for HTTPS
  • On WSUS 6.2 and later (at least Windows Server 2012), port 8530 for HTTP and 8531 for HTTPS
</edit>

 So to make the adjustment you must specify the port in the TechNet step 3 to look like this http(s)://servername:port

 After this you can perform a wuauclt.exe /detectnow on the client machine to detect the WSUS server and start reporting. The process can take 10 minutes or more. Sometimes a simple reboot on the client will force a detection.

 After my friend made the appropriate changes (adding the port number in the GPO) and rebooted the client, the computers started reporting.

Comments

Post a Comment

Popular posts from this blog

DISM An error occurred while attempting to start the servicing process for the image.

Image
This is an issue I've had a few times and when you look around on the forums you see multiple answers. I found the right one on an obscure forum that I can't think of right now. The quick answer is this: Use the correct version of DISM to service the image . They must be in the same "generation". For Windows 8.1 and Windows Server 2012 R2 this version is : 6.3.9600.16384 For Windows 8 and Windows Server 2012 and below this version is : 6.2.9200.16384 Background and Setup: I have a Windows Server 2012 box running System Center Configuration Manager 2012 R2. We are in the process of switching our primary OS for new systems to Windows 8.1 Enterprise x64. As I build my images the old fashioned I tend to forget a few things from time to time. In this case I built the image without installing the .NET feature. The instructions to do that are here: http://technet.microsoft.com/en-us/library/dn482069.aspx So I'm following the instructions to get a refresher on
Read more

SCCM 2012 R2 Windows XP refresh to Windows 7

Image
As the deadline for the End of Life of Windows XP approaches I was tasked with the job to make the upgrade to Windows 7  happen in the simplest manner possible. Here is my story. My first objective was how: 1. You could make two task sequences. One to capture user data and the second to deploy the OS and restore the data. This made no sense to me so I didn't go this route. I mean there had to be a better way. 2. You could make one task sequence that captured the user data deployed the OS and restored the data all in one sequence. This is a completely unattended approach and that's the way I like it. You need a few things to get started. 1. You need Windows AIK for Windows 7 and the supplement which can be found at the following links. Windows 7 AIK http://www.microsoft.com/en-us/download/details.aspx?id=5753 Windows 7 AIK Supplement http://www.microsoft.com/en-us/download/details.aspx?id=5188 *Later on you'll need the Windows 8 AIK as well. The links are refer
Read more

Optiplex 380 STOP Error: NMI Parity Check/Memory Parity Error

Image
I received a support ticket today from one of our schools saying they had a strange error coming up. I asked the usual questions like did you reboot, what color is the screen, etc. She said it was the BSOD, but it looked different. After going to take a look at the machine I saw the error and I hard rebooted the machine. I came to see this error: At first thought I figured this was a memory error, but it was not. After I removed each stick of RAM one-by-one the error persisted. After a bit of Googling I ran across this article. http://www.dell.com/support/troubleshooting/bz/en/bzdhs1/KCS/KcsArticles/ArticleView?c=bz&l=en&s=dhs&docid=604790 This says it's a NIC issue and you can fix it by uninstalling the old driver and reinstalling. This, however, was not the case. The NIC was failing at POST, far too soon for a driver to be the issue. I also updated the BIOS to A07. (Was on A01) This did nothing as well. I resolved the issue by adding a NIC into the machine an
Read more