In System Center Configuration Manager 2007, there was sometimes a challenge to find to correct Installation properties, most of the problem came with the patch files. But in 2012 we don’t have to install msp-files yet. But even then, a friend of mine considered a problem with the new apllication model in SCCM 2012. When you use apllications, and create deployments on collections, there isn’t an option to tell “Run from Distribution Point”, as it is still on Deployments of the 2007 style Packages. So if your SCCM Application Deployment Type which should run on the client, is larger than the default SCCM Client cache size of 5120MB, the download and installation will fail.
So I use for my client installation the following Installation properties (Client Push):
SMSSITECODE=H05 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=FQDN-MP FSP=FQDN-FSP
With SMSCACHEFLAGS you can configure different options, refer to http://technet.microsoft.com/en-us/library/gg699356.aspx for a full list of client installation properties. So I only allow a NTFS Drive for the client cache (NTFSONLY) and the cache will use a maximum of 10 percent of the harddisc (PERCENTDISKSPACE), those 10% are configrued with SMSCACHESIZE. If SMSCACHEFLAGS=PERCENTDISKSPACE is not used, you can specify a amount of MB, but at least 5120MB, for the SCCM cache in the property SMSCACHESIZE. You can configure the client installation settings here:
The only difference of the operting system deployment installation properties is, that no SMSSITECODE must to be used:
SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=FQDN-MP FSP=FQDN-FSP
To uninstall a SCCM 2012 client from a Workstation or Server System, just run “ccmsetup.exe /uninstall”, ccmsetup.exe resides usually in “%windir%ccmsetup”
Hope this helps, any suggestions or your experience with client installation, feel free to leave a comment.
4 thoughts on “SCCM 2012 – Client Installation properties”
How would this handle the uninstall of the client from the site server thatr is also a Management Point. In prev versions of sccm it would whack the MP, unless a special switch was used.
Very interresting blog!
Do you know a way how you could cleanup the cache folder regularly?
I found a VBScript which does it using more or less “UIResource.UIResourceMgr.GetCacheInfo().GetCacheElements”. But this Script only seems to work when launched by a logged in Administrator. A normal User hasn’t enough rights and starting as a StartupScript doen’t work too.
Thanks and regards,
You can achieve this Goal by creating a scheduled Task (Old School 😉 )
Or do it with a Configruation Item, where you also can automatically remediate, when a condition is found, which you decided to clean the Cache.
BTW: The WMI Namespace rootccmsoftmgmtagent and the class CacheInfoEx could help you to get the used space.
thanks for the interesting info,
I was looking for SCCM client installation parameters and reached your blog. (thought it might be interesting info for you).