SCCM WSUS Question

Hello,
I'm looking into using SCCM for WSUS and had a rookie question. Let's assume that everything is setup and I have updates synced and ready for me to pick and chose for deployment and I have two Device Collections, Servers and Workstations with workstations
being anywhere from WXP to WIN8. Also let's assume I take all the critical updates for WXP to WIN8 and put them all into one package and deploy it out to my Workstation Collection. Will the client only take the updates that are applicable to OS in question
or will my deployment fail because the client on a WXP machine sees an update for a win8 device?

Will the client only take the updates that are applicable to OS in question or will my deployment fail because the client on a WXP machine sees an update for a win8 device?
Software Updates in ConfigMgr use the WUAgent to scan/detect, and then install/apply the relevant updates, so any updates that are "available" will not be deemed "required" unless WUAgent finds the product (and doesn't find the update is present).
It's the same "do I have it, do I need it" logic that is used for WSUS and windowsupdate.com.
You need to be aware that there are performance penalties on the client and the infrastructure, if you advertise/deploy vast amounts of stuff to vast amounts of clients.
There are also limitations on the maximum number of updates in a package, etc.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

SCCM 2012 - Question before deployment (WSUS/SCUP and other feature).

Hello,
Sorry for the question but I'm a newbie about Microsoft SCCM architecture...
I have to deploy a new WSUS (4.0) server for my new servers (Windows 2012) and I ask myself how I can install him correctly with idea of a futur SSCM system.
About WSUS, this server is only for the new servers (Windows 2012) which can not receive update by our current WSUS server (Windows 2003 WSUS 3.0 SP1). I think I need also upgrade my AD schema to the 2012 level before ?
And from what I understood of SSCM especially for software management (deploy and updates), there is a specific role "Software Update Point" which uses WSUS for Microsoft Product and SCUP for the third party tools.
I am wondering which server configuration is the best for my future SSCM architecture.
Firstly, can I setup my WSUS to a new server and add the role "SSCM - Software Update Point" on the same server later ? If it's possible, what type of server is recommended ?
Just for the WSUS feature I had expected a VM with a dual core CPU, 4GB RAM, 40GB for the system and 100GB only for the update data (a total of 250 servers and clients which can use 2003,2008,2012,XP,7,Office2010,Exchange 2010).
Regarding SSCM in general, Is it recommended to have multiple server for SSCM for a total of 100 servers and 150 clients ? If yes can we separate them by role ?
I think I will have another questions later but it's a good start.
Thanks in advance for your good advice !
Have a nice day,
Clement

Hi,
Thanks for your advice, I have many questions because I did not want setup an SSCM now but it seems it's the better solution (my first need is to deploy MS update on my new servers).
If I install my WSUS service on my server I could not reuse it directly for my SSCM (because I must start with a fresh installation of WSUS?).
Regarding the hardware, I thinks that minimum requirements isn't a good idee (see bellow).
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_MinHWReqs that
Hardware component
Requirement
Processor
Minimum: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support
Minimum: 1.4 GHz
RAM
Minimum: 2 GB
Free disk space
Available: 10 GB
Total: 50 GB
Do you believe that an dual core with 4GB is correct ?
And for the disk at least 100GB just for the WSUS and 200GB for the storage of system image and package deployment (third party tools) ?
Edit : value is totaly different here :
http://technet.microsoft.com/en-us/library/hh846235
Stand-alone primary site
Up to 100,000 clients
SQL Server is installed on the site server computer
8 cores (Intel Xeon E5504 or comparable CPU)
32 GB of RAM
550 GB hard disk space for the operating system, SQL Server, and all database files
I thinks if we deploy an SSCM, we will use it for the deployment of system (clients), applications (Office, third party tools), updates (MS and third party tools) but also for the managing of our infrastructure (SSCM seems very powerfull).
Regards,
Clément

Basics of SCCM - WSUS Relationship

Hi all,
Just had a question about how updates in SCCM 2007 work. At a very basic level, I understand it to work like this:
SCCM Side: WSUS syncs with Microsoft to build metadata list of all available updates > SCCM leverages WSUS metadata to provide a list of available updates visible under "Software Updates" in SCCM console >
SCCM Admins can then created Update Lists and Deployment Packages based on the wsus metadata > Deployment Packages are applied to Collections
Client Side: CCM client runs an update scan > CCM client leverages the machine's WUA to check available updates on the SCCM server > CCM Client makes a list of the updates that it needs but does
net yet have installed > downloads the updates and installs them from the DP
My question is about what source the CCM client/WUA uses to check which updates are available. Does it simply check the update packages which have been applied to all those collections that it happens to be a member of?
Also, is WSUS completely passive in this whole process - i.e. is it merely a conduit for SCCM to source metadata about available updates?
Thanks for any help!

A handful of comments here:
First, don't confuse packages with deployments. They are two different things in both 2012 and 2007. Packages are simply the binary files that ConfigMgr places on DPs. Clients download the binaries from these when they are needed. Deployments determine what
updates are assigned to or required on clients.
As mentioned, update metadata, basically the definition of all possible updates and how to know what systems the updates apply to comes from the WSUS instance corresponding to the SUP.
The scan cycles kick the WUA into action to scan for updates. The Normal scan cycle is like an incremental and the re-eval cycle scans for all deployed updates to make sure that they are still installed and reinstall them if they aren't. The normal scan
cycle is kicked off at various other times also linked with deployments.
Finally, for using the required attribute, which is reflective of how many clients need a particular update, I think this a reactive approach that is anti-security as it reflects the past and not the current state of the environment. Granted the past may
only be a day ago; however, in security terms, that doesn't matter. Being pro-active in this case, i.e., making all potentially applicable and in-scope updates available comes at the cost of disk space, nothing more. Thus, I generally recommend against using
this attribute.
As for WMI, think of ConfigMgr as a WMi automator -- just about everything that ConfigMgr does involves WMI. In simple terms, WMI is just a DB storing info on local systems.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM/WSUS issue after importing March CSA patch bundle

Hi, I am having an issue with security patch deployment since Tuesday night. Debugging is ongoing. I am running SCCM 2012 CU2.
Coincidentally, the problem appeared shortly after importing the March XP CSA (Custom Support Agreement) patch bundle into SCCM. From the client end, WUAHandler.log reported continuous failures/retries. On lower-end machines, system performance
became very poor. From the server end, starting up the Windows Server Update Services mmc (yes, I know you're not supposed to be doing anything in here, which I'm not) results in a connection error. The detailed error message is shown further down.
It was difficult to get the client machines to stop "thrashing" per WUAHandler.log. It wasn't until I de-installed/re-installed WSUS and ASP.NET that things quieted down yesterday afternoon. All appeared to be stable until this morning
when I re-added "Windows XP Custom Support" under the SUP Component Properties tab, imported the CSA bundle info, initiated a CAB synchronization from Microsoft, and re-enabled Software Updates on the clients.
Again, I would get the error when starting up the Windows Server Update Services mmc.
I am doing everything again, but this time one step at a time. My working theory is that there is some kind of corruption caused by the CSA import (this worked just fine up until Feb.). A few hours ago, Microsoft published a new CSA
patch bundle because a patch was apparently forgotten. Is it possible that there was some kind of corruption included with the original bundle published on Tuesday?
I will post what I find as a result of my debugging.
Thanks,
Nick.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)

Yes, WCM.log showed the same 503 error starting on the Wednesday morning at 2:53am, and I also noticed wsuspool had stopped. My most noticeable symptom was the thrashing of wuahandler.log on the clients, causing poor system performance on machines with 2gb
of memory. Multiple de-installs/re-installs of WSUS failed to clear the issue until we increased the memory setting in IIS.
Nick
WCM.log:
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String
ServerName, Boolean UseSSL, Int32 PortNumber) $$<SMS_WSUS_CONFIGURATION_MANAGER><03-11-2015 02:53:26.225+240><thread=30872 (0x7898)>
Remote configuration failed on WSUS Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-11-2015 02:53:26.226+240><thread=30872 (0x7898)>

SCCM WSUS Deployment Package Confirmation

Hello,
Our WSUS setup is pretty much finalized but wanted a quick clarification so I can draw out a procedure. Let's assume I have 400 security updates that I need to make sure are deployed and I have E:\WSUS\Security Updates. I'm going to make 4 Software Update
Groups with 100 updates each. I make SUG 1 and create a package in the above mentioned folder with a name similar to the Deployment Name, lets assume Security Update Group 1 4-9-2014.
Overnight the deployment was a success and when I come in the following morning I'm ready to deploy the second software update group. Should I be creating new package for the second SUG or use the first deployment package? What exactly will happen if
I use the first deployment package? Will the data from the first SUG be part of the package or will it only contain date from the second update group?

Update Groups are in no way tied to update packages. Update groups organize updates and are used to assign the updates to clients (via collections). Update packages are simple repositories of the update binaries. Once a client determines that it needs to
install an update assigned to it, it will pull the update from any available update package. The client knows nothing about either update groups or update packages.
So to answer the questions:
Should I be creating new package for the second SUG or use the first deployment package?
- It doesn't really matter. I generally create calendar based update packages for all updates within that period whether it be yearly, semi-annually, quarterly, bi0-annually, whatever. My only rule of thumb here is not let the package get too big because
then you may have issues if the package ever gets corrupted.
What exactly will happen if I use the first deployment package?
- Nothing special as long as the package is available to client it doesn't know or care.
Will the data from the first SUG be part of the package or will it only contain date from the second update group?
- Neither. There is no connection between the two objects. As mentioned, update groups contain the updates (the metadata) and the packages contain the binaries. Both have distinct purposes in the process.
As a final note, you mentioned using "E:\WSUS" -- actually two notes.
- Each update package must have its own unique (sub-)directory.
- Don't use the directory configured as the WSUS update repository -- that is a folder for exclusive WSUS use and bad things will ensue if you try to use it. The package source directories should typically be part of your normal software reposiotry in their
own unique and distinct folders.
Jason | http://blog.configmgrftw.com

Had to replace a WSUS server that went south, now SCCM WSUS not pulling updates

We had a 08 R2 machine serving as our WSUS server, it failed a few weeks ago and had to be replaced and was replaced with a VM 2012 R2 box. I removed the older server from SCCM, proceeded to set up the new server (it has the same name as the old on)
and re-add it back to sccm. I thought everything was okay but when I checked the logs yesterday I noticed that it wasn't syncing with the new server. The WCM.log file:
Successfully connected to server: wsus-01.friver.local, port: 8530, useSSL: False   3/26/2014 8:51:37 AM   3648 (0x0E40)
Successfully refreshed categories from WSUS server   3/26/2014 8:51:45 AM   3648 (0x0E40)
Attempting connection to WSUS server: wsus-01.friver.local, port: 8530, useSSL: False   3/26/2014 8:51:50 AM   3648 (0x0E40)
Successfully connected to server: wsus-01.friver.local, port: 8530, useSSL: False   3/26/2014 8:51:50 AM   3648 (0x0E40)
Category Company:94d731de-22a6-4458-dc4d-b5267de026fc (Adobe Systems, Inc.) not found on WSUS   3/26/2014 8:51:50 AM   3648 (0x0E40)
Starting WSUS category sync from upstream...   3/26/2014 8:51:50 AM   3648 (0x0E40)
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()   3/26/2014 8:51:55 AM   3648 (0x0E40)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500   3/26/2014 8:51:55 AM   3648 (0x0E40)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=Cor-sccm-02.FRIVER.LOCAL SITE=FR1 PID=7624 TID=3648 GMTDATE=Wed Mar 26 12:51:55.295 2014 ISTR0="wsus-01.friver.local" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0   3/26/2014 8:51:55 AM   3648 (0x0E40)
Waiting for changes for 60 minutes   3/26/2014 8:51:55 AM   3648 (0x0E40)
the wsyncmgr.log doens't have anything in it at the moment other than sync failed and it will retry in 60 minutes, after the next attempt I will post more from there. Did I miss a step somewhere or was there an additional step I should have taken to
clean out the old server from SCCM that I'm not aware of?

I did, still no go. Here is the entry from WCM.log
Starting WSUS category sync from upstream...   3/26/2014 12:51:50 PM   3648 (0x0E40)
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssNotFound: ~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning()   3/26/2014 12:51:55 PM   3648 (0x0E40)
Failed to set Subscriptions on the WSUS Server. Error:(-2146233088)Unknown error 0x80131500   3/26/2014 12:51:55 PM   3648 (0x0E40)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=Cor-sccm-02.FRIVER.LOCAL SITE=FR1 PID=7624 TID=3648 GMTDATE=Wed Mar 26 16:51:55.707 2014 ISTR0="wsus-01.friver.local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0   3/26/2014 12:51:55 PM   3648 (0x0E40)
Waiting for changes for 60 minutes   3/26/2014 12:51:55 PM   3648 (0x0E40)
Trigger event array index 0 ended.   3/26/2014 1:00:04 PM   3648 (0x0E40)
SCF change notification triggered.   3/26/2014 1:00:09 PM   3648 (0x0E40)
Populating config from SCF   3/26/2014 1:00:09 PM   3648 (0x0E40)
From wsyncmgr.log
Starting Sync   3/26/2014 3:34:14 PM   4992 (0x1380)
Performing sync on local request   3/26/2014 3:34:14 PM   4992 (0x1380)
Read SUPs from SCF for Cor-sccm-02.FRIVER.LOCAL   3/26/2014 3:34:14 PM   4992 (0x1380)
Found 1 SUPs   3/26/2014 3:34:14 PM   4992 (0x1380)
Found active SUP wsus-01.friver.local from SCF File.   3/26/2014 3:34:14 PM   4992 (0x1380)
Sync failed: WSUS update source not found on site FR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource   3/26/2014 3:34:14 PM   4992 (0x1380)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=Cor-sccm-02.FRIVER.LOCAL SITE=FR1 PID=7624 TID=4992 GMTDATE=Wed Mar 26 19:34:14.721 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site FR1. Please refer
to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0   3/26/2014 3:34:14 PM   4992 (0x1380)
Sync failed. Will retry in 60 minutes   3/26/2014 3:34:14 PM   4992 (0x1380)
Setting sync alert to active state on site FR1   3/26/2014 3:34:14 PM   4992 (0x1380)
Sync time: 0d00h00m00s   3/26/2014 3:34:14 PM   4992 (0x1380)

SCCM WSUS Synchronization fails with error 0x80131904

With no reason the software update point in SCCM 2012 CU3 fails to synchronize update from the local installed WSUS service. I have checked the WSUS Sync manager log and what I have got is in the image below. I have tried to uninstall and the WSUS service
and reinstalled it but no success. I have also used the clean up option from the WSUS console and no success yet.
From the log below I am quite sure that if I can force the removal or clean up those updates that are failing to get saved the SCCM Update point synchronization might be able to fully synchronize. I hope someone can help me out. Thanks in advance.
Event view error - 2148734208
Wsyncmgr.log

I need WCM.log for investigation. Please upload this file to Skydrive and post the link here.
Juke Chou
TechNet Community Support

SCCM/WSUS report on updates needed and what type of update

Hello all. I have been trying to get a report that will show the updates needed on a computer broken down by update type (security, critical, rollup, etc.). I am getting duplicate entries in the results, and don't know what I need to do to
filter out the results that don't apply to the computer in question. Here is what I have so far:
SELECT distinct sys.Netbios_Name0, catinfo.CategoryInstanceName, summ.QNumbers, summ.ID, summ.Title, ps.LastStatusTime, os.LastBootUpTime0
FROM v_UpdateComplianceStatus css
JOIN v_R_System sys ON css.ResourceID = sys.ResourceID
JOIN v_GS_PatchStatusEx ps ON sys.ResourceID=ps.ResourceId
JOIN v_GS_OPERATING_SYSTEM os ON os.ResourceID=sys.ResourceId
JOIN v_ApplicableUpdatesSummaryEx summ ON ps.UpdateID=summ.UpdateID
JOIN v_CICategories_All catall ON catall.CI_ID = css.CI_ID AND css.Status = 2
JOIN v_CategoryInfo catinfo ON catinfo.CategoryInstance_UniqueID = catall.CategoryInstance_UniqueID
AND ((catinfo.CategoryInstanceID = 26) OR (catinfo.CategoryInstanceID = 30) OR (catinfo.CategoryInstanceID = 33) OR (catinfo.CategoryInstanceID = 34))
WHERE sys.Netbios_Name0 = 'MachineName'
AND (ps.LastStateName <> 'Install Verified' AND ps.LastStateName <> 'Preliminary Success')
AND summ.Title NOT LIKE '%(LEGACY)%'
ORDER BY sys.Netbios_Name0, summ.ID
This gives me the updates in question that are needed, but produces mulitple rows for the same update. I'm probably missing something simple, but I'd appreciate any input. Thanks! Chip

Yes, I know this is an old post, I’m trying to clean them up.
I have run this query and it does not produce duplicates rows. It does however show that some SU have multiple classifications, hence why you are see it a few times.
http://www.enhansoft.com/

MBAM with SCCM Reporting Question

My company has SCCM 2012 R2 deployed with a CAS and 5 primary sites. If we install MBAM with SCCM integration on all the primary site servers, will the MBAM reports be limited to the primary site, or will there be reports at the CAS level that cover
all of our primary sites?

Ken,
In the 'About MBAM 2.0 SP1' article, in the 'What's new in MBAM 2.0 SP1' section under the heading 'Ability to install MBAM on a primary site server when you install MBAM with Configuration
Manager' it talks about the previous requirement to install MBAM on a central site server. Additionally, under the sub-heading 'System Center 2012 Configuration Manager', it states that you can install MBAM on a primary site server or on a central administration
server...
Hope this helps,
David
MDOP on the Springboard Series on TechNet

SCCM Reporting Question - Removing Duplicates (query)

I have a query created for a software usage report in SCCM. When there are multiple versions of the same software (Acrobat) installed on the same machine, I will receive duplicate results for the same machine. For example, it will come back with Acrobat
9 and another Acrobat 10 for HOSTNAME1. However, only Acrobat 10 has a usage count. Is it possible to delete the row for Acrobat that has a software usage count of "0/null" if there is another Acrobat results showing up that actually has a usage
count? Let me know if I need to clarify. Any suggestions would be appreciated.

Without the query that you are using, it will be impossible for anyone to answer this.
http://www.enhansoft.com/

SCCM Reporting question

Is there another way to run a report in SCCM than using SQL to run it.
MSB

Have you configured a Reporting Services Point?
You can find all the information you need about Reporitng in ConfigMgr 2012 here:
http://technet.microsoft.com/en-us/library/gg712698.aspx
And here is a step-by-step guide for setting it up:
http://www.windows-noob.com/forums/index.php?/topic/4550-using-sccm-2012-rc-in-a-lab-part-11-adding-the-reporting-services-point-role/

SCCM 2012R2 question

Why do people still use SCCM? Use lansweeper and a monitoring system like opsview...

I'm trying to setup System Center Configuration manager 2012 R2. I've got the server setup and created a basic task sequence to install windows 8. I can boot into the PXE environment and select the task that I created. After I select the task I get the following error: "This task sequence can not be run because the program files for XXXXXX cannot be located on a distribution point" I've checked the content status of the boot image and the packages and they are on the distribution point. Can anyone help
This topic first appeared in the Spiceworks Community

SCCM/WSUS 2007 01-2015 Bulletin Patching issue. Some clients patch just fine, some will not download the content.

Bit new to the admin side, so please excuse some ignorance.
We have approx 6000 end points. We setup this months patches and a couple out of cycle ones we noticed. We are getting a TON of clients that will not patch. They are getting the defintions but when we attempt to run the advertised
patches they fail approx 10 seconds later. However, some servers on the same boundry will patch just fine. We get the error message in the logs that when the client was told to download the content from the DP, it spits out error that content does
not exist. The DPs we believe are having the issues are MPs as well sitting in DMZ. We have 2 sites configured basically the same, both DP/MPs in DMZ are the ones having the issues. We have confirmed clients are able to connect anon to the
DP/MP. But again, some clients are patching just fine.
UpdatesDeployment.log has the following warning listed 7 times.
Not refreshing update presence state as error CI Info status received
But yet does see that it needs 7 patches.
EnumerateUpdates for action (UpdateActionInstall) - Total visible updates = 7
No other logs show any errors on the clients. I have confirmed the content is avalible on the DP/MP it is reporting too. Obviously though since other clients sitting right next to them work still.
Any ideas? Trying to avoid working all weekend. Thank you!

We checked every single log on every MP, DP, SS and many clients. For unknown reasons, deleteing and rebuilding the Jan update list did the trick.

WSUS with SCCM 2012 - Products Missing, and Best Practices

Good morning all
I am integrating SCCM with WSUS, and I have a few questions regarding products. I've noticed when running through the "Add site system roles wizard" in SCCM 2012 console that when I go to "Products" it does NOT list a few major
products, such as office 2013, sql server 2013, exchange 2013, etc.
Am I missing something? I'm sure I am...what do I need to do?
Also, if there are any other gotchas or best practices you all can point me in the right direction as far as managing SCCM / WSUS together i'd be greatly appreciated.
Thanks so much!

Do not use WSUS Console to manage the updates. All you things you can finish is in the SCCM Console. Refer to the link posted by Jason.
Juke Chou
TechNet Community Support

SCCM 2012 - WSUS Cleanup

Hello,
I'm tried to find what I needed online but wasn't able to find a resource that wasn't a third party script. I heard of WSUS cleanup utility that comes with SCCM/WSUS, is this true? I would like to have our expired/superseded updates removed from the console
as part of a manual maintenance.
I know the "WSUS" Console has a link to a utility but I was under the impression that there is one specifically for WSUS in SCCM.
EDIT:
Will SCCM automatically remove the expired updates on a 7 day cycle?

Hope this helps
http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
Cheers
Paul | sccmentor.wordpress.com

SCCM WSUS Question

Similar Messages

Maybe you are looking for