|
rjarrett -> Right Click Tools for SCCM? (4/16/2008 2:32:31 PM)
|
There is a way to do it from a centralized method. I don't know if it changed from SMS 2003 or not, but it seems we had to push out a MOF file change and compile it on the client. All of it could be done via an SMS package, but it was not as simple as changing the setting in the central server. Anyone else have ideas?
In any case, your comments "cache is either full or not enough to install" suggest that your cache's are not clearing properly. Two things. First, you might want to investigate "tombstoning" for the cache. Second, are you sure you are not getting "false" messages.
First, there is a tombstone setting in the MOF that regulates how long source files are protected (i.e. cannot be flushed) in the cache. You may be protecting your cache to where it cannot flush.
Second, I have seen clients reporting that the "cache is full" when in fact it was a problem with the Distribution Point. The HASH indicated a corruption, so the client simply hung. When we refreshed the distribution point, the hash mismatch went away and the clients installed without problem. The "cache is full" was a false indicator of the true problem.
|
|
|
|
