Deploying ccmcache location and size changes

I was working on some deployments today and discovered a large chunk of systems that have had ccmcache location set to c:\ccm\cache and size set to 250MB since I migrated to a Current Branch hierarchy.

I did not want to deploy something to all systems in the target collection for this deployment as the ccmexec service would have to cycle, and I’m not sure what would happen if an install were in progress when that happens. My other option would have been to create a collection with only the machines failing with the same “not enough temporary space is reserved” message, and deploy a fix app/package to it.

In the end, I had the list of clients with “not enough space reserved” and just ran the following from my system:

[code language=”powershell”]Invoke-Command -ComputerName PCNAMEHERE,ANOTHERPC,ANDANOTHER,YETANOTHER -ScriptBlock { $Cache = Get-WmiObject -Namespace ‘ROOT\CCM\SoftMgmtAgent’ -Class CacheConfig
$Cache.Location = ‘C:\Windows\ccmcache’
$Cache.Size = ‘5120’
$Cache.Put()
Restart-Service -Name CcmExec }
[/code]

In the future, I’ll probably look at spending some time creating a configuration item with this script utilized for remediation.



Copyright 2016-2019. All rights reserved.

Posted November 26, 2016 by Chris in category "Enterprise Application Deployment", "System Center Configuration Manager

2 COMMENTS :

  1. Pingback: Deploying ccmcache location and size changes, part two. | sccmchris

  2. Pingback: Scripting bulk client actions. | sccmchris

Leave a Reply

Your email address will not be published. Required fields are marked *