Thursday, September 27, 2012 9:24 PM
My question is this when I am ready to create a capture I connect to the deployment share and run the litetocuh script and the wizard starts I select the Capture Task I made and then it gets to the place right before it reboots and fails with an error. The number of errors seems to increase with each time I try it. What do you think the problem could be?
And another thing is I noticed that there is a E drive that is full and has about 40 MB free and the contents of that drive seem to be part of the Deployment share, and I keep getting an error message about the drive being full, I don’t think I have ever had this situation with other images I have made with the drive being full. And if that is the case why does that happen?
- Edited by CompSol123 Thursday, September 27, 2012 9:25 PM Added image
Friday, September 28, 2012 9:27 AMHave you looked at http://social.technet.microsoft.com/Forums/en-US/mdt/thread/243f3245-5f7c-4f0b-b55b-ddda27081385/
Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"
Friday, September 28, 2012 4:35 PM
Under the capturer Task Sequence I disabled the mass storage driver and under the capture Image section I disabled Reboot. Then I manually ran sysprep and it ran the wizard this time with no errors that prevented me from finishing the wizard. Thou I did get a VB error but that did not keep from anything, so I finished the wizard and the PC did not reboot so I rebooted manually and it loaded windows not the deployment process. Now you said I needed to modify the sysprep.ini is this file in the deployment share and of so what do I need to change?
Sunday, September 30, 2012 4:33 PMIts better to do reference images using virtual machine. With VM its easy to roll back to snapshot taken just before sysrep and there is no device driver caused problems. You could try and use VirtualBox for example to see if this same error arises.
- Edited by Jouni J Sunday, September 30, 2012 4:34 PM
Monday, October 01, 2012 1:10 PM
Thanks for the info do you have any ideas as to why it is failing now? The one that it is failing under is the 32 bit version of the image the 64 one that we made works fine.