Criar um Windows 8.1 Referência Imagem com MDT 2013

Overview

  • Informações sobre o ambiente
  • Configuração do ambiente
  • Configurar o WSUS aprovação automática e agenda de sincronização
  • Criar uma estrutura de pastas na imagem de referência para
  • Criar um laboratório de compartilhamento de implantação
  • Configure o compartilhamento de implantação
  • Modificar as regras
  • Modifique o Bootstrap.ini
  • Baixe a mídia de instalação do Windows 8.1 Empresa
  • Adicionar um Sistema Operacional
  • Criar uma sequência padrão Client Task
  • Atualize o MDT Deployment Share – Environment Lab
  • Criar uma nova máquina virtual e começar a criação da imagem de referência

Informações sobre o ambiente

Eu recomendo para instalar um novo Windows Server 2012 (ou R2) da máquina virtual e chamá-lo MDT01 (você pode chamá-lo de qualquer coisa que você quiser, mas essa é a máquina que eu vou fazer referência ao longo deste post). O servidor deve ter o seguinte software instalado:

  • O Windows ADK 8.1
  • MDT 2013
  • Windows Server Update Services 4.0

MDT 2012 atualização 1 não é suportado com o Windows 8.1, nem é o do Windows 8 ADK. É por isso que precisamos de ter os últimos lançamentos de ambos MDT e Windows ADK.

O servidor MDT01 deve ser associado a um domínio. O ideal para um domínio ambiente de laboratório. Você também precisará criar uma conta de usuário do Active Directory, MDT_BA e dar-lhe uma senha como Pa $$ w0rd. A conta MDT_BA ea senha é inserida na seção regrasdescritas mais abaixo e também usado para se conectar ao compartilhamento de implantação.

Configuração do ambiente

1 Comece a instalar o Windows ADK 8.1. Durante a instalação, você terá a opção de instalar vários recursos. Os recursos a seguir são necessários:

  • Ferramentas de Implantação
  • O Windows pré-instalação ambiente Windows (Windows PE)
  • User State Migration Tool (USMT)

2 Continue com a instalação MDT 2013. Isto deve ser relativamente fácil e não necessita de qualquer explicação.
3 Instalar o WSUS 4.0, executando o seguinte comando em um console elevado PowerShell:

4. Paste the following into the same PowerShell console and press Enter :

5. Launch Windows Server Update Services console.
6. The Windows Server Update Services Wizard now appears.

50_2

7. Click Next on the Before You Begin page.
8. Click Next on the Microsoft Update Improvement Program page.
9. Click Next on the Choose Upstream Server page.
10. Click Start Connecting on the Specify Proxy Server page. This might take a few minutes. ClickNext when finished.
11. On the Choose Languages page, select the languages you wish to download updates for. In this post we’ll only be downloading updates in English . Click Next .
12.  On the Choose Products page, deselect everything except for Windows 8.1 . Be aware though that if you’re gonna create a reference image with applications embedded (e.g. Office ), remember to add those applicable applications in WSUS later on, otherwise when the step for installing updates begins your reference image will not have any updates for that application. For the purpose of this post, we’re only creating a thin reference image with no applications. Click Next .
13. Click Next on the Choose Classifications page.
14. Select Synchronize automatically on the Configure Sync Schedule page and specify a time schedule that suits your environment. Click Next .
15. On the Finished page, select Begin initial synchronization and click Finish .

Configure WSUS automatic approval and synchronization schedule

1. Launch the Windows Server Update Services console on MDT01 , expand Update Services -> MDT01 and click on Options . Configure the Automatic Approvals according to the picture below:

50_3

2. Click on Run Rule .

Create a folder structure for the reference image

1. On the MDT01 server, create the following folder structure:

C:\OSD\ReferenceImages (You could of course choose another structure that suits you better, but remember to edit the Rules section described further down in this post)

2. Right-click on the OSD folder and select Properties . On the Sharing tab, click on Advanced Sharing and then Permissions . Everyone should have Full Control . Click OK until you get back to the OSD Properties window.
3. Click on the Security tab and then Edit . Add the MDT_BA account and ammend its permissions with Modify .

Create a lab Deployment Share

1. Open Deployment Workbench on MDT01 .
2. Right click on Deployment Shares and choose New Deployment Share .
3. Enter C:\DeploymentShare as the path for this deployment share and click Next .
4. Choose the default share name suggested ( DeploymentShare$ ) and click Next .
5. Name the deployment share description MDT Deployment Share – Lab Environment and click Next .
6. Click Next on the Options  page.
7. On the Summary page, click Next .
8. Click Finish on the Confirmation page.

Configure the Deployment Share

1. Right-click and choose Properties on the MDT Deployment Share – Lab Environmentdeployment share and click on the Windows PE tab.
2. Select platform x64  and make sure that Generate a Lite Touch bootable ISO image is checked. Change Scratch space size to 128 .

50_5

3. Under the Features  tab of the Windows PE tab, check .NET Framework and Windows PowerShell 3.0 . This step is optional, but necessary if you’d like to add some PowerShell scripts to your task sequence at a later stage.

50_4

4. Click Apply and then OK .

Modify the Rules

1. Right-click and choose Properties on the MDT Deployment Share – Lab Environmentdeployment share and click on the Rules tab.
2. Replace the existing rules with the following:

3. Make sure that you edit the rules so that they suit your environment. For example, my domain is contoso.com. Edit the following rows:

UserDomain= contoso.com
WSUSServer=http://mdt01. contoso.com :8530
BackupShare=\\mdt01. contoso.com \OSD

4. If you’ve choosen to give the MDT_BA user another password, remember to change that row aswell:

UserPassword= Pa$$w0rd

5. Click on Apply and then OK .

Modify the Bootstrap.ini

1. Right-click and choose Properties on the MDT Deployment Share – Lab Environmentdeployment share and click on the Rules tab.
2. Click on Edit Bootstrap.ini .
3. Replace the existing settings with the following:

4. Change the UserDomain=contoso.com row so that it contains your domain instead.
5. If you’ve given the MDT_BA account another password than Pa$$w0rd , change it here aswell.
6. Close Bootstrap – Notepad , click Apply and then OK .

Download the Windows 8.1 Enterprise installation media

1. Log on to either MSDN or TechNet and download the Windows 8.1 Enterprise ISO.
2. Mount the ISO on MDT01 .
3. Browse the mounted ISO and go to <drive-letter>:\sources .
4. Copy the install.wim to C:\Install (create the folder if necessary).

Add an Operating System

1. Go back to the Deployment WorkBench , right-click on Operating Systems and choose New Folder.
2. In the New Folder window, name the folder Windows 8.1 Enterprise x64 and click Next .
3. Click Finish when the task has completed.
4. Right-click on the newly created folder and choose Import Operating System .
5. On the OS Type page, select Custom image file and click Next .
6. Browse to the install.wim file copied earlier and click Next .
7. On the Setup page, select Setup files are not needed and click Next .
8. Specify the Destination directory name Windows 8.1 Enterprise x64 on the Destination page and click Next .
9. Click Next on the Summary page.
10. Click Finish when the process has completed successfully.
11. Optional: Right-click on the newly added operating system and select Rename . Rename it toWindows 8.1 Enterprise x64 – Install .

Create a Standard Client Task Sequence

1. Right-click on Task Sequences and choose New Folder .
2. In the New Folder window, name the folder Windows 8.1 Enterprise x64 and click Next .
3. Click Finish when the task has completed.
4. Right-click on the newly created folder and choose New Task Sequence .

50_6

5. Enter WIN81REF  under Task sequence ID and Windows 8.1 Enterprise x64 – Reference under Task sequence name and click Next .
6. Select Standard Client Task Sequence as your template on the Select Template page and click Next .
7. Select the Operating System created earlier called Windows 8.1 Enteprise x64 – Install and click Next .

50_7

8. Select Do not specify a product key at this time on the Specify Product Key page and click Next .
9. On the OS Settings page, enter your organization information into the Organization field, but leave the Full Name  and  Internet Explorer Home Page values by default (you could change them if’d like) and click Next .
10. On the Admin Password page, select Do not specify an Administrator password at this timeand click Next .
11. Click Next on the Summary page.
12. Click Finish when the process has completed successfully.
13. Right-click on the Windows 8.1 Enterprise x64 – Reference task sequence and selectProperties .
14. Go to the Task Sequence tab.
15. Under the State Restore group, enable  Windows Update (PreApplication Installation) and Windows Update (Post-Application Installation) . You can enable a step by selecting it and clicking on the Options  tab for that step, then uncheck the Disable this step . It’s a good idea to enable both Windows Update steps, if you plan to install application in your reference image.

50_8

16. Disable the BitLocker step.

50_9

17. Click Apply and then OK  in the task sequence window.

Update the MDT Deployment Share – Lab Environment

1. Right-click on MDT Deployment Share – Lab Environment and select Update Deployment Share .
2. Select Optimize the boot image updating process and click Next .
3. On the Summary page, click Next .
4. Click Finish when the process has completed successfully.

Create a new virtual machine and start the reference image creation

1. Copy the LiteTouchPE_x64.ISO file from C:\DeploymentShare\Boot on MDT01 to either a network share or locally on your virtual machine host server.
2. Create a new virtual machine and mount the LiteTouchPE_x64.ISO to the CD/DVD drive of the virtual machine.
3. Boot the virtual machine and let the magic begin.

50_10

4. Once the image has been applied, you’ll get presented with the Start screen . Don’t be afraid and think that something is broken and the task sequence failed. If you click on the Desktop tile, you’ll see that the task sequence is still running.

50_11

5. When sysprep is done, it will start to create a WIM file. At the end the WIM file will be backed up to the path specified earlier in the Rules section.

50_1

That’s it! You now have a reference image ready to be deployed with ConfigMgr 2012 .

Deixe uma resposta

Preencha os seus dados abaixo ou clique em um ícone para log in:

Logotipo do WordPress.com

Você está comentando utilizando sua conta WordPress.com. Sair / Alterar )

Imagem do Twitter

Você está comentando utilizando sua conta Twitter. Sair / Alterar )

Foto do Facebook

Você está comentando utilizando sua conta Facebook. Sair / Alterar )

Foto do Google+

Você está comentando utilizando sua conta Google+. Sair / Alterar )

Conectando a %s

%d blogueiros gostam disto: