Practical skills [WDS encryption] MDT environment application

Recently, the group has relocated its new campus and needs to re-build the MDT service. Due to the large number of workers in the environment, the network port of the employee's computer MDT network installation service is enabled in all stations based on the convenience principle, but there are also security risks. For example, if an employee accidentally starts online installation, the consequences will be very troublesome. There are still many "brain idiots ). To address security problems, the MDT installation service must be able to implement encryption or some preventive measures. After looking for many solutions, qianxin finally found a simple, practical and feasible solution;

I have not found many solutions for this kind of requirement on the Internet. I hope they can help engineers who need it. This solution must be modified on the WDS service, to warn users of operations when the NIC is started;

1. Download The Boot Loader: http://down.51cto.com/data/924060. decompress syslinux-4.04.tar;

2. Copy syslinux-4.04 \ com32 \ menu \ vesamenu. c32 to WDS directory, D: \ RemoteInstall \ Boot \ x64 and D: \ RemoteInstall \ Boot \ x32 folder

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1A1331a2-0.jpg "style =" float: none; "title =" 11.jpg"/>

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1A1334A0-1.jpg "style =" float: none; "title =" 12.JPG"/>

3. In the WDS Directory D: \ RemoteInstall \ Boot \ x64 and D: \ RemoteInstall \ Boot \ x32, back up pxeboot. n12 and rename pxeboot.0;

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1A133N41-2.jpg "title =" 13.JPG"/>

4.20.put a beautiful background image deploymentbackground.jpg in the d: \ RemoteInstall \ Boot \ x64 D: \ RemoteInstall \ Boot \ x32 folder;

5. Copy syslinux-4.04 \ core \ pxelinux.0 to the WDS service directory, in the D: \ RemoteInstall \ Boot \ x64 D: \ RemoteInstall \ Boot \ x32 folder;

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1A1334L9-3.jpg "title =" 14.JPG"/>

6. Rename pxelinux.0 under D: \ RemoteInstall \ Boot \ x64 and D: \ RemoteInstall \ Boot \ x32 to pxeboot. n12.

7. In D: \ RemoteInstall \ Boot \ x64 and D: \ RemoteInstall \ Boot \ x32, create a new folder named pxelinux. cfg and create the "default" file. For parameter configuration, refer to the following:

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1A1335142-4.jpg "title =" 15.jpg"/>

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1A1332S4-5.jpg "title =" 16.JPG"/>

Note: This solution comes from a great Foreign Player. The current solution is provided based on the actual test results in different versions. Note that, the picture in the step may not take effect because of the size of the Trojan. You can test it and make a conclusion. The image problem has been solved. The last complete meitu)

Thanks to 51cto for your help, Thanks.

Finally, I will post the results chart. Thank you!

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1A133N96-6.jpg "title =" 70cf5b6a249681bdd2ea2bee208ce8b2.jpg "/>