"when we went from SCCM2012 to SCCM CB back in December"
I suspect you deployed the 1610 client prior to the hotfix that fixed the
issue of ccmsetup.exe which would orphan content. Go look at the
description of KB3214042, and you'll see its for that exact issue.
"After clients upgrade to Configuration Manager, version 1610, the contents
of the CCM Cache folder (%windir%\ccmcache by default) are orphaned.
Although the files are still present on disk, they are not available for
application installations and will not be managed or deleted by the client.
Installing this update prevents the cache issue on future client upgrades.
Previously upgraded clients will redownload applicable content, and any
expired content can be manually deleted as needed.
"
You won't be able to tell from "client version" which ones used the
ccmsetup which was flawed.. the client version itself did not change.
thankfully, for us, we only deployed the before-the-hotfix ccmsetup.exe
client in the lab, not production.
But yeah, in the lab what I ended up doing was stole http://
rzander.azurewebsites.net/sccm-config-item-to-cleanup-ccmcache/ and stuck
it in a ConfigItem, with a detect and remediation script.
and sent that out to everyone. I figured it "couldn't hurt" to do cleanup
anyway. and it's the lab. So I don't care all that much. For you, for
production... you might want to do a bit more pilot and testing than I did
in the lab. :)
Way more info than you wanted to know...
#########################
#Detection, script, Boolean result value expected
############################
#get CCMCache path
$Cachepath = ([wmi]"ROOT\ccm\SoftMgmtAgent:CacheConfig.ConfigKey='Cache'"
).Location
#Get Items not referenced for more than 30 days
$OldCache = get-wmiobject -query "SELECT * FROM CacheInfoEx" -namespace
"ROOT\ccm\SoftMgmtAgent" | Where-Object { ([datetime](Date) -
([System.Management.ManagementDateTimeConverter]::
ToDateTime($_.LastReferenced))).Days -gt 30 }
#report old Items
if($OldCache) { $false } else { $true }
#####################################
### This is the Remediation Script part#####
#
#####################################
#get CCMCache path
$Cachepath = ([wmi]"ROOT\ccm\SoftMgmtAgent:CacheConfig.ConfigKey='Cache'"
).Location
#Get Items not referenced for more than 30 days
$OldCache = get-wmiobject -query "SELECT * FROM CacheInfoEx" -namespace
"ROOT\ccm\SoftMgmtAgent" | Where-Object { ([datetime](Date) -
([System.Management.ManagementDateTimeConverter]::
ToDateTime($_.LastReferenced))).Days -gt 30 }
#delete Items on Disk
$OldCache | % { Remove-Item -Path $_.Location -Recurse -Force -ea
SilentlyContinue }
#delete Items on WMI
$OldCache | Remove-WmiObject
#Get all cached Items from Disk
$CacheFoldersDisk = (Get-ChildItem $Cachepath).FullName
#Get all cached Items from WMI
$CacheFoldersWMI = get-wmiobject -query "SELECT * FROM CacheInfoEx"
-namespace "ROOT\ccm\SoftMgmtAgent"
#Remove orphaned Folders from Disk
$CacheFoldersDisk | % { if($_ -notin $CacheFoldersWMI.Location) {
remove-item -path $_ -recurse -force -ea SilentlyContinue} }
#Remove orphaned WMI Objects
$CacheFoldersWMI| % { if($_.Location -notin $CacheFoldersDisk) { $_ |
Remove-WmiObject }}
####the end of scripts
Setting rule for what means compliant:
Value Equals “TRUE”
On Fri, Mar 3, 2017 at 7:50 AM, Kent, Mark <[email protected]> wrote:
> I’d really like to know the answer to this. It seems like when we went
> from SCCM2012 to SCCM CB back in December, I see a number of clients with
> orphaned content in their cache folders. New items don’t seem to push out
> the old. When I run a cache clearing option from the Now Micro right click
> tools, it doesn’t delete that old content. I have to do so manually. I
> think in one instance the client still thought the cache was full even
> though it was completely empty.
>
>
>
> Mark Kent
>
> Manager, Client Systems Engineering
>
> Technology Support Services
>
> Resources for Information, Technology and Education (RITE)
>
> http://rite.buffalostate.edu
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Daniel Ratliff
> *Sent:* Monday, February 20, 2017 11:21 AM
>
> *To:* [email protected]
> *Subject:* RE: [mssms] Client Cache Settings
>
>
>
> Posted on UV for the docs team to update.
>
>
>
> https://configurationmanager.uservoice.com/forums/300492-
> ideas/suggestions/18395980-client-cache-documentation-appears-incorrect
>
>
>
> *Daniel Ratliff*
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Beardsley,
> James
> *Sent:* Monday, February 20, 2017 10:37 AM
> *To:* [email protected]
> *Subject:* RE: [mssms] Client Cache Settings
>
>
>
> I think you’re right. I don’t think this is documented correctly unless
> something has changed with the way it works in CB. I will have to test this
> to confirm.
>
>
>
> Anyone else know this for sure… one or way another?
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Daniel
> Ratliff
> *Sent:* Friday, February 17, 2017 7:37 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Client Cache Settings
>
>
>
> My understanding as well. It orphans the cache element in WMI. Seems like
> it is misdocumented?
>
>
>
> *Daniel Ratliff*
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Beardsley,
> James
> *Sent:* Friday, February 17, 2017 4:30 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Client Cache Settings
>
>
>
> Also about client cache but different question… I noticed on the link you
> posted, it says this:
>
>
>
> Note
>
> The cache folder is a regular Windows folder, so you can automate deletion
> of the folder contents using a script, a utility, or with the PowerShell
> cmdlet Remove-Item.
>
>
>
> In the “old’n days” of ConfigMgr (2007-2012), I always heard (maybe
> incorrectly) it was a no-no to delete folders from ccmcache because they
> were tied to WMI so closely and if you deleted a cache folder and then
> tried to run the deployment again from Run Advertised Programs/Software
> Center, WMI would think the content still existed in ccmcache and would
> just fail to run. It wasn’t smart enough to know that it had to be
> downloaded again.
>
>
>
> Doesn’t sound like that’s true anymore…? Or did I misunderstand it in
> previous versions of CM.
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Jason
> Sandys
> *Sent:* Tuesday, February 14, 2017 4:50 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Client Cache Settings
>
>
>
> Nice find Russ – it would make too much sense to actually put that on the
> page that client setting page in the documentation. Guess I’ll add it J
>
>
>
> J
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Russ
> Rimmerman
> *Sent:* Tuesday, February 14, 2017 12:34 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Client Cache Settings
>
>
>
> https://docs.microsoft.com/en-us/sccm/core/clients/manage/
> manage-clients#BKMK_ClientCache
>
>
>
> “Cache is adjusted to whichever size is less.”
>
>
>
> *From:* [email protected] [mailto:listsadmin@lists.
> myitforum.com <[email protected]>] *On Behalf Of *Andrew
> Sanders
> *Sent:* Tuesday, February 14, 2017 12:24 PM
> *To:* [email protected]
> *Subject:* [mssms] Client Cache Settings
>
>
>
> In ConfigMgr CB, these options exist for controlling cache size in client
> settings:
>
>
>
> [image: Inline image 1]
>
>
>
> Which setting takes precedence, size or percentage? For instance, if I
> have a 100GB hard drive and I set the size to 10,000MB, but set the
> percentage to 1% (1,000MB), which wins? I can't find anything in the
> documentation that gives a clear answer.
>
>
>
> --
>
> *Andrew Sanders* | *Manager, Client Computing **Architecture*
>
> Systems & Networks | Information Technology Services | The University of
> North Carolina at Greensboro
>
> (336) 334-5028 (p) | (336) 334-5932 (f)
>
> 107A McNutt Center | 1400 Spring Garden Street | Greensboro, NC | 27403
>
> [email protected] | http://its.uncg.edu
>
> Microsoft Certified IT Professional | Microsoft Certified Technical
> Specialist
>
>
>
> [image: Image removed by sender.]
>
>
>
>
>
>
> ------------------------------
>
> *Confidentiality Notice:* This e-mail is intended only for the addressee
> named above. It contains information that is privileged, confidential or
> otherwise protected from use and disclosure. If you are not the intended
> recipient, you are hereby notified that any review, disclosure, copying, or
> dissemination of this transmission, or taking of any action in reliance on
> its contents, or other use is strictly prohibited. If you have received
> this transmission in error, please reply to the sender listed above
> immediately and permanently delete this message from your inbox. Thank you
> for your cooperation.
>
>
>
>
> The information transmitted is intended only for the person or entity to
> which it is addressed
> and may contain CONFIDENTIAL material. If you receive this
> material/information in error,
> please contact the sender and delete or destroy the material/information.
>
>
> ------------------------------
>
> *Confidentiality Notice:* This e-mail is intended only for the addressee
> named above. It contains information that is privileged, confidential or
> otherwise protected from use and disclosure. If you are not the intended
> recipient, you are hereby notified that any review, disclosure, copying, or
> dissemination of this transmission, or taking of any action in reliance on
> its contents, or other use is strictly prohibited. If you have received
> this transmission in error, please reply to the sender listed above
> immediately and permanently delete this message from your inbox. Thank you
> for your cooperation.
>
>
>
>
> The information transmitted is intended only for the person or entity to
> which it is addressed
> and may contain CONFIDENTIAL material. If you receive this
> material/information in error,
> please contact the sender and delete or destroy the material/information.
>
>
>
>
--
Thank you,
Sherry Kissinger
My Parameters: Standardize. Simplify. Automate
Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger,
http://www.smguru.org
