SCCM 2016 – Add Operating System Image
Now we have the Boot Image configured, Distribution Point Configured and DHCP ready. The environment is ready for deployment, but still needs to add flavours of OS to be deployed.
SCCM uses same windows image to deploy to various types of systems like Servers, Laptops, Desktops, Virtual disks and virtual machines. SCCM uses WIM Files for this purpose. “A Windows operating system image is a self-contained file using the Windows Imaging Format (WIM). A WIM differs from other image formats such as ISO because it’s file-based. It’s designed to store files and then use an image index to reference those files.”
A WIM file can contain multiple image indexes because it has to store each file only once. For example, say you use ConfigMgr or MDT to build a custom image, and then later use the same process to build another image that has extra applications. You can store both images in the same WIM file, but files that are common to both images are stored only once. In this way, WIM is an effective and efficient way of building custom images, which is why they’re the foundation of operating system deployment (OSD) in ConfigMgr.
To add an Operating System Image in SCCM 2016, just Launch SCCM Console and Go to Software Library > Operating systems.
Right Click on Operating Systems
Specify the path to the Operating system image file. It must be UNC path.
Click Next to Continue
Specify Name, Version and or any comments.
Click Next To Continue
To Create the Operating System Image, Click Next
Wizard will provide you details of the task whether it is completed successfully or not.
Click Close to Finish
This completes the Adding an Operating System Image to SCCM 2016
References:
Book: Learn System Center Configuration Manager in a Month of Lunches: Covers SCCM 1511 and windows 10
By James Bannan
Comments: 4
Articles at your site are a great help; hoping to get a little more information here would be helpful: “Specify the path to the Operating system image file. It must be UNC path.”
Is this the path to some image file that sccm is going to referece and suck in as I build the image? Is this the path the clients will use to find the file when they boot? If it’s the path the clients will use, do I put something there before I start all this, or does this process put something there or am I just way out in the weeds.
Actually this path is used as source for the wim file of the operating system.
This path will not be used to deploy to client. Clients will get copy of it from the distribution points.
After adding the operating system, you will need to deploy or distribute it to distribution points to be able to used by clients.
Thank you for the info! Clearing up the picture for me little by little. To complete my lack of concept, can you tell me: Does the o.s. expect a file to already be there (and then is there an article for how to build and place this image?)? Or will it build something in there?
To Successfully Deploy the Operating system System to Client, you have to follow few of the blogs with detailed information in them.
Follow blogs on – https://harmikbatth.com/2017/02/