MTC IDM

Thank you, we were able to figure out how to reduce the size of the .wim file and reduce the amount of time spent imaging based on your explanation. We are now running into a different problem. With our deployments, we want the Post Image Configuration process to be as close to zero touch as possible. In order to do that, we have set the Administrator account to Auto Login after deployment. However, after capturing the image with SmartDeploy, the registry keys that make this possible are erased, leaving us to have to go to every computer and log into the administrator profile twice in order to start the configuration we need. I've tried accomplishing this with a .vbs script found on the thread below. However, whenever the deployment gets to the POSTIMAGE phase, it tells me it cannot find the script, even though it's present on the image and the file path is correct. Is there any other way I can accomplish this?

Hello all, Is there any way we can target or exclude specific partitions from being imaged during a SmartDeploy deployment? At our institution, our computers are required to have a certain program installed that is roughly 40gb in size. This results in a rather large image that we send down to each computer through the network, and as a result we isolated the files for this program to it's own dedicated partition (for our purposes the A: drive). What we want to do is capture just the OS and System Reserve partitions and exclude this other partition. This is would drastically reduce size of the image we are sending through the network and hopefully reduce the time it takes to image a computer. Is there a way to do this? We do not want to wipe the A: partition. We have already tried only capturing the reference VM disk C: and System Reserve partitions, however whenever we send this image as deployment to the computer, it erases the program partitions contents. After reading the SmartDeploy documentation, we wanted to try the "Wipe and load drives" option on the Answer File, but since we didn't capture the A: it gives us the error that the existing partitions do not match the partition structure of the reference virtual machine. We are hoping there's a way to do this without having to capture the A: drive each time. Thanks in advance for the help.