Application Deployment Policy Creation Flow
The application model of Configuration Manager 2012 uses Configuration Items. So the deployment and policy creation is a little different from the package creation. I am trying here to explain the flow of events which happens till the policy created on the server for a specific deployment.
When you create the deployment for an application the SMS provide inserts the data to the basic table and depending on the trigger, it will update the table change notification tables as any other process does.
The application details are as below which is was used
Application ID : ScopeId_2A471255-BD73-43F1-B1C0-613FC1A40798/Application_c637da7c-a62d-494e-a71e-b863b1a7196b/1
Application CI_ID : 224
Deployment ID : {D82B1B46-9636-4560-AE1A-22110840A7AC}
Assignment ID : 1677218
Collection SITEID: 00100015 ,
Collection ID : 14
Now the SMSDBMON comes to action
You would see the following changes and corresponding files getting dropped by SMSDBMON
RCV: INSERT on CI_CIAssignments for CIAssignmentNotify_iu [16777218 ][157236] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RCV: INSERT on RBAC_ChangeNotification for Rbac_Sync_ChangeNotification [431 ][157237] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RCV: INSERT on CrpChange_Notify for CrpChange_Notify_ins [14 ][157238] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RCV: UPDATE on CI_CIAssignments for CIAssignmentNotify_iu [16777218 ][157239] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RCV: UPDATE on CI_CIAssignments for CIAssignmentNotify_iu [16777218 ][157240] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RCV: UPDATE on CI_AssignmentTargetedCIs for CI_AssignmentTargetedCIs_ADDED [16777218 ][157241] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RCV: UPDATE on CI_AssignmentTargetedCIs for CI_AssignmentTargetedCIs_CIAMGR [16777218 ][157242] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RCV: INSERT on RBAC_ChangeNotification for Rbac_Sync_ChangeNotification [432 ][157243] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
CIA File is dropped in objgmgr.box
Modified trigger definition for Object Replication Manager[CIAssignmentNotify_iu]: table CI_CIAssignments(AssignmentID) on insert,update, file CIA in dir C:\Program Files\Microsoft Configuration Manager\inboxes\objmgr.box\ SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\objmgr.box\16777218.CIA [157236] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
RBC file is dropped for the RBAC on hman.box
Modified trigger definition for Hierarchy Manager[Rbac_Sync_ChangeNotification]: table RBAC_ChangeNotification(ID) on insert, file RBC in dir C:\Program Files\Microsoft Configuration Manager\inboxes\hman.box\ SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\hman.box\431.RBC [157237] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
CRP file for the policypv.box with <collectionID>.CRP
Modified trigger definition for Policy Targeting Evaluator[CrpChange_Notify_ins]: table CrpChange_Notify(CollectionID) on insert, file CRP in dir C:\Program Files\Microsoft Configuration Manager\inboxes\policypv.box\policytargeteval\ SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\policypv.box\policytargeteval\14.CRP [157238] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:56:58 PM 2536 (0x09E8)
There are few other files which get dropped bases on the CI Model, currently not taking in to consideration on this.
Now the Objreplmgr component then picks the CIA file and process the same
***** Processing Application Assignment {D82B1B46-9636-4560-AE1A-22110840A7AC} ***** SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:58 PM 2932 (0x0B74)
Deleting notification file C:\Program Files\Microsoft Configuration Manager\inboxes\objmgr.box\16777218.CIA SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:58 PM 2932 (0x0B74)
Found file trigger for C:\Program Files\Microsoft Configuration Manager\inboxes\objmgr.box\16777218.ADD SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:58 PM 2932 (0x0B74)
Info: Sussessfully get New CI Added notification file C:\Program Files\Microsoft Configuration Manager\inboxes\objmgr.box\16777218.ADD for CI Assignment Id 16777218, new CI added to this assignment SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:58 PM 2932 (0x0B74)
CI Assignment {D82B1B46-9636-4560-AE1A-22110840A7AC} has 1 Targeted CI(s) SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:58 PM 2932 (0x0B74)
PolicyID {D82B1B46-9636-4560-AE1A-22110840A7AC} PolicyVersion 1.00 PolicyHash SHA256:387A3415CDE9CE97E3213077D3DD3305FAF79085F5B156A4186F89740436CBF0 SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:58 PM 2932 (0x0B74)
Notifying policy provider about changes in policy content/targeting SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:59 PM 2932 (0x0B74)
Successfully created policy for CI Assignment {D82B1B46-9636-4560-AE1A-22110840A7AC} SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:59 PM 2932 (0x0B74)
Catalog evaluation: Getting model id for CI Assignment ID = 16777218 SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:59 PM 2932 (0x0B74)
Catalog table insert/update evaluation for Model Id 224 SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:56:59 PM 2932 (0x0B74)
Notifying policy provider about changes in policy content/targeting SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:00 PM 2932 (0x0B74)
Successfully updated Policy Targeting for CI Assignment {D82B1B46-9636-4560-AE1A-22110840A7AC} SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:00 PM 2932 (0x0B74)
Once this is completed you would find the CI_assignments table update
At the same time the CRP file which is dropped in the
Found 14.CRP SMS_POLICY_PROVIDER 8/23/2015 6:56:58 PM 2796 (0x0AEC)
Adding to delete list: C:\Program Files\Microsoft Configuration Manager\inboxes\policypv.box\policytargeteval\14.CRP SMS_POLICY_PROVIDER 8/23/2015 6:56:58 PM 2796 (0x0AEC)
--WaitForInboxChangeNotification SMS_POLICY_PROVIDER 8/23/2015 6:57:00 PM 2796 (0x0AEC)
Now the objereplmgr find the related CI items and do the needful. The relation is like this for CI_ID related to this application with CI_ID 224
Assigned CIs: [ 39 226 ] SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:00 PM 2932 (0x0B74)
Begin processing Assigned CI: [39] SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:00 PM 2932 (0x0B74)
39 Referenced VS CIs: [ ] SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:00 PM 2932 (0x0B74)
VersionInfo policy for CI 39 is Machine type SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:00 PM 2932 (0x0B74)
VersionInfo policy for CI 39 is Machine type SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
PolicyID Windows/All_Windows_Client_Server/VI/VS PolicyVersion 1.00 PolicyHash SHA256:2D646F6A67F56E7A13A7EBF26C6488EA4BB7D9C2AA83447DFC3B3647B9015243 SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
VersionInfo policy for CI 39 is up-to-date SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
VersionInfo policy Windows/All_Windows_Client_Server/VI/VS is up-to-date SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
Begin processing Assigned CI: [226] SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
Creating VersionInfo policy for CI 226 SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
Creating VersionInfo policy ScopeId_2A471255-BD73-43F1-B1C0-613FC1A40798/RequiredApplication_c637da7c-a62d-494e-a71e-b863b1a7196b/VI/VS SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
226 Referenced VS CIs: [ 224 225 149 122 133 ] SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:01 PM 2932 (0x0B74)
##############
##############
You would then see that the CI_assignment processing is done
Successfully updated CRCs for CI Assignment {D82B1B46-9636-4560-AE1A-22110840A7AC} SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:05 PM 2932 (0x0B74)
Successfully processed Application Assignment {D82B1B46-9636-4560-AE1A-22110840A7AC} SMS_OBJECT_REPLICATION_MANAGER 8/23/2015 6:57:05 PM 2932 (0x0B74)
We would then see that PAC file getting dropped by smsdbmon
Modified trigger definition for Policy Targeting Evaluator[PolicyAssignmentChg_Notify_iu]: table PolicyAssignmentChg_Notify(PADBID) on insert,update, file PAC in dir C:\Program Files\Microsoft Configuration Manager\inboxes\policypv.box\policytargeteval\ SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:57:13 PM 2536 (0x09E8)
SND: Dropped C:\Program Files\Microsoft Configuration Manager\inboxes\policypv.box\policytargeteval\16809612.PAC [157247] SMS_DATABASE_NOTIFICATION_MONITOR 8/23/2015 6:57:13 PM 2536 (0x09E8)
The policy provider then would see that processing
Found the certificate that matches the SHA1 hash. SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
Completed batch with beginning PADBID = 16809612 ending PADBID = 16809614. SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
--Process Policy Changes SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
Found some Policy changes, returning New LastRowversion=0x000000000035604C SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
Processing Updated Policies SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
Building Collection Change List from New and Targeting Changed Policies SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
--Update Policy Targeting Map SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
**** Evaluating Collection 14 for targeting changes **** SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
Advanced client policy changes detected for collection 14, *** 3 Added & 0 Deleted ***. SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
--Process Policy Targeting Map SMS_POLICY_PROVIDER 8/23/2015 6:57:19 PM 3720 (0x0E88)
You should then see the relation in respolicymap table for the all the members of the collection
Hope this Helps
Sudheesh Narayanaswamy