Specify any workgroup name you like but I stick to WORKGROUP just for simplicity. We don’t want our reference machine to join the domain as joining the domain will cause Group Policy Objects to be applied to the image which could in turn install software, none of which we want included in the base image. Next, we need to specify our machine to join a workgroup and not a domain. If you are using a Windows image that provides multiple Images such as Home Basic, Home Premium and Professional then you need to make sure you specify the correct image from the list. The install.wim file in the source Windows media only contains a single image so Image 1 automatically selected from the. In this demonstration, I am using Windows 8.1 Enterprise with Update (圆4). Next, we need to specify our source operating system. You should always use the 32-bit (x86) boot image because with this one image we can support both 32-bit and 64-bit operating system images however if you use the 64-bit boot image, that is only able to support 64-bit operating system images. Next, we need to give our Task Sequence a name and specify the boot image to use. In the Task Sequence Wizard, select the Build and capture a reference operating system option. Once you have imported your base Operating System Images, we need to create a new Task Sequence. If you are supporting many operating systems, I would highly recommend creating a folder structure to aid locating the images. Repeat this for as many Operating System versions and architectures as you need to support. iso file you plan to use for your installations to a suitable directory in your SCCM source structure and import the Operating System Images as shown above. In this part, we will create task sequences to build and capture the reference images and update them as needed. In this first part, we will lay the foundation for what will become the core of the deployment – the Windows Operating System images. The end goal will be to use Configuration Manager with MDT integration to provide a rich end-user experience for deploying operating systems. This is the first in what will become a multi-part series of posts on configuring Operating System Deployment in Configuration Manager 2012 R2.
0 kommentar(er)
