Software Update Deployment - Job error (0x80072f0c) received for assignment

I'm deploying a software update to my test clients but half of them failed with error below;
UpdateStore.log -
Failed to refresh sync message. Error = 0x87d00310.
WUAHandler.log
OnSearchComplete - Failed to end search job. Error = 0x80072f0c.
Scan failed with error = 0x80072f0c.
Updates Deployment
Job error (0x80072f0c) received for assignment ({0F2CA22F-BB7A-4ED8-9794-15AB24B83E09}) action
Do you have any recommendation ?

Since no one has replied to this post, I recommend that you contact Microsoft Support (CSS) directly, they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

Job error (0x80004005) received for assignment

I have a SP2 client that is failing to download the patch content. The client has been repaired, wmi repository rebuilt,software distribution folder rebuilt, and the sccm client has been uninstalled/reboot/installed. The cache folder is not repopulating
after the client was installed again after removal. The logs show the following errors. Any ideas on a solution?
UpdateDeployment:
Job error (0x80004005) received for assignment ({C6F24DB9-54F5-4018-906D-980C0B9A0BFF}) action
UpdatesDeploymentAgent 4/1/2013 3:26:53 PM
4632 (0x1218)
Updates will not be made available UpdatesDeploymentAgent
4/1/2013 3:26:53 PM 4632 (0x1218)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SMS_SUMAgentAssignmentError_AdvanceDownloadJob
AssignmentId = "{C6F24DB9-54F5-4018-906D-980C0B9A0BFF}";
ClientID = "GUID:15be7fe2-c379-4e72-842d-1ca16c820ffa";
DateTime = "20130401192653.419000+000";
insAssignmentId = "{C6F24DB9-54F5-4018-906D-980C0B9A0BFF}";
MachineName = "computer";
ProcessID = 976;
SiteCode = "ABC";
ThreadID = 4632;
Win32ErrorCode = 2147500037;
SDMAgent:
Failed to get SDM CI (Site_87BC43B8-0AA4-4C97-B5DE-F9A5735BCEF3/SUM_ac8b33b5-2df2-4e6a-8d48-105ba0cc3bff) from type store
CTypeStore::GetCI(Site_87BC43B8-0AA4-4C97-B5DE-F9A5735BCEF3/SUM_ac8b33b5-2df2-4e6a-8d48-105ba0cc3bff:1) failed (0x8007000d).
UpdatesHandler:
No updates to process. Cannot continue the job ({5770FB4E-6350-40CA-9633-67D7C53E11A9}).
Failed to initiate job. Error = 0x80004005
UpdatesHandler 4/1/2013 3:26:53 PM
4008 (0x0FA8)

Hello This error Win32ErrorCode = 2147500037 completelly shows WMI error,
whenever you recive this error, cleint will not download any software/updated,
for resolve this issue you will have to remove SMSClientAgent from Client machine, then reboot the machine, then again install the sms client agent,
and then iniate the machine policy and run the update or software, your application will isntall now,
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please mark as helpful/answer if this resolved your issue

How to troubleshoot Software Update Deployment Errors

Hi Guys,
Could you guys please help me to troubleshoot 'Software Update Deployment Errors'. I have been trying to troubleshoot the below mentioned errors but I am not sure what step should I take for each different errors.
Could you guys please help me stating what kind of troubleshooting steps should we take for such update deployment errors.
Many Thanks,
Chandan

You would have to examine client-side logs like UpdatesDeployment.log, U*.log in general, ScanAgent.log, WUAHandler.log, WindowsUpdate.log and CI*.log.
Torsten Meringer | http://www.mssccmfaq.de

How to calculate the compliance for an software update deployment

Hi All,
I am trying to find as how do we calculate the compliance for an software update deployment.
Scenario, We have about 4000 machine in the domain. but we have some stale records in the domain which is about 1200. The AD cleanup for the stale records is planned for sometime in March.
So total number of machines in a collection (including the stale machines) are 5200.
The current compliance of that deployment shows the following status:
Complaint : 1156
In Progress : 1724
Error : 38
Unknown : 2462
And in the unknown, we have :
Client check failed/Active: 2
Client check failed/Inactive: 6
Client check passed/Active: 732
Client check passed/Inactive: 1722
Can you please suggest in understanding the formula that should be followed to get the compliance.

Your Compliancy, should be based solely off of the number of computers within CM12.
There are no “if”, “and” or “but” able it. This is the only way to truly and reliably provide numbers to management.
Again it should be very simple calculation:
(Total outstanding Security SU, Total outstanding
Critical SU, Total outstand Service packs, Total outstand Update Rollups, Total outstand Updates, Total outstand Definition Updates, Total outstand tools, Total outstand Feature packs) Vs Total applied SU (all Classifications)
Or
Total # of 100% patched PCs vs Total # of PCs as seen by CM12.
If you use any other calculation then you MUST include a disclaimer that you are filtering out computers because they might be invalid. Or you MUST define exactly how you are calculating the number. Therefore any compliancy rate that your calculate maybe
invalid too or at least it will change once you clean up AD.
I will never hide low compliancy numbers to management, I will always show it to them.
In many case I will ask to give a presentation to Management to explain why the numbers are so low.
Provide them with a list of action items that need to be done in order to bring up the number to more reasonable level. I also set their expectation on what a reasonable level is.
100% is unachievable; there is no exception to this!
95-99% Very excellent but expect to spend lots of $$$s to obtain these percentages.
90-95% is really, really, good; expect to spend $$s in this range.
85-89% is good; expect to set strict procedures
81-84 is ok but you could do better
Below 80% is bad
In your case, I would start by saying AD is dirty and need to be clean up, this has been schedule for March 2015. I would follow up this to say, in order to keep AD clean the follow procedures need to be define / updated / followed. You should also define
exactly what you are doing to ensure that all computers are management by CM12.
IMO these is no simple answer of this.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

HT4623 I Can't able to download IOS 7. I n my software update it is giving an error " Unable to check for updates. An error occured while checking for software update". What can be done for this error?

I Can't able to download IOS 7. I n my software update it is giving an error " Unable to check for updates. An error occured while checking for software update". What can be done for this error?

Me too having the same thing what's the solution for this how can I update

HT4623 my iphone software update states :an error occurred while checking for a software update?

My software update states "an error occurred while checking for the update?

Are you doing on the device under Settings or in iTunes? Try updating through iTunes if you can.

Windows Update Agent rebooting systems after Software Update deployment

I have a software update deployment that is configured to install software updates on a collection of servers at 4:00 AM with a suppressed reboot. The updates get deployed and no reboot occurs as expected. Then ~8 hours later WUA starts up and the
servers get rebooted.
There is a maintenance window applied to the collection from 4:00 AM to 6:00 AM to allow the updates to install.
I've read a few forum and blog posts on this issue and have implemented some settings via GPO, but the reboots are still occurring. The settings that were applied are referenced in the link below.
https://support.microsoft.com/kb/2476479?wa=wsignin1.0
Here is a snippet from the WindowsUpdate.log:
2014-10-22 12:00:26:153 1428 8a88 AU Received AU Resume timeout
2014-10-22 12:00:26:153 1428 8a88 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
2014-10-22 12:00:26:153 1428 8a88 AU Can not perform non-interactive scan if AU is interactive-only
2014-10-22 12:02:08:512 1428 8a88 AU AU received policy change subscription event
2014-10-22 12:16:43:463 1428 8a88 AU ########### AU: Uninitializing Automatic Updates ###########
2014-10-22 12:16:43:479 1428 8a88 WuTask Uninit WU Task Manager
2014-10-22 12:16:43:697 1428 8a88 Service *********
2014-10-22 12:16:43:697 1428 8a88 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-10-22 12:16:43:697 1428 8a88 Service *************
2014-10-22 12:19:29:728 1428 e584 Misc =========== Logging initialized (build: 7.8.9200.16604, tz: -0400) ===========
2014-10-22 12:19:29:728 1428 e584 Misc   = Process: C:\WINDOWS\system32\svchost.exe
2014-10-22 12:19:29:728 1428 e584 Misc   = Module: c:\windows\system32\wuaueng.dll
2014-10-22 12:19:29:728 1428 e584 Service *************
2014-10-22 12:19:29:728 1428 e584 Service ** START ** Service: Service startup
2014-10-22 12:19:29:728 1428 e584 Service *********
2014-10-22 12:19:29:744 1428 e584 Agent   * WU client version 7.8.9200.16604
2014-10-22 12:19:29:744 1428 e584 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
2014-10-22 12:19:29:744 1428 e584 Agent   * Access type: No proxy
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2014-10-22 12:19:29:744 1428 e584 Agent   * Network state: Connected
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2014-10-22 12:19:29:791 1428 e584 Agent *********** Agent: Initializing global settings cache ***********
2014-10-22 12:19:29:791 1428 e584 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS server:
http://Internal-WSUS.Domain:8530
2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS status server:
http://Internal-WSUS.Domain:8530
2014-10-22 12:19:29:791 1428 e584 Agent   * Target group: (Unassigned Computers)
2014-10-22 12:19:29:791 1428 e584 Agent   * Windows Update access disabled: No
2014-10-22 12:19:29:791 1428 e584 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2014-10-22 12:19:29:806 1428 e584 WuTask WuTaskManager delay initialize completed successfully..
2014-10-22 12:19:29:822 1428 e584 Report CWERReporter::Init succeeded
2014-10-22 12:19:29:822 1428 e584 Agent *********** Agent: Initializing Windows Update Agent ***********
2014-10-22 12:19:29:822 1428 e584 DnldMgr Download manager restoring 0 downloads
2014-10-22 12:19:29:838 1428 e584 AU ########### AU: Initializing Automatic Updates ###########
2014-10-22 12:19:29:838 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
2014-10-22 12:19:29:838 1428 e584 AU AIR Mode is disabled
2014-10-22 12:19:29:838 1428 e584 AU   # Policy Driven Provider:
http://Internal-WSUS.Domain:8530
2014-10-22 12:19:29:838 1428 e584 AU   # Detection frequency: 22
2014-10-22 12:19:29:838 1428 e584 AU   # Approval type: Disabled (User preference)
2014-10-22 12:19:29:838 1428 e584 AU   # Auto-install minor updates: No (User preference)
2014-10-22 12:19:29:838 1428 e584 AU   # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Pre-install notify)
2014-10-22 12:19:29:838 1428 e584 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
2014-10-22 12:19:29:838 1428 e584 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2014-10-22 12:19:29:853 1428 e584 AU AU finished delayed initialization
2014-10-22 12:19:29:884 1428 e584 AU #############
2014-10-22 12:19:29:884 1428 e584 AU ## START ## AU: Search for updates
2014-10-22 12:19:29:884 1428 e584 AU #########
2014-10-22 12:19:29:884 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
2014-10-22 12:19:30:416 1428 e584 Report *********** Report: Initializing static reporting data ***********
2014-10-22 12:19:30:416 1428 e584 Report   * OS Version = 6.2.9200.0.0.197008
2014-10-22 12:19:30:416 1428 e584 Report   * OS Product Type = 0x00000008
2014-10-22 12:19:30:416 1428 e584 Report   * Computer Brand = HP
2014-10-22 12:19:30:416 1428 e584 Report   * Computer Model = ProLiant BL460c Gen8
2014-10-22 12:19:30:416 1428 e584 Report   * Platform Role = 1
2014-10-22 12:19:30:416 1428 e584 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Revision = I31
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Name = Default System BIOS
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Release Date = 2014-02-10T00:00:00
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Sku Number = 641016-B21
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Vendor = HP
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Family = ProLiant
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Major Release = 255
2014-10-22 12:19:30:431 1428 e584 Report   * Bios Minor Release = 255
2014-10-22 12:19:30:431 1428 e584 Report   * Locale ID = 1033
2014-10-22 12:19:30:431 1428 e584 AU <<## SUBMITTED ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:431 1428 dae0 Agent *************
2014-10-22 12:19:30:431 1428 dae0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:30:431 1428 dae0 Agent *********
2014-10-22 12:19:30:431 1428 dae0 Agent   * Online = No; Ignore download priority = No
2014-10-22 12:19:30:431 1428 dae0 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-10-22 12:19:30:431 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-10-22 12:19:30:431 1428 dae0 Agent   * Search Scope = {Machine & All Users}
2014-10-22 12:19:30:431 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
2014-10-22 12:19:30:494 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
2014-10-22 12:19:30:494 1428 dae0 Agent *********
2014-10-22 12:19:30:494 1428 dae0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:30:494 1428 dae0 Agent *************
2014-10-22 12:19:30:509 1428 d158 AU >>## RESUMED ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:509 1428 d158 AU   # 0 updates detected
2014-10-22 12:19:30:509 1428 d158 AU #########
2014-10-22 12:19:30:509 1428 d158 AU ## END ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:509 1428 d158 AU #############
2014-10-22 12:19:30:509 1428 d158 AU All AU searches complete.
2014-10-22 12:19:30:525 1428 e584 AU #############
2014-10-22 12:19:30:525 1428 e584 AU ## START ## AU: Search for updates
2014-10-22 12:19:30:525 1428 e584 AU #########
2014-10-22 12:19:30:525 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
2014-10-22 12:19:30:525 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
2014-10-22 12:19:30:525 1428 e584 AU <<## SUBMITTED ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:30:525 1428 dae0 Agent *************
2014-10-22 12:19:30:525 1428 dae0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:30:525 1428 dae0 Agent *********
2014-10-22 12:19:30:525 1428 dae0 Agent   * Online = Yes; Ignore download priority = No
2014-10-22 12:19:30:525 1428 dae0 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-10-22 12:19:30:525 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-10-22 12:19:30:525 1428 dae0 Agent   * Search Scope = {Machine & All Users}
2014-10-22 12:19:30:525 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
2014-10-22 12:19:30:525 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2014-10-22 12:19:30:541 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:541 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:556 1428 dae0 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab"
2014-10-22 12:19:30:588 1428 dae0 Agent Checking for updated auth cab for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 at
http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab
2014-10-22 12:19:30:588 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
2014-10-22 12:19:30:603 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:603 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:775 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
2014-10-22 12:19:30:791 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:791 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:791 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
2014-10-22 12:19:30:806 1428 dae0 Misc Microsoft signed: Yes
2014-10-22 12:19:30:806 1428 dae0 Misc Infrastructure signed: Yes
2014-10-22 12:19:30:822 1428 dae0 EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-10-22 12:19:30:978 1428 dae0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-10-22 12:19:30:978 1428 dae0 PT   + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL =
https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
2014-10-22 12:19:31:025 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
2014-10-22 12:19:31:025 1428 dae0 Agent *********
2014-10-22 12:19:31:025 1428 dae0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-10-22 12:19:31:025 1428 dae0 Agent *************
2014-10-22 12:19:31:025 1428 d158 AU >>## RESUMED ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:31:025 1428 d158 AU   # 0 updates detected
2014-10-22 12:19:31:025 1428 d158 AU #########
2014-10-22 12:19:31:025 1428 d158 AU ## END ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-10-22 12:19:31:025 1428 d158 AU #############
2014-10-22 12:19:31:025 1428 d158 AU All AU searches complete.
2014-10-22 12:19:31:025 1428 d158 AU AU setting next detection timeout to 2014-10-23 14:19:28
2014-10-22 12:19:36:025 1428 e214 Report REPORT EVENT: {E04012FD-8FFD-4259-96D5-A5A34127F0A0} 2014-10-22 12:19:31:025-0400 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
Synchronization Windows Update Client successfully detected 0 updates.
2014-10-22 12:19:36:025 1428 e214 Report CWERReporter finishing event handling. (00000000)
2014-10-22 12:29:29:914 1428 e584 AU AU invoking RebootSystem (OnRebootNow)
2014-10-22 12:29:30:055 1428 e584 AU Allowing auto firmware installs at next shutdown
2014-10-22 12:29:30:102 1428 e584 Misc WARNING: SUS Client is rebooting system.
2014-10-22 12:29:30:102 1428 e584 AU AU invoking RebootSystem (OnRebootRetry)
2014-10-22 12:29:30:367 1428 e584 Shutdwn Checking to see whether install at shutdown is appropriate
2014-10-22 12:29:30:367 1428 e584 Shutdwn user declined update at shutdown
2014-10-22 12:29:30:367 1428 e584 AU AU initiates service shutdown
2014-10-22 12:29:30:367 1428 e584 AU ########### AU: Uninitializing Automatic Updates ###########
2014-10-22 12:29:30:399 1428 e584 WuTask Uninit WU Task Manager
2014-10-22 12:29:30:445 1428 e584 Agent Sending shutdown notification to client
2014-10-22 12:29:30:445 5788 8084 COMAPI WARNING: Received service shutdown/self-update notification.
2014-10-22 12:29:30:461 1428 e584 Report CWERReporter finishing event handling. (00000000)
2014-10-22 12:29:30:539 1428 e584 Service *********
2014-10-22 12:29:30:539 1428 e584 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-10-22 12:29:30:539 1428 e584 Service *************
Any assistance is appreciated.
-Tim

Hi,
Any update?
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Ios 7 software update reports an error

Trying to install the iOS 7 on my iphone 4 and I receive this error
"Software Update Failed
An error occurred downloading iOS 7.0"

At the "HELLO" screen. "Slide to open >
So far I really like it. Very bright icons and some new easy ways to access things
But then again, I have been using it for all of 1 minute lol

Software Updates Deployment Shows "Unknown" Computers, Previously Had Compliant

I'm not sure what is going on, but can anyone tell me why a software updates deployment would all of a sudden show all computers as having an "Unknown" status? Previously, most computers were "Compliant" and there were a couple
with errors. When I went to check it (about a week after the original deployment), I found it had reset all to "Unknown" status. This was yesterday, and now today there are a couple computers showing "Compliant" but most are
still "Unknown". It is not set up with ADR, so it's not (at least I don't think) looking for newer updates. Any ideas?

A re-evaluation of the software update deployment, which you configure in the client settings, can cause this behavior. That's why you should always use the reports for compliance checks and not the deployments node.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Software Updates Deployment Evaluation.

Hi,
I would like to get some clarification around the Software Updates Deployment Eval. cycle. (SCCM R2 CU3)
Example scenario:
I have a Software Update Group that contains 200 updates. This SUG includes updates that are prerequisites for other updates in the same SUG. So, when scanning occurs. Only one of these updates are at that particular time considered applicable.
The software update deployment deadline is reached. The update is installed, as expected. The then agent reports compliance against the update deployment.
Then comes the Software Update Scan schedule, when a new scan is made against the SUP more updates are now detected as required because of the previously installed update - from the same SUG which are deployed.
This leaves me in a situation where the agent is compliant against the Software Update deployment and non-compliant in regards to the actual Software Update Group.
I can of course just hit the schedule for Software Update Deployment Evaluation manually on the agent or simply do something (adding an update or whatever) that modifies the actual software updates deployment policy. This would in turn cause a new evaluation
to occur at the client.
Bottom line. Is my conclusion correct or have i missed something here?
If i'm correct, a good thing would be to add scheduling options available for the actual "software update deployment evaluation".
That would really come in handy in situations like above scenario.
Br,
Chris

The next scheduled scan cycle will pick up the newly applicable but non-compliant updates in the deployment.
However, note that update compliance at the client level is done against the entire update catalog as this is actually done by the Windows Update Agent (WUA) which knows nothing about ConfigMgr. Thus, the fact that an update is in a deployment or not is
completely irrelevant as far as compliance and compliance reporting goes (which is part of the reason why compliance reporting in ConfigMgr is tricky).
Updating the policy of an update deployment will kick off a scan cycle (just like creating a new deployment will) on the clients which is why you are probably seeing this behavior as addressing the scenario.
Jason | http://blog.configmgrftw.com | @jasonsandys
Thanks Jason,
What you are describing exactly matches the point I’m trying to make here. There is no correlation what so ever between update scans and actual software update deployments. The logic just isn't there. Which is a logic that is lacking
– in my opinion.
I really do think there is room for improvement here.
Case:
A customer wants to minimize the spread of reboots (a maint. window overnight should be sufficient for the agent to get the server fully up to date). The admin – who also wants to minimize effort in regards to worrying about MS bundling\prereq
requirements – simply wants it all to be taken care of by the updates deployment agent.
Example:
Software update deployment contains required updates as well as updates that will not be detected as required - until the deployment has been run – and a new update scan cycle has taken place.
The server reboots and updates deployment agent says all is fine – with regards to the deployment in it's current state, of course.
But it's not.
The server then issues a new scan (maybe 4 hours later and way behind the end of the maint. window) according to the software updates scan schedule, and suddenly 10 more updates are applicable, but still within the same deployment.
What happens? Nothing, sadly. Next maint. window? Nothing.
Not even a (client agent set – and scheduled) software update deployment re-eval takes care of this since – according to my findings – the deployment will never really be evaluated against again without administrative intervention.
Suggestion:
Whenever a software update deployment has been run, succeeded and passed the "after reboot" detectjob. Initiate a new evaluation of this deployment in full – of course including a pre-eval software updates scan. Just add
a few steps to the logic of updates deployment.
Evaluate.
Apply.
Initiate a new scan.
Re-Evaluate.
Apply again (if needed)
Reboot
Initiate a new scan.
Re-evaluate
Isn’t this the way WAUA has always worked? Why shouldn’t this method be adopted here as well? Why should ConfigMgr not honour the procedure?
Result:
Administrative relieve. Since I know that a software update deployment will always do the job, in full. No need for manual triggers or policy modifications.
Caveats:
I do realize the fact that – if this would be the scenario - the admin sometimes will not be aware of what might happen during the nightly maint. window since he cannot solely rely on compliance data.
Anyways:
This should at least be a deployment option in future releases.
"Force rescan and deployment re-evaluation after first run." Simple.
Would make life easier and keep the spread of reboots concentrated to one night and to a minimum. (Given the appropriate length of maint. windows of course)
Consider things like KB2919355 and how WUAU agent handles that against Windows Update.
Br,
Chris

Software update failed An error occured downloading iOS 8.0

I still trying to update my iPhone5S and iPhone4S but to no avail
What to do after receiving error messages:
A. via mobile:
"Software update failed
An error occurred downloading iOS 8.0"
B. via iTunes...won't even proceed... saying my connection Timed out
"There was a problem downloading the software for the iPhone*** 's
The network connection was reset.
Make sure your network settings are correct
and your network connection is active, or try again later."
Note:
- My connection was working perfectly well during those numerous attempts (probably more than 50 times).
- iPad was updated after 7 attempts
Question:
How can I update the 2 iPhone?
How can I proceed?

Same issue here with iPad Mini. What should I do??

Software Update Failed An error occurred downloading iOS 7.0

I can't seem to update my iPad mini. Looks like the release of iOS 7 just came out and it's not letting me update. I keep getting a message "Software Update Failed An error occurred downloading iOS 7.0".
Can anyone from apple tell me why I'm getting this message? And how to resolve it.
Thanks for any help.

The entire planet Earth is trying to download the same thing at the same time.
Give it some time.

Software Update Failed: An error occurred whilst downloading iOS 7.0."

Tried three times and three HOURS later, ON eACH Occassion!!:
"Software Update Failed: An Error Occurred whilst downloading iOS 7"
I am in South Africa

Hey there,
As Sneaky_Mouse suggested the best option is atm iTunes. Servers are probably going crayze.
If you cannot do it like that as well you can look for an iOS 7 ipsw (image file) and then, hold down either Option or Shift (on a Mac or Windows PC) and click Update; this will allow you to select the ipsw image.
http://www.techradar.com/news/software/applications/ios-7-is-here-and-ready-for- download-1182104
Hope it helps,

Software Update Failed An error occurred downloading iOS 8.1.3

I can not get the phone to update the OS? I tried different wifi points, and still no luck. I tried this at least 6 times with the same result. It looks to download, and then says it is 'preparing' for a while, and then it pukes out the message "Software Update Failed An error occurred downloading iOS 8.1.3". Anyone know how to resolve this? Thanks!

I've made a blog post on this error "
SOFTWARE UPDATE FAILED AN ERROR OCCURRED WHILE DOWNLOADING IOS 8.X.X
I hope this might help for those who are facing problem to update their iPhone or iPad. Here is the link https://shrishailtalukar.wordpress.com/2015/01/20/software-update-failed-an-erro r-occurred-while-downloading-ios-8-x-x-solution/

Change Software Updates deployment priority

Hi
We use SCCM 2012 R2 CU2.
whenever a new client is being installed and registered it gets its policies and deployments.
our problem is that there are many software updates that being deployed and it takes a very long time until they finish their installation.
while what is more important for us is the clients to get software deployments
before the software updates.
I know I can change packages priority but as I understand - it only changes the priority between the software packages.
is there any way to make the software deployments to be installed before the software updates for new clients?
even if there's no build-in solution, I'd be happy to get a friendly workaround.
I thought about auto-adding the clients to a software update deployment collection only after all the packages are being deployed, but maybe some of you can come up with something better
thanks!

You can't prioritize in policy for a client. The first policy that arrives is the first that's being served..
If you're talking about the first thing after the OS deployment, then I would try to update my clients completely during the deployment already. That would solve your problem already. In that same scenario, you could also think about installing
computer or user targetted applications during the task sequence. For examples about both scenario's see:
Computer-targeted:
http://www.petervanderwoude.nl/post/install-computer-targeted-application-during-os-deployment-via-powershell-and-configmgr-2012/;
User-targeted:
http://www.petervanderwoude.nl/post/install-user-targeted-applications-during-os-deployment-via-powershell-and-configmgr-2012/.
If you're not talking about an OS deployment, your only option is indeed to add the clients later to the software update collection(s). In that case you could also try to automate it via PowerShell by using the
Add-CMDeviceCollectionDirectMembershipRule.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Software Update Deployment - Job error (0x80072f0c) received for assignment

Similar Messages

Maybe you are looking for