Вы находитесь на странице: 1из 4

Configure the client cache

The client cache stores temporary files for when clients install applications and programs.
Software updates also use the client cache, but always attempt to download to the cache
regardless of the size setting. Configure the cache settings, such as size and location, when you
manually install the client, when you use client push installation, or after installation.

You can specify the cache folder size using client settings in the Configuration Manager console.
For more information, see Client cache settings.

The default location for the Configuration Manager client cache is %windir%\ccmcache and the
default disk space is 5120 MB.

 Important

Don't encrypt the folder used for the client cache. Configuration Manager can't download content
to an encrypted folder.

About the client cache

The Configuration Manager client downloads the content for required software soon after it
receives the deployment but waits to run it until the deployment scheduled time. At the
scheduled time, the Configuration Manager client checks to see whether the content is available
in the cache. If content is in the cache and it's the correct version, the client uses the cached
content. When the required version of the content changes, or if the client deletes the content to
make room for another package, the client downloads the content to the cache again.

If the client attempts to download content for a program or application that is greater than the
size of the cache, the deployment fails because of insufficient cache size. The client generates
status message 10050 for insufficient cache size. If you increase the cache size later, the result is:

 For a required program: The client doesn't automatically retry to download the content.
Redeploy the package and program to the client.
 For a required application: The client automatically retries to download the content when
it downloads its client policy.

If the client attempts to download a package that's less than the size of the cache, but the cache is
full, all required deployments keep retrying until:

 The cache space is available


 The download times out
 The retry count reaches its limit
If you later increase the cache size, the client attempts to download the package again during the
next retry interval. The client tries to download the content every four hours until it tries 18
times.

Cached content isn't automatically deleted. It remains in the cache for at least one day after the
client uses that content. If you configure the package properties with the option to persist content
in the client cache, the client doesn't automatically delete it. If the cache space is used by
packages that were downloaded within the last 24 hours, and the client must download new
packages, either increase the cache size or choose the option to delete persisted cache content.

Use the following procedures to configure the client cache during manual client installation, or
after the client is installed.

Configure the cache during manual client installation

Run the CCMSetup.exe command from the install source location and specify the following
properties that you require, and separated by spaces:

 DISABLECACHEOPT
o SMSCACHEDIR
o SMSCACHEFLAGS
o SMSCACHESIZE

 Note

Use the cache size settings available in Client Settings in the Configuration Manager
console instead of SMSCACHESIZE. For more information, see Client cache settings.

For more information about how to use these command-line properties for CCMSetup.exe,
see About client installation properties.

Configure the cache during client push installation

1. In the Configuration Manager console, go to the Administration workspace, expand Site


Configuration, and select the Sites node.
2. Select the appropriate site. On the Home tab of the ribbon, in the Settings group,
select Client Installation Settings, and choose Client Push Installation. Switch to
the Installation Properties tab.
3. Specify the following properties, separated by spaces:
o DISABLECACHEOPT
o SMSCACHEDIR
o SMSCACHEFLAGS
o SMSCACHESIZE

 Note
Use the cache size settings available in Client Settings in the Configuration Manager
console instead of SMSCACHESIZE. For more information, see Client cache
settings.

For more information about how to use these command-line properties for
CCMSetup.exe, see About client installation properties.

Configure the cache on the client computer

1. On the client computer, open the Configuration Manager control panel.


2. Switch to the Cache tab. Set the space and location properties. The default location
is %windir%\ccmcache.
3. To delete the files in the cache folder, choose Delete Files.

Configure client cache size in Client Settings

Adjust the size of the client cache without having to reinstall the client. Use the cache size
settings available in Client Settings in the Configuration Manager console. For more
information, see Client cache settings.

Uninstall the client


You can uninstall the Configuration Manager client software from a computer by
using CCMSetup.exe with the /Uninstall property. Run CCMSetup.exe on an individual
computer from the command prompt, or deploy a package to uninstall the client for a collection
of computers.

 Note

You can't uninstall the Configuration Manager client from a mobile device. If you must remove
the Configuration Manager client from a mobile device, you must wipe the device, which deletes
all data on the mobile device.

1. Open a Windows command prompt as an administrator. Change the folder to the location
in which CCMSetup.exe is located, for example: cd %windir%\ccmsetup
2. Run the following command: CCMSetup.exe /uninstall

 Tip

The uninstall process displays no results on the screen. To verify that the client successfully
uninstalls, see the following log file: %windir%\ccmsetup\logs\CCMSetup.log

If you need to wait for the uninstall process to complete before doing something else, run Wait-
Process CCMSetup in PowerShell. This command can pause a script until the CCMSetup process
completes.

Вам также может понравиться