This while as of 2203 this utility still worked, I have written a new tool called "MECM Offline Update GUI" that is a PowerShell based utility. I have put the "ConfigMgr Offline Updating Tool" here for historical purposes but it is no longer maintained. I recommend using the new "MECM Offline Update GUI".
NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS POST. Test in a lab environment. Use this utility at your own risk. If your environment catches fire and burns to the ground, it aint my fault!
Obtaining the utility: Download here (https://www.ithierarchy.com/ITHv3/sites/default/files/2022-07/ConfigMgr%20Offline%20Updating%20and%20Guide.zip)
Obtaining and importing offline updates
Note: Several scripts have been prepared that will allow updates to be imported with minimal effort all three scripts are located at <Source>\1602OfflineUpateScripts No other files should be in this folder:
- Retrieve the Usage Data Microsoft will need to create the Update Packs
- First, Copy the “ConfigMgr Offline Updating Utility.exe” file to an empty folder on the Standalone Primary/CAS server, Then Run it as Administrator.
- Select “Export Update Information CAB from CAS/Primary”, then Click the “Export Usage” button.
Note: you can review the data that is being sent by reading ConfigMgrUsageData.csv in the ConfigMgrUsageData folder. - Copy the entire folder and all its contents that you put the ConfigMgr Offline Updating Utility in to an Internet connected computer
- First, Copy the “ConfigMgr Offline Updating Utility.exe” file to an empty folder on the Standalone Primary/CAS server, Then Run it as Administrator.
- Downloading Update Packs:
- Run as administrator the “ConfigMgr Offline Updating Utility.exe” that is in the folder you copied over on the Internet Connected computer.
- Select “Download Updates from Internet”, then Click the “Download Updates” Button. If you are running ConfigMgr 1511 or 1602, Select the ConfigMgr Version 1511-1602, otherwise it will not download that update packs.
NOTE: This step can take a long time depending on the number of updates and internet connection speed (these can be several GB in size). The application will also seem like it has locked up and is not responding, but the application is actually working. You can see the updates downloading by monitoring the ConfigMgrUpdatePacks folder that is created in the folder you copied over. Please be patient.
- Once it is completed, copy the entire folder back over to the CAS/Standalone Primary Site Server.
- Importing the Updates:
- On the CAS/Standalone Primary Site Server, Run as administrator the “ConfigMgr Offline Updating Utility.exe” again.
- Select Import Updates to CAS/Primary, then click the “Import Updates” button.
NOTE: Again his step can take a long time depending on the number of updates and their size (these can be several GB in size). The application will also seem like it has locked up and is not responding, but the application is actually working. You can see the updates downloading by monitoring the ConfigMgrUpdatePacks folder that is created in the folder you copied over. Please be patient.
Update does not appear in console
Issue: The offline update does not show up in the console under “Updates and Servicing”
Symptoms:
Log file located at “<CMInstallDrive>:\Program Files\Microsoft Configuration Manager\Logs\dmpdownloader.log has the (or similar) entry near the end of the log: “WARNING: Manifest.cab can’t be null or empty. Retrying in next polling cycle”
Note: It is best to open ConfigMgr logs with the “CMTrace.exe” tool located at “<CMInstallDrive>:\Program Files\Microsoft Configuration Manager\tools”.
Resolution:
- Look at the files in the “<CMInstallDrive>:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline”.
- Open a second Windows Explorer window, and browse to “<CMInstallDrive>:\ConfigMgrServiceConnection\ConfigMgrUpdatePacks\”
- Compare the files and folders in step 1 and step 2. Most likely step 1 is missing some of the files and from step 2. Copy all the missing files from the folder in step 2.
- Paste the files from step 3 into the folder in step 1.
|
|
|
|
- Right click on the “SMS_EXECUTIVE” Service then click on "Stop"
Note: This may take a while to stop. be patient."
- Right click on "SMS_EXECUTIVE (text)" in "Task Manager", then click on “Start”.
- Monitor the “<CMInstallDrive>:\Program Files\Microsoft Configuration Manager\Logs\dmpdownloader.log” using CMTrace. You should see the line towards the bottom of the log that says “Get new Easy Setup Package IDs”, after which it will start to extract the updates.
|
|
|
|
|
ConfigMgr update never leaves the “Downloading” state.
Resolution 1
- Restart the “SMS_Executive” service
Resolution 2
- Look at the files in the “<CMInstallDrive>:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline”.
- Open a second Windows Explorer window, and brows to “<CMInstallDrive>:\ConfigMgrServiceConnection\ConfigMgrUpdatePacks\”.
Compare the files and folders in step 1 and step 2. Most likely step 1 is missing some of the files and from step 2. Copy all the missing files from the folder in step 2.
- Paste the files from step 3 into the folder in step 1.
- Right click on task bar, then click on “Task Manager” in the popup menu.
- In Task Manager, Select the Services tab.
- Right click on the “SMS_EXECUTIVE” Service then click on "Stop"
Note: This may take a while to stop. be patient."
- Right click on "SMS_EXECUTIVE (text)" in "Task Manager", then click on “Start”
- Monitor the “<CMInstallDrive>:\Program Files\Microsoft Configuration Manager\Logs\dmpdownloader.log” using CMTrace. You should see the line towards the bottom of the log that says “Get new Easy Setup Package IDs”, after which it will start to extract the updates.
- You may need to wait 90 minutes for the status to change to “Available”.
- In the ConfigMgr console, go to “AdministrationàCloud ServicesàUpdates and Servicing”
Comments