Change SMS Cache Size

[phil@abtec.net]

I need to make the SMSCACHESIZE larger due to large software installations such as adobe creative suite. I have tried adding the option smscachesize=10240 to make it 10gb but when i check the cache size after deployment it is still 5120.

 

i have tried editing the program and putting the switch at the end of the ccmsetup.exe and also in the installation options in the Task Sequence

 

but both do not work

 

any help would be great.

 

Thanks

 

Phil

[Peter van der Woude]

Do you need to change the cache for new clients, then you need to use the SMSCACHESIZE parameter during the installation. Otherwise you need to either create a script to change is, or use a tool (like right-click) to change the size.

[Vortex]

Sorry to jump on this thread, but how exactly do I set the sms chache size within a task sequence?

 

The task Sequence is deployed to new machines and installs windows then the client, followed by some applications however the cache is not large enough to install all of the applications.

 

I have set SMSCACHESIZE=10240 within the task sequence editor, under the "Setup windows and configuration manager" task. I placed this setting within the properites bo of the client package. However it doesnt seem to work and the chache is still the default size.

[Rocket Man]

You could manually do it by opening up the ConfigMgr Client from the CTRL Panel on the machines...Cache tab and edit it's size there.....or as Peter said the Right click tools gives extra functionality...one been able to resize the cache remotely (once the target machines are active and switched on)

 

 

Rocket Man

[Vortex]

But i want to install applications at windows 7 deploy at the same time, and to do this i need to set the cache before the applications are installed.

 

I need a way of automaticaly setting the cache size within the task sequence as windows 7 is deployed. otherwise my task sequence fails due to space requirements. If you understand.

[Rocket Man]

What applications are failing?

 

Im not sure what you mean now.....I install all my packages at OSD time with a default TS configuration....Office2010, Adobe*3, Ie9, java, updates..VS2010, CS6 and more without having to change any size of cache!! (5120 default).

 

 

 

But then I am running directly from DP(using BITS) and not downloading.

 

Rocket Man

[Vortex]

 

But then I am running directly from DP(using BITS) and not downloading.

 

Rocket Man

 

How do I set it to run directly from DP without downloading ?

 

Is this practical in the long term (say 30 machines at once) will it cause heavy network traffic?

 

Thanks.

[Rocket Man]

For starters you must be running a default TS and choosing to download all content first (This is much heavier and taxing on your network..never mind the fact it takes 3 times longer for OSD to be accomplished).

 

Have you distributed your software and configured it to copy to a content share on DP?

At TS deploy time at the DP settings part there should be a drop down box which allows you to access content directly from DP!!

 

BITS will be used when choosing this which is Background Intelligent transfer System which is less taxing on the network when it comes to OSD or software deployment!

 

 

 

One more thing you have not by any chance specified to persist client cache when you created your software packages(not a good idea if you did for packages so large...this should only be done if the software has to run multiple times like antivirus or power management software to shut machines down etc.)..

 

Rocket Man

[Vortex]

OK let me start again,

 

I have a task sequence that images a new machine with windows 7 x86.

 

 

This is the software that is set to install after the OS and after the Client, these all work tested through software center ( Adobe CS3 only works when increasing the cache size beyond default even though the folder is only 1.8GB).

 

 

 

Ok so now here is the settings i have for the client install stage:

 

 

 

However this highlighted property does not seem to work. Any ideas? If it did work then there would be no problem.

 

There must be a simple way to set the cache size at install during the task sequence? or at least before the application install phase.

[Rocket Man]

try this:

http://www.myitforum...ze-m195932.aspx

 

 

Create the script.vbs...create a package from it and slot it in directly after your setup windows and Configuration component of the TS

 

 

Rocket Man

[Vortex]

try this:

http://www.myitforum...ze-m195932.aspx

 

 

Create the script.vbs...create a package from it and slot it in directly after your setup windows and Configuration component of the TS

 

 

Rocket Man

 

That script is for 2007, but this is what i need i think, I just need to find one that will work with 2012.

[ozthe2]

Here's how I did it in Config Manager 2012: http://fearthemonkey.co.uk/how-to-change-the-configuration-manager-2012-cache-size-using-the-application-method/

[Peter33]

You can do that also with a simple powershell line.

 

powershell -executionpolicy bypass -command $sms=gwmi -namespace root\ccm\softmgmtagent -class cacheconfig;$sms.size = "10000";$sms.put()

 

This needs a restart of the ccmexec service though. So reboot the Client just after Setting the Cache size.

[ozthe2]

I love powershell! PS > Everyone needs to learn to use it. I'm using Powershell on a near daily basis now.

 

I have not looked into seeing what powershell cmdlets are available for config manager yet however I can say that my (non-powershell) method does not require a reboot of any kind. This is useful if you are about to deploy a large app. You can deploy the cache size change as a pre-req of the large app deployment.

[mark6960]

by default a task sequence does not use the ccmcache folder to deploy applications - it saves the locally to an auto created folder on the root of C:\ called SMS_tasksequence (or something like that). CCM cache only comes into play with individual applications and "most" are going to be under 5GB until you get into applications like autocad or some of the Microsoft developer tools. Be sure to check the smsts.log file which will give you why something is erroring out.

[n00blar]

Sorry to resurrect this thread, but I have the exact same issue and I'm still unable to change cache size from within a task sequence.

 

I know I can do it as a package, an app, etc, etc, but I want to do it as part of a task sequence. I even read a MS Blog that says that it's supposed to work using SMSCACHESIZE=10240 in Setup Windows and ConfigMgr section, but it just doesn't work.

 

Has anyone been able to get this to work from a task sequence?

 

Thanks!!

 

 

OK let me start again,

I have a task sequence that images a new machine with windows 7 x86.



This is the software that is set to install after the OS and after the Client, these all work tested through software center ( Adobe CS3 only works when increasing the cache size beyond default even though the folder is only 1.8GB).




Ok so now here is the settings i have for the client install stage:




However this highlighted property does not seem to work. Any ideas? If it did work then there would be no problem.

There must be a simple way to set the cache size at install during the task sequence? or at least before the application install phase.

[Config_Mgr_noob]

I'm currently having the same issue but with a VBS script I found online that will increase the cache size. However, up until a week ago I'm receiving an Access Denied error message within the smsts.log of the client PC being imaged. From what I'm gathering, it has to do with the directory that mark6960 indicated. Mark, why would I receive an Access Denied error to that directory since I am able to deploy apps and images using my network access account? What kind of permissions does the account require to run any vbs or application in the directory located in C:\sms_tasksequence?