You can do this as below 1. Configure Automatic updates should be enabled and 2. Specify intranet Microsoft Update service location should be disabled. Configure WSUS to deploy updates using Group Policy. I created this step by step guide for those people that dont understand or want to know how to configure WSUS to deploy updates using Group Policy. The process is very simple, but very efficient for a large and even a small network. To understand what Im talking about, think of a network of 3. PCs, maybe that network is already in your company you deployed a WSUS server but clients still go to Microsoft for updates, and you want to point them to your WSUS Server. Off course is an ugly job to do this manually for 3. Group Policy comes in. All you have to do is make a some configuration settings in WSUS, create a new GPO Group Policy Object, configure that GPO, and attach it to an OU Organizational Unit in AD. Easy haanow lets see how its done. First lets configure WSUS settings open your WSUS console, go to Options and click Computers. Im posting this to hopefully helpout anyone else who might encounter this. I have a Win2008r2 domain, and my clients decided to stop talking to the WSUS server. This is where we tell WSUS how computers are added to groups. Im going to talk about groups in a moment. The default option is to add those computers manually, but we dont want that, so choose the second option Use Group Policy or registry setting on computers. Click OK. Now lets talk about groups and create some. The main purpose of groups in WSUS are to organize computers. Think of this groups like OUs in AD. To create some groups right click on All Computers an choose Add Computer Group. Im going to create two groups here, one will be XP Computers, for all my Windows XP systems, and the second one is called 7 Computers, where all Windows 7 computers will reside. We are done with WSUS for now. Now lets go on the DC to create the update policy. Open Group Policy Management from Administrative Tools Group Policy Management. Here we need to create two GPO, one for the Windows XP computers and another one for Windows 7 computers. Right click the OU where your Windows XP computers reside and choose Create a group policy in this domain, and link it here. Give the GP a name and click OK. Now right click this GP and choose Edit. Forums/getfile/1033146' alt='Wsus Specify Intranet Microsoft Update Location' title='Wsus Specify Intranet Microsoft Update Location' />Find quick solutions to Microsoft Windows Server Update Services errors that may impede your system updates, due to IIS and Group Policy settings issues. How to fix Windows Update error 80072EE2 when clients fail to receive updates over an intranet Windows Server Update Services WSUS 3. SP2 server. Open Specify intranet Microsoft update service location, select Enable, and under Options type the address of your WSUS server, in the form httpservernameport. Windows ComponentsWindows Update Policy Setting Comment Allow nonadministrators to receive update notifications Enabled Automatic Updates detection frequency. Windows Server Update Service a. WSUS is Microsoft free tool they provide for deploying patches and updates. In my experience this tool is pretty much used by. Here are the steps to configure SSL on your servers running the Windows Server Update Services. This guide was written using Server 2012 R2, however it should be the. Migrating WSUS from 3. SP2 to Server 2012 r2. T203000Z. Migrating Windows Server Update Services from Windows Server 2008 R2 WSUS 3. SP2 to Windows. Solution I am not sure how the pcs could have shown up in the WSUS console. By default, the pcs will point to the Microsoft update site. The GP is setup to. Expand Computer Configuration Policies Administrative Templates Windows Components Windows Update. As you can see we have a lot of options here to configure Windows updates, but Im going to configure just some of them, the rest Ill live it to you. Open Configure Automatic Updates, select Enable and under Options choose the way updates are going to be installed on clients. Open Specify intranet Microsoft update service location, select Enable, and under Options type the address of your WSUS server, in the form http servername port. Port is optional, and use it only if your WSUS site is installed on a different port 8. Here you can put the Net. Bios name, FQDN or IP. In this case Im going to use the Net. Bios name. Open Enable client side targeting, select Enable. You remember on WSUS those two groups that we created XP Computers and 7 Computers, now is time to use one of them. In the Target group name for this computer type XP Computers, click OK, and close the Group Policy Management Editor. We still need to configure updates for the Windows 7 systems, so create a new GPO on the Windows 7 OU. Follow the same steps like before until you reach Enable client side targeting. In the box type 7 Computers, and click OK. Your GP Management console should look like this by now We are done configuring, its time to test. Restart the clients or force the policy on them in order to take effect but if you are not in rush, just wait between 9. I forced the policy since I have only two clients using gpupdate force command. Now if you take a look in WSUS, you should see your clients, already added in their computer groups. Here is my Windows XP systemand here is my Windows 7 system. There are situation when clients dont appear in WSUS after the policy is applied especially on XP systems, and in most cases all you have to do is have patience. Want content like this delivered right to your email inboxFixing Windows Server Update Services Error 8. EE2 Not Updating Clients. An update to WSUS 3. SP2 on Windows Server 2. R2 and Windows Server 2. Windows Server Update Services WSUS andor Internet Information Services IIS making clients unable to update via WSUS showing error 0x. EE2. To me, the subversive update number is not clear yet. So, if you know for sure the exact update that does this, please comment. On the surface at least, the server looks OK It synchronizes with upstream Microsoft servers, displays newly published updates, approves and declines as been told, and downloads approved updates flawlessly. But deep inside the WSUS server, things are a mess The WSUS server is the only computer that can get updates from itself, it cannot communicate with clients, and after a few days, all computersexcept for the WSUS server itselfare listed as This computer has not reported status for X or more days. Further investigations reveals clients ranging from Windows XP to Windows 7 and Windows 8 fail to update showing. Windows could not search for new updates. An error occurred while checking for new updates for your computer. Errors found Code 8. EE2. Windows Update encountered an unknown error. Windows Update error 8. WSUS, then its not a simple case of limited access to update. Visiting Event Viewer Custom Views for Server Roles, or hitting the Roles list collapse sign plus sign inside the square on Server Manager and looking into each roles events, youd be surprised to see theres no recent events or perhaps no events at all listed for Web Server IIS. This shows that IIS and its pipings are broken and client computers cannot communicate with the server. Another symptom and a confirmation of the broken IIS hypothesis is a selection of the following warning and error events listed for Windows Server Update Services Level. Event IDDescription. Error. 12. 00. 2The Reporting Web Service is not working. Error. 12. 01. 2The API Remoting Web Service is not working. Error. 12. 02. 2The Client Web Service is not working. Error. 12. 03. 2The Server Synchronization Web Service is not working. Error. 12. 04. 2The Simple. Auth Web Service is not working. Cyberlink Powerdirector 8 Ultra Full Crack Idm. Error. 12. 05. 2The DSS Authentication Web Service is not working. Warning. 13. 00. 1Client computers are installing updates with a higher than 1. This should be monitored. Warning. 13. 00. 2Client computers are installing updates with a higher than 2. This is not normal. Error. 13. 04. 2Self update is not working. To fix this, you need to reinstall WSUS and IIS roles preserving the data. Backup and Delete SUS Database and Preserve WSUS Update Files. Use SQL Server Configuration Manager to stop the SQL Server MSSQLSERVER service. Backup the SUSDB database files in SQL data folder MSSQLDATASUSDB. MSSQLDATASUSDBlog. Use SQL Server Management Studio to connect to the SQL Server and delete the SUSDB database. Rename the WSUS content data folder to WSUS. Unlike the SQL step, theres no need to stop the Update Services service prior to manipulation. Remove WSUS and IIS Server Roles. Open Server Manager and remove Web Server IIS and Windows Server Update Services roles. When asked for, leave the check boxes clear for the removal of WSUS database, log files and downloaded update files. Restart the server. During the installation of WSUS 3. SP2, the Server Manager on Windows Server 2. R2 actually looks for Windows Server Update Services 3. SP2 Dynamic Installer for Server Manager x. Edition KB9. 72. So, when it tries Searching for updates itll show the following error Installation failed. The update could not be found. Either the update is not applicable to this computer or the update no longer exists. Verify that the update still exists and is applicable to this computer from your WSUS server or Windows Update. To give your server a chance at receiving updatesincluding Windows Server Update Services 3. SP2 Dynamic Installer for Server Manager x. Edition KB9. 72. Microsofts website, temporarily disable intranet Microsoft update service location Edit the Default Domain Policy in Group Policy Management, open Computer Configuration Policies Administrative Templates Windows Components Windows Update Specify intranet Microsoft update service location, take a note of your servers custom URLs e. Set the intranet update service for detecting updates. Set the intranet statistics serverand set it as Not Configured. Now open Command Prompt and run gpupdate force to tell Windows to forcibly re apply GP settings. Add WSUS and IIS Server Roles. Open Server Manager and add Web Server IIS and Windows Server Update Services roles. Configure WSUS 3. SP2 installation and finish Add Roles Wizard. When asked for, leave the Begin initial synchronization checkbox unchecked, since everythings going to be replaced with the backup. Also, based on the same principle, when choosing Products and Classifications, pick a single product with fewest updates possible e. Silverlight. Windows Update now recommends the installation of Update for Windows Server Update Services 3. SP2 for x. 64 based Systems KB2. Its a 2. 8 MB download from Microsoft servers if youre curious. You can update it online, or do it later via your local update serveronce its back online. Use SQL Server Configuration Manager to stop the SQL Server MSSQLSERVER service. Replace SUSDB. mdf and SUSDBlog. Rename WSUS. bak folder to WSUS and restart the Windows Server. Edit the Default Domain Policy and set update server URLs to what they have originally been e. GP settings using gpupdate force. Youre good to go.