Providing updates to software and maintaining managed resources is a reality of networked, distributed computing. An effective software update management process is necessary to maintain operational efficiency, overcome security issues, and maintain the stability of the network infrastructure. However, because of the changing nature of technology and the continual appearance of new security threats, the task of effective software update management can be challenging.
- Troubleshooting Software Updates Client Issues Sccm 2012
- Pc Troubleshooting Software
- Sccm 2012 Troubleshooting Software Updates Windows 7
- Sccm 2012 Software Updates Process
- Sccm 2012 Troubleshooting Software Updates Mac
- Sccm 2012 Troubleshooting Software Updates Windows 10
The Microsoft System Center Configuration Manager 2007 software updates feature provides a set of tools and resources that can help manage the complex task of tracking and applying software updates to client computers in the enterprise. Click any link in the following section for overview information about software updates.
Software Updates Providing updates to software and maintaining managed resources is a reality of networked, distributed computing. An effective software update management process is necessary to maintain operational efficiency, overcome security issues, and maintain the stability of the network infrastructure.
For more details on how to do software updates using configuration manager please check this link http://technet.microsoft.com/en-us/library/bb680701.aspx
Troubleshooting
Server side
The component which takes care of software update is software update point (SUP). So first we need to check if the software update point is installed correctly. If installed correctly you will have the entries in the log SUPSetup.log as shown below
SUPSetup.log
<04-27-2010 23:51:04>
<04-27-2010 23:51:04> SMSWSUS Setup Started....
<04-27-2010 23:51:04> Parameters: C:PROGRA~1MICROS~1bini386ROLESE~1.EXE /install /siteserver:SCCM SMSWSUS
<04-27-2010 23:51:04> Installing Pre Reqs for SMSWSUS
<04-27-2010 23:51:04> Installing Pre Reqs for Role SMSWSUS
<04-27-2010 23:51:04> Found 0 Pre Reqs for Role SMSWSUS
<04-27-2010 23:51:04> Completed Installion of Pre Reqs for Role SMSWSUS
<04-27-2010 23:51:04> Installing the SMSWSUS
<04-27-2010 23:51:04> Correct and supported WSUS Server version is installed.
<04-27-2010 23:51:04> Invoking process 'C:WINDOWSMicrosoft.NETFrameworkv2.0.50727RegAsm.exe' 'C:Program FilesMicrosoft Configuration Managerbini386wsusmsp.dll'
<04-27-2010 23:51:30> Registered DLL C:Program FilesMicrosoft Configuration Managerbini386wsusmsp.dll
<04-27-2010 23:51:30> Installation was successful.
Once installed you need to make sure that it is configured the logs which can be of help are WCM.log and WSUSctrl.log. If you find errors then make sure that the WSUS is working well.For the same you can check the following link http://technet.microsoft.com/en-us/library/dd939799(WS.10).aspx
The logs if configured correctly should look like this.
WSUSctrl.log
SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 3432 (0xD68).SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:33 PM3216 (0x0C90)
This is a WSUS Role as WSUS registry key exists.SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:33 PM3432 (0x0D68)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:33 PM3432 (0x0D68)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:33 PM3432 (0x0D68)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=2.0.0.0, Major Version = 0x20000, Minor Version = 0x0SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:33 PM3432 (0x0D68)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:33 PM3432 (0x0D68)
Successfully connected to local WSUS serverSMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:33 PM3432 (0x0D68)
Troubleshooting Software Updates Client Issues Sccm 2012
Local WSUS Server Proxy settings are correctly configured as Proxy Nameand Proxy Port 80SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:35 PM3432 (0x0D68)
Waiting for changes for 0 minutesSMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:35 PM3432 (0x0D68)
Timed Out...SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:35 PM3432 (0x0D68)
…………………..
…………………..
…………………..
SMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:35 PM3432 (0x0D68)
There are no unhealthy WSUS Server components on WSUS Server SCCMSMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:35 PM3432 (0x0D68)
Successfully checked database connection on WSUS server SCCMSMS_WSUS_CONTROL_MANAGER4/27/2010 11:51:38 PM3432 (0x0D68)
WCM.log
This SCCM system is the Top Site where WSUS Server is configured to Sync from Microsoft Update (WU/MU) OR do not Sync.SMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:50:36 PM5992 (0x1768)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111SMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:50:37 PM5992 (0x1768)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001SMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:50:37 PM5992 (0x1768)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=2.0.0.0, Major Version = 0x20000, Minor Version = 0x0SMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:50:37 PM5992 (0x1768)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)SMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:50:37 PM5992 (0x1768)
Successfully connected to server: SCCM.MYLAB.IN, port: 80, useSSL: FalseSMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:51:23 PM5992 (0x1768)
Verify Upstream Server settings on the Active WSUS ServerSMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:51:23 PM5992 (0x1768)
Successfully configured WSUS Server settings and Upstream Server to Microsoft UpdateSMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:51:34 PM5992 (0x1768)
Successfully connected to server: SCCM.MYLAB.IN, port: 80, useSSL: FalseSMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:51:39 PM5992 (0x1768)
……………………….
……………………….
STATMSG: ID=6617 SEV=E LEV=M SOURCE='SMS Server' COMP='SMS_WSUS_CONFIGURATION_MANAGER' SYS=SCCM SITE=LAB PID=3040 TID=5992 GMTDATE=Tue Apr 27 18:23:49.259 2010 ISTR0=' ISTR1=' ISTR2=' ISTR3=' ISTR4=' ISTR5=' ISTR6=' ISTR7=' ISTR8=' ISTR9=' NUMATTRS=0SMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:53:49 PM5992 (0x1768)
completed unpublishing previous clientsSMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:53:49 PM5992 (0x1768)
completed checking for client deploymentSMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:53:49 PM5992 (0x1768)
Successfully inserted the WSUS Enterprise Update Source object {A36F27F1-F657-437E-9EBF-8531FE189A6B}SMS_WSUS_CONFIGURATION_MANAGER4/27/2010 11:54:03 PM5992 (0x1768)
Once you confirm that the WSUS configuration is over then you need to make sure that the SUP is able to synchronize with the Microsoft update catalogue site and the same can be checked in this log.
WSUSsyncmgr.log
Performing sync on local requestSMS_WSUS_SYNC_MANAGER4/27/2010 11:59:54 PM6112 (0x17E0)
STATMSG: ID=6701 SEV=I LEV=M SOURCE='SMS Server' COMP='SMS_WSUS_SYNC_MANAGER' SYS=SCCM SITE=LAB PID=3040 TID=6112 GMTDATE=Tue Apr 27 18:29:54.530 2010 ISTR0=' ISTR1=' ISTR2=' ISTR3=' ISTR4=' ISTR5=' ISTR6=' ISTR7=' ISTR8=' ISTR9=' NUMATTRS=0SMS_WSUS_SYNC_MANAGER4/27/2010 11:59:54 PM6112 (0x17E0)
STATMSG: ID=6704 SEV=I LEV=M SOURCE='SMS Server' COMP='SMS_WSUS_SYNC_MANAGER' SYS=SCCM SITE=LAB PID=3040 TID=6112 GMTDATE=Tue Apr 27 18:30:18.547 2010 ISTR0=' ISTR1=' ISTR2=' ISTR3=' ISTR4=' ISTR5=' ISTR6=' ISTR7=' ISTR8=' ISTR9=' NUMATTRS=0SMS_WSUS_SYNC_MANAGER4/28/2010 12:00:18 AM6112 (0x17E0)
Synchronizing WSUS server SCCMSMS_WSUS_SYNC_MANAGER4/28/2010 12:00:18 AM6112 (0x17E0)
Synchronizing WSUS server sccm.mylab.in ...SMS_WSUS_SYNC_MANAGER4/28/2010 12:02:16 AM5220 (0x1464)
sync: Starting WSUS synchronizationSMS_WSUS_SYNC_MANAGER4/28/2010 12:02:16 AM5220 (0x1464)
sync: WSUS synchronizing categoriesSMS_WSUS_SYNC_MANAGER4/28/2010 12:02:44 AM5220 (0x1464)
……………..
,……………………
Synchronizing update e6d5e961-e5c4-4816-b414-648feba450b7SMS_WSUS_SYNC_MANAGER28/04/2010 5:53:10 PM4380 (0x111C)
Synchronizing update 35a0b603-61ce-4f1e-b2dd-3cc36cdf8b31SMS_WSUS_SYNC_MANAGER28/04/2010 5:53:11 PM4380 (0x111C)
Synchronizing update 333bf753-7abb-4fce-a15f-a1862ecf838bSMS_WSUS_SYNC_MANAGER28/04/2010 5:53:11 PM4380 (0x111C)
Synchronizing update 136df562-d188-4e79-8879-8d8082c97614:Definition Update for Windows Defender - KB915597 (Definition 1.81.438.0)SMS_WSUS_SYNC_MANAGER28/04/2010 5:53:12 PM4380 (0x111C)
Done synchronizing SMS with WSUS Server sccmcen.scs.inSMS_WSUS_SYNC_MANAGER28/04/2010 5:53:13 PM4380 (0x111C)
STATMSG: ID=6702 SEV=I LEV=M SOURCE='SMS Server' COMP='SMS_WSUS_SYNC_MANAGER' SYS=SCCMCEN SITE=CEN PID=1880 TID=3256 GMTDATE=Wed Apr 28 12:23:13.745 2010 ISTR0=' ISTR1=' ISTR2=' ISTR3=' ISTR4=' ISTR5=' ISTR6=' ISTR7=' ISTR8=' ISTR9=' NUMATTRS=0SMS_WSUS_SYNC_MANAGER28/04/2010 5:53:13 PM3256 (0x0CB8)
Updated 3072 items in SMS database, new update source content version is 2SMS_WSUS_SYNC_MANAGER28/04/2010 5:53:13 PM3256 (0x0CB8)
Once the synchronization is successfully done, updates will be available in the update repository. You can then go ahead and create the deployment template and schedule for installation. On more details on how to please check the following link.
http://blogs.technet.com/configurationmgr/archive/2009/08/17/guide-to-software-updates-deployment-in-configuration-manager-2007.aspx
Once done if you check the status messages for your created update packages you will find the following status messages.
SeverityTypeSite codeDate / TimeSystemComponentMessage IDDescription
InformationMilestoneCEN28/04/2010 4:21:28 PMSCCMCENSMS_DISTRIBUTION_MANAGER2301SMS Distribution Manager successfully processed package 'TEST' (package ID = CEN00003).
InformationMilestoneCEN28/04/2010 4:21:27 PMSCCMCENSMS_DISTRIBUTION_MANAGER2300SMS Distribution Manager is beginning to process package 'TEST' (package ID = CEN00003).
InformationMilestoneCEN28/04/2010 4:21:21 PMSCCMCENSMS_DISTRIBUTION_MANAGER2330SMS Distribution Manager successfully distributed package 'CEN00003' to distribution point '['Display=SCCMCEN']MSWNET:['SMS_SITE=CEN']SCCMCEN'.
Info
Distribution Manager is beginning to process package 'TEST' (package ID = CEN00003).
InformationAuditCEN28/04/2010 4:20:59 PMSCCMCENMicrosoft.ConfigurationManagement.dll30068User 'SCSAdministrator' updated a package named ' TEST' (CEN00003) to the site distribution points.
InformationMilestoneCEN28/04/2010 4:12:14 PMSCCMCENSMS_DISTRIBUTION_MANAGER2300SMS Distribution Manager is beginning to process package 'TEST' (package ID = CEN00003).
InformationMilestoneCEN28/04/2010 4:12:08 PMSCCMCENSMS_DISTRIBUTION_MANAGER2301SMS Distribution Manager successfully processed package 'TEST' (package ID = CEN00003).
InformationMilestoneCEN28/04/2010 4:12:06 PMSCCMCENSMS_DISTRIBUTION_MANAGER2330SMS Distribution Manager successfully distributed package 'CEN00003' to distribution point
Distribution Manager is beginning to process package 'TEST' (package ID = CEN00003).
InformationAuditCEN28/04/2010 4:11:21 PMSCCMCENMicrosoft.ConfigurationManagement.dll30125User 'SCSAdministrator' added new distribution points to a package named ' TEST' (CEN00003).
InformationAuditCEN28/04/2010 4:11:20 PMSCCMCENMicrosoft.ConfigurationManagement.dll30000User 'SCSAdministrator' created a package named ' TEST' (CEN00003).
Once these steps are done then the rest of the things happens in the client.
Client Side
In the client side first thing we need to check is the locationservices.log to make sure that the correct SUP point is detected by the client, else make sure that the client is correctly reporting to the SCCM server and that the software update is enabled. Make sure that the server name and the port is specified correctly.
Locationservices.log
Calling back with the following WSUS locations LocationServices 4/29/2010 10:39:40 AM 2844 (0x0B1C)
WSUS Path='https://SCCMCEN.SCS.IN:443', Server='SCCMCEN', Version='2' LocationServices 4/29/2010 10:39:40 AM 2844 (0x0B1C)
Calling back with locations for WSUS request {10066528-1C1B-4A0C-958B-F29ACBEDBBDF} LocationServices 4/29/2010 10:41:31 AM 2844 (0x0B1C)
Calling back with the following distribution points LocationServices 4/29/2010 11:27:23 AM 2552 (0x09F8)
Distribution Point='SCCMCEN.SCS.INSMSPKGC$CEN000034ea80bd5-c8ac-4f98-be8a-1c18f24a34e4', Locality='LOCAL', DPType='SERVER', Version='6487', Capabilities='<Capabilities SchemaVersion='1.0'><Property Name='SSL' Version='1'/></Capabilities>', Signature=' LocationServices 4/29/2010 11:27:23 AM 2552 (0x09F8)
Now once the policy agent triggers the scan cycle the windows update agent in the client will contact the WSUS server which in our case is also the SUP point. Once the scan is successfully completed this information is send as state message to the SCCM server. This can be checked in windowsupadte.log or you can check WUAhandler.log under SCCM client log.
WUAHandler.log
Async searching of updates using WUAgent started. WUAHandler 4/29/2010 10:42:20 AM 3488 (0x0DA0)
Async searching completed. WUAHandler 4/29/2010 11:24:21 AM 1496 (0x05D8)
Successfully completed scan. WUAHandler 4/29/2010 11:24:25 AM 2752 (0x0AC0)
Its a WSUS Update Source type ({D4F72DDB-F6C4-4B05-835F-A8C23098857A}), adding it. WUAHandler 4/29/2010 11:25:24 AM 2752 (0x0AC0)
Existing WUA Managed server was already set (https://SCCMCEN.SCS.IN:443), skipping Group Policy registration. WUAHandler 4/29/2010 11:25:25 AM 2752 (0x0AC0)
Added Update Source ({D4F72DDB-F6C4-4B05-835F-A8C23098857A}) of content type: 2 WUAHandler 4/29/2010 11:25:25 AM 2752 (0x0AC0)
Async searching of updates using WUAgent started. WUAHandler 4/29/2010 11:25:25 AM 2752 (0x0AC0)
Async searching completed. WUAHandler 4/29/2010 11:26:28 AM 2396 (0x095C)
Successfully completed scan. WUAHandler 4/29/2010 11:26:32 AM 3756 (0x0EAC)
Completion of scan is important and if the same is not successfully done you can take the help of the following link to troubleshoot the issues. This link is of WSUS troubleshooting but you can get hints to troubleshoot the error code.
http://blogs.technet.com/sus/archive/2009/11/17/tips-for-troubleshooting-wsus-agents-that-are-not-reporting-to-the-wsus-server.aspx
Now when the policy agent triggers the software update deployment cycle the scan result is compared with the catalogue and then it downloads only the required updates and install on schedule. You can check the updatestore.log, updatedeploymemt.log for more details. You can also check windowsupdate.log for more details.
Updatedeployment.log
Service startup system taskUpdatesDeploymentAgent4/28/2010 7:49:39 PM3468 (0x0D8C)
Software Updates client configuration policy has not been received.UpdatesDeploymentAgent4/28/2010 7:49:39 PM3468 (0x0D8C)
Software updates functionality will not be enabled until the configuration policy has been received. If this issue persists please check client/server policy communication.UpdatesDeploymentAgent4/28/2010 7:49:39 PM3468 (0x0D8C)
Software Updates feature is disabledUpdatesDeploymentAgent4/28/2010 7:49:39 PM3468 (0x0D8C)
Software Updates client configuration policy has not been received.UpdatesDeploymentAgent4/28/2010 7:49:39 PM3468 (0x0D8C)
Software updates functionality will not be enabled until the configuration policy has been received. If this issue persists please check client/server policy
communication.UpdatesDeploymentAgent4/28/2010 7:49:39 PM3468 (0x0D8C)
………………….
…………………
Pc Troubleshooting Software
Evaluation initiated for (1) assignments.UpdatesDeploymentAgent4/29/2010 10:39:20 AM336 (0x0150)
Deadline received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D})UpdatesDeploymentAgent4/29/2010 10:39:20 AM3344 (0x0D10)
Enforcement trigger will be effective when the current action completesUpdatesDeploymentAgent4/29/2010 10:39:20 AM3344 (0x0D10)
Message received: '<?xml version='1.0' ?><SoftwareUpdatesMessage MessageType='EvaluateAssignments'><UseCachedResults>True</UseCachedResults></SoftwareUpdatesMessage>'UpdatesDeploymentAgent4/29/2010 10:39:30 AM3940 (0x0F64)
Evaluation initiated for (0) assignments.UpdatesDeploymentAgent4/29/2010 11:01:55 AM4064 (0x0FE0)
……………………………….
DetectJob completion received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D})UpdatesDeploymentAgent4/29/2010 11:26:59 AM3856 (0x0F10)
……………………..
Added update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_9fb3050e-26f2-4ccc-b9b0-b453ff58aaa9) to the targeted listUpdatesDeploymentAgent4/29/2010 11:26:59 AM3856 (0x0F10)
Added update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) to the targeted listUpdatesDeploymentAgent4/29/2010 11:26:59 AM3856 (0x0F10)
Added update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_d2e84b36-f0fd-4434-825d-a753a338b0bd) to the targeted listUpdatesDeploymentAgent4/29/2010 11:26:59 AM3856 (0x0F10)
…………………..
Sccm 2012 Troubleshooting Software Updates Windows 7
……………………
Update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) Progress: Status = ciStateDownloading, PercentComplete = 83, Result = 0x0UpdatesDeploymentAgent4/29/2010 11:27:36 AM1068 (0x042C)
Progress received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D})UpdatesDeploymentAgent4/29/2010 11:27:38 AM12 (0x000C)
DownloadJob completion received for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D})UpdatesDeploymentAgent4/29/2010 11:27:38 AM12 (0x000C)
EnumerateUpdates for action (UpdateActionInstall) - Total visible updates = 3UpdatesDeploymentAgent4/29/2010 11:27:38 AM2960 (0x0B90)
Starting install for assignment ({3B1C5820-953D-4EFB-BDB7-3ABEE4C9788D})UpdatesDeploymentAgent4/29/2010 11:27:38 AM12 (0x000C)
………………….
Update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) Progress: Status = ciStateInstalling, PercentComplete = 100, DownloadSize = 0, Result = 0x0UpdatesDeploymentAgent4/29/2010 11:31:26 AM440 (0x01B8)
Update (Site_D4F72DDB-F6C4-4B05-835F-A8C23098857A/SUM_de919dec-2021-474a-8a7f-d632c2068146) Progress: Status = ciStatePendingSoftReboot, PercentComplete = 0, DownloadSize = 0, Result = 0x0UpdatesDeploymentAgent4/29/2010 11:31:31 AM3568 (0x0DF0)
CTargetedUpdatesManager - Job completion received.UpdatesDeploymentAgent4/29/2010 11:31:32 AM496 (0x01F0)
Job Id = {A807D023-9E41-4FE5-A528-6120C46C1134}UpdatesDeploymentAgent4/29/2010 11:31:32 AM496 (0x01F0)
No pending install assignmentUpdatesDeploymentAgent4/29/2010 11:31:33 AM440 (0x01B8)
EnumerateUpdates for action (UpdateActionInstall) - Total visible updates = 3UpdatesDeploymentAgent4/29/2010 11:31:33 AM2236 (0x08BC)
No installations in pipeline, notify reboot.UpdatesDeploymentAgent4/29/2010 11:31:33 AM440 (0x01B8)
Notify reboot with deadline = Thursday, Apr 29, 2010. - 11:31:33, Ignore reboot Window = FalseUpdatesDeploymentAgent4/29/2010 11:31:33 AM440 (0x01B8)
The execution manager will have the following entries
Execmgr.log
Mandatory execution requested for program Software Updates Program and advertisement {3D49D216-341B-4456-B52C-A0A480C06BEC}execmgr4/29/2010 11:27:50 AM2188 (0x088C)
Creating mandatory request for advert {3D49D216-341B-4456-B52C-A0A480C06BEC}, program Software Updates Program, package {3D49D216-341B-4456-B52C-A0A480C06BEC}execmgr4/29/2010 11:27:50 AM2188 (0x088C)
Sccm 2012 Software Updates Process
CExecutionRequest::Overriding Service Windows as per policy.execmgr4/29/2010 11:27:50 AM2188 (0x088C)
Execution Manager timer has been fired.execmgr4/29/2010 11:27:50 AM3256 (0x0CB8)
Executing programin Admin contextexecmgr4/29/2010 11:27:50 AM2188 (0x088C)
Execution Request for package {3D49D216-341B-4456-B52C-A0A480C06BEC} program Software Updates Program state change from NotExist to NotifyExecutionexecmgr4/29/2010 11:27:50 AM2188 (0x088C)
Executing program as an update.execmgr4/29/2010 11:27:51 AM2188 (0x088C)
Executing Update Programexecmgr4/29/2010 11:27:51 AM2188 (0x088C)
Updates Installation started for the passed command lineexecmgr4/29/2010 11:27:51 AM2188 (0x088C)
Looking for MIF file to get program statusexecmgr4/29/2010 11:31:31 AM440 (0x01B8)
Script forPackage:{3D49D216-341B-4456-B52C-A0A480C06BEC}, Program: Software Updates Program succeeded with exit code 0execmgr4/29/2010 11:31:31 AM440 (0x01B8)
Execution is complete for program Software Updates Program. The exit code is 0, the execution status is Successexecmgr4/29/2010 11:31:31 AM440 (0x01B8)
The user has logged off.execmgr4/29/2010 11:38:13 AM2788 (0x0AE4)
Once update is installed, then depending on the reboot setting the system will be rebooted. This information is tracked using
RebootCoordinator.log
Shutdown is already in progressRebootCoordinator4/29/2010 11:38:10 AM3792 (0x0ED0)
Reboot initiatedRebootCoordinator4/29/2010 11:38:10 AM3792 (0x0ED0)
User logoff notification receivedRebootCoordinator4/29/2010 11:38:13 AM2788 (0x0AE4)
Shutdown is already in progressRebootCoordinator4/29/2010 11:38:17 AM2788 (0x0AE4)
Reboot initiatedRebootCoordinator4/29/2010 11:38:17 AM2788 (0x0AE4)
For information on the other logs you can check the following link which will give you more information on the logs which you can use for troubleshooting.
http://technet.microsoft.com/en-us/library/bb693878.aspx
The other links which will be of help to you
Configuring Software Updates :http://technet.microsoft.com/en-us/library/bb633119.aspx
Tasks for Software Updates:http://technet.microsoft.com/en-us/library/bb693776.aspx
Software Updates Security Best Practices and Privacy Information:http://technet.microsoft.com/en-us/library/bb633068.aspx
Troubleshooting Software Updates :http://technet.microsoft.com/en-us/library/bb693492.aspx
Technical Reference for Software Updates :http://technet.microsoft.com/en-us/library/bb693784.aspx
Since few months ,Microsoft publishing some great guides (deep dive) on SCCM Configmgr understanding and troubleshooting process ,tips and tricks that will help Configmgr administrators in solving issues.
It is really hard to find these useful links through search engines when needed for reference and to send it internally for the team to go through .
I have tracked all the useful links in my OneNote and I have decided to let it go out for public incase for reference.
This blog post will be updating now and then ,when there is new content available.
1. Understanding and Troubleshooting Content Distribution in Microsoft Configuration Manager: This guide helps administrators understand the content distribution process and serves to build a foundation for diagnosing and resolving general content distribution related problems
2.Software Updates in Configuration Manager Current Branch Deep Dive – Client Operations
3.Troubleshooting the Database Replication Service in Microsoft Configuration Manager: This guide helps determine the type of DRS problem you are experiencing, explains how the processes work and offers troubleshooting suggestions for some of the most common problems.
4.Troubleshoot the Install Application task sequence in Microsoft Configuration Manager: This guide helps you understand the Install Application task sequence process and troubleshoot common problems that may occur. The Install Application task sequence step issued to install applications as part of the overall task sequence.
Sccm 2012 Troubleshooting Software Updates Mac
5.Troubleshooting PXE boot issues in Configuration Manager 2012:Helps administrators diagnose and resolve PXE boot failures in System Center 2012 Configuration Manager(ConfigMgr 2012 or ConfigMgr 2012 R2).
6.Software Update Management Troubleshooting in Configuration Manager: This guide helps you troubleshoot the software update management process in Microsoft System Center Configuration Manager, including client software update scanning, synchronization issues and detection problems with specific updates.
7.Configuring Software Update synchronization in System Center Configuration Manager: This guide explains the System Center Configuration Manager software update synchronization process from start to finish. Each step in the process is explained, including the various settings that control how update retrieval and synchronization are performed, common problems seen with each step in the process, as well as general troubleshooting tips.
8.complete guide to Microsoft WSUS and Configuration Manager SUP maintenance
9.Flowchart - Update replication for System Center Configuration Manager :These data flows display the process by which an in-console update you select to install replicates to additional sites. These flows also display the process of extracting the update to run prerequisite checks and to install updates at a central administration site and at primary sites.
Sccm 2012 Troubleshooting Software Updates Windows 10
See you all in the next post!