Before we build the MDT server, let's start by introducing the infrastructure environment. To simplify deployment, my dns+dhcp +AD+WDS+MDT is all integrated on the 2012DC1, but in a production environment it is not recommended that the MDT server be placed on the same server as the DC.
Because my DHCP and WDS have been installed before the WDS deployment experiment, so here is not the introduction, about the installation and configuration of DHCP and WDS, please refer to the previous article:
Two configuration servers for Windows server R2wds Deployment Services
This way, when the entire environment is set up, the client can automatically contact the MDT server after it has acquired the IP via PXE boot.
So far, all the basic environments and MDT and ADK have been installed, and now we're ready to configure the MDT server.
You first need to create a new deployment shared directory, which is the folder that each deployed machine needs to access. Simply put: is a shared directory, to ensure that each machine can access this directory, read the files in the directory. Because our operating system and control scripts are all under this directory. If this directory is not properly accessed, there is no way to talk about the normal deployment. Therefore, the success or failure of MDT deployment depends entirely on this shared directory. Let's take a look at the specific process of creating deploymentshare.
Run "Deploymentworkbench" to open the MDT console and right-click on "Deploymentshares", "New deploymentshare" to create the shared directory. This directory is best to create disk partitions that are larger on disk space, because subsequent drivers, as well as system upgrades, updates, and backups may take up a lot of disk space. Again, the MDT server is recommended to be deployed on a separate server.
650) this.width=650; "style=" WIDTH:650PX;HEIGHT:289PX; "title=" 1.png "alt=" Wkiom1ovyy3jehsoaagaq8x2yto066.jpg "src= "Http://www.it165.net/uploadfile/files/2014/0609/20140609174607762.jpg"/>
Specify the network share path, because I am here is the test environment, so the default C drive "C:\DeploymentShare", but in the actual production environment do not use C drive
650) this.width=650; "style=" WIDTH:650PX;HEIGHT:539PX; "title=" 2.png "alt=" Wkiol1ovzi-czdgxaafdu-zakpc391.jpg "src= "Http://www.it165.net/uploadfile/files/2014/0609/20140609174607763.jpg"/>
Set share name
650) this.width=650; "style=" WIDTH:650PX;HEIGHT:537PX; "title=" 3.png "alt=" Wkiom1ovyy_tenmtaaf-6j3-ah4830.jpg "src= "Http://www.it165.net/uploadfile/files/2014/0609/20140609174607764.jpg"/>
Shared description
650) this.width=650; "style=" width:650px;height:534px; "title=" 4.png "alt=" Wkiol1ovywojqwywaafli2w4tik007.jpg "src= "Http://www.it165.net/uploadfile/files/2014/0609/20140609174608765.jpg"/>
The default is good, if you do not want to select these options during the installation process, all uncheck can 650) this.width=650; "style=" width:650px;height:538px; "title=" 5.png "alt=" Wkiom1ovyzdyhtqwaahvltubalc498.jpg "src=" Http://www.it165.net/uploadfile/files/2014/0609/20140609174608766.jpg " />
Here are the different meanings of each of the above options:
Ask if a computer backup should be performed: Ask if the computer needs to perform a backup
Ask for a product key: Ask product key, generally large companies will have a KMS server, if not generally also use MAK activation
Ask to set the local administrator password: Ask if you need to set up an administrator password locally, we do not choose this, because we will create the task sequence when the unified set
Ask if an image should is captured: asks if you want to capture the image before deployment
Ask if BitLocker shouble be enabled: asks if BitLocker is enabled (for BitLocker deployment needs to use TPM chip, if no TPM 2.0 chip is not recommended to deploy BitLocker encryption. In addition BitLocker encryption if the key storage may also use Microsoft another technology Mbam)
Confirm MDT Configuration
650) this.width=650; "style=" WIDTH:650PX;HEIGHT:537PX; "title=" 6.png "alt=" Wkiol1ovywthxwshaahqwzniap8608.jpg "src= "Http://www.it165.net/uploadfile/files/2014/0609/20140609174608767.jpg"/>
Complete
650) this.width=650; "style=" width:650px;height:536px; "title=" 7.png "alt=" Wkiom1ovyzkxnqtjaajimvbstxe816.jpg "src= "Http://www.it165.net/uploadfile/files/2014/0609/20140609174608768.jpg"/>
Then confirm that we shared out the Deploymentshare folder whether everyone has RW's permission 650) this.width=650; "style=" WIDTH:650PX;HEIGHT:427PX; "title=" 8.png "alt=" wkiol1ovywaafdl5aakcle30kqw674.jpg "src=" http://www.it165.net/uploadfile/files/2014/0609/ 20140609174609769.jpg "/>
Confirm the Everyone permission to ensure that everyone has access to
650) this.width=650; "style=" width:650px;height:415px; "title=" 9.png "alt=" Wkiom1ovyzttr6hvaai6d1zwr6c558.jpg "src= "Http://www.it165.net/uploadfile/files/2014/0609/20140609174609770.jpg"/>
Test, you can access to this folder through \\2012dc1\DeploymentShare$, description of the correct configuration 650) this.width=650; "style=" width:650px;height:488px; "title=" 10.png "alt=" wkiol1ovywiblfy0aakod1s5r3i531.jpg "src=" http://www.it165.net/uploadfile/files/2014/0609/ 20140609174610771.jpg "/>
Above we have completed the sharing of the new MDT directory, in the next chapter we will configure the MDT
This article is from the "Red 阝 per file" blog, please be sure to keep this source http://tsingtao.blog.51cto.com/3075625/1664994
Deploy the WIN8 system using MDT2013-Create an MDT directory share