When you view the “Systems Management” applet in the control panel on the “Advanced” tab you will see in the bottom leaf a section called “Temporary Program Download Folder”. In this section you specify in Megabytes (MB) how much of the client’s disk space is to be allocated when an advance client receives an advertisement that is configured to downward the program locally. If this is the case it is downloaded to the Temporary Program Download Folder’s “Current Location” which is by default located in the %WinDir%\System32\CCM\Cache directory folder.
From the”Advanced” tab you can modify the “Amount of disk space to use” by moving the slider, using the up and down arrows or by manually adding the value into the window. You can also change this programmatically using various scripting technologies which is beyond the scope of this post.
You can also change the location of the cache by clicking the “Change Location” button and browse for the new location. You can also clear the cache by clicking the button “Delete Files” and then select ‘Yes’ to the prompt asking you “Are you sure you want to delete the files”
The SMS default cache size value of 250 MB is sufficient for most site organizations but you may find that the cache size is too small. This is especially true if you have a very large infrastructure and are distributing an abundance of packages such as hotfixes and patches or if you are distributing large packages such as the various Microsoft office suites.
It is important to note here that if the cache is full or there in insufficient space remaining for a package to be downloaded the advertised program may not download and therefore it will not be able to execute. This can happen if the package is locked by the client agent.
When a package is downloaded to the advanced client cache the client agent places a lock on the package and the lock is not removed until a day later (24 hours) after the program is executed or a month (30 Days) if the package has not be executed. When the lock is removed from the package a day or a month later depending in the circumstance it cannot be re-locked until it is removed from the client cache and downloaded again.
When your packages need to be downloaded locally to the advanced client and the cache is full or lacks sufficient free space to accommodate the download the client will enumerate the packages in the cache if any exist and attempt to determine if the existing packages in the cache have already executed and the allotted 24 hours has not yet passed. If it finds packages where this is the case the agent then deletes them to allow more free space and then attempts to download the package again. On the second attempt to download the package if there is now sufficient free space remaining the package is downloaded to be executed.
If you have a package or multiple packages that when combined are too large to fit into the cache they will not be downloaded and this is a good indication that your client’s cache size is insufficient for your infrastructure.
This HTA script will take an SMS client machine name from an input text box and then return the SMS clients
This VBS script will take a list of SMS client machine names from a text file called MachineList.Txt
This VBS script will take a local or remote machine name from an input box and then will prompt you to