Josh1

I have two but not of the different kinds. I have a 64bit image for 32 and 64, I think this may be the problem.

Thanks John, something weird that happened yesterday I went to image a machine yesterday and after the network boot I picked the 32 bit image then after the files loaded I was given the same error message, but when I loaded the 64bit image it imaged fine, no problems. The 32 bit and 64 bit image are the same until I can get a 32 bit image of 7 I put a 64bit in where the 32 should go. Now this machine that worked was different than the others I tried to do before. The 30 machines that failed were all of the same batch, 2 of them worked the rest (30) failed. If I can verify the 64bit works fine then I will have to upload a 32 bit image to WDS right? Do you think the problem is that there is a mismatch in images a 64 is not going to work with a 32 image?

Do you think a BIOS update would help if it happens with just about every machine we try? And if the system does need a BIOS update would there be an easier way to do this instead of having to update every system's BIOS before we image it, do you think there is something else? And I seem to have registered with two user names in the past. I must have forgotten I did so, I just wanted to let you guys know this so it is clear I am not hijacking this post or am doing an automated reply, thanks sorry for the confusion.

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? This is what I have done to try to fix the problem: 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?

Well from what I have been hearing it cannot be done. Basically what I wanted to do is we have a local admin group that we put on every machine we image. Our imaging is done on a separate network, and then after the imaging is done we join it to the working network and add it to the domain. What I was hoping to insert some sort of command into to our imaging solution that would once joined to the domain would add this local admin group to every pc we image and then join to the domain. But I think the best way to do this is to just push it down through Group policy when we join it to the network Thanks

My question is this when we image our machines they are on a different subnet then our working network. When we are done with the imaging we add the computer to the same subnet as the other computers are then we join it to the domain. How can we add a local admin that is part of the working network when we have not yet joined the system to the domain but when we do add it to the domain it shows up? I have already tried adding the Administrators1=DOMAIN\GROUPNAME in the customsettings.in file then after it was imaged joined the machine to the domain but did not see our group show up. Am I doing something wrong? Thanks