Ever want to know where in the CCMCache the content was located for that package that was downloaded? Ever think you found it, then figured out it wasn’t the most updated version of the content? I quick wrote this script to help me find where in the cache the content is located, and spits back the most updated version of it.
ConfigMgr
ConfigMgr Client Provisioning Mode
Update 8/14/2019 – SEE MORE INFO AT BOTTOM… – MS created official Docs for Prov Mode & 1902 pulls machines out of Prov Mode automatically after 48 hours – Docs HERE
Update 8/3/2018 – With ConfigMgr 1806, The client no longer goes into Provisioning Mode if you run a Compatibility Scan. Confirmed in my lab!
Update 3/15/2018 – Ran several more tests to learn what actions are available to run during Provisioning mode. Scroll to bottom for updates.
Original Post:
I’ve been doing a lot of testing with Provisioning Mode. I needed to know what was going on when a system was in provisioning mode.
Quick Overview of what works and what is difference. (As I continue testing, I’ll continue to update this list)
- Works Normally
- Software Center
- Lists all Deployments available & required it knew about before entering provisioning mode
- Can Install any of those by clicking “Install”
- ConfigMgr Control Panel
- You can still trigger actions, or change cache size
- By Triggering Actions, you can get deployments to install if they are past deadline
- You can still trigger actions, or change cache size
- Software Center
- Differences
- Policy doesn’t update Automatically
- Does NOT report to CM (Inventory)
- Does NOT run Required Deployments automatically once deadline hits.
BGIn-Place Upgrades
If (You Enjoy Reading)
{
I thought that was a clever title, but it seems more confusing the longer I look at it… anyway, this is the follow up post to take BGinfo from MDT, and add it’s capabilities to the ConfigMgr In-Place Upgrade Task Sequence Process. If you’ve been working with in-place upgrade task sequences, you’ll know they are a different beast than regular OSD. You can’t just call an application and expect it to show up on the screen.. like in OSD, you can say Command Line Step: notepad.exe… and guess what, a notepad.exe window opens during the TS.. freaking amazing!
BGinfo Updating MDT Default Templates
If you use MDT, then you’re familiar with their use of changing the background and adding system information during the OSD process. This is pretty handy to get some basic info, but with a little tweaking, you can add additional data that can be very useful to make visible during OSD.
Basics, the required files used during this process are stored here: MDT Package\Tools\x64 & x86
ConfigMgr Lab – Adding Ninite Apps
So you have a Personal ConfigMgr lab, but you want to add some app deployments to better simulate your actual environment. So you add Chrome, Reader, and a couple others (NOT JAVA). Next Month, they are out of date. You probably don’t have time to keep your personal lab app deployments updated, so you keep deploying old versions. How about, you leverage ninite.com’s ability to dynamically install the latest version of the app every time? Now you’re asking, “Isn’t the command line version that supports silent install cost money?” Yes, yes, it does, to use ninite’s silent install, you need the Pro version. What, you don’t want to pay for pro when it’s your personal lab? I hear you. Powershell to the rescue! It doesn’t make it completely silent, but it will allow you to automate it to work with the ConfigMgr App Model during OSD and Post OSD.