Very interesting thank you. Yes, we did do the upgrade a couple days before this revised version came out. I thought I took all the proper steps to address things based on this article but I will go over it once again. Appreciate it!
Mark Kent Manager, Client Systems Engineering Technology Support Services Resources for Information, Technology and Education (RITE) http://rite.buffalostate.edu<http://rite.buffalostate.edu/> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Chobeaux, Sebastien Sent: Friday, March 3, 2017 9:13 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] Client Cache Settings You may have been impacted by this https://support.microsoft.com/en-gb/help/3214042/interoperability-update-for-system-center-configuration-manager-version-1610 “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.” Notice the “can be manually deleted as needed” I’ve used this script to cleanup the orphaned cache http://rzander.azurewebsites.net/sccm-config-item-to-cleanup-ccmcache/. Hope that helps -- Sébastien Chobeaux De : listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] De la part de Kent, Mark Envoyé : vendredi 03 mars 2017 08:50 À : mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Objet : RE: [mssms] Client Cache Settings 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<http://rite.buffalostate.edu/> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Monday, February 20, 2017 11:21 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Beardsley, James Sent: Monday, February 20, 2017 10:37 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Friday, February 17, 2017 7:37 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Beardsley, James Sent: Friday, February 17, 2017 4:30 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Tuesday, February 14, 2017 4:50 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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 From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Russ Rimmerman Sent: Tuesday, February 14, 2017 12:34 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Andrew Sanders Sent: Tuesday, February 14, 2017 12:24 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Client Cache Settings In ConfigMgr CB, these options exist for controlling cache size in client settings: [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 apsan...@uncg.edu<mailto:apsan...@uncg.edu> | http://its.uncg.edu Microsoft Certified IT Professional | Microsoft Certified Technical Specialist [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. ________________________________ AVIS IMPORTANT: Les renseignements contenus ou joints à ce courriel sont pour l'usage exclusif du destinataire ou de l'institution à qui ce courriel s'adresse et peuvent contenir des renseignements privilégiés, confidentiels et exempts de divulgation conformément à la Loi sur l'accès à l'information municipale et la protection de la vie privée. Dans l'éventualité que le récepteur du présent courriel n'est pas le destinataire concerné ou la personne autorisée à acheminer le message au destinataire concerné, vous êtes, par la présente, avisé(e), que toute divulgation, diffusion, distribution ou reproduction de la présente communication est strictement interdite. Si vous recevez ce message par erreur, veuillez immédiatement en informer l'expéditeur ou l'expéditrice par courriel et détruire celui-ci ainsi que toutes les pièces jointes qu'il comporte. Merci de votre collaboration.
