Change the location of the SMSPKG folder (SMS_CPSx$ share)

With ConfigMgr 2007, I could specify the drive for the distribution point to store compressed package data (the "SMSPKG") folder before I created any packages and it would get created on that drive.  However, this functionality seems to be missing in ConfigMgr 2012.  At the point of adding the distribution point role, I can choose where ConfigMgr will decompress content to (automatic, c:, d:, e: etc.) but I just leave this as automatic and control it using the no_sms_on_drive.sms file.

So, how can I get ConfigMgr 2012 to use a different drive of my choice for the SMSPKG folder?

Just to be clear, I am NOT talking about the SMSPKGC, SMSPKGD folders, I am talking about the location where PCK and delta files get created - at the moment, it seems hardcoded to be created on the same drive as InstallDir - which is not good for us.

Andy

August 15th, 2012 9:57am

It should use the same drive as the DP. I think if you add the no_sms_on_drive.sms file after you have sent packages to the DP there's a little more too it but I can't recall what.


Free Windows Admin Tool Kit Click here and download it now
August 15th, 2012 12:16pm

A note here on PCK files in 2012: they are temporary in nature only and *not* persisted on the source or destination sites so this is not nearly as big of a deal in 2012 and thus you shouldn't have to micro-manage its location.

August 15th, 2012 1:40pm

I know this does help you in any way but just as a side note; Why would anyone ever install ConfigMgr on the C drive????
Free Windows Admin Tool Kit Click here and download it now
August 19th, 2015 10:00am

I think I disagree with that.  On a Primary Site Server where the application is installed to C: and ContentLib is directed to E:, I believe it is still important to have control where the SMSPKG folder decides to live.  In my case (the above example) I find it silly to not have greater control on where these temp files are generated as the drive may not be sized to handle it.  Specifically when the packages are very large.  Also worth mentioning is that in my configuration, the primary and DP roles are split onto different systems.  Also, I have the, NO_SMS_ON_DRIVE.SMS flag set on C: and the SMSPKG "temp" folder still got generated there.
August 19th, 2015 2:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics