After several days of repeated testing, I finally completed the test of ADS deployment XP. It seems that without repeated failures and experiments, it is impossible to obtain the accumulation of technology and knowledge from the victory.
ADS does not support the desktop operating system in principle, because the ADS control client must rely on the ADS proxy, and there are two ways to enter the ADS proxy environment. The first is to install the proxy on Windows 2000 Server and Windows Server 2003. Program, which only supports a limited number of system versions; the other is a proxy environment that uses PXE to boot to ADS. From the above, it can be seen that ADS agents occupy a vital position in order to truly realize fully automated deployment.
After many trials, XP's fully automated deployment is still feasible. The focus is on choosing the right deployment sequence and modifying the execution task script. In this experiment, my method is as follows:
1, install the XP prototype, do system preparation, generate a fully automated mini installation response file, and modify the corresponding variables, and finally manually execute sysprep and its necessary parameters ;
2, add this device in the ADS server, modify the default task to boot-to-da, add the corresponding variable of this device and grant control;
3, open the prototype, check whether it successfully enters the proxy environment And enter the ready state;
4, create a new Capture-Image task script, the task sequence is: capture the system image (or other partition image) -> modify the prototype sysprep.inf (because the sysprep on the prototype. Inf contains ADS variables, the automatic mini installation will not be executed correctly after restarting, so modify the variables to actual values) -> Change the prototype default task to boot-to-hd —> reboot ;
Note : Although this step is performed according to the automation concept, when the prototype re-enters the system, the control of ADS will be wrong, first manifested at the end of the task execution. Step reboot without feedback, resulting in the execution state of the task has been, this time you need to manually stop the task. The reason is very simple. The ADS proxy is not installed on the prototype. Attempts have been made to add adsdevice /rc at the end of the task script. However, it is found that this command is not allowed in the proxy environment, so it is finally necessary to release it manually. However, I feel that the last reboot can be replaced with shutdown, so that after the prototype is powered off, the ADS device can release the control normally, otherwise you will find that after the prototype is restarted, you cannot release the control in ADS device management.
5, add the client device to be deployed in the ADS device, modify the default task to boot-to-da, add the variable corresponding to this device and grant control;
6, open this client, check whether it is Successfully enter the proxy environment and enter the standby state;
7, create a new Deploy-Image task script, the task sequence is: the client partition (if there are multiple partitions, you can add multiple partition instructions) -> deployment Image (add multiple instructions if you are deploying a multi-partition image) —> Modify sysprep.inf on the target client —> Modify the prototype default task to boot-to-hd —> reboot ;
At this point, ADS deploys XP even if it is completed. If the client supports remote booting of the network card, then it realizes full automation in the true sense. I hope that the ADS agent supports XP or 2000PRO. I tried to unpack the agent to remove the system version verification. Unfortunately, I really don't want to give up on these. I hope other friends can modify the agent to support the desktop system.
In this experiment, I probably took a moment to capture and deploy the image in the same time. In the PIV2.4G/128M virtual machine, each time takes more than 10 minutes, and this time is only to capture the pure system. The image may be longer if the system has application software installed or if it contains other partition image captures. When Ghost is cloned in a single machine, it only takes more than 3 minutes, but the advantages of ADS are obvious.
Next I will find a real-world environment for large-scale deployment testing, hoping to get an actual data to compare Ghost webcast.