Beware the SMSCACHEFLAGS=MAXDRIVESPACE Properties
Gentlepersons, I will start this post by saying we are already circumventing the issue I am about to describe with custom code. When once uses the Client.MSI property of "SMSCACHEFLAGS=MAXDRIVESPACE" to place the SCCM Cache Directory on the drive with the most space, it will choose an "ATTACHED" drive if there is one with more space than the internal disks. Of course this means that when the user disconnects the drive, the SCCM Cache is no longer present and all further SCCM Advertisement processing ceases to function. Again we are using a custom script to deploy the agent so we can get around the issue, but we would prefer to use the vanilla code, for simplicitiy and ongoing support sake. Plus, if I am not mistaken, one would not be able to use this flag as an option in the Client Push method due to its unreliability. As a side note, there are many entries in other forums about reporting on SMS Cache info. One has to update the Hardware Inventory MOF to collect the data. Then there are also script available to update the cache directory. We are on SCCM SP2 R2. What would be the process to put in a request to have Microsoft fix this in future Service pack releases? Thanks, Mike Bivona HP Enterprise Services
October 23rd, 2010 4:14pm
If you want Microsoft to only look at NON USB (local) drives and not all drives when using the MaxDriveSpace command then you can submit it to the Connect site https://connect.microsoft.com/ Select the product, in this case you can submit it for ConfigMgr 2007 and V.next if you like. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
October 24th, 2010 6:49pm
Can you post the script you use?-- Onions have layers, so does SCCM, and both will make you cry..
October 24th, 2010 6:58pm
Matt, Thank you for the quick response. I logged in to the connect page and submitted the "bug".
October 25th, 2010 11:42pm