How to enable Offline Servicing for Operating System Images in Configuration Manager 2012
How to / Nasıl yaparım:
In Configuration Manager 2012 there is a new feature for applying updates to operating system images while they are in the Configuration Manager library. This means any operating system image you see in the Operating Systems > Operating Systems Images node from the Software Library wonderbar can be updated with Component Based Servicing (CBS) updates. By updating an image in the Software Library instead of performing a new build and capture of the operating system image you will gain a few distinct advantages. You will be able to reduce the risk of vulnerabilities during operating system deployments and reduce the overall operating system deployment to the end user. You will also reduce the administrative effort to maintain your operating system images.
The feature is applicable for Component Based Servicing (CBS) updates and for the following operating systems:
Microsoft Windows Vista SP2 and later Microsoft Windows Server 2008 SP2 and later Microsoft Windows 7 SP1 and later Microsoft Windows 2008 R2 SP1 and later
As mentioned previously, offline servicing is available for CBS updates. This will work in coordination with the Configuration Manager Software Updates Point role.
Here are a couple steps to do before we start.
Configure the Software Update Point Deploy updates to you Configuration Manager 2012 clients
Once the first two steps are completed, we can service operating system images in your Configuration Manager library.
From the Software Library wonderbar, select Operating System > Operating System Images Select an image you would like to update. This needs to meet the supported platforms listed above. Select an image then click Schedule Updates from the ribbon.
The Update Operating System Image wizard will appear. A list of updates will be presented. The list contains updates meeting the following criteria: The updates are CBS updates The updates have been downloaded in your Configuration Manager environment. The updates have not successfully been deployed to your image file through the offline servicing feature
These updates are filtered to match the architecture of the image file.
(Illustrated above; The schedule updates wizard presenting updates for a .wim file)
So now we have set our servicing schedule. Let’s go through the servicing process.
When the schedule time occurs for updating the .wim file, the site server will copy the .wim file from the package source and the appropriate updates from the content library to a temp folder. The site server will mount the .wim file in the temp folder. Through the use of DISM the selected updates are applied to the .wim file. The updates will be applied to all applicable images in the .wim file. Upon success, the wim is restored to the package source location. The original copy of the .wim file preserved as a backup copy to help you easy revert if an update causes any issues. Configuration Manager only retains one back up copy. So the previous back up copy will be removed if it exists. After the process is completed, the update status can be viewed from within the console. In the event of a failure, you will see which updates could not be successfully applied to the .wim file. Additionally, a historical view of the updates can be seen from the image property page.
(Illustrated above; A successful update to a .wim file in the ConfigMgr Software Library. Notice the Update Status tab showing the updates that were processed during the last task.)
(Illustrated above; properties page of an image in the Software Library. All updates that have been successfully installed can be viewed here.)
After the servicing is complete, you will need to still perform an “Update Distribution Point” action on the image. This will ensure the newly updated image is updated and available on assigned distribution points in your ConfigMgr infrastructure.