SCCM Offline Servicing for Operating System Images

When deploying a new machine via ConfigMgr OSD one question that often comes up is how updates deployment on new machines should be handled, while the answer to the question varies and depends on many factors in this article I will show you how you can use ConfigMgr SUP to implement what is known as offline servicing for windows updates, in a way you can imagine it as a way to deploy updates to machine before the actual image is deployed to the computers.

SCCM Offline Servicing Components

SCCM Offline Servicing is not an entirely new feature as it was available in the previous release of the product what Microsoft did with ConfigMgr 2012 is fully integrate offline servicing capabilities in the ConfigMgr console.

SCCM Offline Servicing builds on existing components and features that make up ConfigMgr and Windows deployment technologies, namely WIM files, so from a configuration point of view all you will need is a working SUP and the WIM image file on the ConfigMgr server.

It has to be noted that SCCM Offline Servicing can only be used for Component Based Servicing (CBS) updates meaning that you cannot use offline servicing to deploy, for example, Internet Explorer 11 to a Windows 7 machine as that’s a task sequence or application deployment job.

SCCM Offline Servicing in Action

Once the requirements have been satisfied let’s see how offline services works in practice in the ConfigMgr admin console navigate to [Software] –> [Operating System] –> [Operating System Images] and select the WIM file for the image you want to update and either right click on it or select Schedule Updates from the ribbon interface

Schedule Update

[su_note note_color=”#ffff96″ text_color=”#000000″ radius=”5″]Note: I assume you already have already downloaded necessary updates and/or created an Update Deployment group[/su_note]

In the window that will open select all updates you want to deploy on the OS image and the correct architecture for the image you’re servicing

Offline Servicing Updates Selection

[su_note note_color=”#ffff96″ text_color=”#000000″ radius=”5″]Note: If the update selection window appears empty follow instructions in this article. [/su_note]

In the following window select a schedule to deploy the update and if the updated image should be deployed to distribution points in the hierarchy

SCCM Offline Servicing Updates Schedule

Review information in the Summary page and when ready click next to start the Offline servicing process.

Offline Servicing Process in Detail

Once the schedule for updating the WIM file starts the site server will wake up and start the offline servicing task

  • The Site server will copy the WIM file and appropriate update files from the content library to a temporary folder
  • The WIM file will be mounted via dism.exe
  • Through dims.exe selected updates are applied to the wim file (or in case of multiple WIM to all applicable images)
  • Once the update process is complete the WIM file is restored to the package source location
  • The original version of the WIM file is preserved as backup copy in case of issues to allow an easy way to revert the operation

Once the process is completed the update status can be viewed from within the console selecting the image that has been serviced and selecting the Update Status together with an historical view of updates deployed to the WIM file

SCCM Offline Servicing Update Status

Same information is available accessing image’s properties under the Installed Updates tab

SCCM Offline Servicing Update Status

Like with most of ConfigMgr components you can follow the whole process monitoring the OfflineServicingMgr.log log file below you can find relevant content of the file of the Offline Servicing of the Windows 10 image in my lab

[su_spoiler title=”SCCM Offline Servicing” style=”fancy”]

SMS_EXECUTIVE started SMS_OFFLINE_SERVICING_MANAGER as thread ID 5180 (0x143C).  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.277-120><thread=2500 (0x9C4)>
Checking if there are schedule(s) which need to be run at this time.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.285-120><thread=5180 (0x143C)>
Schedule with ID 16777217 is marked for RunNow by the administrator  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.286-120><thread=5180 (0x143C)>
The Schedule with ID 16777217 will be run now. It’s run time is at gio ott 15 22:55:00 2015 W. Europe Daylight Time   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.291-120><thread=5180 (0x143C)>
Schedule with ID 16777217 (package ID ALX00015, source site ALX) is active on site with site code ALX  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.291-120><thread=5180 (0x143C)>
Using Deployment Kit (version: 10.0) installed at ‘C:Program Files (x86)Windows Kits10’, registry key name is KitsRoot10  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.291-120><thread=5180 (0x143C)>
Schedule processing thread started. ThreadID = 0x17E8 (6120)  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.292-120><thread=5180 (0x143C)>
1 Schedule(s) are marked for RunNow by the administrator  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.292-120><thread=6120 (0x17E8)>
1 Schedule(s) are scheduled to be run at this time  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.292-120><thread=6120 (0x17E8)>
Processing started for Schedule with ID 16777217  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.294-120><thread=6120 (0x17E8)>
STATMSG: ID=7900 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 20:55:00.294 2015 ISTR0=”16777217″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.294-120><thread=6120 (0x17E8)>
Initialization of schedule processing succeeded  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.412-120><thread=6120 (0x17E8)>
There is an image associated with this schedule.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.413-120><thread=6120 (0x17E8)>
Total number of individual updates to be installed is 5.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.413-120><thread=6120 (0x17E8)>
STATMSG: ID=7903 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 20:55:00.414 2015 ISTR0=”ALX00015″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.414-120><thread=6120 (0x17E8)>
Copy image ( ID ALX00015, size 3266 MB )  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.470-120><thread=6120 (0x17E8)>
copying file from ‘\szhv-cm01OSDWIMWindows 10 x64 Enterprise Goldinstall.wim’  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.470-120><thread=6120 (0x17E8)>
to ‘C:ConfigMgr_OfflineImageServicingALX00015install.wim’ ….  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:55:00.470-120><thread=6120 (0x17E8)>
Copying (25% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:56:26.020-120><thread=6120 (0x17E8)>
Copying (50% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:57:54.319-120><thread=6120 (0x17E8)>
Copying (75% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 22:59:29.013-120><thread=6120 (0x17E8)>
Copying (100% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:53.959-120><thread=6120 (0x17E8)>
STATMSG: ID=7905 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:00:53.959 2015 ISTR0=”ALX00015″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:53.963-120><thread=6120 (0x17E8)>
[Schedule ID 16777217] Started processing image package with ID ALX00015  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:53.963-120><thread=6120 (0x17E8)>
STATMSG: ID=7906 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:00:53.964 2015 ISTR0=”ALX00015″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:53.964-120><thread=6120 (0x17E8)>
wimgapi.dll tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:54.031-120><thread=6120 (0x17E8)>
Image package file with ID ALX00015 contains 1 image(s)  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:54.045-120><thread=6120 (0x17E8)>
Processing image at index 1  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:54.045-120><thread=6120 (0x17E8)>
Mounting image at index 1. Image file=’C:ConfigMgr_OfflineImageServicingALX00015install.wim’, MountDirectory=’C:ConfigMgr_OfflineImageServicingALX00015ImageMountDir’, ImageFileType=’WIM’, Mode=’ReadWrite’  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:00:54.045-120><thread=6120 (0x17E8)>
Image OS information: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:11.537-120><thread=6120 (0x17E8)>
Checking if update (1 of 5) with ID 16782294 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:11.670-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:11.784-120><thread=6120 (0x17E8)>
Applicability State = APPLICABLE, Update Binary = C:ConfigMgr_OfflineImageServicing64e31a0d-0aae-4c94-8099-b986044369fcwindows10.0-kb3081449-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:26.053-120><thread=6120 (0x17E8)>
Applying update with ID 16782294 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:26.053-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:26.116-120><thread=6120 (0x17E8)>
STATMSG: ID=7908 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:02:37.088 2015 ISTR0=”16782294″ ISTR1=”ALX00015″ ISTR2=”1″ ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:37.089-120><thread=6120 (0x17E8)>
This update binary was successfully updated on the mounted image.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:37.090-120><thread=6120 (0x17E8)>
Checking if update (2 of 5) with ID 16782298 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:37.372-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:37.394-120><thread=6120 (0x17E8)>
Applicability State = APPLICABLE, Update Binary = C:ConfigMgr_OfflineImageServicingd9721f97-0a68-4b5e-b0fd-20c7d408ac44windows10.0-kb3081452-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:46.294-120><thread=6120 (0x17E8)>
Applying update with ID 16782298 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:46.295-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:02:46.318-120><thread=6120 (0x17E8)>
STATMSG: ID=7908 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:03:00.793 2015 ISTR0=”16782298″ ISTR1=”ALX00015″ ISTR2=”1″ ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:03:00.793-120><thread=6120 (0x17E8)>
This update binary was successfully updated on the mounted image.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:03:00.793-120><thread=6120 (0x17E8)>
Checking if update (3 of 5) with ID 16782401 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:03:09.389-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:03:10.362-120><thread=6120 (0x17E8)>
Applicability State = APPLICABLE, Update Binary = C:ConfigMgr_OfflineImageServicingb122e579-03b8-4389-ba6c-1ae33adc7fdfwindows10.0-kb3093266-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:03:32.372-120><thread=6120 (0x17E8)>
Applying update with ID 16782401 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:03:32.372-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:03:32.403-120><thread=6120 (0x17E8)>
STATMSG: ID=7908 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:08:05.947 2015 ISTR0=”16782401″ ISTR1=”ALX00015″ ISTR2=”1″ ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:05.950-120><thread=6120 (0x17E8)>
This update binary was successfully updated on the mounted image.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:05.951-120><thread=6120 (0x17E8)>
Checking if update (4 of 5) with ID 16784701 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:06.329-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:06.370-120><thread=6120 (0x17E8)>
Applicability State = APPLICABLE, Update Binary = C:ConfigMgr_OfflineImageServicing58666e4f-17d6-4778-9bfd-6b5187e44acbwindows10.0-kb3099406-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:16.969-120><thread=6120 (0x17E8)>
Applying update with ID 16784701 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:16.969-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:17.026-120><thread=6120 (0x17E8)>
STATMSG: ID=7908 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:08:30.593 2015 ISTR0=”16784701″ ISTR1=”ALX00015″ ISTR2=”1″ ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:30.593-120><thread=6120 (0x17E8)>
This update binary was successfully updated on the mounted image.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:30.594-120><thread=6120 (0x17E8)>
Checking if update (5 of 5) with ID 16784719 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:39.337-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:40.374-120><thread=6120 (0x17E8)>
Applicability State = APPLICABLE, Update Binary = C:ConfigMgr_OfflineImageServicingf204e535-351e-4c1a-80c6-9ea09c925c0cwindows10.0-kb3097617-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:56.933-120><thread=6120 (0x17E8)>
Applying update with ID 16784719 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:56.933-120><thread=6120 (0x17E8)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:08:56.951-120><thread=6120 (0x17E8)>
STATMSG: ID=7908 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:11:37.643 2015 ISTR0=”16784719″ ISTR1=”ALX00015″ ISTR2=”1″ ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:11:37.646-120><thread=6120 (0x17E8)>
This update binary was successfully updated on the mounted image.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:11:37.646-120><thread=6120 (0x17E8)>
Total number of updates that have been successfully applied on the mounted image is 5  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:11:37.647-120><thread=6120 (0x17E8)>
UnMounting Image (Commit Changes = 1) …  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:11:37.647-120><thread=6120 (0x17E8)>
STATMSG: ID=7907 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:14:57.929 2015 ISTR0=”ALX00015″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.929-120><thread=6120 (0x17E8)>
Completed processing image package ALX00015. Status = Success  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.939-120><thread=6120 (0x17E8)>
STATMSG: ID=7904 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:14:57.939 2015 ISTR0=”ALX00015″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.940-120><thread=6120 (0x17E8)>
Create backup copy for image ALX00015  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.943-120><thread=6120 (0x17E8)>
copying image file ‘\szhv-cm01OSDWIMWindows 10 x64 Enterprise Goldinstall.wim’ to ‘\szhv-cm01OSDWIMWindows 10 x64 Enterprise Goldinstall.wim.bak’ …  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.943-120><thread=6120 (0x17E8)>
Copy image ( ID ALX00015, size 3266 MB )  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.944-120><thread=6120 (0x17E8)>
copying file from ‘C:ConfigMgr_OfflineImageServicingALX00015install.wim’  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.944-120><thread=6120 (0x17E8)>
to ‘\szhv-cm01OSDWIMWindows 10 x64 Enterprise Goldinstall.wim’ ….  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:14:57.944-120><thread=6120 (0x17E8)>
Copying (25% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:16:38.317-120><thread=6120 (0x17E8)>
Copying (50% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:18:13.434-120><thread=6120 (0x17E8)>
Copying (75% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:19:58.688-120><thread=6120 (0x17E8)>
Copying (100% complete)…   $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:38.989-120><thread=6120 (0x17E8)>
Original image ‘\szhv-cm01OSDWIMWindows 10 x64 Enterprise Goldinstall.wim’ is backed up at ‘\szhv-cm01OSDWIMWindows 10 x64 Enterprise Goldinstall.wim.bak’  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:38.990-120><thread=6120 (0x17E8)>
Successfully requested image ALX00015 to be updated from its source.~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.104-120><thread=6120 (0x17E8)>
STATMSG: ID=7905 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:21:39.105 2015 ISTR0=”ALX00015″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.106-120><thread=6120 (0x17E8)>
Updated history for image package ALX00015 in the database  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.121-120><thread=6120 (0x17E8)>
Schedule processing succeeded  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.121-120><thread=6120 (0x17E8)>
Processing completed for Schedule with ID 16777217  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.121-120><thread=6120 (0x17E8)>
STATMSG: ID=7901 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_OFFLINE_SERVICING_MANAGER” SYS=SZHV-CM01.mcse.lab SITE=ALX PID=2252 TID=6120 GMTDATE=gio ott 15 21:21:39.121 2015 ISTR0=”16777217″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.121-120><thread=6120 (0x17E8)>
Schedule processing thread stopped~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.372-120><thread=6120 (0x17E8)>
Checking if there are schedule(s) which need to be run at this time.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.372-120><thread=5180 (0x143C)>
This Schedule with ID 16777217 does not have a next run time  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.374-120><thread=5180 (0x143C)>
No more schedules are found to be run at this time or in the future.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.374-120><thread=5180 (0x143C)>
Will sleep till a new schedule is created.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.374-120><thread=5180 (0x143C)>
No schedule exists which needs to be run anytime in future.  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.374-120><thread=5180 (0x143C)>
Offline Servicing Manager thread is exiting.~  $$<SMS_OFFLINE_SERVICING_MANAGER><10-15-2015 23:21:39.375-120><thread=5180 (0x143C)>

[/su_spoiler]

Advertisements

4 thoughts on “SCCM Offline Servicing for Operating System Images

  1. Does the “ConfigMgr_OfflineImageServicing” folder used to temporarily store backup WIMS ever get cleaned up? I think the backed up WIM also remains despite removing an Operating System Image from the console.

    Like

    1. Hi Jack, thanks for your comment!

      On top of my mind I don’t think it is automatically cleaned up but you can manually force this with

      – DISM /cleanup-wim which will remove all stale files
      – DISM /cleanup-mountpoints which as the name implies will remove stale mount points

      I know by experience there are situations where DISM will report all stale files have been cleaned up but nothing gets deleted. Trying to manually remove the folder/files you will get an access denied, in such cases the only solution I am aware of is either rebooting the server and re-running the dism /Cleanup command or using dism /unmount-wim” with the /discard option to avoid the reboot 🙂

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s