The end to end flow of distributing a ConfigMgr 2007 package to a standard DP and a Branch DP in a single site environment

The end to end flow of distributing a ConfigMgr 2007 package to a standard DP and a Branch DP in a single site environment

  • Comments 9
  • Likes

imageHi folks, my name is Yuvaraj Tamil Mani and I’d like to take a minute and share some information about the flow of package distribution to a standard Distribution Point (DP) and a Branch Distribution Point (BDP).

When a package is sent to a standard DP, the Distribution Manager component connects to the SMSPKGdriveletter$ of the DP, copies the package contents, and updates the package status in the database. However, when a package is sent to a branch distribution point, the flow is different and I have tried to explain it in detail with log snippets as you’ll see below.

NOTE The site server logs are SQL enabled; MP and client logs are Verbose and debug enabled.

The following are the details that I used in the examples:

  • Package ID : CS10001E
  • Site server/MP/DP : CS1SRV.NINJAS.COM
  • BDP Name : CS1XP.NINJAS.COM
 
Flow of sending a package to a standard Distribution Point:

The following are the actions performed when you send a package to a standard DP.

1. When you add a package to a standard Distribution Point, the distmgr component is notified with the packageID.PKN in inboxes\distmgr.box.

2. The distmgr component begins the processing of the package with STATMSG 2300:

STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CS1SRV SITE=CS1 PID=4604 TID=5720 GMTDATE=Fri Jan 13 22:36:47.610 2012 ISTR0="Test BDP 2" ISTR1="CS10001E" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CS10001E" SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 5720 (0x1658)

No action specified for the package CS10001E. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 5720 (0x1658)

Start adding package to server ["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\... SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 5720 (0x1658)

["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\ is NOT a Branch DP SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 5720 (0x1658)

3. Distmgr establishes a connection to the DP and checks for the SMSPKGdriveletter$ share:

Established connection to ["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 3272 (0x0CC8)

Signature share exists on distribution point path MSWNET:["SMS_SITE=CS1"]\\CS1SRV\SMSSIG$\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 3272 (0x0CC8)

The distribution point ["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\ doesn't point to an existing path. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 3272 (0x0CC8)

The best drive on the distribution point is C:\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 3272 (0x0CC8)

The best drive for installing package on the distribution point ["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\ is C:\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 3272 (0x0CC8)

Share SMSPKGC$ exists on distribution point ["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:47 AM 3272 (0x0CC8)

4. It creates a subdirectory with the package ID in the SMSPKGC$ share:

Attempting to create subdirectory CS10001E under the export. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:48 AM 3272 (0x0CC8)

The export is accessible. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:48 AM 3272 (0x0CC8)

Successsfully created the package directory CS10001E\ under the export. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:48 AM 3272 (0x0CC8)

Successfully created sub directory CS10001E off MSWNET:["SMS_SITE=CS1"]\\CS1SRV\SMSPKGC$\CS10001E\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:48 AM 3272 (0x0CC8)

5. Distmgr connects to the packageID folder it created and checks if the drive has the enough free space to copy the package contents:

Attempting to make an accessible connection to MSWNET:["SMS_SITE=CS1"]\\CS1SRV\SMSPKGC$\CS10001E\, get its NOS path, and get its number of free bytes. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

Established connection to MSWNET:["SMS_SITE=CS1"]\\CS1SRV\SMSPKGC$\CS10001E\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

Getting the number of free bytes. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

The number of free K bytes 40105592 SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

Successfully made an accessible connection, got a NOS path, and, if requested, got the number of free bytes at this location. SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

6. Distmgr sets the security on the \\ CS1SRV\SMSPKGC$\CS10001E folder and copies the package contents to that folder from the package source. It also copies the signature file (TAR file) to the SMSSIG$ share and sets the security on that folder:

Successfully set access security on MSWNET:["SMS_SITE=CS1"]\\CS1SRV\SMSPKGC$\CS10001E\ for package CS10001E SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

GetPackageSignature() called for package CS10001E with version 1. UnpackedSignature = 0 SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

Copying C:\package source\Test BDP 2\CcmTools.msi to C:\SMSPKGC$\CS10001E\CcmTools.msi, OK SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

RDC:Successfully copied package signature file C:\SMSPKGSIG\CS10001E.1.tar to \\CS1SRV\SMSSIG$\\CS10001E.1.tar SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

RDC:Successfully set access security on \\CS1SRV\SMSSIG$\\CS10001E.1.tar for package CS10001E signature file SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

Successfully copied package CS10001E from C:\package source\Test BDP 2\ to MSWNET:["SMS_SITE=CS1"]\\CS1SRV\SMSPKGC$\CS10001E\ SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

7. Distmgr runs the following query to update the status in the pkgstatus table in SQL and raises a STATMSG 2330:

SQL>>>update PkgStatus set Status = 3, UpdateTime = "01/14/2012 04:06:50", Location = "MSWNET:[""SMS_SITE=CS1""]\\CS1SRV\SMSPKGC$\CS10001E\", ShareName = "", HTTPUrl = "http://CS1SRV/SMS_DP_SMSPKGC$/CS10001E/", SourceVersion = 1, State = 0, SigURL = "http://CS1SRV/SMS_DP_SMSSIG$/CS10001E.1.tar", SigLocation = "MSWNET:[""SMS_SITE=CS1""]\\CS1SRV\SMSSIG$\CS10001E.1.tar" where ID = "CS10001E" and Type = 2 and Personality = 0 and SiteCode = "CS1" and PkgServer = "[""Display=\\CS1SRV\""]MSWNET:[""SMS_SITE=CS1""]\\CS1SRV\" SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=CS1SRV SITE=CS1 PID=4604 TID=3272 GMTDATE=Fri Jan 13 22:36:50.954 2012 ISTR0="CS10001E" ISTR1="["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CS10001E" AID1=404 AVAL1="["Display=\\CS1SRV\"]MSWNET:["SMS_SITE=CS1"]\\CS1SRV\" SMS_DISTRIBUTION_MANAGER 1/14/2012 4:06:50 AM 3272 (0x0CC8)

 

Flow of sending a package to a Branch Distribution point:

The following are the actions performed when you send a package to a Branch Distribution Point:

1. When we add a BDP to a package, the distmgr component checks the DPID in distributionpoints table to determine whether it is a BDP.

SQL>>>select DPID, NALPath from DistributionPoints where NALPath = '["Display=\\CS1XP\"]MSWNET:["SMS_SITE=CS1"]\\CS1XP\' and IsPeerDP = 1 1/14/2012 4:09:57 AM 6748 (0x1A5C)

DPID 11 - NAL Path ["Display=\\CS1XP\"]MSWNET:["SMS_SITE=CS1"]\\CS1XP\ is a Branch DP 1/14/2012 4:09:57 AM 6748 (0x1A5C)

2. Distmgr component inserts an entry into the pkgstatus table with status 0 for the BDP:

SQL>>>insert PkgStatus (ID, Type, SourceVersion, Personality, Location, SiteCode, PkgServer, ShareName, HTTPUrl, Status, State, SigLocation, SigURL, UpdateTime) values ("CS10001E", 2, 1, 0, "", "CS1", "[""Display=\\CS1XP\""]MSWNET:[""SMS_SITE=CS1""]\\CS1XP\", "", "", 0, 2, "", "", "01/14/2012 04:09:57") 1/14/2012 4:09:57 AM 6748 (0x1A5C)

3. Distmgr updates the peerdppkgmap table which has the list of all packages sent to branch distribution points:

SQL>>>insert PeerDPPkgMap (PkgID, DPID) values ('CS10001E', 11) 1/14/2012 4:09:58 AM 6748 (0x1A5C)

SQL>>>>> Done. 1/14/2012 4:09:58 AM 6748 (0x1A5C)

Successfully updated PeerDPPkgMap for DPID 11 and PkgID CS10001E. 1/14/2012 4:09:58 AM 6748 (0x1A5C)

4. Distmgr sends a trigger to policy provider by a file notification in inboxes\policypv folder:

Created policy provider trigger for ID CS10001E 1/14/2012 4:09:58 AM 6748 (0x1A5C)

5. The policy provider creates a policy and policy assignment for the package. It also maps the resources to the policy:

Successfully created policy {133e16b6-e7f4-4a6a-833d-ec64703c884a} and policy assignment {e79d710f-264a-4c1c-86c1-c6c5268a79ef} based on package CS10001E SMS_POLICY_PROVIDER 1/14/2012 4:10:03 AM 3204 (0x0C84)

Successfully updated policy and policy assignment based on package CS10001E SMS_POLICY_PROVIDER 1/14/2012 4:10:04 AM 3204 (0x0C84)

Beginning to update the resource to policy mapping... SMS_POLICY_PROVIDER 1/14/2012 4:10:04 AM 3204 (0x0C84)

Successfully updated the resource to policy mapping for 1 resources SMS_POLICY_PROVIDER 1/14/2012 4:10:09 AM 3204 (0x0C84)

6. When the branch distribution point checks the management point for policy, it receives the policy assignment and downloads the policy:

Total 1 PolicyAssignment(s) found. PolicyAgent_ReplyAssignments 1/15/2012 11:50:23 AM 1536 (0x0600)

Validating PolicyAssignment '{e79d710f-264a-4c1c-86c1-c6c5268a79ef}'. PolicyAgent_ReplyAssignments 1/15/2012 11:50:23 AM 1536 (0x0600)

Compiling policy '{133e16b6-e7f4-4a6a-833d-ec64703c884a}' version '1.00' from 'SMS:CS1' (2012-01-14 04:10:09.463) PolicyAgent_ReplyAssignments 1/15/2012 11:50:24 AM 1536 (0x0600)

Starting download of policy 'CCM_Policy_Policy4.PolicyID="{133e16b6-e7f4-4a6a-833d-ec64703c884a}",PolicySource="SMS:CS1",PolicyVersion="1.00"' from 'http://CS1SRV.NINJAS.COM/SMS_MP/.sms_pol?{133e16b6-e7f4-4a6a-833d-ec64703c884a}.1_00' PolicyAgent_ReplyAssignments 1/15/2012 11:50:24 AM 1536 (0x0600)

Download of policy 'CCM_Policy_Policy4.PolicyID="{133e16b6-e7f4-4a6a-833d-ec64703c884a}",PolicySource="SMS:CS1",PolicyVersion="1.00"' started (DTS job ID: '{5C352D39-D872-45B8-85B5-6401074D6ED1}') PolicyAgent_ReplyAssignments 1/15/2012 11:50:24 AM 1536 (0x0600)

Successfully initiated download of policy 'CCM_Policy_Policy4.PolicyID="{133e16b6-e7f4-4a6a-833d-ec64703c884a}",PolicySource="SMS:CS1",PolicyVersion="1.00"' PolicyAgent_ReplyAssignments 1/15/2012 11:50:24 AM 1536 (0x0600)

Starting download of policy 'CCM_Policy_Policy4.PolicyID="{133e16b6-e7f4-4a6a-833d-ec64703c884a}",PolicySource="SMS:CS1",PolicyVersion="1.00"' from 'http://CS1SRV.NINJAS.COM/SMS_MP/.sms_pol?{133e16b6-e7f4-4a6a-833d-ec64703c884a}.1_00' PolicyAgent_ReplyAssignments 1/15/2012 11:50:24 AM 1536 (0x0600)

Download of policy CCM_Policy_Policy4.PolicyID="{133e16b6-e7f4-4a6a-833d-ec64703c884a}",PolicySource="SMS:CS1",PolicyVersion="1.00" completed (DTS Job ID: {5C352D39-D872-45B8-85B5-6401074D6ED1}) PolicyAgent_PolicyDownload 1/15/2012 11:50:27 AM 2536 (0x09E8)

The policy assignment ID and policy ID in the policyagent.log matches with the ID’s in the policypv.log.

7. Now the peerdpagent creates a job for the package CS10001E for downloading and processing the package content:

PDP_CreateJobData PeerDPAgent 1/15/2012 11:50:27 AM 3232 (0x0CA0)

Created Branch DP job {36676F89-F7EB-4055-9AF5-269FBAC38D58} for package CS10001E PeerDPAgent 1/15/2012 11:50:28 AM 3232 (0x0CA0)

NOTE Each package targeted to the BDP has a job in the following location on WMI:  CCM_PeerDP_Job class under root\ccm\peerdpagent

8. The PeerDPagent checks whether the content for the package is prestaged:

CPDPJob::CheckForPreStagedPkg PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

Checking C:\SMSPKGC$\CS10001E for prestaged CS10001E package PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

Package CS10001E has not been prestaged PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

9. Peerdpagent checks for the BDPTmpWrkFldr directory and creates a temp folder inside it for download:

Directory 'C:\BDPTmpWrkFldr\' already exists. PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

Temp dowload Path: 'C:\BDPTmpWrkFldr\PDP119.tmp' PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

Disconnected 0 users from directory C:\BDPTmpWrkFldr\PDP119.tmp. PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

10. Peerdpagent calls the content transfer manager to start the download:

Calling DownloadContent, the type is 0, priority 2 PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of PDPDownloadStartedEvent

{

ClientID = "GUID:9B783DCB-5511-4C76-864D-01E57731172E";

DateTime = "20120115062028.451000+000";

MachineName = "CS1XP";

PackageID = "CS10001E";

ProcessID = 1920;

SiteCode = "CS1";

SourceVersion = 1;

ThreadID = 2536;

};

PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

11. The content transfer manager completes the download and notifies the peerdpagent:

CTM job {D8718FED-D7A6-439F-8F3E-4B1389B590C8} successfully processed download completion. ContentTransferManager 1/15/2012 11:50:32 AM 1536 (0x0600)

CCTMJob::EvaluateState(JobID={D8718FED-D7A6-439F-8F3E-4B1389B590C8}, State=Success) ContentTransferManager 1/15/2012 11:50:32 AM 2604 (0x0A2C)

CCTMJob::EvaluateState(JobID={D8718FED-D7A6-439F-8F3E-4B1389B590C8}, State=Complete) ContentTransferManager 1/15/2012 11:50:32 AM 2604 (0x0A2C)

12. We can find the notification from CTM in the Peerdpagent.log:

CPDPJob::ProcessProgress PeerDPAgent 1/15/2012 11:50:28 AM 2536 (0x09E8)

Download complete for CTM job {D8718FED-D7A6-439F-8F3E-4B1389B590C8}, downloaded KB 1058 PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

Package CS10001E in state 'DownloadComplete'. PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

instance of PDPDownloadSuccessEvent

{

ClientID = "GUID:9B783DCB-5511-4C76-864D-01E57731172E";

DateTime = "20120115062032.654000+000";

MachineName = "CS1XP";

PackageID = "CS10001E";

ProcessID = 1920;

SiteCode = "CS1";

SourceVersion = 1;

ThreadID = 2536;

};

13. Peerdpagent checks the hash for the package and verifies it with the hash that it got through policy from the MP:

Package CS10001E in state 'HashContentSuccess'. PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

Hash verified for package CS10001E. PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

14. It creates a folder under SMSPKGdriveletter$ with the package ID and copies the content from the temp directory to the PackageID folder and completes the provisioning:

Directory 'C:\SMSPKGC$' already exists. PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

Disconnected 0 users from directory C:\BDPTmpWrkFldr\PDP119.tmp. PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

Package CS10001E in state 'HostingComplete'. PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

Package CS10001E provisioned at C:\SMSPKGC$\CS10001E PeerDPAgent 1/15/2012 11:50:32 AM 2536 (0x09E8)

instance of PDPProvisionSuccessEvent

{

ClientID = "GUID:9B783DCB-5511-4C76-864D-01E57731172E";

DateTime = "20120115062032.998000+000";

MachineName = "CS1XP";

PackageID = "CS10001E";

ProcessID = 1920;

Share = "C:\\SMSPKGC$\\CS10001E";

SiteCode = "CS1";

SourceVersion = 1;

ThreadID = 2604;

};

15. Peerdpagent raises a status 3 (Installed) and you can see the message in peerdpagent.log:

StatusFile message body for package 6271482 :

<PeerDPDownloadStatus><ClientID>GUID:9B783DCB-5511-4C76-864D-01E57731172E</ClientID><Msg PkgID="CS10001E" Location="MSWNET:[&quot;SMS_SITE=CS1&quot;]\\CS1XP\SMSPKGC$\CS10001E\" SiteCode="CS1" Type="2" SourceVersion="1" Personality="0" Status="3" State="3" UpdateTime="1326608432" PackageServer="[&quot;Display=\\CS1XP\&quot;]MSWNET:[&quot;SMS_SITE=CS1&quot;]\\CS1XP\" ShareName="SMSPKG" HttpUrl=""/></PeerDPDownloadStatus> PeerDPAgent 1/15/2012 11:50:32 AM 2604 (0x0A2C)

16. The above status message is sent to the MP_Relayendpoint by ccmexec component:

OutgoingMessage(Queue='mp_mp_relayendpoint', ID={5C3FFB3D-A554-4E4D-AE80-FA65960F2B7F}): Delivered successfully to host 'CS1SRV.NINJAS.COM'. CcmExec 1/15/2012 11:50:33 AM 1536 (0x0600) 

17. The MP_relay.log shows that it received the exact status message(point 15) sent by ccmexec(point 16):

Message Body :

<PeerDPDownloadStatus><ClientID>GUID:9B783DCB-5511-4C76-864D-01E57731172E</ClientID><Msg PkgID="CS10001E" Location="MSWNET:[&quot;SMS_SITE=CS1&quot;]\\CS1XP\SMSPKGC$\CS10001E\" SiteCode="CS1" Type="2" SourceVersion="1" Personality="0" Status="3" State="3" UpdateTime="1326608432" PackageServer="[&quot;Display=\\CS1XP\&quot;]MSWNET:[&quot;SMS_SITE=CS1&quot;]\\CS1XP\" ShareName="SMSPKG" HttpUrl=""/></PeerDPDownloadStatus> MP_RelayEndpoint 1/15/2012 11:50:33 AM 1980 (0x07BC)

18. The MP_relay notifies the distmgr component by dropping a STA file in the inboxes\distmgr.box\INCOMING folder:

Inv-Relay Task: Processing message body MP_RelayEndpoint 1/15/2012 11:50:33 AM 1980 (0x07BC)

Relay: FileType= STA MP_RelayEndpoint 1/15/2012 11:50:33 AM 1980 (0x07BC)

Relay: Outbox dir: C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\incoming MP_RelayEndpoint 1/15/2012 11:50:33 AM 1980 (0x07BC)

19. The distmgr component wakes up and updates the pkgstatus table with status 3 (Installed) and deletes the STA file:

Processing incoming file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\692QVRQ1.STA. SMS_DISTRIBUTION_MANAGER 1/15/2012 11:50:38 AM 4744 (0x1288)

SQL>>>update PkgStatus set Status = 3, UpdateTime = "01/15/2012 11:50:32", Location = "MSWNET:[""SMS_SITE=CS1""]\\CS1XP\SMSPKGC$\CS10001E\", ShareName = "SMSPKG", HTTPUrl = "", SourceVersion = 1, State = 3, SigURL = "", SigLocation = "" where ID = "CS10001E" and Type = 2 and Personality = 0 and SiteCode = "CS1" and PkgServer = "[""Display=\\CS1XP\""]MSWNET:[""SMS_SITE=CS1""]\\CS1XP\" SMS_DISTRIBUTION_MANAGER 1/15/2012 11:50:38 AM 4744 (0x1288)

Successfully update the package status SMS_DISTRIBUTION_MANAGER 1/15/2012 11:50:38 AM 4744 (0x1288)

Successfully delete package status file C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\692QVRQ1.STA SMS_DISTRIBUTION_MANAGER 1/15/2012 11:50:38 AM 4744 (0x1288)

20. The following 3 status messages from peerdpagent are uploaded to the MP_Statusreceiver by ccmexec. These 3 events are present in the peerdpagent.log:

PDPDownloadStartedEvent

PDPDownloadSuccessEvent

PDPProvisionSuccessEvent

OutgoingMessage(Queue='mp_statusreceiver', ID={794CCBEB-50F8-4FBC-967F-1729CB816965}): Delivered successfully to host 'CS1SRV.NINJAS.COM'. CcmExec 1/15/2012 11:50:33 AM 2604 (0x0A2C)

21. MP_statusreceiver receives the status and puts the .SVF files into the inboxes\statmgr.box\statmsgs folder:

Mp Status: processing event done. MP_StatusManager 1/15/2012 11:50:28 AM 1980 (0x07BC)

MP Status: SVF file written successfully to "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\YMUE4GZ2.SVF" MP_StatusManager 1/15/2012 11:50:28 AM 1980 (0x07BC)

MP Status: SVF file written successfully to "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\K5XATWID.SVF" MP_StatusManager 1/15/2012 11:50:32 AM 1980 (0x07BC)

MP Status: SVF file written successfully to "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\42FKA9TO.SVF" MP_StatusManager 1/15/2012 11:50:33 AM 1980 (0x07BC)

Mp StatusForwarder done, hr=0 MP_StatusManager 1/15/2012 11:50:33 AM 1980 (0x07BC)

22. The Statmgr component reads the .SVF files, deletes the files and inserts the status into the database by running the 3 following stored procedures:

sp_InsStatusMessage

sp_InsStatusMessageInsStr

sp_InsStatusMessageAttribute

Read 1 status messages from file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\YMUE4GZ2.SVF". SMS_STATUS_MANAGER 1/15/2012 11:50:28 AM 2080 (0x0820)

Deleted file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\YMUE4GZ2.SVF". SMS_STATUS_MANAGER 1/15/2012 11:50:28 AM 2080 (0x0820)

Read 1 status messages from file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\K5XATWID.SVF". SMS_STATUS_MANAGER 1/15/2012 11:50:32 AM 2080 (0x0820)

Deleted file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\K5XATWID.SVF". SMS_STATUS_MANAGER 1/15/2012 11:50:32 AM 2080 (0x0820)

Read 1 status messages from file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\42FKA9TO.SVF". SMS_STATUS_MANAGER 1/15/2012 11:50:33 AM 2080 (0x0820)

Deleted file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs\42FKA9TO.SVF". SMS_STATUS_MANAGER 1/15/2012 11:50:33 AM 2080 (0x0820)

Beginning a 938-byte SQL transaction to insert 3 status messages and their 7 insertion strings and 6 attribute ID/value pairs into the database. SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

SQL>>>exec sp_InsStatusMessage 3,242142,'SMS Client',1073753174,0,'01/15/2012 06:20:28.451','CS1','','CS1XP','Peer DP Agent',1920,2536,258,30,242143,'SMS Client',1073753175,0,'01/15/2012 06:20:32.654','CS1','','CS1XP','Peer DP Agent',1920,2536,258,30,242144,'SMS Client',1073753193,0,'01/15/2012 06:20:32.998','CS1','','CS1XP','Peer DP Agent',1920,2604,258,30 SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

SQL>>>>> Done. SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

SQL>>>exec sp_InsStatusMessageInsStr 7,242142,0,'CS10001E',242142,1,'1',242143,0,'CS10001E',242143,1,'1',242144,0,'CS10001E',242144,1,'1',242144,2,'C:\SMSPKGC$\CS10001E' SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

SQL>>>>> Done. SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

SQL>>>exec sp_InsStatusMessageAttribute 6,242142,408,'GUID:9B783DCB-5511-4C76-864D-01E57731172E','01/15/2012 06:20:28.451',242142,400,'CS10001E','01/15/2012 06:20:28.451',242143,408,'GUID:9B783DCB-5511-4C76-864D-01E57731172E','01/15/2012 06:20:32.654',242143,400,'CS10001E','01/15/2012 06:20:32.654',242144,408,'GUID:9B783DCB-5511-4C76-864D-01E57731172E','01/15/2012 06:20:32.998',242144,400,'CS10001E','01/15/2012 06:20:32.998' SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

SQL>>>>> Done. SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

Committed the transaction for asynchronous execution. We will poll every 250 milliseconds to determine the success or failure of the transaction. SMS_STATUS_MANAGER 1/15/2012 11:50:38 AM 2080 (0x0820)

22. You can see the above 3 status messages when you select Show messagesàAll on the package status node of the branch distribution point.

Yuvaraj Tamil Mani

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • This is great info...but could you put this into a diagram?  Or even use SuperFlows to present the information?

  • Good Stuff. But as Rod said, a diagram would be real cool.

  • I would imagine there must be dozens of diagrams on the web.

    I find this post quite useful because it shows us what a normal transaction looks like from the logging point of view. I don't troubleshoot diagrams--I troubleshoot running systems and log fishing is how you find the keys to the door.

  • Will be very helpful for troubleshooting..thanks mate!

  • This is very good articles for DP and BDP troubleshooting.

    Thanks Dear.................

  • Good one bro!! I was able to get a clear picture of how the Distribution flow works.. The logging point of view along with the flow was icing on the cake!!

  • An excellent way to put up the content with the details of the logging information. Great work !!

  • Good one Yuvi. Nice work

  • Thx for good description how flow goes. Can you verify any updates from SCCM 2012 if any. Just a quick note to each section.

    rgds, Mark