Compartir a través de

Seguimiento del proceso de implementación de actualizaciones de software en Configuration Manager

  • Artículo

En este artículo se describe cómo realizar un seguimiento de la implementación de actualizaciones de software en Configuration Manager mediante archivos de registro.

Versión original del producto: Microsoft System Center 2012 Configuration Manager, Microsoft System Center 2012 R2 Configuration Manager
Número de KB original: 3090265

Resumen

Al implementar actualizaciones de software en Configuration Manager, normalmente se agregan las actualizaciones a un grupo de actualizaciones de software y, a continuación, se implementa el grupo de actualizaciones de software en los clientes. Al crear la implementación, la directiva de actualización se envía a los equipos cliente. Y los archivos de contenido de actualización se descargan de un punto de distribución a la caché local en el equipo cliente. Las actualizaciones están disponibles para la instalación en el cliente. En la sección siguiente, examinamos este proceso con detalle y se muestra cómo se puede realizar el seguimiento del proceso mediante archivos de registro. Esta información puede ser útil cuando intenta identificar y resolver problemas en el proceso de actualización de software.

Para obtener más información sobre las actualizaciones de software en Configuration Manager, consulte Introducción a las actualizaciones de software.

Nota:

Los fragmentos de código de registro proporcionados en este artículo se aplican a Configuration Manager 2012 y 2012 R2. Las entradas de registro de otras versiones de Configuration Manager pueden ser diferentes.

Creación de un grupo de actualizaciones de software

Al crear un grupo de actualizaciones de software en la consola de Configuration Manager, se crea una instancia de la SMS_AuthorizationList clase . Esta instancia contiene información sobre el grupo de actualizaciones de software y tiene relaciones con las actualizaciones de software en el grupo de actualizaciones de software.

A continuación se registran SMSProv.log:

CSspClassManager::PreCallAction, dbname=CM_PS1    SMS Provider  
PutInstanceAsync SMS_AuthorizationList       SMS Provider  
CExtProviderClassObject::DoPutInstanceInstance    SMS Provider  
Updating SDM content definition.   SMS Provider  
Try to sync permission table : Declare @Ids RBAC_Object_Type;insert into @Ids (ObjectKey, ObjectTypeID) values (N'ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_9D013E6D-EF76-43F6-ACC4-80749AB8D90A',34);exec spRBAC_SyncPermissions @ObjectIds=@Ids,@RoleIDs=N'',@AdminIDs=N''     SMS Provider  
Successfully synced permission table              SMS Provider  
Auditing: User CONTOSO\Admin created an instance of class SMS_AuthorizationList.    SMS Provider

Como parte del proceso de creación del grupo de actualizaciones de software, SMSProv inserta datos en las tablas CI_ adecuadas, entre las que se incluyen:

  • CI_ConfigurationItems
  • CI_ConfigurationItemRelations
  • CI_ConfigurationItemRElations_Flat
  • CI_DocumentStore
  • CI_CIDocuments
  • CI_LocalizedProperties

SMSDBMON supervisa cuándo se insertan datos en estas tablas y quita los archivos de notificación de CI (CIN) en objmgr.box. A continuación se registran SMSDBMon.log:

RCV: INSERT on CI_ConfigurationItems for CINotify_iud [16777264 ][60216]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_ConfigurationItems for CINotify_iud [16777264 ][60217]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777264 ][60218] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777264 ][60219] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777264 ][60220] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777264 ][60221] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777264 ][60222] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777264 ][60223] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_ConfigurationItems for CINotify_iud [16777264 ][60224]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_ConfigurationItems for CINotify_iud [16777264 ][60225]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on RBAC_ChangeNotification for Rbac_Sync_ChangeNotification [363 ][60226] SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\objmgr.box\16777264.CIN [60225]    SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\hman.box\363.RBC [60226]    SMS_DATABASE_NOTIFICATION_MONITOR

El Administrador de replicación de objetos se reactiva cuando los archivos se quitan en objmgr.box y procesa el grupo de actualizaciones de software. A continuación se registran ObjReplMgr.log:

File notification triggered.      SMS_OBJECT_REPLICATION_MANAGER  
+++Begin processing changed CIN objects      SMS_OBJECT_REPLICATION_MANAGER  
***** Processing AuthorizationList ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_9D013E6D-EF76-43F6-ACC4- 80749AB8D90A *****   SMS_OBJECT_REPLICATION_MANAGER  
Deleting notification file E:\ConfigMgr\inboxes\objmgr.box\16777264.CIN           SMS_OBJECT_REPLICATION_MANAGER  
+++Begin collecting targeting information for Affected CIs   SMS_OBJECT_REPLICATION_MANAGER  
+++Completed collecting targeting information for Affected CIs               SMS_OBJECT_REPLICATION_MANAGER  
Affected CIs (1): 16777264            SMS_OBJECT_REPLICATION_MANAGER  
CI 16777264 is NOT Targeted         SMS_OBJECT_REPLICATION_MANAGER  
Successfully processed AuthorizationList ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_9D013E6D-EF76-43F6-ACC4-80749AB8D90A   SMS_OBJECT_REPLICATION_MANAGER  
Set last row version for Configuration Item to 0x0000000000296047     SMS_OBJECT_REPLICATION_MANAGER

Los cambios realizados en las tablas CI_* se replican en los sitios secundarios a través de la replicación de la base de datos. Esta operación permite que el grupo de actualizaciones de software aparezca en el sitio secundario.

Los grupos de actualizaciones de software son elementos de configuración (ICI) y el identificador de tipo de CI para los grupos de actualizaciones de software es 9. Puede ver los grupos de actualizaciones de software ejecutando la siguiente consulta SQL:

SELECT * FROM vSMS_ConfigurationItems WHERE CIType_ID = 9

Para ver las relaciones de una CI de grupo de actualizaciones de software a las API de actualización de software, ejecute la siguiente consulta SQL:

SELECT CIR.* FROM CI_ConfigurationItemRelations CIR
JOIN CI_ConfigurationItems CI ON CIR.FromCI_ID = CI.CI_ID
WHERE CI.CIType_ID = 9

Crear manualmente una implementación para el grupo de actualizaciones de software

Cuando se crea una implementación para un grupo de actualizaciones de software, se crea una instancia de la SMS_UpdateGroupAssignment clase . La instancia contiene información sobre la implementación. A continuación se registran SMSProv.log:

PutInstanceAsync SMS_UpdateGroupAssignment       SMS Provider  
CExtProviderClassObject::DoPutInstanceInstance        SMS Provider  
Auditing: User CONTOSO\Admin created an instance of class SMS_UpdateGroupAssignment.    SMS Provider

A continuación, el componente Descargador de revisiones de actualizaciones de software descarga las actualizaciones del directorio de origen del paquete especificado. A continuación se registran PatchDownloader.log en el directorio %TEMP%:

Trying to connect to the root\SMS namespace on the PS1SITE.CONTOSO.COM machine. Software Updates Patch Downloader  
Connected to \\PS1SITE.CONTOSO.COM\root\SMS      Software Updates Patch Downloader  
Trying to connect to the \\\PS1SITE.CONTOSO.COM\root\sms\site_PS1 namespace on the PS1SITE.CONTOSO.COM machine.     Software Updates Patch Downloader  
Connected to \\PS1SITE.CONTOSO.COM\root\sms\site_PS1     Software Updates Patch Downloader  
Download destination = \\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7-455a-a51b-aaeca7b7d7e1.1\windows6.1-kb2807986-x86.cab .       Software Updates Patch Downloader  
Contentsource = http://wsus.ds.download.windowsupdate.com/msdownload/update/software/secu/2013/02/windows6.1-kb2807986-x86_83d5bb38d8c50d924f3dcd024b20fe33afbd9d14.cab.      Software Updates Patch Downloader  
Downloading content for ContentID = 471, FileName = windows6.1-kb2807986-x86.cab.     Software Updates Patch Downloader  
Download http://wsus.ds.download.windowsupdate.com/msdownload/update/software/secu/2013/02/windows6.1-kb2807986-x86_83d5bb38d8c50d924f3dcd024b20fe33afbd9d14.cab to C:\Users\Admin\AppData\Local\Temp\2\CABBA79.tmp returns 0       Software Updates Patch Downloader  
Successfully moved C:\Users\Admin\AppData\Local\Temp\2\CABBA79.tmp to \\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7- 455a-a51b-aaeca7b7d7e1.1\windows6.1-kb2807986-x86.cab       Software Updates Patch Downloader  
Renaming \\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7-455a-a51b-aaeca7b7d7e1.1 to \\\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7-455a-a51b-aaeca7b7d7e1      Software Updates Patch Downloader  
Successfully moved \\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7-455a-a51b-aaeca7b7d7e1.1 to \\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7-455a-a51b-aaeca7b7d7e1      Software Updates Patch Downloader

Una vez descargadas las actualizaciones, el proveedor de SMS agrega cada actualización al paquete especificado. A continuación se registran SMSProv.log:

Requested class =SMS_SoftwareUpdatesPackage    SMS Provider  
Requested num keys =1    SMS Provider  
CExtProviderClassObject::DoExecuteMethod AddUpdateContent    SMS Provider  
*** SspPackageInst::AddUpdateContent ***    SMS Provider  
CObjectLock::UserHasLock: ********** User CONTOSO\Admin has lock for object SMS_SoftwareUpdatesPackage.PackageID="PS100001" with LockID: DCE6F1B5-1EE8-47CB-85A7-3027E51119A7 **********     SMS Provider  
CObjectLock::ReleaseLock: ********** User CONTOSO\Admin has released lock for object SMS_SoftwareUpdatesPackage.PackageID="PS100001" with LockID: DCE6F1B5-1EE8-47CB-85A7-3027E51119A7 **********     SMS Provider  
SspPackageInst::AddContent() called for these ContentIDs - {471}    SMS Provider  
SspPackageInst::AddContent() called with these CIContentSourcePath - {"\\PS1SITE\SOURCE\Updates\Win7"}    SMS Provider  
RefreshDPs value is FALSE. DP(s) will not be updated at the end of the operation    SMS Provider  
These Contents will be added to Software Updates Package - PS100001 with PackageSource - \\PS1SITE\SOURCE\Updates\Win7    SMS Provider  
Adding Content with ID 471, UniqueID d09e9a92-20e7-455a-a51b-aaeca7b7d7e1 and ContentSource \\PS1SITE\SOURCE\Updates\Win7 to the Package    SMS Provider  
ContentFileName = windows6.1-kb2807986-x86.cab, SourceURL = http://wsus.ds.download.windowsupdate.com/msdownload/update/software/secu/2013/02/windows6.1-kb2807986- x86_83d5bb38d8c50d924f3dcd024b20fe33afbd9d14.cab, ImportPath = , ContentFileHash = SHA1:83D5BB38D8C50D924F3DCD024B20FE33AFBD9D14      SMS Provider  
File Source = \\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7-455a-a51b-aaeca7b7d7e1\windows6.1-kb2807986-x86.cab    SMS Provider  
File Destination = \\PS1SITE\SOURCE\Updates\Win7\d09e9a92-20e7-455a-a51b-aaeca7b7d7e1     SMS Provider  
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=57376560      SMS Provider

Una vez agregadas todas las actualizaciones al paquete, el proveedor de SMS actualiza el paquete y registra las siguientes entradas:

CExtUserContext::EnterThread : User=CONTOSO\Admin Sid=0x01050000000000051500000068830AA65AAB72A155BCE9324F040000 Caching IWbemContextPtr=00000000036B7E50 in
Process 0xc68 (3176)    SMS Provider  
Context: SMSAppName=Configuration Manager Administrator console    SMS Provider  
Context: MachineName=PS1SITE.CONTOSO.COM    SMS Provider  
Context: UserName=CONTOSO\Admin    SMS Provider  
Context: ObjectLockContext=c00c315d-b15d-4b0e-9844-017205cc2443    SMS Provider  
Context: ApplicationName=Microsoft.ConfigurationManagement.exe    SMS Provider  
Context: ApplicationVersion=5.0.7958.1000     SMS Provider  
Context: LocaleID=MS\0x409    SMS Provider  
Context: __ProviderArchitecture=32      SMS Provider  
Context: __RequiredArchitecture=0 (Bool)      SMS Provider  
Context: __ClientPreferredLanguages=en-US,en    SMS Provider  
Context:  __GroupOperationId=755382    SMS Provider  
Context:  __WBEM_CLIENT_AUTHENTICATION_LEVEL=6    SMS Provider  
CExtUserContext : Set ThreadLocaleID OK to: 1033    SMS Provider  
CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider  
ExecMethodAsync : SMS_SoftwareUpdatesPackage.PackageID="PS100001"::RefreshPkgSource    SMS Provider  
Requested class =SMS_SoftwareUpdatesPackage    SMS Provider  
Requested num keys =1    SMS Provider  
CExtProviderClassObject::DoExecuteMethod RefreshPkgSource    SMS Provider  
Auditing: User CONTOSO\Admin called an audited method of an instance of class SMS_SoftwareUpdatesPackage.     SMS Provider  
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=57376336    SMS Provider

Cuando se crea la asignación de grupo de actualización, el proveedor de SMS inserta información sobre la asignación de la CI_Assignments tabla. Esto desencadena SMSDBMON, que notifica al Administrador de replicación de objetos para procesar la asignación de grupo de actualización quitando un . Archivo CIA en objmgr.box. A continuación se registran SMSDBMON.log:

RCV: INSERT on CI_CIAssignments for CIAssignmentNotify_iu [16777222 ][60916]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CrpChange_Notify for CrpChange_Notify_ins [14 ][60917]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_CIAssignments for CIAssignmentNotify_iu [16777222 ][60920]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_AssignmentTargetedCIs for CI_AssignmentTargetedCIs_CIAMGR [16777222 ][60921] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_CIAssignments for CIAssignmentNotify_iu [16777222 ][60923]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_AssignmentTargetedCIs for CI_AssignmentTargetedCIs_CIAMGR [16777222 ][60924] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_CIAssignments for CIAssignmentNotify_iu [16777222 ][60926]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on CI_AssignmentTargetedCIs for CI_AssignmentTargetedCIs_CIAMGR [16777222 ][60927] SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\objmgr.box\16777222.CIA [60916]    SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\policypv.box\policytargeteval\14.CRP [60917]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on PolicyAssignmentChg_Notify for PolicyAssignmentChg_Notify_iu [16786995 ][60929] SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\policypv.box\policytargeteval\16786995.PAC [60929] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on PkgNotification for PkgNotify_Add [PS100001 ][60930]     SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\distmgr.box\PS100001.PKN [60930]      SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on PolicyAssignmentChg_Notify for PolicyAssignmentChg_Notify_iu [16786995 ][60931] SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on PolicyAssignmentChg_Notify for PolicyAssignmentChg_Notify_iu [16786995 ][60932] SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\policypv.box\policytargeteval\16786995.PAC [60931] SMS_DATABASE_NOTIFICATION_MONITOR

Después de que Object Replication Manager detecte el archivo CIA en objmgr.box, procesa el archivo y crea la directiva para la asignación de actualizaciones de software. A continuación se registran ObjMgr.log:

File notification triggered.    SMS_OBJECT_REPLICATION_MANAGER  
+++Begin processing changed CIA objects    SMS_OBJECT_REPLICATION_MANAGER  
***** Processing Update Group Assignment {3ACE84D4-7B2A-4D86-81AF-07E2AC255745} *****   SMS_OBJECT_REPLICATION_MANAGER  
Deleting notification file E:\ConfigMgr\inboxes\objmgr.box\16777222.CIA    SMS_OBJECT_REPLICATION_MANAGER  
CI Assignment {3ACE84D4-7B2A-4D86-81AF-07E2AC255745} has 3 Targeted CI(s)    SMS_OBJECT_REPLICATION_MANAGER  
PolicyID {3ACE84D4-7B2A-4D86-81AF-07E2AC255745} PolicyVersion 1.00 PolicyHash SHA256:63BAFA808F969849B40B2B727B49BC5093B965782716DDE3490528681CF27ACC     SMS_OBJECT_REPLICATION_MANAGER  
Notifying policy provider about changes in policy content/targeting    SMS_OBJECT_REPLICATION_MANAGER  
Successfully created policy for CI Assignment {3ACE84D4-7B2A-4D86-81AF-07E2AC255745}    SMS_OBJECT_REPLICATION_MANAGER  
Notifying policy provider about changes in policy content/targeting    SMS_OBJECT_REPLICATION_MANAGER  
Successfully updated Policy Targeting for CI Assignment {3ACE84D4-7B2A-4D86-81AF-07E2AC255745}   SMS_OBJECT_REPLICATION_MANAGER  
No file trigger for E:\ConfigMgr\inboxes\objmgr.box\16777222.CIV - status 2    SMS_OBJECT_REPLICATION_MANAGER  
Assigned CIs: [ 16777264 ]    SMS_OBJECT_REPLICATION_MANAGER  
Begin processing Assigned CI: [16777264]    SMS_OBJECT_REPLICATION_MANAGER  
Creating VersionInfo policy for CI 16777264   SMS_OBJECT_REPLICATION_MANAGER  
Creating VersionInfo policy ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_9D013E6D-EF76-43F6-ACC4- 80749AB8D90A/VI    SMS_OBJECT_REPLICATION_MANAGER  
16777264 Referenced CIs: [ 929 930 1041 1042 1132 1133 ]    SMS_OBJECT_REPLICATION_MANAGER  
VersionInfo policy for CI 16777264 is Machine type    SMS_OBJECT_REPLICATION_MANAGER  
PolicyID ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_9D013E6D-EF76-43F6-ACC4-80749AB8D90A/VI PolicyVersion 1.00 PolicyHash SHA256:6EFE96F3D67773CA965EC67EC60B602FC78242509A096FCF44C2D5FDD5B2FC76     SMS_OBJECT_REPLICATION_MANAGER  
Notifying policy provider about changes in policy content/targeting    SMS_OBJECT_REPLICATION_MANAGER  
Updated dependent policy references to CIA {3ACE84D4-7B2A-4D86-81AF-07E2AC255745}     SMS_OBJECT_REPLICATION_MANAGER  
STATMSG: ID=5800 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OBJECT_REPLICATION_MANAGER" SYS=PS1SITE.CONTOSO.COM SITE=PS1 PID=5404 TID=3380 GMTDATE=Thu Jan 23 20:31:38.889 2014 ISTR0="Microsoft Software Updates - 2014-01-23 03:30:52 PM" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=414 AVAL0="{3ACE84D4-7B2A-4D86-81AF-07E2AC255745}"    SMS_OBJECT_REPLICATION_MANAGER  
Successfully updated CRCs for CI Assignment {3ACE84D4-7B2A-4D86-81AF-07E2AC255745}      SMS_OBJECT_REPLICATION_MANAGER  
Successfully processed Update Group Assignment {3ACE84D4-7B2A-4D86-81AF-07E2AC255745}     SMS_OBJECT_REPLICATION_MANAGER  
Set last row version for CI Assignment to 0x0000000000296628             SMS_OBJECT_REPLICATION_MANAGER

Después de recibir una notificación por parte del Administrador de replicación de objetos, el proveedor de directivas actualiza la directiva para los clientes. A continuación se registran PolicyPv.log:

File notification triggered.    SMS_POLICY_PROVIDER  
Found 14.CRP    SMS_POLICY_PROVIDER  
Adding to delete list: E:\ConfigMgr\inboxes\policypv.box\policytargeteval\14.CRP    SMS_POLICY_PROVIDER  
Processing any pending PolicyAssignmentChg_Notify   SMS_POLICY_PROVIDER  
Updating ResPolicyMap    SMS_POLICY_PROVIDER  
Policy or Policy Target Change Event triggered.    SMS_POLICY_PROVIDER  
File notification triggered.    SMS_POLICY_PROVIDER  
Building Collection Change List from Collection Member Notification files    SMS_POLICY_PROVIDER

--Handle PolicyAssignment Resigning    SMS_POLICY_PROVIDER  
Completed batch with beginning PADBID = 16786995 ending PADBID = 16786996.    SMS_POLICY_PROVIDER

--Process Policy Changes    SMS_POLICY_PROVIDER  
Found some Policy changes, returning New LastRowversion=0x000000000029662B    SMS_POLICY_PROVIDER  
Processing Updated Policies    SMS_POLICY_PROVIDER  
Building Collection Change List from New and Targeting Changed Policies    SMS_POLICY_PROVIDER

--Update Policy Targeting Map    SMS_POLICY_PROVIDER  
**** Evaluating Collection 14 for targeting changes ****    SMS_POLICY_PROVIDER  
Advanced client policy changes detected for collection 14, ** 5 Added & 0 Deleted ***.     SMS_POLICY_PROVIDER

--Process Policy Targeting Map    SMS_POLICY_PROVIDER  
**** Process notification table to update resultant targeting table ****    SMS_POLICY_PROVIDER

SQL Server Profiler que cubre todo el proceso muestra las siguientes entradas:

insert into CI_CIAssignments (AssignmentAction, Description, AssignmentName, DesiredConfigType, DisableMomAlerts, DPLocality, AssignmentEnabled, EnforcementDeadline, EvaluationSchedule, ExpirationTime, LimitStateMessageVerbosity, LogComplianceToWinEvent, NonComplianceCriticality, NotifyUser, OverrideServiceWindows, PersistOnWriteFilterDevices, RaiseMomAlertsOnFailure, RandomizationEnabled, RebootOutsideOfServiceWindows, SendDetailedNonComplianceStatus, StartTime, StateMessagePriority, StateMessageVerbosity, SuppressReboot, UseBranchCache, UseGMTTimes, UserUIExperience, WoLEnabled, TargetCollectionID, LocaleID, Assignment_UniqueID, SourceSite, LastModifiedBy, AssignmentType, CreationTime, LastModificationTime, IsTombstoned) values (2, N'', N'Microsoft Software Updates - 2014-01-23 03:30:52 PM', 1, 0, 16, 1,
'01/30/2014 15:30:00', null, null, 1, 0, null, 1, 0, 1, 0, null, 0, 0, '01/23/2014 15:31:00', 5, 5, 0, 1, 0, 1, 0, 14, 1033, N'{3ACE84D4-7B2A-
4D86-81AF-07E2AC255745}', N'PS1', N'CONTOSO\Admin', 5, '01/23/2014 20:31:31', '01/23/2014 20:31:31', 0)

insert into CI_AssignmentTargetedGroups (CI_ID, AssignmentID) values (16777264, 16777222)

insert into CI_ContentPackages (Content_ID, ContentSubFolder, ContentVersion, Content_UniqueID, MinPackageVersion,PkgID) VALUES ('471', N'd09e9a92-20e7-455a-a51b-aaeca7b7d7e1', '1', N'd09e9a92-20e7-455a-a51b-aaeca7b7d7e1', '0', N'PS100001')

insert Policy(Version, PolicyHash, PolicyFlags, PolicyPriority, DeviceVersion, PolicyID)
values(N'1.00', N'SHA256:63BAFA808F969849B40B2B727B49BC5093B965782716DDE3490528681CF27ACC', 16592, 25, N'''', N'{3ACE84D4-7B2A-4D86-81AF-07E2AC255745}')

insert PolicyAssignment(PolicyAssignmentID, PADBID, Version, PolicyID, IsTombstoned, LastUpdateTime)
values(N'{8d9ba949-d038-4c09-a0cc-af3f07c39d71}', 16786995, N'1.00', N'{3ACE84D4-7B2A-4D86-81AF-07E2AC255745}', 0,
GetUTCDate())

DECLARE @AssignedCIs TABLE(CI_ID INT)  
BEGIN  
INSERT INTO @AssignedCIs  
SELECT DISTINCT ATG.CI_ID FROM CI_AssignmentTargetedGroups ATG  
INNER JOIN vCI_CIAssignments CIA ON CIA.AssignmentID = ATG.AssignmentID  
WHERE CIA.Assignment_UniqueID = '{3ACE84D4-7B2A-4D86-81AF-07E2AC255745}'  
IF @@ROWCOUNT = 0  
BEGIN  
INSERT INTO @AssignedCIs  
SELECT DISTINCT ATCI.CI_ID FROM vCI_AssignmentTargetedCIs_Actual ATCI  
INNER JOIN vCI_CIAssignments CIA ON CIA.AssignmentID = ATCI.AssignmentID  
WHERE CIA.Assignment_UniqueID = '{3ACE84D4-7B2A-4D86-81AF-07E2AC255745}'  
END  
END  
SELECT DISTINCT CI_ID FROM @AssignedCIs

insert Policy(Version, PolicyHash, PolicyFlags, PolicyPriority, DeviceVersion, PolicyID)
values(N'1.00', N'SHA256:6EFE96F3D67773CA965EC67EC60B602FC78242509A096FCF44C2D5FDD5B2FC76', 208, 25, N'''', N'ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_9D013E6D-EF76-43F6-ACC4-80749AB8D90A/VI')

UPDATE Policy SET DeviceBody = NULL where PolicyID='ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_9D013E6D- EF76-43F6-ACC4-80749AB8D90A/VI'

insert PolicyAssignment(PolicyAssignmentID, PADBID, Version, PolicyID, IsTombstoned, LastUpdateTime) values(N'{64ed94a2-ff08-42a7-9e42-b292409c79e8}', 16786996, N'1.00', N'ScopeId_FC8FCC38-4BB1-4245-92F5- 9CE841775019/AuthList_9D013E6D-EF76-43F6-ACC4-80749AB8D90A/VI', 0, GetUTCDate())

insert CI_AssignmentCRCs (AssignmentID, AssignmentCRC, PolicyCRC, ComplianceCRC) values (16777222, N'7a2e8acd', N'c10ba7c5', N'5aeb49f4')

insert into CI_ContentPackages (Content_ID, ContentSubFolder, ContentVersion, Content_UniqueID, MinPackageVersion,PkgID) VALUES ('534', N'de62f3b3-615b-4800-b6ba-51d7c826dd08', '1', N'de62f3b3-615b-4800-b6ba-51d7c826dd08', '0', N'PS100001')

Creación de una implementación mediante una regla de implementación automática

La ejecución de la regla de implementación automática (ADR) se desencadena manualmente, según una programación o una vez completada la sincronización de actualizaciones de software. El componente Motor de reglas evalúa la regla. Si alguna actualización de software coincide con los criterios definidos, el motor de reglas hará lo siguiente:

  • descargar las actualizaciones
  • crear un grupo de actualizaciones de software
  • crear una asignación de grupo de actualizaciones de software

En el ejemplo siguiente se muestra el proceso de creación de grupos de actualizaciones de software e implementación:

RuleEngine.log muestra el principio del procesamiento de reglas:

Found notification file E:\ConfigMgr\inboxes\RuleEngine.box\1.RUL   SMS_RULE_ENGINE  
RuleSchedulerThred: Change in Rules Object Signalled.   SMS_RULE_ENGINE  
Constructing Rule 1 using Auto Deployment Rule Factory  SMS_RULE_ENGINE  
Populating Rule Skeleton            SMS_RULE_ENGINE  
Populating Criterion Skeleton       SMS_RULE_ENGINE  
Populating Action Skeleton          SMS_RULE_ENGINE  
Populating Action Skeleton          SMS_RULE_ENGINE  
CRuleHandler: Need to Process 1 rules           SMS_RULE_ENGINE

RuleEngine.log muestra el procesamiento de reglas y la consulta que se van a ejecutar para buscar actualizaciones que coincidan con los criterios definidos:

CRuleHandler: Processing Rule with ID:1, Name:ADR_Test.    SMS_RULE_ENGINE  
Evaluating Update Criteria for AutoDeployment Rule 1    SMS_RULE_ENGINE  
Evaluating Update Criteria...    SMS_RULE_ENGINE  
Rule Criteria is: <UpdateXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Name="SMS_SoftwareUpdate" LocaleId="1033"><UpdateXMLDescriptionItems><UpdateXMLDescriptionItem PropertyName="_Product" UIPropertyName=""><MatchRules><string>'Product:a38c835c-2950-4e87-86cc- 6911a52c34a3'</string></MatchRules></UpdateXMLDescriptionItem><UpdateXMLDescriptionItem PropertyName="IsSuperseded" UIPropertyName=""><MatchRules><string>false</string></MatchRules></UpdateXMLDescriptionItem><UpdateXMLDescriptionIte m PropertyName="_UpdateClassification" UIPropertyName=""><MatchRules><string>'UpdateClassification:e0789628-ce08-4437- be74-2495b842f43b'</string></MatchRules></UpdateXMLDescriptionItem></UpdateXMLDescriptionItems></UpdateXML>     SMS_RULE_ENGINE  
Inserting PropertyName:_Product, PropertyValue:'Product:a38c835c-2950-4e87-86cc-6911a52c34a3'      SMS_RULE_ENGINE  
Inserting PropertyName:IsSuperseded, PropertyValue:false    SMS_RULE_ENGINE  
Inserting PropertyName:_UpdateClassification, PropertyValue:'UpdateClassification:e0789628-ce08-4437-be74-2495b842f43b'     SMS_RULE_ENGINE  
Query to run is: select CI_ID from dbo.fn_ListUpdateCIs(1033) ci~where IsExpired=0~ and (IsSuperseded=0)~ and (CI_ID in (select CI_ID from v_CICategories_All where CategoryInstance_UniqueID in (N'Product:a38c835c-2950-4e87-86cc-6911a52c34a3')))~ and (CI_ID in (select CI_ID from v_CICategories_All where CategoryInstance_UniqueID in (N'UpdateClassification:e0789628-ce08-4437- be74-2495b842f43b')))    SMS_RULE_ENGINE  
Rule resulted in a total of 1 updates    SMS_RULE_ENGINE  
Evaluation Resultant XML is: <EvaluationResultXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><DefinitionUpdates/><CI_IDs><CI_ID>4514</CI_ID></CI_IDs></EvaluationResultXML>     SMS_RULE_ENGINE

La descarga se inicia para actualizaciones accionables:

Enforcing Content Download Action SMS_RULE_ENGINE  
Download Rule Action XML is: <ContentActionXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><PackageID>CS100006</PackageID><ContentLocales><Locale>Locale:9</Locale ><Locale>Locale:0</Locale></ContentLocales><ContentSources><Source Name="Internet" Order="1"/><Source Name="WSUS" Order="2"/><Source Name="UNC" Order="3" Location=""/></ContentSources></ContentActionXML>        SMS_RULE_ENGINE  
Criteria Filter Result XML is: <EvaluationResultXML xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">  
<DefinitionUpdates/><CI_IDs><CI_ID>4514</CI_ID></CI_IDs> </EvaluationResultXML>    SMS_RULE_ENGINE  
1 update(s) need to be downloaded in package "CS100006" (\\CS1SITE\SOURCE\Updates\EPDefinitions)    SMS_RULE_ENGINE  
List of update(s) which match the content rule criteria = {4514} SMS_RULE_ENGINE  
Downloading contents (count = 34) for UpdateID 4514              SMS_RULE_ENGINE  
List of update content(s) which match the content rule criteria = {737,738,739,740,741,742,2182,2183,2184,2185,2186,2187,2188,2189,3047,3048,3187,3188,3189,3190,3191,3192,3545,3546,3547 ,3548,3549,3550,3551,3552,3553,3554,3555,3556}     SMS_RULE_ENGINE  
Contents 737 is already present in the package "CS100006". Skipping download.         SMS_RULE_ENGINE  
Contents 738 is already present in the package "CS100006". Skipping download.    S MS_RULE_ENGINE  
1 of 1 updates are downloaded and will be added to the Deployment. SMS_RULE_ENGINE

RuleEngine.log muestra la creación del grupo de actualizaciones y la implementación:

We need to create a new UpdateGroup/Deployment          SMS_RULE_ENGINE  
Associated Update Group: ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_4d3480d5-de12-4864-b872-187479e2b381 with RBAC Scope SMS00UNA       SMS_RULE_ENGINE

En los ejemplos siguientes se muestra el proceso de creación de grupos de actualización:

En SMSDBMON.log:

RCV: INSERT on CI_ConfigurationItems for CINotify_iud [16777275 ][66146]           SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777275 ][66148]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on CI_ConfigurationItemRelations_Flat for CI_ConfigurationItemRelations_Flat_From_iud [16777275 ][66149]    SMS_DATABASE_NOTIFICATION_MONITOR  
...
SND: Dropped E:\ConfigMgr\inboxes\objmgr.box\16777275.CIN [66148]                   SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\objmgr.box\16777275.CIN [66149]                   SMS_DATABASE_NOTIFICATION_MONITOR

En ObjReplMgr.log:

File notification triggered.   SMS_OBJECT_REPLICATION_MANAGER  
***** Processing AuthorizationList ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_4d3480d5-de12-4864-b872-187479e2b381 *****        SMS_OBJECT_REPLICATION_MANAGER  
Deleting notification file E:\ConfigMgr\inboxes\objmgr.box\16777275.CIN       SMS_OBJECT_REPLICATION_MANAGER  
Added CI with CI_ID=4514 to the deployment       SMS_OBJECT_REPLICATION_MANAGER  
Created file trigger for E:\ConfigMgr\inboxes\objmgr.box\16777228.CIA             SMS_OBJECT_REPLICATION_MANAGER  
Created file trigger for E:\ConfigMgr\inboxes\objmgr.box\16777228.CIV             SMS_OBJECT_REPLICATION_MANAGER  
Successfully processed AuthorizationList ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_4d3480d5-de12-4864-b872- 187479e2b381    SMS_OBJECT_REPLICATION_MANAGER  
Set last row version for Configuration Item to 0x0000000000487EA9    SMS_OBJECT_REPLICATION_MANAGER

En el ejemplo siguiente se muestra el proceso de creación de la implementación:

En SMSDBMON.log:

RCV: INSERT on CI_CIAssignments for CIAssignmentNotify_iu [16777228 ][66190] SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\objmgr.box\16777228.CIA [66190]            SMS_DATABASE_NOTIFICATION_MONITOR

En ObjReplMgr.log:

+++Begin processing changed CIA objects      SMS_OBJECT_REPLICATION_MANAGER  
***** Processing Update Group Assignment {2ba787b6-4ee9-4b33-b0ff-8663d181c84d} *****    SMS_OBJECT_REPLICATION_MANAGER  
Deleting notification file E:\ConfigMgr\inboxes\objmgr.box\16777228.CIA    SMS_OBJECT_REPLICATION_MANAGER  
CI Assignment {2ba787b6-4ee9-4b33-b0ff-8663d181c84d} has 1 Targeted CI(s)   SMS_OBJECT_REPLICATION_MANAGER  
PolicyID {2ba787b6-4ee9-4b33-b0ff-8663d181c84d} PolicyVersion 1.00 PolicyHash SHA256:0C6D50CBFB36750CCA381B61E014A6C55D821001487C824F9112DAA1C64BAD32     SMS_OBJECT_REPLICATION_MANAGER  
Notifying policy provider about changes in policy content/targeting    SMS_OBJECT_REPLICATION_MANAGER  
Successfully created policy for CI Assignment {2ba787b6-4ee9-4b33-b0ff-8663d181c84d}    SMS_OBJECT_REPLICATION_MANAGER  
Notifying policy provider about changes in policy content/targeting    SMS_OBJECT_REPLICATION_MANAGER  
Successfully updated Policy Targeting for CI Assignment {2ba787b6-4ee9-4b33-b0ff-8663d181c84d}   SMS_OBJECT_REPLICATION_MANAGER  
Found file trigger for E:\ConfigMgr\inboxes\objmgr.box\16777228.CIV    SMS_OBJECT_REPLICATION_MANAGER  
Assigned CIs: [ 16777275 ]   SMS_OBJECT_REPLICATION_MANAGER  
Begin processing Assigned CI: [16777275]    SMS_OBJECT_REPLICATION_MANAGER  
Creating VersionInfo policy for CI 16777275   SMS_OBJECT_REPLICATION_MANAGER  
Creating VersionInfo policy ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_4d3480d5-de12-4864-b872-187479e2b381/VI    SMS_OBJECT_REPLICATION_MANAGER  
16777275 Referenced CIs: [ 1395 1396 1397 1398 1399 1400 1401 3013 3014 3015 3016 3017 3018 3019 3020 3021 3959 3960 3961 4112 4113 4114 4115 4116 4117 4118 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 ]       SMS_OBJECT_REPLICATION_MANAGER  
VersionInfo policy for CI 16777275 is Machine type   SMS_OBJECT_REPLICATION_MANAGER  
PolicyID ScopeId_FC8FCC38-4BB1-4245-92F5-9CE841775019/AuthList_4d3480d5-de12-4864-b872-187479e2b381/VI PolicyVersion 1.00 PolicyHash SHA256:01BECBBF2B3EE56BD5B0742A04404C1C895A4C87B6915D55078AB157FEBA1E0F   SMS_OBJECT_REPLICATION_MANAGER  
Notifying policy provider about changes in policy content/targeting    SMS_OBJECT_REPLICATION_MANAGER  
Updated dependent policy references to CIA {2ba787b6-4ee9-4b33-b0ff-8663d181c84d}    SMS_OBJECT_REPLICATION_MANAGER  
STATMSG: ID=5800 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OBJECT_REPLICATION_MANAGER" SYS=PS1SITE.CONTOSO.COM SITE=PS1 PID=6176 TID=6868 GMTDATE=Thu Feb 06 20:09:17.989 2014 ISTR0="ADR_Test" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=414 AVAL0="{2ba787b6-4ee9-4b33- b0ff-8663d181c84d}"   SMS_OBJECT_REPLICATION_MANAGER  
Successfully updated CRCs for CI Assignment {2ba787b6-4ee9-4b33-b0ff-8663d181c84d}    SMS_OBJECT_REPLICATION_MANAGER  
Successfully processed Update Group Assignment {2ba787b6-4ee9-4b33-b0ff-8663d181c84d}    SMS_OBJECT_REPLICATION_MANAGER  
Set last row version for CI Assignment to 0x0000000000487EB6    SMS_OBJECT_REPLICATION_MANAGER  
+++Completed processing changed CIA objects    SMS_OBJECT_REPLICATION_MANAGER

En el ejemplo siguiente se muestra el proceso de creación de directivas:

En SMSDBMON.log:

RCV: INSERT on CrpChange_Notify for CrpChange_Notify_ins [15 ][66199]   SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on RBAC_ChangeNotification for Rbac_Sync_ChangeNotification [399 ][66200]   SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\policypv.box\policytargeteval\15.CRP [66199]      SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\hman.box\399.RBC [66200]   SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on PolicyAssignmentChg_Notify for PolicyAssignmentChg_Notify_iu [16787957 ][66201]    SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\policypv.box\policytargeteval\16787957.PAC [66201]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: INSERT on PolicyAssignmentChg_Notify for PolicyAssignmentChg_Notify_iu [16787957 ][66202]    SMS_DATABASE_NOTIFICATION_MONITOR  
RCV: UPDATE on PolicyAssignmentChg_Notify for PolicyAssignmentChg_Notify_iu [16787957 ][66203]    SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\policypv.box\policytargeteval\16787957.PAC [66202]    SMS_DATABASE_NOTIFICATION_MONITOR  
SND: Dropped E:\ConfigMgr\inboxes\policypv.box\policytargeteval\16787957.PAC [66203]    SMS_DATABASE_NOTIFICATION_MONITOR

En PolicyPv.log:

File notification triggered.   SMS_POLICY_PROVIDER

--Process Collection Changes    SMS_POLICY_PROVIDER  
Building Collection Change List from Collection Change Notification files    SMS_POLICY_PROVIDER

--Process Collection Member Changes    SMS_POLICY_PROVIDER  
Building Collection Change List from Collection Member Notification files    SMS_POLICY_PROVIDER

--Handle PolicyAssignment Resigning    SMS_POLICY_PROVIDER  
Found the certificate that matches the SHA1 hash.    SMS_POLICY_PROVIDER  
Completed batch with beginning PADBID = 16787957 ending PADBID = 16787958.    SMS_POLICY_PROVIDER

--Process Policy Changes    SMS_POLICY_PROVIDER  
Found some Policy changes, returning New LastRowversion=0x0000000000487EB7    SMS_POLICY_PROVIDER  
Processing Updated Policies    SMS_POLICY_PROVIDER  
Building Collection Change List from New and Targeting Changed Policies    SMS_POLICY_PROVIDER

--Update Policy Targeting Map    SMS_POLICY_PROVIDER  
**** Evaluating Collection 15 for targeting changes ****    SMS_POLICY_PROVIDER

--Process Policy Targeting Map    SMS_POLICY_PROVIDER  
**** Process notification table to update resultant targeting table ****    SMS_POLICY_PROVIDER

--Process Targeting and Collection Membership changes    SMS_POLICY_PROVIDER  
Updating Policy Map    SMS_POLICY_PROVIDER

--UpdateMDMUserTargetingForUser    SMS_POLICY_PROVIDER  
Start Update MDM User Targeting For User  SMS_POLICY_PROVIDER

--UpdatePolicyMapForPA    SMS_POLICY_PROVIDER  
Found 16787957.PAC    SMS_POLICY_PROVIDER  
Adding to delete list: E:\ConfigMgr\inboxes\policypv.box\policytargeteval\16787957.PAC    SMS_POLICY_PROVIDER  
Updating ResPolicyMap    SMS_POLICY_PROVIDER

RuleEngine.log muestra la finalización del procesamiento de reglas:

CRuleHandler: Rule 1 Successfully Applied!   SMS_RULE_ENGINE  
Updated Success Information for Rule: 1     SMS_RULE_ENGINE

Evaluación de implementación e instalación de actualizaciones en clientes

Una vez creada la implementación y la directiva de implementación en el servidor, los clientes reciben la directiva en el siguiente ciclo de evaluación de directivas. Antes de revisar el proceso de evaluación de implementación, es importante encontrar el identificador único de implementación de la implementación. Para buscar el identificador único de implementación, agregue la columna Id. único de implementación en la consola. Para la implementación en el ejemplo siguiente, el identificador único de implementación es {B040D195-8FA8-48D3-953F-17E878DAB23D}.

  1. El Agente de directivas recibe la directiva sobre la recuperación manual de directivas o según la programación. Cuando se recibe la directiva, se registran los siguientes PolicyAgent.log:

    Initializing download of policy 'CCM_Policy_Policy5.PolicyID="{B040D195-8FA8-48D3-953F-17E878DAB23D}",PolicySource="SMS:PR1",PolicyVersion="1.00"' from 'http://PR1SITE.CONTOSO.COM/SMS_MP/.sms_pol?{B040D195-8FA8-48D3-953F-17E878DAB23D}.SHA256:0EE489DB3036BE80BB43676340249A254278BEBDDD80B6004C11FF10F12BC9D6' PolicyAgent_ReplyAssignments  
Download of policy CCM_Policy_Policy5.PolicyID="{B040D195-8FA8-48D3-953F-17E878DAB23D}",PolicySource="SMS:PR1",PolicyVersion="1.00" completed (DTS Job ID: {D53DAB18-ED97-4373-A3BE-3FBA5DB3C6C6}) PolicyAgent_PolicyDownload

    A continuación se registran PolicyEvaluator.log:

    Initializing download of policy 'CCM_Policy_Policy5.PolicyID="{B040D195-8FA8-48D3-953F-17E878DAB23D}",PolicySource="SMS:PR1",PolicyVersion="1.00"' from 'http://PR1SITE.CONTOSO.COM/SMS_MP/.sms_pol?{B040D195-8FA8-48D3-953F-17E878DAB23D}.SHA256:0EE489DB3036BE80BB43676340249A254278BEBDDD80B6004C11FF10F12BC9D6' PolicyAgent_ReplyAssignments  
Download of policy CCM_Policy_Policy5.PolicyID="{B040D195-8FA8-48D3-953F-17E878DAB23D}",PolicySource="SMS:PR1",PolicyVersion="1.00" completed (DTS Job ID: {D53DAB18-ED97-4373-A3BE-3FBA5DB3C6C6}) PolicyAgent_PolicyDownload

    Una vez evaluada la directiva, se evalúa el programador de la fecha límite. El componente Scheduler realiza esta operación. En este ejemplo, la selección aleatoria de fecha límite está deshabilitada en la configuración del cliente del Agente de equipo. Por lo tanto, la evaluación de implementación se inicia en la fecha límite y sin la selección aleatoria. Esto es lo que vemos en el archivo Scheduler.log:

    Initialized trigger ("3E692B0000080000") for schedule 'Machine/DEADLINE:{B040D195-8FA8-48D3-953F-17E878DAB23D}':  
Conditions=1 with deadline 4320 minutes  
Allow randomization override=1  
HasMissedOccurrence=FALSE  
ScheduleLoadedTime="02/09/2014 19:05:947"  
LastFireTime="00/00/00 00:00:00"  
CurrentTime="02/09/2014 19:05:947"    Scheduler  
Processing trigger '3E692B0000080000' for scheduler 'Machine/DEADLINE:{B040D195-8FA8-48D3-953F-17E878DAB23D}'. MaxRandomDelay = 120, MissedOccur = 0, RandomizeEvenIfMissed = 1, PreventRandomizationInducedMisses = 0   Scheduler  
Randomization is disabled in client settings and this schedule is set to honor client setting.   Scheduler  
SMSTrigger '3E692B0000080000' for scheduler 'Machine/DEADLINE:{B040D195-8FA8-48D3-953F-17E878DAB23D}' will fire at 02/09/2014 07:15:00 PM without randomization.   Scheduler

  2. En la fecha límite programada, Scheduler notifica al Agente de implementación de actualizaciones que inicie el proceso de evaluación de implementación, como se muestra en Scheduler.log:

    Sending message for schedule 'Machine/DEADLINE:{B040D195-8FA8-48D3-953F-17E878DAB23D}' (Target: 'direct:UpdatesDeploymentAgent', Name: '')    Scheduler  
SMSTrigger '3E692B0000080000' (Schedule ID: 'Machine/DEADLINE:{B040D195-8FA8-48D3-953F-17E878DAB23D}', Message Name: '', Target: 'direct:UpdatesDeploymentAgent') will never fire again.     Scheduler

    En UpdatesDeployment.log:

    Message received: '<?xml version='1.0' ?>  
<CIAssignmentMessage MessageType='EnforcementDeadline'>  
<AssignmentID>{B040D195-8FA8-48D3-953F-17E878DAB23D}</AssignmentID>  
</CIAssignmentMessage>'    UpdatesDeploymentAgent

    El Agente de implementación de actualizaciones inicia el proceso de evaluación de implementación solicitando un examen de actualización de software. El examen garantiza que las actualizaciones implementadas siguen siendo aplicables. En UpdatesDeployment.log:

    Assignment {B040D195-8FA8-48D3-953F-17E878DAB23D} has total CI = 3   UpdatesDeploymentAgent  
Deadline received for assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D})   UpdatesDeploymentAgent  
Detection job ({99ADA372-0738-44E4-9C4D-EBA30F23E9FD}) started for assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D})   UpdatesDeploymentAgent

    En UpdatesHandler.log:

    Successfully initiated scan for job ({99ADA372-0738-44E4-9C4D-EBA30F23E9FD}).   UpdatesHandler  
Scan completion received for job ({99ADA372-0738-44E4-9C4D-EBA30F23E9FD}).   UpdatesHandler  
Initial scan completed for the job ({99ADA372-0738-44E4-9C4D-EBA30F23E9FD}).   UpdatesHandler  
Evaluating status of the updates for the job ({99ADA372-0738-44E4-9C4D-EBA30F23E9FD}).   UpdatesHandler  
CompleteJob - Job ({99ADA372-0738-44E4-9C4D-EBA30F23E9FD}) removed from job manager list.    UpdatesHandler

  3. En este momento, el componente Scan Agent controla la solicitud de examen. Scan Agent llama a WUAHandler para realizar un examen y, a continuación, devuelve los resultados al controlador de actualizaciones y al Agente de implementación de actualizaciones. Para obtener más información sobre el proceso de examen, consulte Examen de actualizaciones de software en clientes.

    Una vez completado el examen, se notifica al Agente de implementación de actualizaciones. Esto es lo que vemos en UpdatesDeployment.log:

    DetectJob completion received for assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) UpdatesDeploymentAgent  
Making updates available for assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_e06056e3-0199-4c68-8ac3-bdddff356a0a) Name (Security Update for Windows Server 2008 R2 x64 Edition (KB2698365)) ArticleID (2698365) added to the targeted list of deployment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_ada7cf51-66b0-4a00-b37b-68d569d6ff8b) Name (Security Update for Windows Server 2008 R2 x64 Edition (KB2712808)) ArticleID (2712808) added to the targeted list of deployment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_3cbcf577-5139-49b8-afe8-620af5c52f95) Name (Security Update for Windows Server 2008 R2 x64 Edition (KB2705219)) ArticleID (2705219) added to the targeted list of deployment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) UpdatesDeploymentAgent

  4. Updates Deployment Agent genera mensajes de estado para que la implementación actualice el estado actual de evaluación y cumplimiento . Esto es lo que vemos en UpdatesDeployment.log:

    Raised assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) state message successfully. TopicType = Evaluate, StateId = 2, StateName = ASSIGNMENT_EVALUATE_SUCCESS    UpdatesDeploymentAgent  
Raised assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) state message successfully. TopicType = Compliance, Signature = 5e176837, IsCompliant = False    UpdatesDeploymentAgent

    El Agente de implementación de actualizaciones inicia ahora un trabajo para descargar los archivos de actualización de software desde el punto de distribución. Esto es lo que vemos en UpdatesDeployment.log:

    DownloadCIContents Job ({C531FD04-FADA-4F75-A399-EEA2D3EDB56C}) started for assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D})   UpdatesDeploymentAgent  
Progress received for assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D})   UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_e06056e3-0199-4c68-8ac3-bdddff356a0a) Progress: Status = ciStateDownloading, PercentComplete = 0, Result = 0x0   UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_ada7cf51-66b0-4a00-b37b-68d569d6ff8b) Progress: Status = ciStateDownloading, PercentComplete = 0, Result = 0x0   UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_3cbcf577-5139-49b8-afe8-620af5c52f95) Progress: Status = ciStateDownloading, PercentComplete = 0, Result = 0x0   UpdatesDeploymentAgent

    También podemos ver en UpdatesHandler.log:

    Initiating download for the job ({C531FD04-FADA-4F75-A399-EEA2D3EDB56C}). UpdatesHandler  
Update Id = 3cbcf577-5139-49b8-afe8-620af5c52f95, State = StateDownloading, Result = 0x0 UpdatesHandler  
Update Id = ada7cf51-66b0-4a00-b37b-68d569d6ff8b, State = StateDownloading, Result = 0x0 UpdatesHandler  
Update Id = e06056e3-0199-4c68-8ac3-bdddff356a0a, State = StateDownloading, Result = 0x0 UpdatesHandler  
Timeout Options: Priority = 2, DPLocality = 1048578, Location = 604800, Download = 864000, PerDPInactivity = 0, TotalInactivityTimeout = 0, bUseBranchCache = True, bPersistOnWriteFilterDevices = True, bOverrideServiceWindow = False UpdatesHandler

  5. El controlador de actualizaciones inicia la solicitud de descarga del servicio acceso a contenido para las tres actualizaciones accionables que se enumeran anteriormente. El trabajo de descarga se inicia para la actualización secundaria en la agrupación y se registra el identificador de contenido.

    En UpdatesHandler.log

    Bundle update (3cbcf577-5139-49b8-afe8-620af5c52f95) is requesting download from child updates for action (INSTALL) UpdatesHandler  
Content Text = <Content ContentId="fbb5724a-aa0f-47f9-908a-47068fd8ad6f" Version="1"><FileContent Name="windows6.1-kb2705219-v2-x64.cab" Hash="8E8E0175D46B5A8D52C4856FA3D282FAA12ACD63" HashAlgorithm="SHA1" Size="199093"/></Content>  
Bundle update (ada7cf51-66b0-4a00-b37b-68d569d6ff8b) is requesting download from child updates for action (INSTALL) UpdatesHandler  
Content Text = <Content ContentId="3e9b1132-9ccd-439d-b32a-5cefd19735d1" Version="1"><FileContent Name="windows6.1-kb2712808-x64.cab" Hash="060B60401B3DE3DCE053A68C65E9EB050874EB80" HashAlgorithm="SHA1" Size="805071"/></Content>  
Bundle update (e06056e3-0199-4c68-8ac3-bdddff356a0a) is requesting download from child updates for action (INSTALL) UpdatesHandler  
Content Text = <Content ContentId="d2a9ee23-9cab-4843-b040-e2da1cc167e9" Version="1"><FileContent Name="windows6.1-kb2698365-x64.cab" Hash="BF20BB36FC73C0D1F53EA1E635B8AA46C71D7B1F" HashAlgorithm="SHA1" Size="2496330"/></Content>

    El servicio content Access inicia un trabajo de descarga para cada actualización y crea un trabajo de Administrador de transferencia de contenido (CTM). Se crea un trabajo de CTM para cada actualización por separado y CAS.log entradas son similares a las siguientes para cada actualización:

    Requesting content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1, size(KB) 0, under context System with priority Medium ContentAccess  
Created and initialized a DownloadContentRequest ContentAccess  
Target location for content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1 is C:\Windows\ccmcache\1 ContentAccess  
CDownloadManager::RequestDownload fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1.System ContentAccess  
Submitted CTM job {E0452CF4-5B04-4A1A-B8EB-10B11B063249} to download Content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1 under context System ContentAccess  
Successfully created download request {856FA4CA-D02A-4E2C-841E-841ED3C7EC01} for content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1 ContentAccess  
Created and submitted a new Content Request for fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1.System ContentAccess

  6. El Administrador de transferencia de contenido comienza a trabajar en el trabajo de descarga. Primero solicita la ubicación del contenido que se debe descargar. Los Servicios de ubicación controlan esta solicitud de ubicación. Location Services envía la solicitud de ubicación al punto de administración, obtiene la respuesta de ubicación y, a continuación, la devuelve al Administrador de transferencia de contenido. Esto es lo que vemos en ContentTransferManager.log:

    Starting CTM job {E0452CF4-5B04-4A1A-B8EB-10B11B063249}. ContentTransferManager  
CTM job {E0452CF4-5B04-4A1A-B8EB-10B11B063249} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA ContentTransferManager  
Queued location request '{C56C01F2-2388-4710-BF3B-A526DB40E35F}' for CTM job '{E0452CF4-5B04-4A1A-B8EB-10B11B063249}'. ContentTransferManager  
CCTMJob::EvaluateState(JobID={E0452CF4-5B04-4A1A-B8EB-10B11B063249}, State=RequestedLocations) ContentTransferManager

    También podemos ver en LocationServices.log:

    Created filter for LS request {C56C01F2-2388-4710-BF3B-A526DB40E35F}.   LocationServices  
ContentLocationReply : <ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="0"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="PR1" MasterSiteCode="PR1" SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="<http://PR1SITE.CONTOSO.COM/SMS_DP_SMSPKG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f>" Signature="<http://PR1SITE.CONTOSO.COM/SMS_DP_SMSSIG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1.tar>"/><ADSite Name="Default-First-Site-Name"/><IPSubnets><IPSubnet Address="192.168.10.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>PR1SITE.CONTOSO.COM</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site></Sites><RelatedContentIDs/></ContentLocationReply>   LocationServices  
Distribution Point='<http://PR1SITE.CONTOSO.COM/SMS_DP_SMSPKG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f>', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='<http://PR1SITE.CONTOSO.COM/SMS_DP_SMSSIG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1.tar>', ForestTrust='TRUE',   LocationServices  
Calling back with locations for location request {C56C01F2-2388-4710-BF3B-A526DB40E35F}   LocationServices

    El Administrador de transferencia de contenido recibe la ubicación del punto de distribución para el contenido solicitado e inicia un trabajo del servicio de transferencia de datos para iniciar la descarga de la actualización. Esto es lo que vemos en ContentTransferManager.log:

    CCTMJob::UpdateLocations({E0452CF4-5B04-4A1A-B8EB-10B11B063249})   ContentTransferManager  
CTM_NotifyLocationUpdate   ContentTransferManager  
Persisted location '<http://PR1SITE.CONTOSO.COM/SMS_DP_SMSPKG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f>', Order 0, for CTM job {E0452CF4-5B04-4A1A-B8EB-10B11B063249}   ContentTransferManager  
Persisted locations for CTM job {E0452CF4-5B04-4A1A-B8EB-10B11B063249}:  
(LOCAL) '<http://PR1SITE.CONTOSO.COM/SMS_DP_SMSPKG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f>'   ContentTransferManager  
CTM job {E0452CF4-5B04-4A1A-B8EB-10B11B063249} (corresponding DTS job {594E9A72-43D1-48D1-A639-D18DF7D286A2}) started download from 'http://PR1SITE.CONTOSO.COM/SMS_DP_SMSPKG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f' for full content download.   ContentTransferManager  
CCTMJob::EvaluateState(JobID={E0452CF4-5B04-4A1A-B8EB-10B11B063249}, State=DownloadingData)    ContentTransferManager  
CTM job {E0452CF4-5B04-4A1A-B8EB-10B11B063249} entered phase CCM_DOWNLOADSTATUS_DOWNLOADING_DATA    ContentTransferManager

    En CAS.log:

    Location update from CTM for content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1 and request {856FA4CA-D02A-4E2C-841E-841ED3C7EC01} ContentAccess  
Download location found 0 - <http://PR1SITE.CONTOSO.COM/SMS_DP_SMSPKG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f> ContentAccess  
Download request only, ignoring location update ContentAccess  
Download started for content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1 ContentAccess

    En este momento, el servicio de transferencia de datos crea un trabajo de BITS para descargar el archivo y, a continuación, supervisa el progreso de la descarga, como se indica en DataTransferService.log:

    DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} created to download from 'http://PR1SITE.CONTOSO.COM:80/SMS_DP_SMSPKG$/fbb5724a-aa0f-47f9-908a-47068fd8ad6f' to 'C:\Windows\ccmcache\1'.   DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} in state 'DownloadingManifest'.   DataTransferService  
CDTSJob::ProcessManifestCallback - processing manifest for job '{594E9A72-43D1-48D1-A639-D18DF7D286A2}'.  DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} in state 'RetrievedManifest'.   DataTransferService  
Execute called for DTS job '{594E9A72-43D1-48D1-A639-D18DF7D286A2}'. Current state: 'RetrievedManifest'.   DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} in state 'PendingDownload'.   DataTransferService  
Starting BITS download for DTS job '{594E9A72-43D1-48D1-A639-D18DF7D286A2}'.   DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} set BITS job to use default credentials.   DataTransferService  
Starting BITS job '{38E74FCB-4397-4CA9-94AE-BDD49F550EC9}' for DTS job '{594E9A72-43D1-48D1-A639-D18DF7D286A2}' under user 'S-1-5-18'.   DataTransferService  
DTS::SetCustomHeadersOnBITSJob - setting custom headers on DTS job '{594E9A72-43D1-48D1-A639-D18DF7D286A2}':  
<none>   DataTransferService  
DTS::AddTransportSecurityOptionsToBITSJob - Removing security info from DTS job '{594E9A72-43D1-48D1-A639-D18DF7D286A2}'.   DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} in state 'DownloadingData'.   DataTransferService  
Job: {594E9A72-43D1-48D1-A639-D18DF7D286A2}, Total Files: 1, Transferred Files: 0, Total Bytes: 199093, Transferred Bytes: 5760   DataTransferService  
Job: {594E9A72-43D1-48D1-A639-D18DF7D286A2}, Total Files: 1, Transferred Files: 0, Total Bytes: 199093, Transferred Bytes: 199093   DataTransferService  
CDTSJob::JobTransferred : DTS Job ID='{594E9A72-43D1-48D1-A639-D18DF7D286A2}' BITS Job ID='{38E74FCB-4397-4CA9-94AE-BDD49F550EC9}'   DataTransferService  
Job: {594E9A72-43D1-48D1-A639-D18DF7D286A2}, Total Files: 1, Transferred Files: 1, Total Bytes: 199093, Transferred Bytes: 199093   DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} in state 'RetrievedData'.   DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} successfully completed download.   DataTransferService  
BITS job '{38E74FCB-4397-4CA9-94AE-BDD49F550EC9}' is not found. The BITS job may have completed already.   DataTransferService  
CBITSDownloadMonitor(DTSJobID={594E9A72-43D1-48D1-A639-D18DF7D286A2}, BITSJobID={38E74FCB-4397-4CA9-94AE-BDD49F550EC9}) ignoring cancelled object.   DataTransferService  
DTSJob {594E9A72-43D1-48D1-A639-D18DF7D286A2} in state 'NotifiedComplete'.   DataTransferService  
DTS job {594E9A72-43D1-48D1-A639-D18DF7D286A2} has completed:  
Status : SUCCESS,  
Start time : 02/09/2014 19:15:05,  
Completion time : 02/09/2014 19:15:12,  
Elapsed time : 7 seconds   DataTransferService

  7. Una vez completada la descarga, se notifica el servicio CTM y Content Access y marcan los trabajos de descarga como completados. El servicio de acceso a contenido realiza una comprobación hash del contenido descargado para comprobar la integridad del archivo descargado. Este proceso se produce para cada archivo, aunque el ejemplo siguiente implica que se descargue una sola actualización. Esto es lo que vemos en ContentTransferManager.log:

    CCTMJob::EvaluateState(JobID={E0452CF4-5B04-4A1A-B8EB-10B11B063249}, State=Success)   ContentTransferManager  
CCTMJob::EvaluateState(JobID={E0452CF4-5B04-4A1A-B8EB-10B11B063249}, State=Complete)   ContentTransferManager

    En CAS.log:

    Download completed for content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1 under context System   ContentAccess  
The hash we are verifying is SDMPackage:<Content ContentId="fbb5724a-aa0f-47f9-908a-47068fd8ad6f" Version="1"><FileContent Name="windows6.1-kb2705219-v2-x64.cab" Hash="8E8E0175D46B5A8D52C4856FA3D282FAA12ACD63" HashAlgorithm="SHA1" Size="199093"/></Content>  ContentAccess  
CContentAccessService::NotifyDownloadComplete Start Content Hashing   ContentAccess  
Hashing file c:\windows\ccmcache\1\windows6.1-kb2705219-v2-x64.cab   ContentAccess  
Hash matches ContentAccess 2/9/2014 7:15:12 PM 3532 (0x0DCC)  
Hash verification succeeded for content fbb5724a-aa0f-47f9-908a-47068fd8ad6f.1 downloaded under context System ContentAccess

    A continuación, El Agente de implementación de actualizaciones genera un mensaje de estado para actualizar el estado de cumplimiento actual y, a continuación, inicia la instalación de la actualización. Vemos el siguiente mensaje en UpdatesDeployment.log:

    Raised assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) state message successfully. TopicType = Enforce, StateId = 8, StateName = ASSIGNMENT_ENFORCE_ADVANCE_DOWNLOAD_SUCCESS   UpdatesDeploymentAgent  
Starting install for assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D})   UpdatesDeploymentAgent  
ApplyCIs - JobId = {CEE4AA3A-DE7B-4D9F-8949-E421BBBF2993}   UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_3cbcf577-5139-49b8-afe8-620af5c52f95) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0   UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_ada7cf51-66b0-4a00-b37b-68d569d6ff8b) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0   UpdatesDeploymentAgent  
Update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_e06056e3-0199-4c68-8ac3-bdddff356a0a) Progress: Status = ciStateWaitInstall, PercentComplete = 0, DownloadSize = 0, Result = 0x0   UpdatesDeploymentAgent

    También vemos esta entrada en UpdatesHandler.log:

    Job {CEE4AA3A-DE7B-4D9F-8949-E421BBBF2993} is starting execution   UpdatesHandler  
CDeploymentJob::InstallUpdatesInBatch - Batch or non-batch install is not in progress for the job ({CEE4AA3A-DE7B-4D9F-8949-E421BBBF2993}). So allowing install..   UpdatesHandler  
Update (3cbcf577-5139-49b8-afe8-620af5c52f95) added to the installation batch   UpdatesHandler  
Update (ada7cf51-66b0-4a00-b37b-68d569d6ff8b) added to the installation batch   UpdatesHandler  
Update (e06056e3-0199-4c68-8ac3-bdddff356a0a) added to the installation batch   UpdatesHandler  
Got execute info for (3) updates   UpdatesHandler  
Updates installation started as batch   UpdatesHandler

  8. A continuación, el controlador del Agente de Windows Update copia los archivos binarios descargados en el directorio C:\Windows\SoftwareDistribution\Download) y indica al Agente de Windows Update que inicie el proceso de instalación. Esto es lo que vemos en WUAHandler.log:

    Adding file to list for CopyToCache(): C:\Windows\ccmcache\1\windows6.1-kb2705219-v2-x64.cab   WUAHandler  
CopyToCache() for update (fbb5724a-aa0f-47f9-908a-47068fd8ad6f) completed successfully   WUAHandler  
Adding file to list for CopyToCache(): C:\Windows\ccmcache\2\windows6.1-kb2712808-x64.cab   WUAHandler  
CopyToCache() for update (3e9b1132-9ccd-439d-b32a-5cefd19735d1) completed successfully   WUAHandler  
Adding file to list for CopyToCache(): C:\Windows\ccmcache\3\windows6.1-kb2698365-x64.cab   WUAHandler  
CopyToCache() for update (d2a9ee23-9cab-4843-b040-e2da1cc167e9) completed successfully   WUAHandler  
Update(s) downloaded to WUA file cache, starting installation.   WUAHandler  
Async installation of updates started.   WUAHandler  
Update 1 (3cbcf577-5139-49b8-afe8-620af5c52f95) finished installing (0x00000000), Reboot Required? Yes   WUAHandler  
Update 2 (ada7cf51-66b0-4a00-b37b-68d569d6ff8b) finished installing (0x00000000), Reboot Required? Yes   WUAHandler  
Update 3 (e06056e3-0199-4c68-8ac3-bdddff356a0a) finished installing (0x00000000), Reboot Required? Yes   WUAHandler  
Async install completed.   WUAHandler  
Installation of updates completed.   WUAHandler

    También vemos las siguientes entradas en WindowsUpdate.log:

    2014-02-09 19:15:26:130 800 ed0 Agent ** START ** Agent: Installing updates [CallerId = CcmExec]  
2014-02-09 19:15:26:130 800 ed0 Agent * Updates to install = 3  
2014-02-09 19:15:26:254 1048 84c Handler Starting install of CBS update FBB5724A-AA0F-47F9-908A-47068FD8AD6F  
2014-02-09 19:15:29:218 1048 84c Handler Completed install of CBS update with type=3, requiresReboot=1, installerError=0, hr=0x0  
2014-02-09 19:15:29:265 1048 84c Handler Starting install of CBS update 3E9B1132-9CCD-439D-B32A-5CEFD19735D1  
2014-02-09 19:15:30:435 1048 84c Handler Completed install of CBS update with type=3, requiresReboot=1, installerError=0, hr=0x0  
2014-02-09 19:15:30:451 1048 84c Handler Starting install of CBS update D2A9EE23-9CAB-4843-B040-E2DA1CC167E9  
2014-02-09 19:15:39:296 1048 84c Handler Completed install of CBS update with type=3, requiresReboot=1, installerError=0, hr=0x0  
2014-02-09 19:15:39:327 788 9f8 COMAPI - Reboot required = Yes  
2014-02-09 19:15:39:327 788 9f8 COMAPI -- END -- COMAPI: Install [ClientId = CcmExec]

  9. Una vez instaladas las actualizaciones, el Agente de implementación de actualizaciones comprueba si las actualizaciones requieren un reinicio. A continuación, notifica al usuario si la configuración del cliente está configurada para permitir dichas notificaciones. Esto es lo que vemos en UpdatesDeployment.log:

    No installations in pipeline, notify reboot. NotifyUI = True   UpdatesDeploymentAgent  
Notify reboot with deadline = Sunday, Feb 09, 2014. - 19:15:39, Ignore reboot Window = False, NotifyUI = True UpdatesDeploymentAgent  
Raised assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) state message successfully. TopicType = Enforce, StateId = 5, StateName = ASSIGNMENT_ENFORCE_PENDING_REBOOT   UpdatesDeploymentAgent

  10. Una vez reiniciado el equipo, se inicia un examen de detección posterior al reinicio para la implementación. El examen comprueba que se instalan las actualizaciones y genera mensajes de estado para la actualización y la implementación para indicar que las actualizaciones están instaladas y que la aplicación se realizó correctamente. Esto es lo que vemos en UpdatesDeployment.log:

    CTargetedUpdatesManager::DetectRebootPendingUpdates - Total Pending reboot updates = 3   UpdatesDeploymentAgent  
Initiated detect for pending reboot updates after system restart - JobId = {53F4851F-7E63-4C7E-952D-78345039FFFC}   UpdatesDeploymentAgent  
CUpdatesJob({53F4851F-7E63-4C7E-952D-78345039FFFC}): Job completion received.   UpdatesDeploymentAgent  
CUpdatesJob({53F4851F-7E63-4C7E-952D-78345039FFFC}): Detect after reboot job completed with result = 0x0   UpdatesDeploymentAgent  
Raised update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_e06056e3-0199-4c68-8ac3-bdddff356a0a) enforcement state message successfully. StateId = 10, StateName = CI_ENFORCEMENT_SUCCESSFULL   UpdatesDeploymentAgent  
Raised update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_ada7cf51-66b0-4a00-b37b-68d569d6ff8b) enforcement state message successfully. StateId = 10, StateName = CI_ENFORCEMENT_SUCCESSFULL   UpdatesDeploymentAgent  
Raised update (Site_D3A5F7EA-25D4-4C6B-B47C-C74997522A76/SUM_3cbcf577-5139-49b8-afe8-620af5c52f95) enforcement state message successfully. StateId = 10, StateName = CI_ENFORCEMENT_SUCCESSFULL   UpdatesDeploymentAgent  
Raised assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) state message successfully. TopicType = Compliance, Signature = 5e176837, IsCompliant = True   UpdatesDeploymentAgent  
Raised assignment ({B040D195-8FA8-48D3-953F-17E878DAB23D}) state message successfully. TopicType = Enforce, StateId = 4, StateName = ASSIGNMENT_ENFORCE_SUCCESS   UpdatesDeploymentAgent

    En este momento, la implementación de actualizaciones de software se ha descargado y instalado correctamente en el cliente, y el proceso se ha completado.

Informes de mensajes de estado

Durante la fase de implementación, se generan varios mensajes de estado para indicar el estado actual de las actualizaciones y la propia implementación. Una vez que se generan estos mensajes de estado, se procesan de la manera que se describe en Flujo de datos de mensajería de estado.