Examples of using Client cache in English and their translations into Russian
{-}
-
Official
-
Colloquial
Persist content in client cache.
The client cache is currently in use by a running program or by a download in progress.
Check to see if the client cache is in use.
NFS may use Kerberos authentication and a client cache.
Failed to indicate the client cache is currently in use.
Deletes the Configuration Manager 2007 client cache.
Along with the messages from the client cache, a resynchronization complete state message(TopicType=700, StateID=2) is sent.
This step will run if the Configuration Manager 2007 client cache does not exist.
In the Client Cache Configuration Settings section, click one of the following radio buttons to choose how to manage the cache space.
Provides procedures for loading orunloading an application into or from the client cache.
All of the files will be downloaded and stored in the client cache prior to running the task sequence.
Only the most recent version of each virtual application package will reside in the client cache.
The content download cannot be performed because the total size of the client cache is smaller than the size of the requested content.
When a virtual application is deleted the virtual application package is also deleted from the client cache.
When all images and packages are in the client cache, the task sequence begins, andreferences the images and packages from the client cache on the local hard drive.
If an advertised task sequence has been configured to download and run,all dependent programs are downloaded to the Configuration Manager 2007 client cache.
And if the Configuration Manager 2007 client cache size is too small or the program cannot be found, the task sequence will fail and a status message will be generated.
Packages are not validated until after they are downloadedConfiguration Manager 2007 validates the signatures on packages only after they have been downloaded to the client cache.
For more information about configuring the Configuration Manager 2007 client cache see How to Configure the Temporary Program Download Folder(Cache)for Configuration Manager Clients. .
If you configure virtual application packages to download and run locally on the target computer they will be stored in the Configuration Manager 2007 client cache.
Specify whether to locate images and run package programs from a distribution point as required when the task sequence runs, or to download all images andpackages to the Configuration Manager 2007 client cache before running the task sequence.
When a newer version of a virtual application package is started, any previous version of the virtual application package is then deleted andthe newer version is stored in the client cache.
Additionally, if you plan to configure the advertisement for the virtual application package to download to the Configuration Manager 2007 client andrun locally, you must ensure that sufficient space is available in the Configuration Manager 2007 client cache to save the virtual application package.
You can configure the virtual application package advertisement with the setting Download content from distribution point and run locally orwait until the package has been completely downloaded to the client cache.
When this occurs, virtual application packages configured to stream will not successfully run unless the package has been fully downloaded to the Microsoft Application Virtualization Desktop Client cache.
If this option is selected, and the task sequence contains a step tore-partition the hard drive, the re-partition step will fail because re-partitioning the hard drive erases the contents of the Configuration Manager 2007 client cache.
If you use the Install Software task sequence step to deploy a virtual application package and configure the advertisement to Download on Demand,the Configuration Manager 2007 will not maintain the virtual application package in the Configuration Manager 2007 client cache.
To change the amount of time that clients cache folder referrals.
When the cache client(a CPU, web browser, operating system) needs to access data presumed to exist in the backing store, it first checks the cache. .
The client can cache TLS handles for multiple PEAP authenticators.