surfertje

I want to put a image WindowsXP sp3 on a new latitude E6410 thru booting With Winpe 2.x. The first time i wanted to boot with winpe a network error appears. I have put in the Vista and Xp drivers for the Latitude E6410 and now he is not giving me the error networkbut a: windows boot manager error: Windows failed to start. Status 0xc0000017 info: an unexpected error occured. Then i loaded in the boot.wim the drivers for Chipset. But the error remains. Which drivers must i load into the boot.wim to load the E6410 correctly? I mean: which drivers like chipset, network and from which operating system: Xp, Vista or Windows 7 32bit? How can i see what is causing the error when booting the client from wdserver/boot.wim?

I am sorry it is not my intention to break the rules. I shall keep it in mind next time, thanks for your critics.

I already know why the error appears. In the TS within MDT when you import image you must specify the OS where you installed Win7 with, a little strange according to my opinion but it is because the restore is nog running, without stopping yet...

I am really stuck here, someone a idea? Am i doiing something wrong? For example: into audit mode use a sysprep and capture task (from MDT2010), must i do manually run sysprep, then boot with Winpe and capture the image myself, because i would like to do it with MDT2010?

Another problem. I want to start over and did the following: Installed Win7 Pro thru the dvd on a client Vmware Workstation. Ctrl-shift f3 and into audit mode Put an icon on the desktop (to see if copyprofile works) Activated Windows 7 Started Litetouch.wsf thru explorer (making a network connection to the deploymentserver) Choose a sysprep and capture TS (also here the copyprofile set thru "edit unattend.xml) Made a TS in the deploymentshare that deploys the image with the copyprofile set. Started networkboot and choose the above task sequence An error appears after a few minutes: Operating system deployment not completed succesfully: ZTI ERROR Object needed Litetouch deployment failed Return code = -2147.... 0x80004005 Viewing the log files on the client in the minint folder: there is 1 error in the bdd and the wizard.log: Invalid OS GUID (number) specified Maybe it has something to do that i activated the Vmware Workstation machine? What can this be?

Why can't i go back to re-audit mode. When i make a snapshot within Vmware workstation before resealing the client, then months later restore that snapshot (which is still in audit mode)and edit that client image then making a new snapshot and then sysprep again. That way i have a new image and a new snapshot which i can do months later when the client image has to change start over again with this procedure?

Ok, one final quetion though. After i am finished in AUDIT mode, can i then rus the cscript \\server\deploymentshare$\litetouch.wsf in AUDIT mode?. This Litetouch does a sysprep and capture.. So then the only difference is that i do not install the applications in normal mode but in audit mode and then sysprep and capture.

There it is again the äudit mode. Could you please tell me how to use "audit" mode and why i should use this? When i start over again i want to do it wright this time. Never used audit mode. The method i do now is: Install Win7 Pro on a Vmware virtual image. Fill in a new user at the end of setup because that is required Before starting the task sequence from MDT2010 making a Vmware Workstation snapshot Install applications configure Win7 for the end user Do a sysprep and capture Task Sequence in MDT2010 (start this command in Win7 client cscript \\server\deploymentshare$\litetouch.wsf Import a custom image in MDT2010 and import the image i just made edit the unattend.xml so copyprofile is set (but this is not working yet) Make a new Task sequence to deploy this image At the litetouch.wim to WDS as a boot image and then boot the client with Network boot. Choose the right task sequence and there is goes. So what must i do different to use "audit" mode and why? I would appreciate some help

It was not in AUDIT mode. I have installed Win7 and then installed applications and config Win7. So it was after a full Install. I have never worked within audit mode so can you help me out with no Audit mode. How can i solve it without the use of Audit mode? I Think having the Administrator account active with a booting tool and then activated it... No one a idea?

It was not in AUDIT mode. I have installed Win7 and then installed applications and config Win7. So it was after a full Install. I have never worked within audit mode so can you help me out with no Audit mode. How can i solve it without the use of Audit mode? I Think having the Administrator account active with a booting tool and then activated it...

From a vmware workstation virtual machine..

I have looked en don't see a profilelist key or data in the current version.. Have found the key but there are no other users in there but: default and public. I also don't see the administrator user here?

I have looked en don't see a profilelist key or data in the current version..

I have been struggling for days now with the copyprofile setting in MDT2010. What i have done: Imported a (captured) image within MDT2010. Making a tassequence to roll out this image. On the osinfo tab of the tasksequence, edit unattend.xml en in the specialize fase put in: true behind the copyprofile. Now i am getting a error: Cannot parse the answerfile for installation without ...cannot parse of for fase specialize, microsoft Windows ____ Setup... This is due to the copyprofile setting, but what am i doiing wrong? I have chequed the unattend.xml which is used when roll out the image and the copyprofile is in the file with the true text. So this is good. I have never have the copyprofile worked yet... On the client that is beiing sysprepped and captured there is only one profile (account) available that is the local administrator account. Someone a idea?

That's not a problem. Simply change: to: or remove the two lines (they were just a check): i.e.this is the "semi-final" version: and once you have it woreking you can remove also the red PAUSE's. The "command is not recognized as a in- external command", as now said for the 3rd (THIRD) time is because the executable named "bcdboot.exe" is NOT found in the current directory NOR in the current PATH. You need to EITHER: add the path where "bcdboot.exe" is to the PATH variable copy the "bcdboot.exe" in the working directory of the batch change the batch to include the FULL path to the "bcdboot.exe" file. something like: \\server\reminst\images\windows7\bcdboot.exe D:\Windows or: D:\Windows\system32\bcdboot.exe D:\Windows Remember that the general idea is to help you learning how to write your own batches, not that of writing them for you, you need some patience and trial and error, but you also need some time to try understanding WHAT the batch commands do and introduce your own checks. jaclaz Thanks alot, it works perfect! I have tested it and there where no errors. Now i gonna try to understand what you have told me about the batchfiles. And i am gonna post a new question on this forum for a another problem i am struggling for days now about the copyprofile in MDT2010. Again, youve been a great help.