Shulou(Shulou.com)06/02 Report--

Installing the operating system has always been a headache for operation and maintenance personnel. The traditional installation method, which installs the operating system through U disk or CD, is tedious and inefficient. This paper introduces a method of using WDS+MDT to deploy the operating system in batches through the network, which can achieve user autonomy, batch deployment, and unattended installation of the operating system, which greatly improves the efficiency of operation and maintenance.

I. Environmental preparation

The architecture used here is shown below

AD (DC): the Windows deployment server must be a member of the Addomain, or a domain controller, where our WDS is a domain member.

DNS: an effective DNS server is required in the network

The DHCP:windows deployment service relies on DHCP for IP addressing PXE, so there must be a valid DHCP server in the network, where the DHCP is set up in the Cisco switch.

WDS:Windows deployment Services (Window Deployment Services)

MDT:MicrosoftDeploymentToolkit, system deployment tool

Tool preparation:

The ADK:MDT function needs to be supported by some components of ADK, so you must install ADK before installing MDT

Net Framework 3.5 needs to be installed at the same time

Here

Our AD,DNS,DHCP already exists in the company environment, so I just need to set up WDS and MDT.

Here, I choose windows server 2012 WDS and MDT to store the server version on the same server.

MDT tool I choose MDT2013

Download address: https://www.microsoft.com/en-us/download/details.aspx?id=48595

ADK win10

Download address: https://docs.microsoft.com/zh-cn/windows-hardware/get-started/adk-install

Here we skip the process of installing and configuring the AD,DNS,DHCP server and go straight to the topic

II. Server installation

(1) install WDS

I am using the Win Srv2012 Datacenter version here and have joined the domain

Choose to install windows deployment Services (WDS), which I have already installed here

Install .NET Framework 3.5 (I have successfully installed it)

Here, because the system has installed 4.5, the installation of .net.35 will report an error and fail, so you need to install it manually.

Run PowerShell as an administrator and click the following command to install:

Set-ItemProperty-Path 'HKLM:\ SOFTWARE\ Policies\ Microsoft\ Windows\ WindowsUpdate\ AU'-Name UseWUServer-Value 0

Restart-Service-Name wuauserv

Install-WindowsFeature Net-Framework-Core

Set-ItemProperty-Path 'HKLM:\ SOFTWARE\ Policies\ Microsoft\ Windows\ WindowsUpdate\ AU'-Name UseWUServer-Value 1

Restart-Service-Name wuauserv

You can copy all the specific operations, and then paste them all and enter.

Check both the deployment server and the transport server

WDS service installed successfully

(2) configure WDS

Open the windows deployment Services Management console

Right-click to select configuration server

It can be integrated with AD or independent.

Select the path of a remote installation folder, either by default or customized, as long as there is enough disk space, and if you choose the default path, skip the warning directly.

PXE settings respond to all clients

After configuration, as shown in the figure, the WDS server has been Up

(3) install MDT

Download MicrosoftDeploymentToolkit2013_x64.msi for installation

Directly default, you can install it in the next step

(4) install ADK win10

Download ADK win10 for installation

Deployment tools must be installed, and USMT must be installed as appropriate.

It is worth noting that ADK win10's PE environment provides a separate installation package. Install ADK win10 before installing the PE environment

If the server environment cannot be installed online, you can run the installer locally, download the complete installation package, and then upload the installation package to the server to run the installation.

Installation completed

(5) configure MDT workbench (DeploymentWorkbench)

Open "DeploymentWorkbench", select "Deployment Share", right-click, and select "New Deployment Share"

The storage path can be customized. Next step

The mode is hidden sharing. Next step

You can briefly describe the deployment sharing, and the next step

By default, check 3 items, next step

MDT workbench configuration completed

Third, add resources

(1) Import the operating system (OS)

We can set up some folders in New Folder to facilitate the classification of operating systems, and the classification criteria can be set according to Chinese and English, operating system categories, and so on.

Here, take importing win7 as an example.

Load the imported ISO file to the CD drive and click Browse to navigate to the file location

Import completed

After import, double-click to view OS information

(2) Import applications

Similar to importing OS, New Folder classifies

New Application Import Application

Take importing Adobe Reader as an example

The command line is as follows: AdbeRdr11000_zh_CN / sPB / rps

It should be noted that the command line installation of impassable software is different, and most of them are installed by "software name / S". In special cases, you need to query the silent installation statement of the software command line and fill in the commd Line.

Here is a way to get the installation parameters.

PS:

Get an installer and use /? Check it out.

If you don't support /? Parameters. You can also use the silent installation parameters to try ([/ S] [/ silent [/ noreboot]] [/ verysilent [/ sp-] [/ norestart]] [/ Q] [/ qn] [/ qb] [REBOOT=SUPPRESS] [/ s / v/qn] [/ qverysilent / n / z] [/ quiet] [/ SilentInstallNoSponsor] [/ SilentInstall] [/ s / qn] [/ S / qd] [- s] [- Q] etc.)

This step is boring, but it is usually more effective.

(3) Import driver

Two recommended methods for obtaining driver files

First, download the corresponding driver from the official website of the corresponding host model, extract the installation program, extract the inf file, and import it to the MDT workbench.

Second, when the official driver cannot be found, or the official driver is not identified, now the host uses software such as driver wizard to install the driver, and then export the installed driver through software backup and import it to the MDT workbench.

The same classification and import steps

Select the storage path of the driver. The driver here must be in inf format.

The import is successful. Here I will take the import of a USB driver as an example.

(4) Import package

The imported packages can be language packs, updates and SP. I import an update here.

KB2492386 patch imported successfully

IV. System deployment

(1) create a new task sequence

In Task Sequences, right-click New Task Sequences.

Fill in the sequence ID task sequence name

Select the task sequence template, the new deployment system, we choose Standard Client Task Sequence

Select the operating system we just imported

Fill in the key here, no or later. We choose to skip it.

Enterprises can fill in the second item if they have purchased MAK key. After filling in key here, they will no longer ask for key when installing the operating system.

Fill in the user organization IE default page and other information

Set local password

Review summary information

Task sequence set successfully

(2) Editing disk partitions

Select the task sequence you just created, double-click to open the Task Sequence tab, and find Format and Partition Disk (BIOS) under the Preinstall folder to partition and format the disk.

Select the existing partition method first, and click * delete all partitions.

Click this symbol to create a new partition, enter the partition name, and Primary is the main partition. You can set the partition size by percentage or size. Here, I will take 40% as an example, and check Make this boot patrition to set the partition as the system partition, and check QUICK Format at the same time. Point OK Partition complete

Other disks can allocate space according to the method of system partition.

If you only format disk C, you can follow the figure below to retain the contents of other disks, and add a variable under options

Specific logical drive letter equals CRV, and then allocate all the space to it.

(3) set the boot image

Select MDT Deployment Share and right-click to select Properties

If you do not need to install x86 machines, you can fill in the IP address as far as possible without checking x86 network path, so that it will not be affected by Netbios.

We only generate the WIM PE file and uncheck the ISO file, so that we can improve the efficiency when we update the PE image file.

Check the network card and storage driver in drivers and Patches to avoid problems during deployment.

(4) set rules and Bootstrap parameters

Switch to the rules tab, as shown below, automate installation through rules settings, skip unnecessary selection interfaces, reduce human participation, and achieve unattended operating system deployment.

The CustomSettings file can be found in the DeploymentShare\ Control directory, and you can see it in notepad, which is the content in the Rules tab.

Set the Bootstrap parameter, setting "Edit Bootstrap.ini"

The reference for Rules is as follows:

Notes for setting Rules parameters:

[Settings]

Priority=Default

Properties=MyCustomProperty

[Default]

OSInstall=YES / / whether to allow deployment of the operating system to the target computer

SkipBDDWelcome= NO / / whether to skip the welcome screen

SkipCapture= NO / / whether to skip mirror capture

SkipDeploymentType= NO / / whether to skip selecting deployment type

DeploymentType=NEWCOMPUTER

SkipAdminPassword= NO / / whether to skip setting the local administrator password

Adminpassword=

SkipAppsOnUpgrade=NO / / whether to skip the application installation wizard page

SkipComputerName=NO / / whether to skip setting the computer name

SkipProductKey= NO / / whether to skip entering the product key

SkipDomainMembership=NO / / whether to skip add domain or workgroup

SkipComputerBackup= NO / / whether to skip computer backup

SkipBitLocker=YES / / whether to skip BitLocker configuration

SKipTaskSequence=NO / / whether to skip the task sequence (customizable)

SkipFinalSummary= NO / / whether to skip the final summary after the system deployment is completed

SkipTimeZone= NO / / whether to skip the time zone and language settings

TimeZoneName=China Standard Time / / time zone

KeyboardLocale=zh-cn / / Keyboard area

UserLocale=zh-cn / / user area

UILanguage=zh-cn / / language

SkipLocaleSelection= NO / / whether to skip local selection

SkipUserData= NO / / whether to skip user data configuration

SkipSummary= NO / / whether to skip configuration summary confirmation

SLShare=\ *\ logs / / you can specify the location of deployment logs to facilitate daily troubleshooting.

Notes for setting Bootstrap parameters:

[Settings]

Priority=Default

[Default]

DeployRoot=\ 10.0.0.2\ DeploymentShare$ / / shared directory

UserID=administrator / / start administrative account settings

UserDomain=**** / / the domain to which the startup account belongs

UserPassword= / / account corresponding password

KeyboardLocale=zh-cn / / Keyboard language setting

SkipBDDWelcome=YES / / whether to skip the welcome screen

(5) updating the MDT workbench

Right-click Update Deployment Share

(6) add boot image to WDS

Add the newly generated PE wim file to the boot image in WDS

(7) deploy the operating system

After the computer is powered on, start the computer through the network card, DELL brand press F12 to select the network card to start, and HP brand press F9 to select the network card to start

Select task sequence

Select software

During installation

Installation completed

Other operating systems, such as win8.1,win10 deployment steps, are the same as win7, except that the driver corresponding to the host needs to be adapted to the win10 system and needs to be re-collected.

5. Instructions on WDS and DHCP configuration

When WDS, DHCP and Client are located on the same network segment, WDS and DHCP are on different servers, DHCP does not need any additional configuration, and Client can obtain DHCP and WDS servers through broadcasting, thus communicating normally with WDS servers.

When WDS and DHCP are on the same network segment, WDS and DHCP are on different servers, and Client is on other network segments, Client will get a "NO BOOT FILENAME RECEIVED" error when it starts in PXE, and the startup file cannot be found. In this process, Client can actually communicate with DHCP normally (broadcast) and get IP, but cannot contact the WDS server (broadcast).

(1) if you are using Microsoft DHCP Server, configure options 66 and 67 on DHCP (boot\ x64\ wdsnbp.com).

(2) if you are using DHCP on a switch (such as Cisco), you need to configure it on the switch to add both dhcp and WDS server addresses to each vlan, and send Client broadcast requests to the WDS server so that it can communicate with the WDS server normally.

Note: if the client, WDS and DHCP server are located in the same network segment, and this error also occurs, you can also configure and solve the problem according to this method.

CISCO configuration

Same network segment

Ip dhcp pool XXXXX (address pool name)

Option 66 ip XX.XX.XX.XX (WDS IP address)

Different network segments

Ip dhcp pool XXXXX (address pool name)

Next-server XX.XX.XX.XX (IP of WDS)

Option 66 ip XX.XX.XX.XX (IP for WDS)

Option 67 ascii Boot\ x86\ wdsnbp.com

Example.

The WDS address is 172.60.25.180, and the Cisco switch is configured as follows:

Ip dhcp pool Office_VLAN25

Network 172.60.25.0 255.255.255.0

Default-router 172.60.25.1

Dns-server 172.60.30.35 172.30.35.254

Option 66 ip 172.60.25.180

Lease 0 8

!

Ip dhcp pool Office_VLAN26

Network 172.60.26.0 255.255.255.0

Next-server 172.60.25.180

Default-router 172.60.26.1

Dns-server 172.60.30.35 172.30.35.254

Option 66 ip 172.60.25.180

Option 67 ascii Boot\ x86\ wdsnbp.com

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.