WSUS Update KB2938066 and SCCM 2012 R2

Looking at the newly release WSUS update KB2938066 and wondering if I need to apply it to my SCCM WSUS component. If so, what type of impact on the SCCM clients should I be aware of?
Orange County District Attorney

As the update is about securing and hardening WSUS and also the communication with WU/MU, I would definitely apply this update.
The client-side is going to be tricky, depending on the configuration of your windows updates. Jason did a very good post about this here:
http://blog.configmgrftw.com/the-wua-dilemma-in-configmgr/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

WSUS 4.0 and SCCM 2012 SP1 Sync Errors

SCCM 2012 SP1 is installed on a Windows 2012 Std server with the WSUS 4.0 Role installed.
All other links I have found list a 2008 R2 Server with WSUS 3.0 SP2 hence all the "fixes" revolve around hot fixes and patches/settings for WSUS 3.0 or 2008 R2 systems.
WSUS is set for port 8530/8531
SCCM SUP is set for ports 8530/8531
Both are on same machine (single site SCCM 2012 SP1 System)
What does Bad Configuration, SUPs present but no default SUP
mean and how do I fix it?
Recent entry in my WCM.LOG states:
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.401+420><thread=6052 (0x17A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.454+420><thread=6052 (0x17A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.481+420><thread=6052 (0x17A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.489+420><thread=6052 (0x17A4)>
SUP0: SCCM2012.xxdomainnamexx.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

Here is my WCM Log from this mornings "re-attempt"
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:22.156+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.179+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.181+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.194+420><thread=5540 (0x15A4)>
No SUPs are present $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.199+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.220+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.224+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:27.226+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:37.356+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.388+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.493+420><thread=5540 (0x15A4)>
Setting new configuration state to 1 (WSUS_CONFIG_PENDING)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.541+420><thread=5540 (0x15A4)>
Changes in active SUP list detected. New active SUP List is:~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.543+420><thread=5540 (0x15A4)>
SUP0: SCCM2012.MORTONGENERAL.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.546+420><thread=5540 (0x15A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.550+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.553+420><thread=5540 (0x15A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.559+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.562+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.593+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:42.596+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.611+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.614+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.617+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:47.620+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.634+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.637+420><thread=5540 (0x15A4)>
Trigger event array index 0 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:52.640+420><thread=5540 (0x15A4)>
SCF change notification triggered.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.761+420><thread=5540 (0x15A4)>
Populating config from SCF $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.798+420><thread=5540 (0x15A4)>
Waiting for changes for 24 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.813+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.823+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:51:57.826+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.840+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.843+420><thread=5540 (0x15A4)>
Trigger event array index 1 ended. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.846+420><thread=5540 (0x15A4)>
File notification triggered. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:02.849+420><thread=5540 (0x15A4)>
File notification triggered WCM Inbox.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.863+420><thread=5540 (0x15A4)>
Waiting for changes for 23 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 07:52:07.866+420><thread=5540 (0x15A4)>
Wait timed out after 23 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:30.913+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.917+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.920+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 08:15:40.923+420><thread=5540 (0x15A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:31.041+420><thread=5540 (0x15A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.045+420><thread=5540 (0x15A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.048+420><thread=5540 (0x15A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-17-2014 09:15:41.051+420><thread=5540 (0x15A4)>
Randall

How to find who modified Software Update deployment in sccm 2012

Hi,
How to find who modified(Date & Time) software update deployment in SCCM 2012 ?

In the Console :
Monitoring / System Status / Status Message Query
Right Click : "Deployments Created, Modified, or Deleted" - Show Message and select your period.
You'll have your information there.
Benoit Lecours | Blog: System Center Dudes

Top 4 basic issues that are encountered in SCOM 2012 and SCCM 2012

HI,
I need to give a presentation on the basic issues that are encountered in SCOM 2012 and SCCm 2012.
Can anyone help me out with this?
Thanks in advance
Rohith Kumar

Hi,
I am not familiar with SCCM, so I will give some issue I encounterred in SCOM:
1. Not monitored and grey agent, here is an article for your reference:
http://technet.microsoft.com/en-us/library/hh212723.aspx
2. Failed to discover and install agents, this may caused by the action account or install account does not have proper permissions to install the agents. Some time maybe the discovery rule is not enabled.
3. Failed to import Management Pack, this may caused by references MPs are not imported to the management group, or sometime the proper referenced MPs are imported, but there may be incorrect typing in the XML file which defines the management pack.
4. Runas account and Action account fail. If you change password for action account, you may also need to change the password everywhere the account is used in SCOM. For run as account, if the account does not have enough right to run some tasks, we may
encounter errors. You may refer to the below link which take SQL mp for example:
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
Regards,
Yan Li
Regards, Yan Li

Cost of Intune and SCCM 2012 r2 vs SCCM 2012 r2 ICBM

Is there any research/info on pros and cons of SCCM 2012 using intune for internet clinet management vs SCCM 2012 r2 and ICBM? Things like cost, supportabiliy, etc. I have seen intune vs sccm not Intune & SCCM vs SCCM and Internet Client
Based Management.
Cyndy

Hi,
I think the reason is that you cannot manage Windows clients using the WIndows Intune Agent and integrate it with SCCM 2012. The integration with Intune and SCCM 2012 is for Mobile Device Management only so there is no possibility to install the Windows
Intune Agent on a client and then manage it through the SCCM Admin Console.
THe only scenario where that would work is if you manage a Windows 8.1 with the OMA-DM agent and enroll them in Intune as a mobile device with a limited set of features.
So ICBM is still the way to go if you need all the features in SCCM or you want one console to rule them all.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

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.

How does WSUS work when an SCCM 2012 R2 server is newly installed? Should WSUS be installed and configured on same server?

Let me clarify.
We had a functional WSUS server delivering our updates to ours workstations. The location of the WSUS server was pushed out by Group policies.
Later, an SCCM 2012 R2 installation was installed. The original WSUS server was removed. Now WSUS type services appear to be broken.
I tried to start WSUS on the SCCM 2012 R2 server and it does not start. (I assume its not configured).
I want to get WSUS running again but am not sure how to do this safely in conjunction with our SCCM 2012 R2 installation. Do I just reinstall WSUS on the SCCM server and configure? Or is there other preferred methods?
I was not involved in SCCM's installation, so I do not know what was done.
Geoff.

Update functionality is provided via the Software Update Point
https://technet.microsoft.com/en-us/library/gg712312.aspx
... which requires WSUS to be installed - it basically takes control of WSUS.
Any existing group policies defining WSUS servers should be removed so that the SCCM client (which I assume is installed on computers already) can configure accordingly. Otherwise you will have group policy and SCCM client over writing one another to configure
the update server

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

Disable Automatically Deleted Updates Download on SCCM 2012 with WSUS

Hi
I have SCCM 2012 SP1 with WSUS integrated, both are on the same server, I created a structure where I downloaded the updates:
D:\Wsus\HotfixWinX
D:\Wsus = The folder where I installed the WSUS role
HotfixWinX = The folder where I downloaded the hotfix
When I run "Synchronize Software Updates" the updates downloaded with a time of old age are eliminated automatically, have reviewed the log wsyncmgr and I found this:
My question is, how can I prevent updates and updates folders to be automatically deleted?
Thank you.

This is a fully automated process that only works for expired updates. Do keep in mind that after this specific message the updates still exist in the console. For a very good complete explanation, see:
http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

GPO and SCCM 2012 Shared WSUS installation

Hello
At present I have a scenario where SCCM 2012 and wsus are installed on the same server and serving around 600 desktop clients. SCCM is configured to deploy windows updates to the client machine via the sccm client, however the member servers in the
domain do not have the sccm client installed so I have directed them to use the the WSUS installation via GPO. The servers do appear in the wsus console but never report status and never pull down any updates.
Should this setup be possible; to use one wsus instance for both sccm udpate distribution and direct communication from member servers?
windowsupdate.log entries from a member server as follows:
2014-02-04 15:10:01:172
844 1338
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-02-04 15:10:01:172
844 1338
Agent *********
2014-02-04 15:10:01:172
844 1338
Agent * Online = No; Ignore download priority = No
2014-02-04 15:10:01:172
844 1338
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-04 15:10:01:172
844 1338
Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-02-04 15:10:01:172
844 1338
Agent * Search Scope = {Machine}
2014-02-04 15:10:01:350
844 14d8
AU Getting featured update notifications. fIncludeDismissed = true
2014-02-04 15:10:01:351
844 14d8
AU No featured updates available.
2014-02-04 15:10:01:364
844 14d8
AU WARNING: Returning due to error from GetDownloadProgressUx, error = 0x8024000C
2014-02-04 15:10:01:364
844 14d8
AU WARNING: GetInteractiveInstallProgress failed, error = 0x8024000C
2014-02-04 15:10:01:364
564 678
WUApp WARNING: Call to GetInteractiveInstallProgress failed, hr=8024000C
2014-02-04 15:10:02:692
844 1338
Agent * Found 0 updates and 74 categories in search; evaluated appl. rules of 236 out of 825 deployed entities
2014-02-04 15:10:03:234
844 1338
Agent *********
2014-02-04 15:10:03:234
844 1338
Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-02-04 15:10:03:234
844 1338
Agent *************
2014-02-04 15:10:03:238
844 1be4
AU >>## RESUMED ## AU: Search for updates [CallId = {5C25CEFB-5315-4722-A422-790FBC7303B5}]
2014-02-04 15:10:03:238
844 1be4
AU # 0 updates detected
2014-02-04 15:10:03:238
844 1be4
AU #########
2014-02-04 15:10:03:238
844 1be4
AU ## END ## AU: Search for updates [CallId = {5C25CEFB-5315-4722-A422-790FBC7303B5}]
2014-02-04 15:10:03:238
844 1be4
AU #############
Thanks in advance...

Should this setup be possible; to use one wsus instance for both sccm udpate distribution and direct communication from member servers?
No.
Torsten Meringer | http://www.mssccmfaq.de

WSUS 4.0, SQL server, and SCCM 2012 version help

I am trying to get to the bottom of a version question.
We currently have SCCM 2012 R2 up and running, with a DB on a separate server version MSQL 2008 R2. Now we also are using the WSUS integration. I am being told WSUS 4.0 cannot be ran on SQL server 2008 R2, so they could only install and use WSUS version
3.0.
Can anyone out there please shed some light on my version items from above?
Thank you

I am being told WSUS 4.0 cannot be ran on SQL server 2008 R2, so they could only install and use WSUS version 3.0.
(Pedantically speaking this is true because there is no such beast as "WSUS 4".)
However, WSUS v6.2 (Windows Server 2012) and WSUS v6.3 (Windows Server 2012 R2) can most certainly be installed on SQL Server 2008 R2, and the official documentation is at
http://technet.microsoft.com/en-us/library/hh852344.aspx
However, the *preferred* installation methodology, unless you've expressly chosen to use a remote SQL Server, is to use the Windows Internal Database feature which is built into Windows Server 2012 and 2012 R2.
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 Keeps failing on SCCM 2012 R2

Hello all
I am hoping I could get some help with this strange issue:
I am trying to install WSUS on my sccm server prior to the software update point. This what I have done so far:<o:p></o:p>
In server manger I select to install the WSUS role>Click next (I notice there is a feature option to install Windows internal database)
I unchecked this option because I am using my existing sql server for the WSUS instance. I cant seem to find anything that say tells me that when installing sccm 2012 on Windows Server 2012 and you are using the sql database instance for WSUS to do xyz. In
my case as mentioned before unchecked the Windows Internal Database Feature. Then under Roles Services there are three option: WID Database, WSUS Services, Database. I chose WSUS Services and Database. On the next page I defined my source for the downloads,
then the next page DB Instance I entered the instance of the sql server which in my case is also on my sccm 2012 server VMSCCM is the name> Click Check Connection and that was successfully connected to the server. <o:p></o:p>
So here is where everything goes wrong. I then select to install everything at the confirmation page. reboot the server<o:p></o:p>
once rebooted I open server manager and there is message that says Launch post - installation configuration. I then get the following error "Post-deployment
configuration failed see log below is a image for the log located in c:\users\username\appdata\local\temp\tmpFC3D\
<o:p></o:p>
<o:p></o:p>
Phil Balderos

I had similar issues with the WSUS integration with ConfigMgr 2012 R2. I also have the WSUS DB hosted on the same SQL instance where ConfigMgr 2012 installs it's database.
I found WSUS would not function correctly until I added the SYSTEM account to the WSUS Administrators group under Local Users and Groups:
Hope this helps! :-)
Reference Article -->
http://technet.microsoft.com/en-us/library/gg712696.aspx
Look under Plan for WSUS Installation heading. You can also add
NT AUTHORITY\SYSTEM account as a user for the WSUS database (SUSDB) and configure a minimum of the webService database role membership as an alternative to the above
Hello again,
How would I add this account. When I go into th WSUS admin group on the local machines I cannot search for the this type of account. It returns nothing.
Thanks
Phil Balderos

Updates managed by SCCM 2012 R2

Hi,
If I manage and distribute my updates via SCCM 2012 R2, is it a best practice to disable Windows Automatic Updates on clients? In the following article I found that in case of SCCM 2007 it caused some problems regarding to the reboots.
http://support.microsoft.com/en-us/kb/2476479
Thank you,
Dvijne

Unfortunately, ConfigMgr only configures a couple of things including enabling the use of intranet location for updates and the location of that intranet source. It does not disable automatic updates leaving the door open for the WUA to do things on its
own outside the control of ConfigMgr including installing any updates approved directly in WSUS (including new versions of the agent itself which are automatically approved) and rebooting systems which have a pending reboot. Neither of these is desirable in
a ConfigMgr managed environment and thus the recommendation for disabling automatic updates. As for the rest of the Windows Update GPO settings, they are meaningless in the context of ConfigMgr so it doesn't really matter what you set those to if you disable
automatic updates.
Jason | http://blog.configmgrftw.com | @jasonsandys

Equivalent of WSUS "file information" in SCCM 2012 R2

In WSUS, you could r-click on an update, select "file information" and see where in WSUSCONTENT an update was actually located. This was helpful; especically if the update was stored there in an executeable format (not a cab), and you could run
the patch manually. This often works if it won't install through SCCM or WSUS. Does anyone know if it's possible to get this info through SCCM 2012 R2?
Ben JohnsonWY

Thanks everyone and I do appreciate all the input, I understand how this works, but...
This is another case of where something that was quick, simple, and easy in WSUS has been made ridiculously complicated by MicroShaft in SCCM. The Content Info tab isn't what I want, I want to know where it physically is on my server. When you get to
the content ID you can't stretch the column to read it, you have to mouse over it and the popup with a ridculously long path disappears after a few seconds. In the show members listing you can select the unique ID but not content ID and but in the package
folders it uses content ID. Geez! Now if the content ID, with package, were selectable in the show members window it'd be easy. And to top if off, you can't tell by looking at the console which package an update is in. This is something else MS really
needs to work on. It still boggles my mind how they keep removing simple and easy functionality from programs when they come out with new versions. No wonder I couldn't figure this out on my own.
I don't pull updates from MS. I pull the from another source approved for us. They get dropped onto one of my servers. So.....
I'm going back to what Peter suggested; I'm going to look them up using "file info" in WSUS because it's far quicker and easier.
Ben JohnsonWY

Updates Publisher 2011 + SCCM 2012 - no signing certificate every time (Bug?)

Hello everybody,
I got a strange problem with the System Center Updates Publisher 2011 which I want to use with SCCM 2012 (SP1).
Some weeks ago I was able to enable the publishing on the update server (SCUP + SCCM + WSUS are the same machine), to create a self signed certificate and to astablish the connection to the WSUS server.
Some weeks later the SCUP seems to "forgot" the certificate and the option "Enable publishing to an update server" is disabled.
If I try to reactivate this option then I can not create a new self signed certificate anymore.
I get always the "... test connection succeeded. However, no signing certificate was detected ..." dialog.
I also can not choose the existing certificate (.pfx) file ("No certificate information available").
Is this a bug?
Can I deinstall the SCUP completely and create a new certificate again?

Did you open SCUP as administrator? But Yes, you can reinstall SCUP and create another cert or use the existing cert.
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

WSUS Update KB2938066 and SCCM 2012 R2

Similar Messages

Maybe you are looking for