WSUS 4.0 (2012)

I have moved my desktops and servers over from WSUS 3.0 SP2 on Server 2003 to WSUS 4.0 on Server 2012. When I use the WSUS client on my Windows 7 x64 desktop (3.0 sp2) the correct operating system is not reported.
Do I need to install the update listed in the the KB below?
http://support.microsoft.com/kb/2734608?ppud=4&wa=wsignin1.0
The updates appear to only be supported on Server operating systems. The desktop OS is not listed as supported. Will Microsoft release an updated management console for remote management that is compatible with v4.0?
I should note that the correct OS version is listed when I use the console on the server.

>>"No businesses will be deploying Win8 on desktops"?
I work for one of the largest insurance companies in the world. We are installing Windows 8 right now on thousands of workstations. The only thing sweeping generalizations like this show is your bias.
Happy you're deploying Windows 8 across your enterprise.
But that's not the context in which the statement was made. The point was that if managing a Windows Server 2012 system
requires a Windows 8 desktop system, that could be problematic for many organizations. Perhaps a more accurate statement would have been "Many business will not be deploying Windows 8", or perhaps even "Many I.T. Departments will not be adopting Windows
8".
The point of the statement was not to malign Windows 8 as a desktop tool, but to point out that the architectural scenarios that precludes the use of Windows 7 to manage Windows Server 2012 systems remotely is a major discouragement to adopting WS2012.
In my own environment, because I also have chosen not to deploy Win8 on my desktop, I'm forced to use Remote Desktop to access a WS2012 server that I've set up specifically to run an instance of Server Manager so that I can manage all the rest of my WS2012/WS2012R2
systems.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Similar Messages

WSUS reinstall on 2012 SCCM server post-installation task fails to run/finish

I had to re-install WSUS on a 2012 R2 SCCM server (Windows 2012), and am running into several issues re-installing. It may help to point out that the SCCM SQL server is remote, so this isn't a WSUS / SQL 2012 issue.
The sticky post at the top of the WSUS forum has helpful troubleshooting information, and I have tried going through this as well as many other threads on this very topic of re-installing WSUS.
1. Roles for WSUS and WID were removed successfully. The WSUS Website was manually deleted from IIS. As this is a SCCM server, removing the IIS role is not an option.
2. I removed the existing WID database files for SUSDB
3. After rebooting, I verified registry keys were gone, system files were cleaned up, and deleted the program files\update services directory
4. This isn't a permission issue, as I have clearly installed this before on this server.
5. Registry keys, system files, and susdb files no longer exist, and the server has rebooted cleanly.
6. I am able to add the WSUS role selecting WID, and this installs WID without any errors. At this point, simply clicking the post installation task fails, generates an empty .tmp file in my %appdata%\temp folder, and exits the MMC.
7. This file is blank. Absolutely empty, so I couldn't really troubleshoot any post installation tasks.
8. Further investigation shows that the 'C:\Program Files\Update Services\Tools\' directory is gone, and isn't being
generated.
9. Ok... DISM /online /Cleanup-Image /Scanhealth didn't return any issues, so I copied the wsusutil out of the windows\WinSxS directory.
10. Yey! wsusutil postinstall runs, but bombs out on the IIS portion. It generated the DB without an issue, but results
in an IIS generation error. So, I installed WSUS on a clean 2012 install, then copied over the program files\updateServices directory to reclaim the missing files.
The log files show --
2013-12-06 10:30:34 Configuring IIS...
2013-12-06 10:30:35 Start: ConfigureWebsite
2013-12-06 10:30:36 Configuring website on port 8530
2013-12-06 10:30:39 System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.ExecuteIisCustomAction(String arguments)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.Install(Int32 portNumber)
at Microsoft.UpdateServices.Administration.UseCustomWebSite.InstallAndConfigure(IisConfiguration& iisConfiguration, Int32 newPortNumber)
at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
at Microsoft.UpdateServices.Administration.PostInstall.Run()
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
... ok - tripple checked that network service has permissions to .net and windows\temp folders.
netstat -a doesn't show anything running on port 8530 ( in case this was some weird port check in use)
Which goes back to the missing directory problem -- further net searches show that this is a reoccurring issue for some OOBE... sfc /verifyonly shows ... nothing.
What is left to be done at this point? The missing folders from the program directory seems to be a problem for some with some users right out of the box. I have read many other threads where users just formatted and started over. Not exactly a solution
- any help out there on this issue? Any suggestions to determine what file is missing, or generating the IIS issues?

Part of the post install tasks wanted to download some items including the tools folder.
Can you expand on this please. The WSUS post-install tasks do not download anything, except what is acquired during the initial synchronization with Microsoft.
Because of my group policy the WSUS server was trying to download the updates from itself even though it was not setup yet.
What update(s) was the WSUS server trying to "download"?
In fact, if the WSUS Server was not setup yet (but you already had a GPO in place), then the first issue here was performing deployment steps out of order.
But still.... except for the actual installation binaries for the WSUS Server Role on a WS2008SP2/WS2008R2 system, there's nothing the WSUS server needs to get from either Windows Update or a WSUS server. This scenario is actually discussed hundreds of times
in this forum, but complicating matters, this thread isn't about installing WSUS V3.2 on a WS2008SP2/WS2008R2 system, it's about installing WSUS v65 on a WS2012 system, so I'm a bit confused as to what the actual installation environment is that we're discussing.
I changed the WSUS server to get it's windows updates from Microsoft and then the post install task succeeded.
I'd really like to get some more details about what exactly in the "post-install task" was dependent upon content from WU/WSUS.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS on Server 2012 Standard R2 with SCCM 2012 Standard R2 Proper Setup

What is the proper setup (best practice) on setting up WSUS using Server 2012 Standard R2 to work properly with SCCM 2012 R2 Standard using Server 2012 Standard R2 on separate box?
1. Is it using WID or database during the setup of WSUS using Server 2012 Standard R2?
2. Once it setup properly on WSUS using Server 2012 Standard R2 either WID or database (using SQL 2012 Standard SP1), how do I connect with SCCM 2012 R2 Standard using Server 2012 Standard R2 on separate box?
3. On SCCM 2012 R2 Standard using Server 2012 Standard R2 just need to add WSUS Role, right? Is it using WID or database?
Thanks,
Reza

1. Generally, using the SQL instance you use for ConfigMgr is preferred.
2. The Software Update Point connects ConfigMgr to a WSUS instance.
3. See 2.
Jason | http://blog.configmgrftw.com
It's just as Jason said. The SUP role in SCCM basically "sits on top" of the WSUS role, whether it is local or remote is up to you. You basically install WSUS on a server like you normally would WITHOUT configuring it. I have used both WID and SQL. It's
always nicer to put it on your SQL server since that is (should be) backed up regularly and maintained.
Once you have WSUS installed you just point SCCMs SUP role at the installation and it takes over the rest.
Dustin Estes - MCP | www.dustinestes.com

WSUS and SCCM 2012

I'm finally getting around to trying to integrate WSUS with SCCM 2012 - i.e., to begin using SCCM 2012 to manage and deploy all Microsoft updates rather than using plain old WSUS as I have in the past.
My first impression is that it's much more complicated than using WSUS alone. That said, I'm wondering now what are the advantages of using SCCM 2012 to manage Windows Updates rather than using WSUS? So far, I've added all of this complexity to the
process, but I'm not seeing the added benefits after having gone through all this. Anyone else agree?
I'm about to just trash the whole thing and go back to doing it the old way. Thoughts?
Shaun

Jorgen summed it up nicely here:
http://ccmexec.com/2012/08/top-11-reasons-why-you-should-use-configmgr-2012-for-managing-software-updates/
Jason | http://blog.configmgrftw.com

New WSUS on Server 2012 - problem with win8 clients

Hi,
Two weeks ago we created a new Server 2012 and installed the WSUS role from scratch on it. Its version number is: 6.2.9200.16384. It replaced a Server 2008 WSUS server. After some time all the win7 clients updated and reported as
they did on the old and replaced server.
However all our win8 clients refuse to update against this server. They show correctly up in WSUS server console each with 107 needed updates day after day. We have rebooted them and done numerous wuauclt /resetauthorization /detectnow and wuauclt
/detectnow /reportnow, but to no avail.
I paste in some lines from a win8 client winupdate log at the end of this message if someone can figure out what I have to do to get these clients update as they did against the old wsus server. Thanks for help on this issue.
regards Tor
2014-02-03   08:33:38:008   920   153c   Agent   *************
2014-02-03   08:33:38:008   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:38:008   920   153c   Agent   *********
2014-02-03   08:33:38:008   920   153c   Agent      * Online = Yes; Ignore download priority = No
2014-02-03   08:33:38:008   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:38:008   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:38:008   920   153c   Agent      * Search Scope = {Machine & All Users}
2014-02-03   08:33:38:008   920   153c   Agent      * Caller SID for Applicability: S-1-5-18
2014-02-03   08:33:38:008   920   153c   Misc   Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2014-02-03   08:33:38:008   920   1990   AU   >>## RESUMED ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03   08:33:38:008   920   1990   AU      # 0 updates detected
2014-02-03   08:33:38:008   920   1990   AU   #########
2014-02-03   08:33:38:008   920   1990   AU   ## END ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03   08:33:38:008   920   1990   AU   #############
2014-02-03   08:33:38:023   920   153c   Misc   Microsoft signed: Yes
2014-02-03   08:33:38:023   920   153c   Misc   Infrastructure signed: Yes
2014-02-03   08:33:38:023   920   153c   EP   Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab"
2014-02-03   08:33:38:023   920   153c   Misc   Validating signature for C:\Windows\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
2014-02-03   08:33:38:039   920   153c   Misc   Microsoft signed: Yes
2014-02-03   08:33:38:039   920   153c   Misc   Infrastructure signed: Yes
2014-02-03   08:33:38:039   920   153c   EP   Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-02-03   08:33:38:055   920   153c   PT   +++++++++++ PT: Synchronizing server updates +++++++++++
2014-02-03   08:33:38:055   920   153c   PT      + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL = https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
2014-02-03   08:33:38:055   920   153c   Agent   Reading cached app categories using lifetime 604800 seconds
2014-02-03   08:33:38:055   920   153c   Agent   Read 0 cached app categories
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {E7FF661C-6A03-4387-A1EE-1D723B52EF60}.3 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:211   920   153c   Agent      * Found 13 updates and 31 categories in search; evaluated appl. rules of 69 out of 94 deployed entities
2014-02-03   08:33:39:211   920   153c   Agent   *********
2014-02-03   08:33:39:211   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:211   920   153c   Agent   *************
2014-02-03   08:33:39:211   920   1a64   Report   REPORT EVENT: {0786C161-F6DC-4842-85D6-9506124654AD}   2014-02-03 08:33:38:008+0100   1
147 [AGENT_DETECTION_FINISHED]   101   {00000000-0000-0000-0000-000000000000}   0   0   Windows Update Command Line   Success   Software Synchronization
Windows Update Client successfully detected 0 updates.
2014-02-03   08:33:39:211   920   1a64   Report   REPORT EVENT: {1E5D9728-220F-44A3-8BCC-ADE69687531D}   2014-02-03 08:33:38:008+0100   1
156 [AGENT_STATUS_30]   101   {00000000-0000-0000-0000-000000000000}   0   0   Windows Update Command Line   Success   Pre-Deployment Check
Reporting client status.
2014-02-03   08:33:39:211   920   1a64   Report   REPORT EVENT: {57BAB7D0-685B-4D73-BDF7-82AFCE8675B0}   2014-02-03 08:33:39:211+0100   1
147 [AGENT_DETECTION_FINISHED]   101   {00000000-0000-0000-0000-000000000000}   0   0   Windows Update Command Line   Success   Software Synchronization
Windows Update Client successfully detected 13 updates.
2014-02-03   08:33:39:211   920   1a64   Report   CWERReporter finishing event handling. (00000000)
2014-02-03   08:33:39:227   920   153c   Agent   *************
2014-02-03   08:33:39:227   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:227   920   153c   Agent   *********
2014-02-03   08:33:39:227   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:227   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:227   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:227   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:227   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1155
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:258   920   153c   Agent      * Found 11 updates and 29 categories in search; evaluated appl. rules of 58 out of 94 deployed entities
2014-02-03   08:33:39:258   920   153c   Agent   *********
2014-02-03   08:33:39:258   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:258   920   153c   Agent   *************
2014-02-03   08:33:39:258   920   153c   Agent   *************
2014-02-03   08:33:39:258   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:258   920   153c   Agent   *********
2014-02-03   08:33:39:258   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:258   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:258   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:258   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:258   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-2212025170-3189117132-1219651784-500
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:305   920   153c   Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03   08:33:39:305   920   153c   Agent   *********
2014-02-03   08:33:39:305   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:305   920   153c   Agent   *************
2014-02-03   08:33:39:305   920   153c   Agent   *************
2014-02-03   08:33:39:305   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:305   920   153c   Agent   *********
2014-02-03   08:33:39:305   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:305   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:305   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:305   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:305   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1323
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:352   920   153c   Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03   08:33:39:352   920   153c   Agent   *********
2014-02-03   08:33:39:352   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:352   920   153c   Agent   *************
2014-02-03   08:33:39:352   920   153c   Agent   *************
2014-02-03   08:33:39:352   920   153c   Agent   ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:352   920   153c   Agent   *********
2014-02-03   08:33:39:352   920   153c   Agent      * Online = No; Ignore download priority = No
2014-02-03   08:33:39:352   920   153c   Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03   08:33:39:352   920   153c   Agent      * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03   08:33:39:352   920   153c   Agent      * Search Scope = {Current User}
2014-02-03   08:33:39:352   920   153c   Agent      * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1282
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03   08:33:39:383   920   153c   Agent      * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03   08:33:39:383   920   153c   Agent   *********
2014-02-03   08:33:39:383   920   153c   Agent   ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03   08:33:39:383   920   153c   Agent   *************
2014-02-03   08:33:39:383   920   1990   AU   >>## RESUMED ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03   08:33:39:383   920   1990   AU      # 12 updates detected
2014-02-03   08:33:39:383   920   1990   AU   #########
2014-02-03   08:33:39:383   920   1990   AU   ## END ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03   08:33:39:383   920   1990   AU   #############
2014-02-03   08:33:39:383   920   1990   AU   All AU searches complete.
2014-02-03   08:33:39:383   920   1990   AU   AU setting next detection timeout to 2014-02-03 10:18:51
2014-02-03   08:33:44:211   920   1a64   Report   CWERReporter finishing event handling. (00000000)
2014-02-03   08:41:39:472   920   1a64   EP   Got WSUS Client/Server URL: "http://elias:8530/ClientWebService/client.asmx"
2014-02-03   08:41:39:472   920   1a64   PT   WARNING: Cached cookie has expired or new PID is available
2014-02-03   08:41:39:472   920   1a64   EP   Got WSUS SimpleTargeting URL: "http://elias:8530"
2014-02-03   08:41:39:472   920   1a64   PT   Initializing simple targeting cookie, clientId = c5e26849-287b-4b96-ba5d-1489d6fad2f2, target group = , DNS name = dt-ikt-tor.framnes.lan
2014-02-03   08:41:39:472   920   1a64   PT      Server URL = http://elias:8530/SimpleAuthWebService/SimpleAuth.asmx
2014-02-03   08:41:39:519   920   1a64   EP   Got WSUS Reporting URL: "http://elias:8530/ReportingWebService/ReportingWebService.asmx"
2014-02-03   08:41:39:519   920   1a64   Report   Uploading 2 events using cached cookie, reporting URL = http://elias:8530/ReportingWebService/ReportingWebService.asmx
2014-02-03   08:41:39:566   920   1a64   Report   Reporter successfully uploaded 2 events.
2014-02-03   08:42:13:212   920   178c   Report   WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2014-02-03   08:43:40:450   920   178c   AU   ########### AU: Uninitializing Automatic Updates ###########
2014-02-03   08:43:40:450   920   178c   WuTask   Uninit WU Task Manager
2014-02-03   08:43:40:513   920   178c   Service   *********
2014-02-03   08:43:40:513   920   178c   Service   ** END ** Service: Service exit [Exit code = 0x240001]
2014-02-03   08:43:40:513   920   178c   Service   *************

Today I opened Control Panel / Windows Updates and first did a check for new updates (from the WSUS server). Nothing was found and it reported Windows is Updated.   Then I clicked the link Check for updates from Microsoft via internet, and
it found around 24 updates.
This is confirmation of the point that I made in the previous post. The updates are *NEEDED* by this system, but the updates were not *AVAILABLE* from the assigned WSUS Server. You were able to get them from Windows Update, but that does not fix your continuing
issue with the WSUS Server.
but it still reported the original 108 Needed updates.
Exactly. As previously noted, the client is functioning perfectly. The problem is NOT with the client; the problem is with the WSUS Server. The updates that this client needed were not AVAILABLE to be downloaded from the WSUS server.
Why this is the case requires further investigation on your part, but is either because the updates are not properly approved, or the update FILES are not yet downloaded from Microsoft to the WSUS server.
It appears that the wsus server doesn't get any information back from the client despite that it displays new Last contact and Last Status report timestamps.
This conclusion is incorrect. The WSUS Server got every bit of information available from the client -- you've confirmed this by the number of updates reported as "Needed" by the Windows Update Agent to the WSUS Server.
I assumed that the log would display if the updates were downloaded or not.
It will log when the updates are actually downloaded. If there's no log entries for updates being downloaded, then they're not being downloaded. If the logfile says "Found 0 updates", then that means exactly what it says: It couldn't find any approved/available
updates to download.
In your case it "Found 11 updates", but now it will be impossible to diagnose that fault, because you went and got them from Windows Update.
All Win8 versions are checked in the WSUS server's Product list so the updates should at least have been downloaded to the server.
This is why understanding the infrastructure is so critical. Your conclusion is invalid based on the premise given, and you may be using improper terminology which only confuses the rest of us as well.
First, selecting updates for synchronization only gets the update metadata (i.e. the detection logic) downloaded to the WSUS database.
The Second Step in this process is to Approve those updates for one or more WSUS Target Groups that contain the appropriate client systems. Following the approval of an update, the WSUS Server downloads the INSTALLATION FILE for that update.
Once the WUAgent sees an approved update and the installation file is available, then the WUAgent will download the file and schedule the update for installation.
Most of the post I read about my problem is about upgrading a 2008 WSUS server to support Win8 / Server 12 clients. When I try to run this update on my Server 12 WSUS it refuses to run (probably because it is for Server 2008).
Yeah.. totally different issue in those posts than what you're describing here.
What should I do to try to track down the problem?
Well.... now that it's 11 days since the logfile was posted, and you've already updated that system, we'll first need to find another system exhibiting the same issue.
Then I'll need to ask a number of questions to properly understand the environment, as well as what you have or have not done.
Then, from there, we can attempt to figure out why your Windows 8 client apparently sees some updates as approved/available but is still not downloading them. We do not yet have sufficient information to even speculate on a possible cause -- there are several.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS not Downloading 2012 r2 patches

The issue I seem to have in a prod environment (WSUS on 2012r2) is, I get all server 2008 patches no issue, but the server 2012 patches, they aren't even being down loaded, I can retrieve the list from MS directly from the windows update panel.
But WSUS is not actively retrieving the 2012 r2 patches, so they do not show up in the WSUS dashboard at all.
Any help would be greatly appreciated.

but the server 2012 patches, they aren't even being down loaded
ut WSUS is not actively retrieving the 2012 r2 patches, so they do not show up in the WSUS dashboard at all.
Did you SELECT the Windows Server 2012 and Windows Server 2012 R2 product categories to be synchronized?
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Can we re-activate Adobe patches once expired in SCUP and syncronized to WSUS and SCCM 2012 as expired?

Hi,
I expired a couple of Adobe patches in SCUP and published them in WSUS. They got synchronized in WSUS and SCCM as expired. After about two weeks those expired patches got cleaned from SCCM ( at least from UI).
I want to activate them again in SCUP and re-publish as active patches in SCCM. But its not working - I've tried WSUS cleanup and SCUP cleanup already!
Is there any way to re-active expired patches published by SCUP in WSUS and SCCM ? & How?
Excerpt from SCUP.Log:
PublishItem: Item 'Reader Multi Lingual User Interface 10.1.4 Update (UpdateId:'5c22235f-a3d9-48db-95eb-a60ec1886e8e' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')' is on the update server and is expired, no publish actions are possible.

The key here is knowing WHY those updates were "expired" in the first place.
Most likely they were expired because they superseded another update. If so, merely duplicating and publishing won't achieve anything, because the duplicated/re-published update will also be superseded and get promptly expired again.
Ergo, if expired because superseded, the superseding package will need to be customized to remove the supersession references and it also will need to be republished, which also means that certain other considerations may need to be taken as well ... such
as the fact that you now have multiple packages that will conflict with one another that no longer have the requisite supersession metadata.
Regarding this scenario. Configuration Manager 2012 introduced the option to NOT EXPIRE superseded updates, or to defer the expiration for a specified number of days. This is not a SCUP thing; it's a ConfigMgr thing.
Configure the ConfigMgr product to behave the way you desire. Problem solved. :)
If YOU actually expired them in SCUP... then just UNEXPIRE them and republish. Shouldn't be any need to duplicate and republish. This is what Microsoft does all the time. Expire Update 'A' Rev 100 on Monday; publish Update 'A' Rev 101 on Patch Tuesday.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 SP1 with remote WSUS on Server 2012 and SQL Server 2012

I am rebuilding my SCCM 2012 lab on Server 2012 R2 x64 OS now.
I have 1 primary site, remote SQL server 2012, and remote WSUS server.
Is the WSUS console still required on my primary site running server 2012? If so are the below the correct steps to get this working?
Install Console on primary server:
Go to Server Manager à Add Roles and features, Navigate to the features section.
Remote Server Manager tools
>Role Administration Tools
--Select Windows Server Update Services Tools Only
Are there any post hotfixes to install?
Intalling WSUS full version on remote server:
Go to Server Manager à Add Roles and features, Server Roles section.
Windows Server Update Services
Do I need to select this as well on the remote wsus server? >Role Administration Tools -Select Windows Server Update Services Tools Only
Since my SQL server is on a remote server do I select the below only?
Are there any post hotfixes to install?

Hi,
One Part of the question is already answered. The second part is: If you want to use a remote SQL Server you need to select exactly what you selected in your screenshot.
Regards,
Thomas
Thomas Hanrath [MCT | Regional Lead Germany] |
http://www.hanrath.de
Microsoft Learning Blog |
http://blog.microsoftlearning.de

WSUS on server 2012 fails to open

I successfully installed WSUS role on server 2012 R2 and pointed its database to SQL 2012 during installation. I was prompted to specify the instance name, but since the sql is installed on the same server I entered the server name as was able to verify
the connection. Database was successfully created in SQL, but when I try to open WSUS console, it opens up but does not connect to its service.
Came across someone else's post with a similar problem, but using wsusutil.exe postinstall SQL_INSTANCE_NAME=<database server name> fails.
http://blogs.technet.com/b/reshard_sharps_blog/archive/2013/08/18/wsus-post-deployment-configuration-fails.aspx
I didn't specify  CONTENT_DIR=C:\Wsus as I don't want to store updates locally until additional storage becomes available.
PS C:\Program Files\Update Services\tools> .\WsusUtil.exe postinstall SQL_INSTANCE_NAME=W2012\mssqlserver
Log file is located at C:\Users\Administrator\AppData\Local\Temp\2\tmpC758.tmp
Post install is starting Fatal Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured
to allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid)

2014-03-31 16:40:46 Importing SQLServer.xml...
2014-03-31 16:40:46 Importing WindowsXP64BitEditionVersion2003.xml...
2014-03-31 16:40:46 Importing DefinitionUpdateSusXml.xml...
2014-03-31 16:40:46 Importing ClientServicingApiDetectoid.xml...
2014-03-31 16:40:46 Importing default detectoids succeeded.
2014-03-31 16:40:48 Synchronization in progress. Please cancel synchronization and rerun postinstall again. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.GetServerVersion()
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.FixSubscriptionCategories()
2014-03-31 16:40:48 StartServer encountered errors. Exception=Synchronization in progress. Please cancel synchronization and run postinstall again.
2014-03-31 16:40:48 Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

WSUS has no 2012 R2 updates

I have a 2008 R2 server running WSUS and cannot see any patches for Server 2012 R2 (2012 is fine, just not R2). Currently running version 3.2.7600.226.
Anyone know anything I can do to correct this? Also if any other info is needed, please let me know. Thanks!

Do you have Server 2012 R2 selected under products?
admin console > options > products and classifications > Products > Microsoft > Windows > Windows Server 2012 R2

Install WSUS on Server 2012 R2 in an environment that only has Server 2008 & Server 2008 R2 servers?

I want to use WSUS on Windows Server 2012 R2 in an environment that has only Server 2008 and Server 2008 R2 servers in production. I currently have one WSUS server setup on 2008 R2 that will serve in one geographic location and the WSUS Server 2012 R2 that
I looking to setup will be at a separate geographic location.
Has anyone tried this? Are there any problems one can expect? Is this a bad idea?

Has anyone tried this?
Thousands!!! :-)
Are there any problems one can expect? Is this a bad idea?
No. Why would you think it might be?
Have you read the product documentation and familiarized yourself with the system requirements and support capabilities of the product?
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Unable to reinstall WSUS on SCCM 2012 Server

I'm trying to reinstall WSUS on my SCCM 2012 Server after having removed the SUP role from SCCM and then following
these steps to remove WSUS from the server. However I am not able to reinstall WSUS. I also tried all of the steps outlined
here but no luck. Here are the results from the WSUSSSetup.log:
2014-05-05 12:16:44 Success   MWUSSetup          Detected that setup was launched through Server Manager
2014-05-05 12:16:45 Success   MWUSSetup          Validating pre-requisites...
2014-05-05 12:16:45 Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2014-05-05 12:16:45 Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2014-05-05 12:19:05 Success   MWUSSetup          Initializing installation details
2014-05-05 12:19:05 Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
2014-05-05 12:19:05 Success   MWUSSetup          Installing wYukon using ocsetup
2014-05-05 12:19:05 Success   MWUSSetup          Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
2014-05-05 12:19:16 Error     MWUSSetup          The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
2014-05-05 12:19:16 Error     MWUSSetup          ExecCmd failed (Error 0x80070643: Fatal error during installation.)
2014-05-05 12:19:16 Error     MWUSSetup          Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error
during installation.)
2014-05-05 12:19:16 Error     MWUSSetup          CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
2014-05-05 12:19:16 Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2014-05-05 12:19:23 Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
I am at a loss, any suggestions would be greatly appreciated. Perhaps I can try installing SQL express and use that as my database rather than WID, since the problem appears to be with WID installation?
Shaun

Another question then - is it okay to have WSUS reside on the same server as SCCM, but without using SCCM SUP role to manage updates?
I would strongly discourage it. If you're using a single Configuration Manager instance, then most notably ConfigMgr installs an SSL-enabled Management Point website which has been known to interfere with a non-SSL standalone WSUS server.
But perhaps more importantly, looking for the long term, if at some point you determined you wanted to enable a Software Update Point, you'd be backed into the corner with your standalone WSUS already installed on the Site Server.
Converting an in-use WSUS Server to a SUP is fraught with complications, the least of which is being without a patch management environment for some period of time whilst you "convert" from standalone WSUS to ConfigMgr Software Updates.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

WSUS Mixed Environment (2012 & 2008 R2)

Hi,
We're looking to deploy WSUS in an enterprise environment with a central datacentre (which also hosts the internet connection), and around 20 remote sites. The plan is to have the upstream WSUS on a virtual 2012 R2 server at the datacentre, and remote WSUS
servers (running in replica mode) at each site.
Although we have 2012 R2 host servers at the datacentre, we don't (as yet) have them at each of the remote sites (they're still on 2008 R2). My question is... is it possible to have a WSUS 2012 R2 upstream server with WSUS 2008 R2 (WSUS 3.2?) servers as
replicas? I understand that I will need to change the port used between the upstream and replica, but is there any compatibility issues with this approach?
Thanks
Tony

Hi Tony,
We can use the WSUS 3.0 SP2 as the downstream server.
When we configure the upstream of the WSUS 3.0 SP2 server, we need specify the port used by the upstream sever. Here is the screenshot of my lab server.
Best Regards.
Steven Lee
TechNet Community Support

Legacy WSUS GPOs & SCCM 2012

Good Afternoon All -
We are in the process of introducing SCCM 2012 onto our production network. Currently, we don't use WSUS to it's full potential, yet still have a few GP's that configure some of each workstation's update settings such as update location, frequency,
reboots, etc. Eventually, all of this will be taken over by SCCM, though.
Questions
1. Will SCCM's Client / SUP settings override and Group Policy for WSUS, does a GP win out, or is it a toss up?
2. When (assuming it's needed) do these WSUS policies need to be changed and/or disabled? Previously, I believe that I've just disabled any existing WSUS policy and let the SCCM client configure each machine.
3. So that there's no window where clients may NOT be configured how we want, would the best thing be to be configure SCCMSUP policy, deploy the clients, then change / disable WSUS GPOs?
4. If SCCM is configured the way we want, is there any need for any SUP related GPO's to exist for managed clients? (Besides the SCUP WSUS one which enables "Allow signed content from
intranet Microsoft update service location”)
Thanks for your help!
Ben K.

I've found that even though a GPO should overwrite the Local Policy set by SCCM this isnt actually the case.
If you look at the WUAHandler.log file you see entries for the following
Enabling WUA Managed server policy to use server: http://MYSCCMWSUSSERVER.MYDOMAIN.COM
Waiting for 2 mins for Group Policy to notify of WUA policy change...
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://GPOsetwsusserver
Failed to Add Update Source for WUAgent of type (2) and id ({9F08A663-567F-4A1A-8F1A-F56DF97D3E66}). Error = 0x87d00692.
theres an MS blog on the issue here
https://blogs.technet.com/b/sus/archive/2008/12/02/wuahandler-log-failed-to-add-update-source-for-wuagent-error-0x80040692.aspx
The options are
1. Remove the group policy at the domain level
or
2. Use the same WSUS server as the Software Update Point for the SCCM as well
Thats not very helpful in my scenerio as I'd like to keep the SCCM client installed for software metering & reporting, but i'd like the WSUS server to be set by GPO for these specific computers as their updates are managed by a vendor because
of the be-spoke software running on them
MCP, MCSE, MCSA, MCITP, MCTS, MCDST

WSUS 4.0 (2012)

Similar Messages

Maybe you are looking for