![]() Personally my build number is the date the image was built, in the format of 050216. It’s also a good idea to append the name with a build number for your images. I suggest the name should clearly identify the operating system, the edition and architecture. Name the folder “Production Images”.Ĭ) Then create a subfolder called “Windows 10 ENT 圆4” or something similar according to your own naming conventions.ĭ) Right-click on the “Windows 10 ENT 圆4” folder you just created and select “Add Operating System Image”Į) Enter the full UNC path to the reference image which you copied into your software repository in step 1.1 above.į) Click on Next and give your reference image a name. ![]() Expand the “Operating Systems” folder and then expand “Operating System Images”.ī) Right-click on the “Operating System Images” node and select Folder > Create Folder. Your Software Library workspace should equally be organized with a clear folder structure.Ī) Open the SCCM console and click on the Software Library workspace. You may have a different folder structure – what matters is that it should be organized so you it’s easier to locate everything. My folder structure for storing OS images looks like this: I suggest organizing the software repository with a clear folder structure. In my case I have a folder called “Sources” where I store all my software, packages, and images relating to SCCM. We left the previous post after having captured the image using MDT, which saved the image into the “Captures” folder inside the MDT deployment share root.īefore importing the image into SCCM we have to copy/move the image to the SCCM software repository. Step 1) Import the Windows 10 Reference Image into SCCMġ.1) Copy the Reference Image to the SCCM Software Repository I’m going to assume you already have SCCM up and running and have access to your SCCM software repository. ![]() We’ll then create a package for our unattend.xml answer file to be used in our task sequence. ![]() Here, we’ll start off with importing our reference image into SCCM and then creating our task sequence to deploy the image. In the second post we created our unattended answer file and captured our reference image. Recap: In the first post we built our reference image using MDT and customized our default profile. This is the final part of a three-part series on Windows 10 OSD using MDT and SCCM 2012 R2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |