Bnaquin

Being that I can get Windows 7 to install from DVD and am able to use MDT to deploy the base Windows 7 image to this machine, I am going to do an install then create a custom image and see if I can deploy it back to that machine. If so, then I'll try deploying to an older machine that we currently have out for our users. My best guess is that there is one minute difference in the machines which is keeping the new machines from finishing the install from our images. Just very frustrating is all.

We are using MDT 2010 and a custom image. The image pushes out to all of our other machines with no problems. I'm thinking it's a driver issue, but I'm not sure which one. I can push the install.wim file from the Windows 7 DVD to the machine with no problems as well. The machine is an Intel Core i5-660 Processor, 2GB, 250GB 7200RPM S-ATA HDD, no diskette drive, PCI/PCIe Small Form Factor (2x3), Intel HD Graphics, DVD Recordable, Intel Gigabit Ethernet. Which logs do I need to be looking at and where are they located?

During my installation of Windows 7 Enterprise, after a reboot I get a screen that says "Starting Services" then it errors. The error I get is: The computer restarted unexpectedly or encountered an error. The only option I have is to select OK, then it reboots and does the same thing over and over. Any suggestions?

I tested all day Friday and here's what I came up with. I brought 2 images from HQ to the District Office with me. One image was the Standard Image, and the other is a CAD/Design image. I imaged the test computer with the Design image with no problems. So I decided to sysprep it, and send it back to the image server as a test image and bring it back down to the test computer. Still no problems. Next I reimaged the test computer with their Standard image. The image came down just fine, but when I tried to Sysprep it, Sysprep gave me a Fatal Error message. So I decided to reimage the test computer using the Standard Image that I brougt from HQ. The image came down just fine. Upon trying to Sysprep the test computer, I got the Fatal Error with Sysprep again. So I am being led to believe that the problem I was having is with our Standard image and now into a deeper problem, why am I getting the Fatal Error with Sysprep and how to fix it. From what I have read, the error is because an image can only have sysprep w/ Generalize ran on it 3 times max. Is there any truth in this? If so, is there anyway to roll back the counter on this? Anyways, I'm gonna do some more research and see what I can come up with. Thanks guys! Glenn

I mounted both the Install.wim file and my custom image file. I did a comparison between the two as far as the oem*.inf files and I don't see any differences. Both have the same amount of files. The thing that I don't understand is that if I create the image at the Main Office, it's works here. Tomorrow, I am going to take one of my custom images to one of our District Offices and set it up there and see if it deploys. I'm beginning to think it has to do with something on their deployment servers even though they should all be the same. I dunno, just my guess. If you can think of anything else please let me know. Thanks, Glenn

Not to my knowledge there wasn't. Is there a way I can check to see if any drivers were added to the image and if so, is there a way that I may remove them.

Background: We have a Main Office with surrounding District Offices through out the state. Each District Office and Main Office each have their own Reference Server for Images. We are using Imagex to capture custom images and MDT 2010 to deploy the images. Problem: At the Main Office, I can create custom images and deploy them with no problems at all. However, at our District Offices, our tech reps build a computer, load Win 7 Enterprise, and add any software or changes that they want, create the image using Imagex. Once they go through the steps to add that image to MDT and deploy the image, they get an error. The error that they get is in the install section of the deployment, right after it comes up and says copying files, which goes from 0 - 100 almost instantly, it starts to expand files then stops with the error: “Windows cannot install required files. Make sure all files required for installation are available, and restart installation.” In the details, 3 errors were found. These were the messages: “Setup failed applying image \\R02172MD000\DeploymentShare$\OperatingSystem\VPNLaptops\EdVPN.wim, rc=31. ZTI Error – Non-zero return code by LTIApply, rc=31. Litetouch deployment failed, Return Code = -2147467259 0x80004005.” Now they use the exact same procedure that I do here at the Main Office. I did have one of the offices bring their image here and I set it up in MDT on our server and it still gives the same error. I have tried capturing the image with Imagex /flags "Enterprise" as well. I am at a loss as to why all of the images I create and deploy at HQ work just fine, but am not able to deploy any custom images created in the District Offices or why I can't get the image that I obtained from our District Office to work after setting it up in MDT. Any information and help would be appreciated. Also, if you need more info, let me know! Thanks, Glenn