Enjoy Sharing

Configuration Manager Client Package source version keeps incrementing/increasing causing disk space to fill up in schedule.box

The first time I realized the problem is when I found that my replication isn’t going too well between my CAS and Primary. I soon found out that my disk space has run out on the partition ConfigMgr was installed on. That might be causing problem with replication, but what is causing my disk to fill up? Checking folder-by-folder I then found the offending folder that is filling up my drive. It was Program Files\Microsoft Configuration Manager\inboxes\schedule.box specifically the ‘tosend’ folder.

I did also realize that my server is busy transferring files. This can be seen by looking at the sender.log. I soon noticed it was the ConfigMgr agent package file and can be seen in the monitoring workspace that it is in the midst of updating all the DPs. Shockingly I noticed the version number of the Configuration Manager Client Package has gone up close to 200, notice version 180 from the distmgr.log.

Found notification for package ‘CL100003’    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    7140 (0x1BE4)
Used 0 out of 3 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    7140 (0x1BE4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    6628 (0x19E4)
Starting package processing thread, thread ID = 0x2304 (8964)    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:53 AM    7140 (0x1BE4)
Starting package processing thread, thread ID = 0x1A60 (6752)    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    7140 (0x1BE4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    7140 (0x1BE4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<FQDN> SITE=CAS PID=2644 TID=8964 GMTDATE=Wed Sep 10 17:37:54.312 2014 ISTR0="Configuration Manager Client Package" ISTR1="CL100002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CL100002"    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
Start updating the package CL100002…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CL100002, Version=180, Status=2300    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<FWDN>SITE=CAS PID=2644 TID=6752 GMTDATE=Wed Sep 10 17:37:54.344 2014 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="CL100003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CL100003"    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Start updating the package CL100003…    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Taking package snapshot for package CL100002 from source \\<FQDN>\SMS_CAS\Client    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    8964 (0x2304)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CL100003, Version=180, Status=2300    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Taking package snapshot for package CL100003 from source \\<FQDN>\SMS_CAS\ClientUpgrade    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The size of package CL100003, version 180 is 1576 KBytes    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Successfully created RDC signatures for package CL100003 version 180    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Creating hash for algorithm 32780    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The hash for algorithm 32780 is D6279C75363ECFBE0F4A64447E472F512261393FFBE6246AB153ACEF41C53094    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The RDC signature hash for algorithm 32780 is 9CEFAE33CC2B4475D5B67C8C6046A48834B03C292B59C16222070B6161168017    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
STATMSG: ID=2376 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<FWDN> SITE=CAS PID=2644 TID=6752 GMTDATE=Wed Sep 10 17:37:54.600 2014 ISTR0="CL100003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CL100003"    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=CL100003, Version=180, Status=2376    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The source for package CL100003 has changed or the package source needs to be refreshed    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Adding these contents to the package CL100003 version 180.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
The Package Action is 1, the Update Mask is 32 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Use drive E for storing the compressed package.    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)
Successfully created/updated the package CL100003    SMS_DISTRIBUTION_MANAGER    9/11/2014 3:37:54 AM    6752 (0x1A60)

 

This happened during my hierarchy expansion from a standalone primary to a CAS and multiple primaries. The Configuration Manager Client Package though still the same packageID had its source path changed to the CAS server UNC path and that may have triggered a package update. Trying to stop the DP transfer by deleting the package or removing content didn’t work because it will be grayed out.

image

In order to be able to do that you need to go into SQL. First create 2 new packages for the Configuration Manager Client Package and Configuration Manager Client Upgrade Package. They will be having new package IDs. Note them down!

Then using the SQL Server Management Studio console find out what is your existing ClientDeploymentSettings. Enter the below statement in your new query window.

select * from CM_CAS.dbo.ClientDeploymentSettings

 

This wil return the result of your FullPackageID and UpgradePackageID. Next we will update it to the new packageID of the new packages you’ve just created. Use the below statements

update CM_CAS.dbo.ClientDeploymentSettings set FullPackageID = ‘<new package ID>’ where FullPackageID = ‘<old package ID>’

 

Now do the similar for the UpgradePackageID

update CM_CAS.dbo.ClientDeploymentSettings set UpgradePackageID = ‘<new upgrade package ID>’ where UpgradePackageID = ‘<old upgrade package ID>’

 

After this you can go ahead and remove the package from the DPs. It will not be grayed out anymore.

If this still does not solve your problem especially after a reboot (this might re-occur after a reboot), investigating further you will find this in your hman.log.

HandleRBACPermissions : Check if there is request.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
End sync rbac permissions.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Update site server active directory informtion into DB    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Handle auto-upgrade client configuration changes    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Update auto-upgrade client configurations    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: client.acu file was found. client upgrade packages need to be updated.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Current client upgrade settings are: FullClientPackageID=CL100002, ClientUpgradePackageID=CL100003, ClientUpgradeProgramName=Configuration Manager Client Upgrade Program, ClientUpgradeAdvertisementID=CL120000, ClientUpgradeVersion=5.00.7958.1000.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully requested package CL100002 to be updated from its source.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully requested package CL100003 to be updated from its source.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully updated packages CL100002 and CL100003    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Client upgrade command line will be modified to ccmsetup.exe /AutoUpgrade /UpgradePackageVersion:240    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
Updating supported platforms for auto-upgrade client program.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully updated program Configuration Manager Client Upgrade Program of package CL100003 with new command line: ccmsetup.exe /AutoUpgrade /UpgradePackageVersion:240    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)
INFO: Successfully modified the command line for client upgrade program Configuration Manager Client Upgrade Program in package CL100003.    SMS_HIERARCHY_MANAGER    9/11/2014 2:12:02 PM    5160 (0x1428)

 

Realize that client.acu file is found in the Program Files\Microsoft Configuration Manager\inboxes\hman.box path and that is what is instructing the package to be updated. It is a file with 0kb. So go ahead and delete that file from your server and that should stop your Configuration Manager Client Package from wrongly self updating itself.

 

 

 

Enjoy!!!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s