Continuing the topic of automating deployment using a USB flash drive made by MDT, previously described a workaround for the problem caused by task sequence problems in the deployment process, followed by a problem with the MDT deployment times error, to introduce the solution today
First of all, to describe the specific situation of the problem, when using MDT deployment, it is found that the individual machine will prompt faied to apply the error of the image, this is a very strange phenomenon, because only a very few machines have this problem, this is why? Test found that the use of network deployment will also prompt this problem, and the information is consistent error, this is not an accidental phenomenon, there must be some unknown reasons.
After the use of the most original USB stick installation method to test, found that the deployment is not a problem, then certainly not the cause of the machine, then I carefully recalled the key to the problem, I suddenly think of this machine before capturing the image, the choice of disk partition is D drive, suddenly suddenly, It seems that the crux of the problem is the 100M partition, in the PE environment, the 100M partition is divided into the drive letter of the C drive, and we define the deployment strategy is which partition is the C drive on which partition, so the operating system will be installed on the 100M partition, but because of the problem of too little disk space, Installation is definitely a failure, after I entered the PE environment to see the 100M partition of the available space, found that the free space becomes 0M, also confirmed my point of view, after I deleted the 100M partition, re-tested, this time there is no problem with the deployment. It seems that this is also the current scenario needs to be improved, for the 100M partition of the machine, the deployment of the operating system may fail, but I remember that some machines even if there is a 100M partition, when capturing the image is also the C drive, also represents the 100M partition is not divided by the letter, for this machine, Automatic deployment of MDT can be successful, but in a nutshell, automatic deployment on machines with 100M partitions is a possibility of failure, which is also a perfect place to be.
It is also important to note that after the MDT deployment is completed, the operating system will also execute a set of related scripts, the general content is to restore the previously captured user data, install the application, apply Group Policy, etc., in this process will be in the C-disk set up a temporary folder at the beginning of the SMS, In this process must be careful not to unplug the U disk or network cable, you must let this set of scripts to complete, otherwise MDT will always think that the deployment has not been completely completed, C disk under the temporary folder will not be deleted, may cause the problem is, then enter the system will always pop up the window inserted into the USB flash drive, and cannot be closed , and will also appear when using MDT automatic deployment, after selecting the task sequence will be a direct flash back to restart the system, which is due to the last deployment of the script was not completely completed, so make sure to complete the entire deployment process, the temporary folder under the C disk is automatically deleted and then unplug the USB flash drive or network cable
This article is from the "Just Make It Happen" blog, so be sure to keep this source http://mxyit.blog.51cto.com/4308871/1633180
MDT USB Drive Automatic Deployment Error Resolution II