Windows Server R2 uses the WDS service to implement a bulk-install operating system demo

Source: Internet
Author: User

Yesterday in the 51cto circle of friends saw a demonstration of the WDS deployment, I refer to the above step to discover a lot of problems, in how to capture the packaged Windows Server 2003 has encountered a problem, that is, the production of WinPE Boot Mirror, I added it to the installation image, found that add always error, and then prepare to write a technical reference to this blog post, found to understand, 2nd is to add the NIC driver, if the driver package without Microsoft Windows Lab (WHQL) certified signature is unable to be installed, This is a tricky issue, I believe that any problem is a solution, just a matter of time, if the problem can not be solved, then this presentation is very chicken, this demo is only limited to the WHQL-certified signature of the network card driver, can be installed on the corresponding machine, and the other has no effect, This is too food, I tried two ways on the Internet No line through the Group Policy to ignore visas, no effect, press F8 to disable unauthorized driver Visa also has no effect, I am not clear if the certificate in their own local issued by this limit, anyway, this demo practical value is not big, Just use WDS as a service.

Topology diagram: (Drawing with Edraw tool)


Concept:

First ask a question, what does WDS do, what does it do, and why should I build a WDS service?

Okay, I'm just going to answer that. The WDS service is the abbreviation for Windows Deployment Services, a tool used to implement a bulk distribution deployment operating system, which is designed to simplify the installation of the operating system, saving time and energy


Scenario Analysis

If a company needs to install 5~10, it is sure to use a USB stick directly installed on the solution, the use of that method does not matter, feel nothing, a pack is tired, a waste of time just


What if a company needs to install 50~100, or even 500 units?

The problem comes, for the amount of less, what methods are good solution, the quantity is big, the problem comes, this is the rhythm of the whole dead, you can not eat a day do not drink the 500 set up? Even with 10 USB sticks, you can not solve each other's copy installation, so the batch installation is necessary


Environment:

Hardware selection is very important, if the high-volume deployment, the hardware is still required, you set up the server performance is very high, network environment, the switch can not be too vegetable, also want to gigabit network port, here is to pull this digression

1. A computer, recommended a little better, installed on Windows Server R2 operating system, you can also install Windows Server 2008, the following provides a

My Computer Configuration environment is as follows, is installed in the real machine, not the VMware workstation inside the virtual machine

Operating system Windows R2 Server Enterprise 64-bit SP1 (DirectX 11)

Processor AMD a10-7870k Radeon R7, Compute cores 4c+8g four-core

Motherboard Ming Szeto ms-a88fx FS m.1 (AMD K15)

Memory 8 GB (unknown ddr3l 1600MHz)

Primary hard disk br240g (GB/SSD)

2.win7 Mirroring

https://msdn.itellyou.cn/???????? There are thunder words, very convenient, no words do not recommend, wait too long, but there is MD5 verification, more security

http://www.panduoduo.net/????????? This strong suggestion, for example: Windows 7 iso, can download what you need, but the flaw is no MD5 verification, there may be some risks


3. Network Card driver????????????????????????????????????? This thing you can go to the official manufacturer of the motherboard to download, can also be downloaded from the computer's brand model, the proposal is to use the original system of the driver of the Master Lu, drive life, do a local backup, and then put this backup ready on the line


4.AIK Tool???????????????????????????????????????? This I did not try to succeed, but can recommend everyone to download, recommend the use of Windows Server 2008 system to try

https://technet.microsoft.com/zh-cn/??? Download through the address link here, if you are interested in Microsoft, you can also learn some of the latest dynamic technology inside


The approximate idea is to say:

    1. Install Active Directory services, referred to as AD (active directories)

    2. To install the DHCP service and the deployment service

    3. Enable the client to install the operating system on the client


Details:

  1. Before installing the Active Directory service, it is recommended to modify the host name, or you can not modify it, note the purpose is to facilitate identification

  2. Configure the static IP address, must be configured in advance, or later modified to waste time, so these details must be prepared in advance, otherwise the modification is a headache thing

  3. Configure Dns,dns to fill in the address of the DHCP server, the address of the local DHCP server is 192.168.1.101

  4. When you install AD, the first time you create a domain, it must be a new scope, or there is a problem, if this is the case, return to the front to see if it is a domain, joined the domain to fill the domain controller server

    Address, this scope, only as an additional scope, or a secondary group scope, if not joined to the domain, it is definitely a problem with the computer name settings, modify, and then restart, and then add, this problem solved

  5. Authorizing the DHCP server to start

  6. Set the Active Directory restore password, this password is not this Active Directory server password, can be the same, not recommended, this Active Directory restore password must be set difficult, why? It is very dangerous to prevent the Active Directory server from being deleted directly, which can cause the whole domain controller to lose its function, but it doesn't matter what I'm demonstrating here.

  7. When installing WinPE, choose to Add the WinPE launcher in the boot image , which is used to capture the image, the name is captured, you want to customize any pure version of the system can be used in a similar way, the same, Here can not be used to guide the installation of the real machine, this is equivalent to inserting a USB flash drive, boot into the Windows PE system, so be sure to follow the boot program to install the system to differentiate, and boot boot is divided into x86 architecture boot boot system and x64 boot program boot system, So in the installation of the AIK package, select the appropriate architecture, because here I capture the Windows Server 2003 is the x86 architecture, so I chose the x86 WinPE, where the capture modified to capture x86 better, So to capture x64, the naming of course is capture x64 better

  8. When downloading AIK, you need to choose to download the version that supports Windows Server 2008, which is the address provided here https://www.microsoft.com/zh-CN/download/details.aspx?id=9085 , or you will find that when you enter the system to capture, the input wdscapture command is not, this need to uninstall and re-download

  9. After capturing the installation image for Windows Server 2003, here we need to restart the Windows Deployment service, with the Windows 2003.wim System Installer in the Install Image column

  10. After completing the above Windows 2003.wim System program, I now need to verify the virtual machine on my installation process, then you need to download a win7 32bit image, and then unzip, in the boot image, the system boot boot to add access, I think the name of the boot 32bit here is more appropriate, so here to start the image up to 4 boot images can be, respectively, capture 32bit,capture 64bit,boot?32bit,boot 64bit, this is the most reasonable, There's something wrong with me here that doesn't affect my effectiveness.

  11. In the real client to demonstrate the deployment of WDS to install the operating system, input F2 or F3, each version of the motherboard into the BIOS system function keys are different, some F11, some F6, some F12, into the inside after the bios of the Windows boot boot sequence to modify a bit, First turn on the network start service, and then the network boot service order to modify, the network boot up the top, the same in the virtual machine also need to boot through the BIOS to modify the boot sequence

  12. If you want to demonstrate the installation of the operating system through the virtual machine, the network mode is modified to bridge mode , so that you can get the real machine assigned IP address, in determining the virtual machine can obtain the address of the time, look at the DHCP service, see there are rented address pool there is no leased address, Then ping, ping This command is the most commonly used in the network, but also the most use of a command, especially in the company, whether you are engaged in network engineers, management, operations engineer, this is a necessary tool, very practical

  13. If you want to deploy the operating system through a real machine, the driver is a big problem, if you use the motherboard of the manufacturer of the zone has been authorized by the signing of Microsoft, then congratulations, this is too worthwhile for you, is simply tailored for you, to congratulate you, in the future if you want to install the operating system in bulk, Can do so, although not perfect, no unattended installation so readily, there is no one key to the operation of Ghost Easy, of course, the bulk is still very advantageous, this is worth affirming


Demo Process:

First step: Install the Active Directory service


    1. Modify the computer name to facilitate later maintenance identification



2. Manually modify the IP address, set the DNS address

Because when the DHCP server is configured, the address of the DHCP server must be set to manual, the client needs the DHCP server to assign the address, the Active Directory must be specified in the DNS, or the Active Directory is fixed, so the DNS server must be specified by the IP address , and the DNS server is used to do the parsing of the name


3. Add Active Directory Service

Tick the Active Directory Domain Services

Note if the. NET framwork is installed successfully, it is not successful and needs to be installed later on


II. installation of DHCP services and Deployment Services

1. Configuring the DHCP service and Windows Deployment Services

Add the DHCP server and Windows Deployment Server

Give the DHCP server a name and try to express what this is for, for example: for the bulk deployment of Windows operating system use , the following I filled out this is problematic, no installation standards to

IPV6 is disabled here, the broadcast spread time is prolonged when the DHCP server is prevented from using

Okay, now DHP server and Widnows Deployment Services are set up.

Third, build Active Directory server

    1. Configuring Active Directory Servers

???? Here I directly through the graphical way to add, how to save the hassle of how to come, you can also through the command, for example, enter "Dcpromo" in the Run

Note that the first time you create an Active Directory server, be sure to select "New Domain in New Forest", this new domain is both the root domain and the first domain controller

Here's my Active Directory the name of the scope is:abc123.com, Note that when the name of the time can not be random random, must be in advance to think well, a little taken after the back is not able to modify , want to modify each place to be modified again, Therefore must be cautious, do not want the above DHCP server, the name is wrong, modify it is finished

I have a little problem here, do not affect this demonstration, for example: My NetBIOS name here has been modified to abc1230.com

It must be noted here, once the version here can not be degraded, I now this host as a domain controller, can not be reduced to the basic function of the additional domain controller, it can only upgrade, it is fully backward compatible with the server, which is the Microsoft software, which is generally the case, irreversible operation, So before doing such operations to consider clearly beforehand, whether you want to use this server as a domain control server, if so, this server is best performance in all aspects of stability, and the hardware are relatively new, to ensure that it can be used for 4-5 years or more, otherwise that would not mean anything, You can not build a domain controller every day, the domain migration and comparison of the trouble, if you do not back up, the previous work has been vain, the thankless thing is best not to do, must have planning and preparation beforehand

Click "Yes" here to set up the DNS server while building the Active Directory server

This is the Active Directory server's restore password, note that this password is not your domain controller (install this computer host's Administrator account) password, but restore the password of the domain controller, if one day you regret, want to restore this domain control to workgroup computer, Can use this password, so this password to set difficult, you forget also does not matter, of course, remember is the best, since can be reduced to a normal computer, you think this is how horrible, I think the design of Microsoft here is a bit of a problem, I do not know how to think, everyone pay attention to this point on the line

In order to make it clearer, I cut off my help, so I can look at the last place where I made the mark.

OK, Active Directory and DNS server are all set up

The following must restart the computer, the Active Directory will take effect, click "Restart"

Iv. managing Deployment Servers

Note that when the DHCP server is set up,you must click "Authorize"or the client computer will not obtain an IP address.

Now to configure the Windows Deployment Server, first add the server

Here is a domain controller, you can choose this machine.

Configure the server after the add is complete

Remote installation folder, this casually put a disk, it is recommended to put in addition to the system disk other disks, which are stored in some of the deployment of the boot files, network drivers, etc., put on the other disk is better, if you need to deploy a lot of operating systems, or will occupy a portion of disk space, Security considerations should not be placed on the system tray.

Check both of the above, the DHCP 60 port here, more easily occupied by other servers, the client can not obtain an IP address when the time to examine this

I don't care so much here.

Here, just remove the tick and add it later

Now we are in the Widnows deployment server to complete the "Install image" step of the preparation work

Select "Add installation Image" in the installation image

Here is the image group to create the installation image, for easy identification, write a specific point

This is the image path after decompression, this is very clear, I did not follow the online, in the D disk to build a folder, take a name install, And then the image inside the Install.wim and Boot.wim files copied to the new folder inside, said before, how convenient on how to come, the principle of knowing on the line

This is the installation image that is added on the Windows Server R2

Start adding a boot image below

As in the same

This name is the start of the client machine, press F12 appears the name of the installation system, this is to write a detailed, easy to choose

Five, install AIK below

Path to WinPE


Note that you must choose to add a boot image here

Here the name I take capture, actually fill in capture 32bit better, this is 32bit wipe boot program

Six, encapsulating Windows Server 2003

Mount the Windows Server 2003 CD, copy Sysprep.exe and Setupcl.exe two files from the inside to the root of the C drive, and these two files are encapsulated windows

Important files for the Server 2003 operating system are installed on the operating system that operates Windows Server 2003 before the operating system is encapsulated. NETFramework and MSXML, such as the installation package I used



This must be set to start from the network card

Seven, start capturing system mirroring for Windows Server 2003

Be sure to select " bridging Mode " here.

After opening the virtual machine, when the F12 appears, press F12, enter the selection screen, here I choose capture, because I am here to capture the Windows Server 2003 system image

Select Capture

I have a bit of a problem in this place, I repeatedly press the shutdown key caused, but again shutdown, restart, and then enter there is no problem

The Wdscaputure tool for this place is available in the download AIK version of the address that can be found

Here I need to capture the image of the system disk, the default system is installed in the root directory of the C drive, the image name fills in the actual captured system version name, for example, Windows 2003.wim

The following is to provide the image server address (the host to build AD), fill in its address, that is, 192.168.1.101, need to provide authentication account Abc123\administrator, password is the host to build the ad management account password, The captured image files are automatically uploaded to the E:\RemoteInstall\Images\Windows Server 2003 directory.

Image group name, I first created in front of Ha, so here is, I certainly choose to put in this, so in advance this work should be ready, not created, you can install the image inside the set to create a good, and then again to choose the

Found that there is a created image, the Windows Deployment Service refresh, in the installation image has the corresponding option, do not need to re-add

As shown below

The following need to add boot image, here I first down a win7 32bit image file, then unzip, and then as shown below, add the boot boot file, as shown in:

The name here can be changed to boot 32bit more appropriate, then did not think so much, only quite a boot installed in Windows Server 2003

Now the boot image has x86 boot driver, that is, Windows 2003 (x86)

Viii. installing an operating system that uses WinPE capture to make Windows Server 2003


Need to provide Windows domain account login to be able to install

The operating system version here is very much, I choose Windows Server 2003

Choose to install on the 0 partition, the first 1 disks, that is, the system disk C drive

The following if you really need to install the format of the words, here if the real machine demo to this step, the installation is basically can be over, so Ann does not install depends on with you , here the general format is really starting to re-install the system once again, the format of the behavior is no room for estoppel, Must be careful in the format of your hard disk, the data is valuable, after the format of the cost is very high, sometimes may not be able to find back, the risk is very large, so it's okay to do not format words, install the system is also very hurt hard disk, here by the way, I here is a virtual machine, do not matter, I still want to see what the final result is, so I'll just click "OK"

After the operation, basically is the next step, the next, until the completion, so it is no longer one by one display

Nine, in the real machine client deployment Win7 operating system (my desktop network card driver is currently not authorized, so demonstrate how to use the process)

After Windows Vista, Operating system installation files are Install.wim and Boot.wim, so here is omitted the image capture process, direct use can be, the problem is to solve the problem of motherboard network card driver signature, if your motherboard network card support Microsoft authorized signature, then congratulations, this experiment to you have helped me here gigabyte of H1 10M-S2 Desktop motherboard does not support, I demonstrated this desktop Szeto ms-a88fx FS m.1 (ADM K15) motherboard also support, after all, are assembly machines, deployment of Dell, Lenovo's machine, HP machine, Asus Machine, like the brand is not dare to fake, copyright issues are litigation issues, The use of pirated fines is pretty strong, so this bottleneck problem is here, if everyone is brand, that is basically installed is stable and secure, it is called a refreshing

Failed to add NIC driver

This only needs to add the network card driver, the other can not be added, such as the NIC driver is as follows:

to ignore the installation of the driver package by using Group Policy to find out or not


Here choose to ignore, also not, after the restart system by pressing F8, disable the driver package signature installation also has no effect, does not demonstrate

The client needs to modify the BIOS, the network boot to the top, and then the following phenomenon will occur, and then when the F12 appears, press F12 to

Choose the operating system installed 64bit bit, here Windows 7 (x64) and Windows Server (x64), choose that one is the same, representing the same meaning, are as x64 architecture system boot, no difference, the start interface is not the same, Only this difference, so can be modified in front of the boot 64bit better, this step after you choose to choose what system to install

Here is the network card driver problem, my assembly machine's network card driver signature is not authorized, unable to install, the demonstration process on this kind, if is the brand machine, here can be directly realized, this demonstration to here, involves the knowledge point content very much


Windows Server R2 uses the WDS service to implement a bulk-install operating system demo

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.