Toolzz. com . Many companies are now planning to upgrade their machines from Windows XP to Windows 7 or Windows 8 and will be using SCCM to do so. In the SP1 version of SCCM 2. OSD to fail. This blog will describe the right steps to deploy Windows 7 and also Windows 8. Peerguardian 2 Download Phoenix Labs Games more. This because there are no differences between deploying them. In the steps taken below we presume this is a clean install and you don’t have an Windows 7 image file.

First install hotfix http: //support. Site Servers. This is required to do a successful PXE boot. Enable the Network Access Account.

The “Network Access Account” is needed during deployment in Win. PE. The account is uses to access the content on the network. Often forgotten so we start with it. In the Configuration Manager console, navigate to Administration, choose  Site Configuration, right- click on the Primary site, and select Configure Components, Software Distribution.

In the Network Access Account tab, click the Specifiy the account that access network locations, choose Set and Add the network access account and provide it with a password choose OK to finish the config. Enable PXE support and boot. In the Configuration Manager console, navigate to Administration, choose  Site Configuration, and choose Servers and Site System Roles, and select the server which hosts you’re distribution point.

In the results pane, double click the Distribution Point role and select the PXE tab, place a checkmark on Enable PXE support for Clients, answer Yes for the firewall port question. Check the Allow this distribution point to respond to incoming PXE requests and Enable unknown computer support also I’ve removed the password option but this is not required.

Click OK and the SCCM machine will distribute the settings. Next step is to distribute the Boot Images to the distribution points. In the Configuration Manager console, navigate to Software Library, Operating Systems, Boot Images. Right click the X6. Distributed Content, Click Next and click Add, Distribution Point choose you’re distribution point.

Continue through the wizard to complete the distribution. DON’T Forget to repeat this step for the X8. Enable the PXE boot image. How Much To Pay For Window Installation on this page. In the Configuration Manager console, navigate to Software Library, Operating Systems, Boot Images. Right click the X6. Properties. In the results pane, click Data Source, and enable the  Deploy this boot image from the PXE service point. Select OK and the distribution point will be updated.

This part describes how to create a deployment packages and how to deploy it.

Build, Capture and deploy Windows 7 and Windows 8 in SCCM 2012 SP1.

1. In our environment we have a single AD forest and use Config Mgr 2012 R2.We have the following folder structure: Domain\Servers\Exchange.
2. Significant changes to Software Updates in Configuration manager 2012 compare with previous Version.One of the cool Feature is Automatic Deployment Rule which.
3. If you would like to read the other parts of this article series please go to: SCCM 2012 Client Deployment (Part 1) SCCM 2012 Client Deployment (Part 2).

DON’T Forget to repeat this step for the X8. Add the Windows 7 Operating System. Here’s where it get’s a bit tricky, SP1 doesn’t support the old Operating System Installers so a little change in SP1.

First of all I created the following structure to get a structured collection of Operating System Deployments. Second I extracted the Windows 7 ISO and copied it to \\demo- sccm. Sources\OSD\OSD Uploads\Windows. Next is build and capture the new image. Now we are going to build a new WIM file.

This will be an template file which SCCM uses to rollout new Operating System Deployments. In the Configuration Manager console, navigate to Administration, choose  Software library, Operating Systems, Task Sequences, Create a folder called Windows 7 x. Create Task Sequence. At the Create new task sequencechoose Build and Capture a reference operating system image, Next. In the Task Sequence Information, give the task sequence a logical name like “Build and Capture – Windows 7 Pro x. NLD” , choose the “Boot Image (x.

I filled in the password to login in the reference machine after the build and capture. If the license key is also not necessary both settings can be set in the Deploy Sequence afterwards. In the Configure Network choose the workgroup option. This because Sysprep will not work when you join the machine to a domain. In the Install Configuration Manager Client section leave this default (installation properties can be blank, we will change this in the actual deployment.) Next. At the Include Updates we checked Do not install any software updates, choose Next. Choose Next at the Install Applications.

Choose Next at the System Preparation Section. Fill in the details on the Image Properties and choose Next. At the Save As dialog box, choose the created  \\demo- sccm. Sources\OSD\OSD\Captures\ folder and give the image a proper name. Choose Save, Next and Finish the task sequence.

Right click the newly created task sequence and choose Edit. Click on the last partition task, choose Add, General, Set Task Sequence Variable. This is to assign the C: \ as boot drive. Otherwise the sequence will install Windows on D: \. Name tab type Assign C: \ to Boot drive, at the task Sequence Variable type OSDPreserve.

Drive. Letter with the value false place the task behind the partition tasks. Choose OK to apply the task sequence changes. Now we are going to distribute the task sequence to the distribution point; right- click the newly build task sequence and choose deploy. I’ve chosen the collection All Unknown Computers, this results that the capture is available for everyone.

In a test environment this is not issue but in production it’s not recommended, choose Next. In the Make available to the following choose Only Media and PXE, Next. Just next, next finish to the configuration; no additional changes are required. OK now it’s get exiting; if everything went well you now can startup you’re client machine to boot with F1.

At the task Sequence Wizard, choose the Build and Capture – Windows 7 Pro x. NLDThe capture begins, the sequence finishes some steps to build the new WIM file.

In these steps you will see that the new WIM file is build in de Captures directory. Deploy the captured image in a task sequence.

Next we going to create the deploy sequence to rollout the WIM image to the clients. In the Configuration Manager console, navigate to Administration, choose  Software library, Operating Systems, Task Sequences, Create a folder called Windows 7 x. Create Task Sequence.

At the Create new task sequencechoose Install an existing image package, Next. In the Task Sequence Information, give the task sequence a logical name like “Deploy – Windows 7 Pro x.

NLD“, choose the “Boot image (x. Fill in the domain, Domain OU and account (this is a test environment but please do not use administrator)In the Install Configuration Manager Client section and set the installation properties to SMSMP=Demo- SCCM0. Next. At the state migration we deselect all check boxes because we do not use this in the lab., choose Next. At the Include Updates we checked Do not install any software updates, choose Next. Choose Next at the Install Applications and finish the wizard.

Right click the newly created task sequence and choose Edit. Choose Add, General, Set task Sequence Variable.

Name tab type Assign C: \ to Boot drive, at the task Sequence Variable type OSDPreserve. Drive. Letter with the value false place the task behind the partition task. Choose OK to apply the task sequence changes. Now we are going to distribute the task sequence to the distribution point; right- click the newly build task sequence and choose deploy.

I’ve chosen the collection All Unknown Computers, this results that the deployment is available for everyone. In the Make available to the following choose Only Media and PXE, Next. Just next, next finish to the configuration; no additional changes are required.

OK now it’s get exiting; if everything went well you now can startup you’re client machine to boot with F1. Choose the new created task sequence! That’s it! The deployment will run successfully!!