ConfigMgr 2012 – Where’s my PXE CacheExpire gone!?

ConfigMgr 2012 – Where’s my PXE CacheExpire gone!?

  • Comments 2
  • Likes

 

In ConfigMgr 2007 we had a registry key called CacheExpire which would allow a client to start a new PXE session after 60 minutes. The idea is, if a build is mandatory the cache will hold onto the session to ensure it doesn’t get into a rebuild loop.

It was a bit of a pain when you were developing/testing your OSD builds because if it failed, you had to wait for the cache to run out or clear it manually. So many engineers would change the key to 120 seconds or so.

HKLM\Software\Microsoft\SMS\PXE\ CacheExpire=120

I’ve recently been testing a new build in ConfigMgr 2012 using PXE as my boot method, and went in search of the CacheExpire value to speed up the process, and found its no longer there. In fact, the entire PXE key is missing.

The reason is quite simple, in ConfigMgr 2012 the PXE Service Point is no longer a separate role – it’s now integrated with the Distribution Point role. So I checked in the DP registry key for a CacheExpire… no luck.

HKLM\Software\Microsoft\SMS\DP

So I decided to try and create one and see how it went… bingo, my PXE Cache is now 120 seconds.

Fox the lazy, here’s the exported key & value

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP]
"CacheExpire"="120"

Matt Shadbolt

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Great find! It's funny the previous owner of our 2007 environment never figured this out, and it was one of my first "wins" over our environment once I inherited it. Now in 2012, I knew I had to add it to our environment because everyone depends on reimaging/reimporting etc... fairly quickly. Our PC Techs frequently are moving systems around to image, so one less thing for them to worry about. Thanks!

  • Awesome ! You save me a lot of time !

    Thanks !