Guys

Is there a KB for how to setup that the WSUS updates go thru the SCCM instead of the Internet?  Is thru a Group Policy? 

Hello - I am currently running into an issue in SCCM 2012 where my Windows updates are installing for my clients, but they are never reporting that they installed. All devices show "Unknown" under Monitoring > Deployments with the following details under "Category": Client Check passed/Active

For some backstory, we recently had an issue where SCCM/WSUS synchronization totally broke down on our SCCM server, so I had to reinstall WSUS and add back the SUP role in ConfigMgr console. 

Everything is synchronizing and installing perfectly, it's just the reporting feature that is bombing out now for some reason.

Note, if I go to Software Library > Software Updates > Software Update Groups I can see the working compliance state there for all the different Software Update Groups we have setup, but if I look at the same software update groups via Monitoring > Deployments it shows 0% compliant and all devices as "Unknown". 

Let me know if you need any other info or log file postings. 

Thanks for the help in advance. 

SCCM 2012 R2 CU3 + Endpoint Protection. I am seeing an increasing number of clients reporting out of date Forefront definitions. Spent a bit of time checking and this seems to be a known problem - in Windowsupdate.log seeing

ISusInternal::GetUpdateMetadata2 failed, hr=8007000E

There are a few threads on this which seem to indicate this to be nothing to do with SCCM but a WSUS error that MS are writing a fix for. However from what I read this is not going to be available until June/July 2015

I have written a batch file as so as recommended in this thread

http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx

sc config wuauserv type= own
bcdedit /set increaseuserVA 3072

Followed by a reboot

I am finding that with a lot of coaxing i.e. 2-3 or more reboots, software scan cycle, software deployment evaluation cycle that most eventually update but some will not and I've ended up rebuilding PCs

Therefore trying to work out the best course of action to keep the estate compliant

Is there any merit in trying to deal with the WSUS database? - you could in theory completely delete it, reinstall and setup SCCM all over again. I'd be loath to do all this unless it has a real benefit. Going through the WSUS Server Cleanup Wizard didn't remove anything as I assuming SCCM 2012 R2 does most of it for you these days

So looking for advice please

Ian Burnell, London (UK)

Greetings,

I have an issue where a large number of PCs and servers in my environment are not detecting available software updates that were deployed after patch Tuesday.  Details are as follows:

I am running SCCM 2012 R2 with CU3 on a virtual 2012 R2 server with SQL 2012 SP2 on the same VM.

I believe this started happening since last month's (April) patch cycle.  A vast majority of my clients detect available patches, install, and reboot as they should, but a large handful do not. I have checked the WUAHandler, UpdatesDeployment, UpdatesHandler, UpdatesStore, and WindowsUpdate logs on various problematic clients, and all do not show any errors when the SCCM client scans for updates.  Specifically the WUAHandler and UpdatesDeployment logs show the scans complete successfully with zero errors but do not detect any available updates.  Is this also true if I log into the PC/server and manually run the Software Updates Scan from the SCCM applet within control panel.  If I run Windows Update from a client and have it check online from windows update, it finds patches so I know the update agent works.

I know the issue is not due to patches not downloaded or deployed within SCCM as machines with the same operating system as those that are having issues received the same patches.  In one example I reinstalled the sccm client and within an hour it detected patches and I received the notification within the system tray.  In another example I reinstalled the agent but it did not detect patches.  And again, the logs on the client do not show any errors.  It simply does not detect any patches are available.  The machines that are having issues are running various operating systems (Windows 7 x86, Server 2003 SP2, Server 2008 R2, and Server 2012.)

In some occasions, rebooting the PC or server has resolved this for a random machine but for most of the affected machines, a reboot doesn't do anything to help.

If anyone has any suggestions on where to look or what to do to help troubleshoot or resolve, I would appreciate it.

Thanks,

Mike G

Hi all,

i need your kind advice on FEP configuration in sccm 2012.

i have configured software updates FEP definitive updates to be synced every 24 hours but i am not getting any alert on the status either started, success or failures i wud like to get the alertvia email. Is there a way i can use scom for monitoring how can i do it. Pls help

 or

Regards, Pratap

Dear SCCM users and/or technicians,

My objective is to update SCCM to the last version. 

I am in a test environment with SCCM v 5.0.7804.1600.

I tried to apply R2 CU5 hotfix [KB3054451] and also R2 CU1 [KB2938441] but impossible to complete it.

Here is the Error message :

I tried to search on the web without success.

Where is located the right files in order to sucess my update ?

Thank you very much for your assistance.

Niko

In order to troubleshoot maintenance window issues in servicewindowmanager.log it would be useful to know what the 'type' refers to (e.g. updates, task sequence etc):

OnIsServiceWindowAvailable called with: Runtime:1, Type:4 ServiceWindowManager 27/05/2015 09:18:22 7716 (0x1E24)

I've seen type 2, 4 and 6 mentioned in the logs

Thanks

David

We don't have a maintenance window defined for the client collection but see servicewindowmanager.log references 'out of hours' 22:00-5:00.  The deployment doesn't have a tick against allow software updates installation outside the maintenance window.  Does out of hours count as a maintenance window re this tick box?   We have also increased the computer restart client setting to 9 hours which exceeds the out of hours window - could this be the issue?  I tried reducing this in a new client setting and publishing to a test collection but no difference

Software center shows many required updates as 'waiting to install'

Thanks

David

CUpdateAssignmentsManager received a SERVICEWINDOWEVENT START Event UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
Suspend activity in presentation mode is selected UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
At least one user has elected to suspend non-business hours activity when in presentation mode. Checking for presentation mode. UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
Proceeding to non-business hours activites as presentation mode is off. UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
Auto install during non-business hours is disabled or never set, selecting only scheduled updates. UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
A user-defined service window(non-business hours) is available. We will attempt to install any scheduled updates. UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
Attempting to install 0 updates UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
No actionable updates for install task. No attempt required. UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
Updates could not be installed at this time. Waiting for the next maintenance window. UpdatesDeploymentAgent 27/05/2015 22:00:00 6816 (0x1AA0)
CUpdateAssignmentsManager received a SERVICEWINDOWEVENT END Event UpdatesDeploymentAgent 28/05/2015 05:00:00 6316 (0x18AC)
No current service window available to run updates assignment with time required = 1 UpdatesDeploymentAgent 28/05/2015 05:00:00 6316 (0x18AC)
Attempting to cancel any job started at non-business hours. UpdatesDeploymentAgent 28/05/2015 05:00:00 6316 (0x18AC)
Cancellation not allowed in the current job state UpdatesDeploymentAgent 28/05/2015 05:00:00 6316 (0x18AC)

A Timer Event has occurred ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
    Sending Message SERVICEWINDOWEVENT:START event ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
    The Service Window=45dca355-3249-4845-b8aa-72d0e604548e has started at 05/27/15 22:00:00 ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
Checking Service Windows to find Next Event..... ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
    Next Event Time is at 05/28/15 05:00:00. Service Window with ID:45dca355-3249-4845-b8aa-72d0e604548e. Is the next event the beginning of the window? No ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
    Scheduling the Timer Task ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
    Scheduled the timer to fire on 05/28/15 05:00:00 ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
OnIsServiceWindowAvailable called with: Runtime:900, Type:2 ServiceWindowManager 27/05/2015 22:00:00 1676 (0x068C)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 27/05/2015 22:00:00 1676 (0x068C)
OnIsServiceWindowAvailable called with: Runtime:1, Type:4 ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
OnIsServiceWindowAvailable called with: Runtime:1, Type:6 ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
        Biggest Active Service Window has ID = 45dca355-3249-4845-b8aa-72d0e604548e having Starttime=05/27/15 22:00:00 ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
            Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
ActiveServiceWindow has 25200 seconds left ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
Program can run! Setting *canProgramRun to TRUE ServiceWindowManager 27/05/2015 22:00:00 6816 (0x1AA0)
OnIsServiceWindowAvailable called with: Runtime:900, Type:6 ServiceWindowManager 27/05/2015 22:00:00 1676 (0x068C)
        Biggest Active Service Window has ID = 45dca355-3249-4845-b8aa-72d0e604548e having Starttime=05/27/15 22:00:00 ServiceWindowManager 27/05/2015 22:00:00 1676 (0x068C)
            Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 27/05/2015 22:00:00 1676 (0x068C)
ActiveServiceWindow has 25200 seconds left ServiceWindowManager 27/05/2015 22:00:00 1676 (0x068C)
Program can run! Setting *canProgramRun to TRUE ServiceWindowManager 27/05/2015 22:00:00 1676 (0x068C)

All, 

CM2012 R2 CU4. Two monthly ADRs for Office 201x x86 and x64 targeting my 'immediate testers' group. (Double/Triple-checked this) Criteria for each is:

• Date Released or Revised:Last Month
• Product: "Microsoft Lync 2010" OR "Office 2010" OR Office 2013"
• Title:-sharepoint OR -32-bit OR -servers
• Update Classification:"Critical Updates" OR "Definition Updates" OR "Security Updates"

Checking the two ADR SUGs I see my expected April 2015 CritSecs and Definition updates but also 2889923. The Update Classification for that is 'Updates', and NO other updates are showing for that Classification. I also see 2889953, which *is* a Critical Update (I will be removing this one for now). No other monthly ADRs have 'Updates'...

Why would just this one Update be included when no others are. Is there some dark magic at hand? Should I direct this to WSUS.

Thanks

Niick

Hello guys !  I know that the question in the "title" of the thread is a bit vague, so let me explain my issue :)

First of all grab a pencil and a sheet of paper, I am gonna introduce some concepts of our infrastructure which are necessary in order to understand my problem.

So let's say I have 4 different network zones (1, 2, 3, 4) where different windows domains are hosted (A, B, C, etc.).

Without giving too much information about our infrastructure, the final drawing is as follow :

Primary site (with SUP) in Network zone 1 Domain A

And I have

1 MP/DP/SUP in the network zone 2, Domain A, managing untrusted domains in zone 2

1 MP/DP/SUP in the network zone 3, Domain A, managing untrusted domains in zone 3

1 MP/DP/SUP in the network zone 4, Domain A, managing untrusted domains in zone 4

So in abstract, all SUPs are in the same windows domain sharing the same DB managing different untrusted windows domains.

Everyone still here ? :)

So, all SUP roles installed, all my clients in the untrusted domains receives the 4 SUPs (locationservice.log). I've read a lot of documentation and topics and I understood that since 2012 SP1 (My version is 2012R2 CU3 if my memory is still fine), SCCM supports multiple SUPs.

My problem in fact is that, for example, a client in a domain in network zone 2, takes the SUP of the network zone 1 which is not allowed regarding our security policy, it should take the SUP from the same network zone (alias 2). But as I understood, that shouldn't be a big deal since after 4 unsuccessful attempts  at the interval of 30 minutes between the intervals (in other words 2 hours) it should roll the SUPs and try to connect to another one, excepted that after few days, it doesn't and the client is still trying to reach my primary site in network zone 1 ...

Then I came across the following article which describe exactly my issue : http://blogs.technet.com/b/umairkhan/archive/2014/10/03/configmgr-2012-r2-multiple-sup-scenario-clients-not-failing-over-to-the-other-sup.aspx

Error 0x80072ee2 in WindowsUpdate.log etc.

So I applied the workaround by adding the error code to the "WSUS Scan Retry Error Codes" but unfortunately it doesn't do the trick ... And my client continues to try to contact the primary site and not the SUP he's supposed to.

Is it clear enough ?

So my questions are quite simple ...

1. Am I doing it right ?

2. Is there a way to force the SUP through a registry hack such as for the MP (AllowedMPs) ?

Any other suggestion is welcome !

Thank you :)

I have a configuration baseline that is checking for the following 2 patches:

• KB2834140
• KB2670838

These are prerequisite patches for IE 11 (which we are beginning to roll out). I wanted to try to address machines that don't have the updated ahead of IE 11 deployment. I created a single configuration baseline that looks for the x86 and x64 patches, then deployed that to all my workstations.

I was kind of surprised to see the number of machines that have error 80072EE2 (which is an HTTP timeout). I presume that the timeout is trying to reach MS updates, but I can't find a log that points me in that direction. The DcmWmiProvider.log has the following entries:

Initialize called for the provider	UDAProvider	5/28/2015 8:05:38 AM	4608 (0x1200)
CreateInstanceEnumAsync called for the provider	UDAProvider	5/28/2015 8:05:38 AM	4608 (0x1200)
CreateInstanceEnumAsync called for the provider	UDAProvider	5/28/2015 8:05:44 AM	4608 (0x1200)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:06:37 AM	3600 (0x0E10)
ScanForUpdate called in the provider	DcmSUMProvider	5/28/2015 8:06:37 AM	3600 (0x0E10)
Adding error code: (0x80072ee2) for Job:F74CEB40-B92A-4A78-973D-D0C3A4662821	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Failed in discovering instance.
Unknown error (Error: 80072EE2; Source: Unknown)	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Failed to do HandleCreateInstanceEnumAsync().
Unknown error (Error: 80072EE2; Source: Unknown)	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Failed to process CSUMProvider::GExecQueryAsync.
Unknown error (Error: 80072EE2; Source: Unknown)	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Job: F74CEB40-B92A-4A78-973D-D0C3A4662821 already had error returned earlier. Returning the same error.	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Job: F74CEB40-B92A-4A78-973D-D0C3A4662821 already had error returned earlier. Returning the same error.	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Job: F74CEB40-B92A-4A78-973D-D0C3A4662821 already had error returned earlier. Returning the same error.	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)

I'd like to understand what DCM is doing here, and what next steps would be, but I'm a little stuck on where to go from here. Pointers would be appreciated.

2015-05-19 16:19:08:335 1480 cf8 AU Triggering AU detection through DetectNow API
2015-05-19 16:19:08:335 1480 cf8 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2015-05-19 16:19:08:335 1480 cf8 AU Triggering Online detection (interactive)
2015-05-19 16:19:08:335 1480 cf8 AU Adding timer:
2015-05-19 16:19:08:335 1480 cf8 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-05-19 15:19:08, not idle-only, not network-only
2015-05-19 16:19:08:335 1480 bc8 AU #############
2015-05-19 16:19:08:335 1480 bc8 AU ## START ##  AU: Search for updates
2015-05-19 16:19:08:335 1480 bc8 AU #########
2015-05-19 16:19:08:335 1480 bc8 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2015-05-19 16:19:08:335 1480 bc8 IdleTmr WU operation (CSearchCall::Init ID 18) started; operation # 224; does use network; is not at background priority
2015-05-19 16:19:08:335 1480 bc8 IdleTmr Incremented idle timer priority operation counter to 2
2015-05-19 16:19:08:335 1480 bc8 Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 18]
2015-05-19 16:19:08:335 1480 bc8 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {D023DBFE-C8C5-4E40-B88D-0C6A8304F539} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2015-05-19 16:19:08:335 1480 628 Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 18]
2015-05-19 16:19:08:335 1480 628 Agent *************
2015-05-19 16:19:08:335 1480 628 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 18]
2015-05-19 16:19:08:335 1480 628 Agent *********
2015-05-19 16:19:08:335 1480 628 Agent   * Online = Yes; Ignore download priority = No
2015-05-19 16:19:08:335 1480 628 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"
2015-05-19 16:19:08:335 1480 628 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-05-19 16:19:08:335 1480 628 Agent   * Search Scope = {Machine & All Users}
2015-05-19 16:19:08:335 1480 628 Agent   * Caller SID for Applicability: S-1-5-21-2821014886-3934871671-2542969025-500
2015-05-19 16:19:08:335 1480 628 Agent   * RegisterService is set
2015-05-19 16:19:08:351 1480 628 EP Got WSUS Client/Server URL: "http://SCCM-CLOUDW-PS2.CloudW.net:8530/ClientWebService/client.asmx"
2015-05-19 16:19:08:351 1480 628 Setup Checking for agent SelfUpdate
2015-05-19 16:19:08:351 1480 628 Setup Client version: Core: 7.9.9600.17489  Aux: 7.9.9600.17489
2015-05-19 16:19:08:351 1480 628 EP Got WSUS SelfUpdate URL: "http://SCCM-CLOUDW-PS2.CloudW.net:8530/selfupdate"
2015-05-19 16:19:08:382 1480 628 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2015-05-19 16:19:08:413 1480 628 Misc  Microsoft signed: NA
2015-05-19 16:19:08:413 1480 628 Misc  Infrastructure signed: Yes
2015-05-19 16:19:08:413 1480 628 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\TMP6C48.tmp with dwProvFlags 0x00000080:
2015-05-19 16:19:08:429 1480 628 Misc  Microsoft signed: NA
2015-05-19 16:19:08:429 1480 628 Misc  Infrastructure signed: Yes
2015-05-19 16:19:08:429 1480 628 Setup FATAL: GetClientUpdateUrl failed, err = 0x8024D009
2015-05-19 16:19:08:429 1480 628 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2015-05-19 16:19:08:429 1480 628 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
2015-05-19 16:19:08:679 1480 628 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
2015-05-19 16:19:08:679 1480 628 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =http://SCCM-CLOUDW-PS2.CloudW.net:8530/ClientWebService/client.asmx
2015-05-19 16:19:08:679 1480 628 PT WARNING: Cached cookie has expired or new PID is available
2015-05-19 16:19:08:679 1480 628 EP Got WSUS SimpleTargeting URL: "http://SCCM-CLOUDW-PS2.CloudW.net:8530"
2015-05-19 16:19:08:694 1480 628 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 225; does use network; is at background priority
2015-05-19 16:19:08:694 1480 628 PT Initializing simple targeting cookie, clientId = 764620ad-4497-4fda-8c94-09edddd2dc69, target group = , DNS name = testvm-lc-x86.lc.local
2015-05-19 16:19:08:694 1480 628 PT   Server URL = http://SCCM-CLOUDW-PS2.CloudW.net:8530/SimpleAuthWebService/SimpleAuth.asmx
2015-05-19 16:19:08:710 1480 628 WS WARNING: Nws Failure: errorCode=0x803d0013
2015-05-19 16:19:08:710 1480 628 WS WARNING: Soap fault info:
2015-05-19 16:19:08:710 1480 628 WS WARNING: reason: Server was unable to process request. ---> Access is denied
2015-05-19 16:19:08:710 1480 628 WS WARNING: code: Server
2015-05-19 16:19:08:710 1480 628 WS WARNING: detail: <detail/>
2015-05-19 16:19:08:710 1480 628 WS FATAL: OnCallFailure failed with hr=0X80244007
2015-05-19 16:19:08:710 1480 628 WS FATAL: NwsCallWithRetries<Functor>( Functor(_clientId, _targetGroupName, _dnsName, &_result)) failed with hr=0x80244007
2015-05-19 16:19:08:710 1480 628 IdleTmr WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 225) stopped; does use network; is at background priority
2015-05-19 16:19:08:710 1480 628 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244007
2015-05-19 16:19:08:710 1480 628 PT WARNING: PopulateAuthCookies failed: 0x80244007
2015-05-19 16:19:08:710 1480 628 PT WARNING: RefreshCookie failed: 0x80244007
2015-05-19 16:19:08:710 1480 628 PT WARNING: RefreshPTState failed: 0x80244007
2015-05-19 16:19:08:710 1480 628 PT   + SyncUpdates round trips: 0
2015-05-19 16:19:08:710 1480 628 PT WARNING: Sync of Updates: 0x80244007
2015-05-19 16:19:08:710 1480 628 PT WARNING: SyncServerUpdatesInternal failed: 0x80244007
2015-05-19 16:19:08:710 1480 628 Agent   * WARNING: Failed to synchronize, error = 0x80244007
2015-05-19 16:19:08:710 1480 628 Agent   * WARNING: Exit code = 0x80244007
2015-05-19 16:19:08:710 1480 628 Agent *********
2015-05-19 16:19:08:710 1480 628 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 18]
2015-05-19 16:19:08:710 1480 628 Agent *************
2015-05-19 16:19:08:710 1480 628 Agent WARNING: WU client failed Searching for update with error 0x80244007
2015-05-19 16:19:08:710 1480 628 IdleTmr WU operation (CSearchCall::Init ID 18, operation # 224) stopped; does use network; is not at background priority
2015-05-19 16:19:08:710 1480 628 IdleTmr Decremented idle timer priority operation counter to 1
2015-05-19 16:19:08:726 1480 b10 AU >>##  RESUMED  ## AU: Search for updates [CallId = {D023DBFE-C8C5-4E40-B88D-0C6A8304F539} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2015-05-19 16:19:08:726 1480 b10 AU   # WARNING: Search callback failed, result = 0x80244007
2015-05-19 16:19:08:726 1480 b10 AU #########
2015-05-19 16:19:08:726 1480 b10 AU ##  END  ##  AU: Search for updates  [CallId = {D023DBFE-C8C5-4E40-B88D-0C6A8304F539} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2015-05-19 16:19:08:726 1480 b10 AU #############
2015-05-19 16:19:08:726 1480 b10 AU All AU searches complete.
2015-05-19 16:19:08:726 1480 b10 AU   # WARNING: Failed to find updates with error code 80244007
2015-05-19 16:19:08:726 1480 b10 AU AU setting next detection timeout to 2015-05-19 20:19:08
2015-05-19 16:19:08:726 1480 b10 AU Adding timer:
2015-05-19 16:19:08:726 1480 b10 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-05-19 20:19:08, not idle-only, not network-only

Can anyone help me with this error please?

Hi All,

I am experiencing a problem with the Software Update Packages created by ADR. A red cross icon appears for all the software update packages which we are using for update deployment in our environment,In configmgr console under software update packages no update items were present. 

In wsyncmgr.log log, getting message  'Deleted 15 Orphaned content folders in packages(PackageName)', the same meesaage appears for all software update packages. 

Thanks

Pallavi

I want these thing in my custom patching report

1.      Patches are pushed in deployment to different collections. Need data to show the List of servers actually failed and Succeeded or with the Enforcement State.
2.      Server once patched I need a List of patches actually deployed to the server and list of patches not required by the Server.
3.      For collection against patch Bundle I need to pull data to list  how many servers need which patch.

My env. is ConfigMgr 2007 installed on windows server 2008R2, and now, we built two windows server 2012 and 2012R2 servers.

I installed the ConfigMgr client on the windows server 2012, and the status is normal as I check.

Now when I download the security updates, it shows the errors:  The server returned an invalid or unrecognized response

I checked the PatchDownloader.log and it shows the errors as below:

Michael Chiang

I see this error in our environment in the WindowsUpdate.log and I'm trying to determine the cause/fix.  The UpdateId is not always the same but the rest of the warning is:

2015-05-18 16:10:21:196 3188 9c74 COMAPI   - Updates found = 1
2015-05-18 16:10:21:196 3188 9c74 COMAPI ---------
2015-05-18 16:10:21:196 3188 9c74 COMAPI --  END  --  COMAPI: Search [ClientId = CcmExec]
2015-05-18 16:10:21:196 3188 9c74 COMAPI -------------
2015-05-18 16:10:21:220 1116 398 DnldMgr ***********  DnldMgr: Copy update to cache [UpdateId = {9C2B554D-0781-4609-9F80-D056E8505D03}.200]  ***********
2015-05-18 16:10:21:222 1116 398 DnldMgr   * WARNING: Copy update to cache failed with exit code = 0x80070002
2015-05-18 16:10:21:222 3188 93c0 COMAPI WARNING: ISusInternal::CopyUpdateToCache2 failed, hr=80070002

I have seen some articles that suggest deleting the C:\WINDOWS\SOFTWAREDISTRIBUTION folder and letting it rebuild, but this did not work for me.

Any ideas are appreciated.

Thanks,

FP

Hi!

How can we disable Software Update Service from the Configuration Manager and remove the WSUS Server settings from the clients?

Thanks.

So, this is one of the odd ones.

We have setup our SCCM/SCEP to send e-mails when new malware are found in selected collections (Alerts).

During last week, I was surprised to see that our environment was without malware at all (according to the endpoint protection status in the SCCM console) . That's very unlikely to happen, so I started to go about test the SCEP client on a newly installed W81 machine. I did a few test with the following http://www.eicar.org/86-0-Intended-use.html

SCEP instantly found the string as malware, which is what I hoped for. I waited to see if the client would report that back to SCCM as usually, but no. Nothing ever shows up in the console.

Long story short; we went back to see when the last time we ever recieved an e-mail based on a malware-alert in SCCM. The last e-mail was dated march 14th 2015.

So we went back to see what happened on our clients back in march, and during our troubleshooting we went through every software update we released in march, and it appears thatKB3025417 is causing the trouble here. (Note: I also suspect that the update itself is unnecessary given we have SCEP, and the update is related to windows defender. However, the update is seen as required by all W81 clients)

We ended up excluding the mentioned update, and reinstalled a client and voila; SCEP works fine again. The minute we install the update, SCEP on the client is no longer reporting the found malware back to SCCM. Also, uninstalling the update doesn't do anything. The damage is done.

We found a few other reporting similar behaviour. While they don't mention the KB itself, I suspect it's very same issue: https://social.technet.microsoft.com/Forums/en-US/34903763-b423-41b4-8783-b75df94337d0/scep-email-alerts-stopped-working-in-sccm-2012-r2?forum=FCSNext

The environment is SCCM 2012 R2 CU4, Antimalware Client Version: 4.8.204.0, Windows 8.1 x64

Also, note that everything around the SCCM client seems healthy. Deployments are installing and reporting back as usual. Nothing else seems broken, and the SCEP component is also healthy.

This is probably a case for MS Support, but given that I see a few others with the same issue, I also suspect that there's alot more out there with the same problem. They just don't know yet, or haven't figured out why it stopped working.

Any pointers or comments to above is much appreciated.

Thanks in advance.

Martin Bengtsson | www.imab.dk

Hi,

We are running SCCM 2012 SP1 with Software Update Point on Windows 2012. Since the beginning of the week we are unable to synchronize our Software Update and we receive this error message in the Site Status logs:

Error 7001 from WSUS_Control_Manager

Failures were reported on WSUS Server "servername" for WSUS components "WSUSService,".Solution: Verify that the failed WSUS components are installed and running. WSUS

Error 6703 from WSUS_SYNC_Manager

Synchronization failed.
Message: The operation has timed out.
Source: .

Here's the content of the wsyncmgr.log:

SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 4296 (0x10C8). SMS_WSUS_SYNC_MANAGER 2013-02-20 2:34:12 PM 4440 (0x1158)
Log level 2 SMS_WSUS_SYNC_MANAGER 2013-02-20 2:34:17 PM 4296 (0x10C8)
Next scheduled sync is a retry sync at 2013-02-20 2:37:30 PM SMS_WSUS_SYNC_MANAGER 2013-02-20 2:34:17 PM 4296 (0x10C8)
Starting Sync SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:53 PM 4296 (0x10C8)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Read SUPs from SCF for servername SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Found active SUP servername from SCF File. SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=servername SITE=GPP PID=2956 TID=4296 GMTDATE=Wed Feb 20 20:33:55.734 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:55 PM 4296 (0x10C8)
Synchronizing WSUS server servername SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:56 PM 4296 (0x10C8)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=servername SITE=GPP PID=2956 TID=4296 GMTDATE=Wed Feb 20 20:33:56.872 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:56 PM 4296 (0x10C8)
Synchronizing WSUS server servername ... SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:59 PM 4612 (0x1204)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 2013-02-20 3:33:59 PM 4612 (0x1204)
Sync failed: The operation has timed out SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=servername SITE=GPP PID=2956 TID=4296 GMTDATE=Wed Feb 20 20:49:03.157 2013 ISTR0="" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
Setting sync alert to active state on site GPP SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)
Sync time: 0d00h15m07s SMS_WSUS_SYNC_MANAGER 2013-02-20 3:49:03 PM 4296 (0x10C8)

We were able to sync before, but since a couple days we are receiving these errors.

We have a scheduled job on our remote SQL server that re-index the database (http://gallery.technet.microsoft.com/ScriptCenter/6f8cde49-5c52-4abd-9820-f1d270ddea61/) but even after it runs, we still have the problem.

I know that some Windows updates were applied to this server on Sunday night, here's the list:

- KB2803676

- KB2799494

- KB2797052

- KB2795944

- KB2792100

- KB2790655

- KB2789650

- KB2789649

- KB2778344

Maybe it's not related to our problem, but I wanted to give more information than less.

Thank you!