locked
SCCM Client Upgrade from 1511 to 1602 created new Cache directory c$\CCM\Cache RRS feed

  • Question

  • Hello,

    Within the last few weeks, we have made a change to our SCCM 1602 environment where we changed our "Production Client Version" from 5.00.8325.1000 (1511 client) to 5.00.8355.1000 (1602 client).  Under the Monitoring pane, in SCCM console, we did see the Production client deployment status showing clients were getting automatically upgraded which was good.  Then we recently received word that a new cache directory was created on some of these updated clients in C:\CCM\Cache and the C:\Windows\ccmcache directory was empty with the exception of the skpswi.dat file.  So then when we checked the new Cache folder, we did see that the new Cache folder C:\CCM\Cache had package content both old and new content.

    It didnt happen to all clients but i do see the Autoupgrade task looks like it created the folder structure by looking at ccmsetup.log:

    [JIDONELT2] Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 4/28/2016 1:50:04 PM 15632 (0x3D10)
    Ccmsetup command line: "C:\CCM\Cache\1y\ccmsetup.exe" /AutoUpgrade /UpgradePackageVersion:1 ccmsetup 4/28/2016 1:50:04 PM 15632 (0x3D10)
    Client OS Version 6.1 Service Pack 1.0 ccmsetup 4/28/2016 1:50:04 PM 15632 (0x3D10)
    Unable to open WMI namespace, "root\standardcimv2\embedded". HRESULT = 0x8004100e ccmsetup 4/28/2016 1:50:04 PM 15632 (0x3D10)
    Upgrade code '{252DA259-82CA-4177-B8D0-49C78937BA3E}': product = '{ED04C8CD-1D31-4144-AFDB-20E0BC6A8636}', installed = 1, version = 5.00.8355.1000 ccmsetup 4/28/2016 1:50:04 PM 15632 (0x3D10)
    Loaded command line: "C:\CCM\Cache\1y\ccmsetup.exe" ccmsetup 4/28/2016 1:50:04 PM 15632 (0x3D10)

    We are trying to identify why this happened and if it's normal maybe with 1602 version??

    Thanks!




    • Edited by TomW11 Monday, May 9, 2016 7:06 PM
    Monday, May 9, 2016 6:46 PM

Answers

  • We are having the same issue after upgrading to 1511 on a 25,000+ environment. Logs pointed to this being caused by the client upgrade. We had to turn off auto upgrade. We remediated via a script but the problem resurfaced. We ended up remediating with a Configuration Baseline to enforce it. We are afraid to turn on auto upgrade or disable the CB until this issue is fixed. I am not sure if it has something to do but there is a MOF file on each client "SWDistSchema.mof" that has those settings hardcoded.

    //**************************************************************************
    //* Instances of: CacheConfig
    //**************************************************************************
    instance of CacheConfig
    {
     Location = "C:\\CCM\\Cache";
     Size = "250";
     Inuse = "0";
     NextAvailableId = "0";
    };

    //* EOF SwDistSchema.mof


    Gabriel Lopez

    Tuesday, May 17, 2016 2:34 PM

All replies

  • Dear Sir,

        Not sure why does this happen, in my lab (all computers have 1602 client installed) the cache location is still the same as previous (C:\windows\ccmcache). I will suggest you to open a case with Microsoft Support to confirm it.

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, May 12, 2016 9:36 AM
  • I've just seen this in an environment that I upgraded to 1602 from SCCM 2012 R2 SP1. Did you find the cause and fix that we can implement?

    Cheers

    Damon

    Tuesday, May 17, 2016 8:01 AM
  • We are having the same issue after upgrading to 1511 on a 25,000+ environment. Logs pointed to this being caused by the client upgrade. We had to turn off auto upgrade. We remediated via a script but the problem resurfaced. We ended up remediating with a Configuration Baseline to enforce it. We are afraid to turn on auto upgrade or disable the CB until this issue is fixed. I am not sure if it has something to do but there is a MOF file on each client "SWDistSchema.mof" that has those settings hardcoded.

    //**************************************************************************
    //* Instances of: CacheConfig
    //**************************************************************************
    instance of CacheConfig
    {
     Location = "C:\\CCM\\Cache";
     Size = "250";
     Inuse = "0";
     NextAvailableId = "0";
    };

    //* EOF SwDistSchema.mof


    Gabriel Lopez

    Tuesday, May 17, 2016 2:34 PM
  • Gabriel,

    Thanks for posting your results! that is a great find with the mof file.  We recently engaged Microsoft about this and awaiting their remediation or fix.  Will update thread with results

    Tuesday, May 17, 2016 2:54 PM
  • Great thanks everyone.

    We will look at creating a configuration baseline also to re mediate clients.

    Hopefully they fix this quickly, you can't do much with a client that has a cache of 250MB set!

    Cheers

    Damon

    Tuesday, May 17, 2016 9:18 PM
  • I'm curious if anyone has any new information or experiences in regards to this issue, I have been testing SCCM client deployment (via the Client Push method - eg. right click on a device, install client etc...) in my company on a few systems of various OS and client versions, and found that upgrading a 2012 R2 CU4 client (5.00.7958.1501) to SCCM 1511 client (5.00.8325.1000) is very problematic.

    The initial client upgrade on such systems begins, then eventually fails with the following in the ccmsetup.log:

    "MSI: Setup was unable to compile the file SmsClient.mof The error code is 80041002 ccmsetup 7/7/2016 1:21:46 PM 22176 (0x56A0)"

    Which then triggers a rollback and the old (now defunct) client's ccmexec is relaunched.

    Right after this relaunch the C:\CCM\Cache folder is created with a 250MB limit.

    If you then wait 120 mins for the next automatic installation attempt, the 1511 client installs successfully, but will still utilize the 250MB limit, C:\CCM\Cache location.

    I'm curious if there's a known bug in these upgrade scenarios, and if others are experiencing the same behavior in regards to the SmsClient.mof and rollback, resulting in this erroneous cache size and location.


    • Edited by clemato Wednesday, July 27, 2016 10:55 PM
    Wednesday, July 27, 2016 10:53 PM
  • If you can reproduce this consistently, then you need to open a case with Microsoft so they can figure out what's going on and if it is indeed a bug.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, July 28, 2016 2:24 AM
  • We had the same issue upgrading from 2012 R2 CU3 to 1511, then we noticed that the issue existed when reinstalling the client on 2012 R2 CU3 for some time.

    We scripted around the "MSI: Setup was unable to compile the file SmsClient.mof " by setting this registry value from MS support: "HKLM:\SOFTWARE\Microsoft\CCM\CcmEval" notifyonly = true, which only corrected the issue some of the time.

    Then we remediated the cache issue with a deployment targeted to affected clients.

    After weeks of Microsoft being unable to provide a fix they gave us a link to this page and insisted that we close the ticket.

    Wednesday, August 3, 2016 8:11 PM
  • Hi all, recently upgraded our environment from 2012 SP1 to 1511, then 1606, and I've found a chunk of my existing clients are also reporting ccmcache as 250mb and located in c:\ccm\cache now. Has this been addressed by the ConfigMgr team yet?
    Saturday, September 17, 2016 5:17 AM
  • Me too.  Clients that fail to upgrade initially are left with a 250MB cache located at C:\CCM\ccmcache

    I can't add anythingthat has not already beed stated.  My logs on the problem machines fit the same exactly.  First CCMSetup attempt fails with a 1603 error. 

    The error in the ccmsetup log is.

    MSI: Setup was unable to compile the file SmsClient.mof
    The error code is 80041002

    Immediately prior to the above error, the install is performing a bunch of WMI calls to delete the WMI namespace, recompiling the MOF, etc.  It feels like it might be tying to compile the smsclient.mof file before the previous steps have completed.

     Then the client tries to install again after a couple of hours.  This time the install succeeds, but the client is left with horked Cache settings.

    I've added some data collectio for reporting, but have not attempter to do a CI to remediate...  So far I have deployed 1602 to 159 of ~17,000 clients.

    Of the 159 that have received Configmgr1602, 

    85 have messed up Ccmcache settins, 40 have reported in "good" cache setting and the rest have not reported in since I enabled the data collection...  So ~ 2/3 of client upgrades are resulting in messed up cache settings for me.

    There is a pseudo-acknowledgement of the problem via blog post on how to work around from Santos Martinez here. https://blogs.technet.microsoft.com/smartinez/2016/06/15/where-did-my-cache-location-go/
    • Edited by ToddMiller Monday, September 26, 2016 10:19 PM added link to Santos' blog
    Monday, September 26, 2016 7:31 PM
  • Logged a case with Micrsoft today.

    Seeing this behavior on 400 / 450 clients. We stopped the client upgrade.

    Configmr Upgrade path - 2012 SP1 CU4 -> 1511 - 1606 latest hotfix

    Client Upgrade path - 2012 SP1 CU4 - 1606 latest hotfix.

    I thought upgrade was going fine untill I later saw the C:\CCM folder created.

    Friday, December 9, 2016 1:16 PM
  • Logged a case with Micrsoft today.

    Seeing this behavior on 400 / 450 clients. We stopped the client upgrade.

    Configmr Upgrade path - 2012 SP1 CU4 -> 1511 - 1606 latest hotfix

    Client Upgrade path - 2012 SP1 CU4 - 1606 latest hotfix.

    I thought upgrade was going fine untill I later saw the C:\CCM folder created.

    Answer MS:

    Thank you for the logs. I just confirmed that the issue is in fact a Code Defect in Current Branch. There’s almost no info on it so there’s no official workaround as of yet.

    But the issue described is exactly as ours with the same :

    MSI: Setup was unable to compile the file SmsClient.mof

    The error code is 80041002        

     

    It seems recompiling it also does not help and in all test clients the cache size and location reverted to default.

    Looks like this is a known issue with the Product Group, we’ll just have to wait for a fix.



    • Edited by Tim NL Tuesday, December 13, 2016 12:14 PM
    Tuesday, December 13, 2016 12:12 PM