none
Temporary Program Download Folder and Windows 7

    Question

  • Hello. My environment is SCCM 2007 SP2. We use OSD to deploy Windows XP and Windows 7. For Windows 7 machine, we use UAC.


    I noticed that on a Windows 7 machine the temporary program download folder shows as C:\WINNT\System\CCM\Cache. Since we are using UAC, the information is grayed out. If I click configure settings, it shows the proper location of C:\windows\system32\ccm\cache and it also uses the correct location.


    I am trying to figure out why it is displaying the incorrect location. Is this a security feature since UAC is being used?


    Thanks for any information.

    Tuesday, November 30, 2010 9:58 PM

Answers

  • I have the same thing.  We are running atop x64 win7.  When gray it shows c:\winNT\System32\CCM\Cache after you open the Configure Settings and the UAC prompt we see the correct path.   C:windows\syswow64\ccm\cache

    I don't think it is a UAC security feature.  I assume it is how the control panel protect feature is written, much like the Cache size is 0.  It might be looking at a different space in WMI or something.  I don't pay too much attention to it because I know the client is working properly.

     


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Tuesday, November 30, 2010 10:26 PM

All replies

  • I have the same thing.  We are running atop x64 win7.  When gray it shows c:\winNT\System32\CCM\Cache after you open the Configure Settings and the UAC prompt we see the correct path.   C:windows\syswow64\ccm\cache

    I don't think it is a UAC security feature.  I assume it is how the control panel protect feature is written, much like the Cache size is 0.  It might be looking at a different space in WMI or something.  I don't pay too much attention to it because I know the client is working properly.

     


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Tuesday, November 30, 2010 10:26 PM
  • I have the same thing.  We are running atop x64 win7.  When gray it shows c:\winNT\System32\CCM\Cache after you open the Configure Settings and the UAC prompt we see the correct path.   C:windows\syswow64\ccm\cache

    I don't think it is a UAC security feature.  I assume it is how the control panel protect feature is written, much like the Cache size is 0.  It might be looking at a different space in WMI or something.  I don't pay too much attention to it because I know the client is working properly.

     


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

    Running into the same issue in our environment, does anyone know if there is a fix for this? 

    Unfortunately in our environment, even though the client is healthy in that it is installing software and updates, we can't "let it ride" with the incorrect location being displayed and the cache size being reported as "0".

    We are only experiencing this on our Win 7 x64 builds, it isn't occuring on our Win XP or Win 7 x86 builds.  We are using SCCM 2007 SP2 as well.  One thought was account security, but it hasn't made a difference whether the user is a local admin or standard user.

    Any thoughts or ideas would be GREATLY appreciated!

    -Fred

    Thursday, February 17, 2011 3:47 PM
  • I have the same thing on Windows 7 Ent x32 & x64

    Just think it's the way it mask the correct value from non-administrator user for some reason

    Did not think much of it since when you can see the correct value after clicking Configure.. and as long as the client works properly.


    ---Packie
    Thursday, February 17, 2011 7:33 PM
  • But it shows the same regardless of whether it's an admin user or standard user ... 

    Believe me, if it was my environment to manage I wouldn't really care so long as it's healthy and SCCM is happy, but unfortunately management won't buy it, as their response is "Why does it work correctly/report correctly in Win XP and Win 7 x86, but not Win 7 x64?", if it did that across the board on all OS's then it would be easy to explain.

    I have to believe there is a fix for it or at the very least, a better explanation as to why it's happening that management would be happy with.

     

    -Fred

    Thursday, February 17, 2011 7:55 PM