Win2008 builds PXE and WDS and switches

  
as a newcomer. For the first time, write something here, and record the part of the work. I hope to exchange ideas with you. A lot of operations come from the Internet, and of course, the help of colleagues, and I would like to thank these big-hearted and dedicated big cattle, through their own practical operations, the operation and experience will be summarized. I hope that you will have more opinions and criticisms. Friends who do the operation and maintenance are inevitably need to install the system for a large number of servers. We usually divide into two situations: one is to have a large number of servers when the machine room is set up; the other is to send the small batches from the local to the machine room, including server replacement and small-lot computer room expansion. Let me talk about my views on these two situations. In both cases, it is undoubtedly necessary to install the system for the server (who knows everything, you want to say.), of course, this may be slightly different, for the first type. In the case of a large number of servers, if we install this efficiency one by one... oh, of course you can know without saying. Generally, the way we go to the IDC room is to put all the servers on the shelves, connect the network according to the designed network topology diagram, configure the required RAID and network parameters, then we will use us as the hen of the installation system. ), that is, the configuration of the PXE and WDS books connected to the LAN where these servers need to be installed, this is the focus of this article. Let's talk about another situation. The average Internet company will have its own assembly test room to test new machine performance and test some new methods to solve the problem. Of course, it will also be used to install the system and test the system. Run on the machine. Of course, we only talk about the part of the installation system here (after all, I am just a little bird, and more need to continue to learn). In the company to install a small batch of machines, if there are very few, but there are hens (machines) that you have not configured to install the system, of course you can use the optical drive, but not all servers have this module, this is likely Use the control port to mount the image installation (of course we are talking about a small number of columns such as two or three), but we still need to use a switch for a desktop or server (of course there is a surplus, this stuff is right Personally, it is not cheap.) Also configure PXE and WDS to deal with the system installation (usually win Server and linux). Therefore, the configuration of WDS and PXE is the basic work of the operation and maintenance staff (? What is PXE and WDS? Of course, GOOGLE will say more than I know), switching between WDS and PXE is also a must, so we It is necessary to talk about this topic. (It’s boring or even shameless to say that so many haven’t entered the theme. It’s inevitable that the first time it’s inevitable to be a little embarrassed and excited.) Win2008 PXE and WDS installation summary We use a dell notebook and an IBM notebook hen ( The system selects windows_server2008_R2_ Enterprise. When the PXE and WDS installation environments are together, the DHCP and TFTP ports conflict. For detailed installation environment implementation, see the fourth point operation guide. (More specific PXE and WDS installation and configuration methods are available online. If you write them down, it is really a piece.) The very painful thing, the next content is that after you have some understanding of the PXE and WDS allocation configuration, there are some method suggestions that need to be installed together.) 1, solve the problem: 1, windows_server2008_R2_Standard system does not support the domain function, can not build a WDS installation environment. 2. When the PXE and WDS installation environments are together, the DHCP and TFTP ports conflict, and the PXE installation environment cannot be used. 2. PXE and WDS working principle analysis: PXE: After the client remotely starts, boot to find the PXE option bar and select, the client NIC starts the DHCP process to obtain the IP address from the server---> DHCP server gives the client an IP Address, at the same time through BOOTP (bootstrap protocol) to tftp server to find the remote boot file, download a pxelinux.0 file, and according to the boot of pxelinux.0 find the default configuration file under the pxelinux.cfg folder ---> According to the configuration file loading kernel and other operations, BOOTP will call the default configuration file, then put the default file into memory, and load vmlinuz and initrd.img according to the contents of the default file. Finally, load the ks.cfg installation file via ftp. WDS: After deploying the WDS server and its clients on the LAN, it starts working. First, the client obtains IP configuration information through the DHCP server during the startup process. The WDS client then looks up the WDS server via broadcast or DHCP. The client then connects to the WDS server and launches a specific boot image, which is WinPE (Windows Preinstallation Environmen). Finally, the client can begin to install the operating system image on the WDS server. 3, Win2008 PXE and WDS installation and analysis First, Win2008 PXE installation environment requires 3 additional components 1, DHCP service: Note: You need to add the startup file name 67 in the scope, and set the remote startup file name to linux-install/Pxelinux.0 2, TFTP service: Note: Need to change the TFTP directory to D:\\OS\\ 3, FTP service: Note: Ensure that the 21 port of FTP is connected correctly, keep the server online. The remaining PXE installation operations are the same as the win2003 system PXE operation. . (The next article will carefully introduce the WDS or PXE method separately.) 2. Win2008 WDS installation environment requires 3 additional components. These three additional components are: DNS (used to find the domain controller DC) Active Directory (AD, 2003 version) Or the 2008 version can be used for authentication) DHCP (for the client to obtain the IP address and the IP address of the WDS server). In addition, it should be noted that the installation of the WDS server (Windows Deployment Services) must be an AD member. Here we can install all four components (AD, DNS, DHCP, WDS) on one server. 1. Active Directory Domain Services: Note: Once the Active Directory domain service is established on the server, the DHCP service requires domain authorization. To start, the authentication login needs to add the domain name in front of the user name. 2. DHCP Note: Because the Active Directory domain service is established, the DHCP service needs to select the domain authorization in the red circle to start. 3. DNS Note: Because Active is established Directory domain service, DNS service is used to find domain controller DC 4, windows deployment service Note: Windows deployment service includes deployment server and transport server (including tftp and ftp services) Which needs to use DHCP tools in windows deployment service Do not listen to port 67 2. Configure DHCP option flag #60 to indicate whether this server or PXE server can obtain DHCP service normally. 4. Win2008 PXE and WDS Operation Guide Because the DHCP and TFTP ports conflict when PXE and WDS are installed together, they cannot be used. PXE installation environment. Therefore, we need to turn off the DHCP and TFTP services in the WDS installation environment that affect the PXE installation environment. When we need to use the PXE installation environment to install the system 1, close the windows deployment service DHCP tool 2, close the windows deployment service tftp transfer service (close the windows deployment service directly here) select the service and then stop 3. Start the TFTP Service 4 service Select the service and then start and then the following PXE installation will appear on the server system installation: When we need to install the system using WDS installation environment 1, open the windows deployment service DHCP tool 2. Open the windows deployment service Start the service 3. Close TFTP Service 4 service
Copyright © Windows knowledge All Rights Reserved