In this post, you will learn about SCCM Persist Content in the Client Cache Option. In Configuration Manager, If you configure the package properties to persist content in the client cache, the client does not automatically delete package content from the cache.
SCCM client cache is the location where it stores the packages on the client before any application runs from it. Cached content is not automatically deleted but remains in the cache for at least one day after the client used that content.
If the cache space is used by packages downloaded within the last 24 hours and the client must download new packages, you can either increase the cache size or choose the option to delete persisted cache content.
In Configuration Manager, you can use the option to Persist content in the client cache when creating the following –
- Applications
- Packages
- OS images
- OS upgrade packages
- Boot images
What is the use of Persist content in the client cache?
The Configuration Manager client indefinitely keeps its cache in the deployment type content. The client persists in the content even if the app is already installed. This option is useful with some deployments, like Windows Installer–based software. Windows Installer needs a local copy of the source content for applying updates.
Important ⚠️This option reduces the available cache space. If you select this option, it might cause a large deployment to fail at a later point if the cache doesn’t have sufficient available space. The default location for the Configuration Manager client cache is %windir%\ccmcache, and the default disk space is 5120 MB.
This option persists in the specific version of the content that the client installs. If you update the content for this app, the client doesn’t automatically cache this content again. Once an action happens that requires the new content, the client downloads the new content version.
Let’s check how can you enable the option for SCCM Applications.
Configure Persist Content in the client cache option for Applications
Follow the steps below to configure the Persist Content in the client cache for Applications –
#Option 1 –
When creating an application, You can use the following process –
In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Applications node.
Select Create Application, and you Manually specify application information in the Create Application Wizard, select Add on the Deployment Types page, and select the option Manually specify the deployment type information.
After completing all needed steps, On the Content page, specify the following information:
- Content location: Specify the location of the content for this deployment type, or select Browse to choose the deployment type content folder.
- Select Persist Content in the client cache option and complete all the application wizard processes.
#Option 2 –
Deployment type Content options for existing Applications
Select an existing application in the Applications node and select the Deployment Types tab. Right-click on the existing deployment type and select Properties, options appear on the Content tab.
Switch to the Content tab, and select Add. Select the option Persist content in the client cache, Click Apply, and OK.
Similarly, you can do for packages and images by moving to properties windows and selecting Persist content in the client cache. As per me, It’s best to use it in some scenarios only for Applications and packages. This option reduces the available cache space.
Let us know your thoughts in the comment section about this option, and how useful is it for you.
Resources
Author
About Author – Jitesh, Microsoft MVP, has over five years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.