surfertje

But when i dispart the disk so it is empty and install win7 then directly make a image, then restore the image must be possible? When i do this after the restore a message appears from the Window Boot manager, the boot selection failed because a required device is inaccessible? But what can this be, it is so simple what i do: clean the disk, make 1 partition and install win 7, then make image, restore image...... When the error's appears i boot with a bootcd and then repair the boot, then Windows starts fine... Do you believe that sysprepping this machine solves the error?

Made a image from a Win 7 Pro machine with Windows PE starting with usb stick. It is a non sysprepped machine (i need this as a master reference pc). When i want to restore this image an hardware error appears. When i boot with a rescue disk there is a option to recover the startup options. Choosing this option works. Windows 7 then starts. When i start with the recover disk and look at the error details i see that: Windows device: partition not found. So there is something wrong with the startup partition. The machine is a Dell Optiplex 760. What can this be? Maybe the startup partition in the image is wrong but i cannot see that in Windows 7. In Windows xp i had a look at the boot.ini but now there is bcdboot which is not so easy to look at. Someone got a idea?

For a year now i am using WIndows Xp pro Sp2 and sysprepping. In sysprep.inf there are options underneath: unattended with the rule: driversigning... etc. Also in sysprep.inf under the massstorage section a complete list of all the mass storage drivers created with a particalar command which i don't know at the moment but the sysprep.inf is filled with all kinds of mass storage. In this way i can install the image to different hardware. It has worked for quit some time know but today i am confused. Restored a image and installed new software. Then started sysprep (like always) and a few minutes later a message appears: hardware - this drivers is not signed for the windows logo etc. He does this for every mass storage device! (and this is many). Because i never had this before i am confued how to solve this. One time i gave a enter for every driver question but then in the end noting happens...(normally he would shout down the machine. What can i do about this? When i leave the list mass storage empty in sysprep i cannot restorel to different hardware anymore...

Thx. I only have the possibility to remove the PXE filter on the server on MDT. How can i use this filter? And when not using the filter according to your second idea, next to adding the litetouch.wim as a boot image in WDS, must the litetouch.xml also created in MDT be connected to the boot image that i just imported? But i really like to use MDT and then PXE boot to the MDT with the unattended install.

I am goiing to start with making a unattend file with the newest WSIm for Windows 7 (i post this here because i believe this is the same as Vista with making a xml file..) and i would like to know what to fill in by: system locale en userlocale. I know that UIlanguage and input locale is for the keyboard so i use: en-US But because i want Dutch as the language for the operating system this must be filled in by system or userlocale i believe? Can someone tell me what duch is for code and where exactly fill in..

Thx. But on your blog i cannot find a guide for deploying with MDT2010 in combination with WDS. That is a discission which i cannot make at the moment. I am now using WDS with windowsxp and sysprep etc. When we go to Windows 7 i am wundering to step over to MDT2010 in combination with WDS but i still cannot find the advantage of using MDT with or without WDS.

Is there a good guide where to start with deploying Windows 7 thru WDS and WAIK / Imagex and Winpe? I have read some of the documents included in the newest WAIK but thats a little different from the former deploy method. They are talking with configuration sets e.d.. I am looking for a step by step wlkthrough to deploy Windows 7 clients.

We are goiing to use Windows 7 shortly. Now we use Windowsxp. Imaging is been done with WDS and Winpe / Imagex. We use .wim files. I capture a configured Winxp and then roll out that sysprepped XP machine to several other Dell machines. I was wundering how you people image Windows 7 with the OEM installs. Sure many of you use Dell machines with OEm versions of Windows. Can one image a Windows 7 OEM install and then roll out that image to several machines?

Thx. But the images from Micrsoft are standard images. After configuring Windows and installing basic software the image is done. Then that image and several different install images thru the organisation , are rolled out to clients when needed. I am using WDS and Winpe/Imagex as the tools and it took me a while to go to the problems that came with these tools (driver problems whith the Dell Optiplex and Latitude clients), so i am not waiting to try another tool like MDT2010.... When i configure a install image .wim from Microsoft so installing software and configuring windows, and then run sysprep to give it a new sid, then that also ok i believe. But if this isn't nessecairy anymore..

Nobody an idea? 1. Windows 7 does use an XML file (autounattend.xml) you can edit this file within the WAIK which is free for download from MS 2. You don't have to resysprep your image unless you want to install applications prior to deployment. the WIM file is already sysprepped and ready to go. 3. you will want to use the Default profile for any changes you want to use for any new user to receive. the Default User folder is a redirct (symbolic link) to the default folder. So with windowsxp it was nessecairy to give the client a new sid and everything but this is not nessecairy anymore with Windows 7? With Windowsxp it was also that the first logon user received the administrator profile. The second user the default profile, this is also gone, the first user gets the default profile directly?

Nobody an idea?

In Windows 7 under the Users folder there are some folders with a lock before it. The folders are: Default User and Public and also All Users. What i am wundering about is: In WIndowsxp the first logon user gets the local administrater profile, because the administrator profile becomes the default. The next new users that logs in to the client gets the defaul user profile. How is that arranged in Windows 7? I see a default user folder where i can't get in. There is also a default folder, and it seems this is de profile you get when you are new to the client. But where is the default user folder for? And the All users profile because there is a public folder, i thought the public folder is the all users folder from windowsxp?

We are using Windows Xp at the moment and Windows Deployment Services and Imagex/ Winpe. I configure a Windowsxp machine then start sysprep and shutdown the machine. Make a image. Restore the image and then sysprep asks which pcnumber it must have and start a batchfile which cleans the system. This is arranged in sysprep.inf also the domain name and the drivers are in sysprep.inf. I have read som stuff about imaging Windows Vista / 7 but then i use sysprep only for the change of SID and al the autoation is be done with a unattend.xml file. I would like a start how i can roll out the images to clients so that WDS / xml files is taking over the sysprep configuration settings. Where to start? The procedure for imaging WindowsXp or Vista are completely different, but i would like to do the same things as with Windows xp. Is it the same when i: Make a unattend.xml with wsim (from the standard vista.wim) and connect it to the install image. In this xml configure the: connect to domain, join the right OU in AD, set the keyboard and language settings configure a client Run sysprep on the clients with the generalize command and shutdown, make the image and roll out that image to the clients which then starts the unattend.xml? Run a batchfile which copy's files thru??

We are now using Windows Deployment Services and Winpe and sysprep locally to deploy the WindowsXp images. We want to step over to Windows 7 soon. With Windows 7 i can use a .xml file to automate the installation (exept for the computer name). Then i still use sysprep. But within the .xml file i have read that automate can be done in the .xml. How can i arrange the user profiles in the .xml file so that every new user that logs in gets this profile? How does Windows 7 handles the default user profile? because under c:\users\ there is a default and a default user profile..

Problem solved. The .wim was corrupt i believe. Replaced it with a copy and error was gone.

I am getting a error when trying to restore a image made with Winpe to a Windows Deployment Service server. The error is: The specified image does not contain a resource location I don't know what the errors mean. The procedure i do to make a image or restore on: Sysprep a installation of xp and then shutdown machine Boot with a USB key with winpe on it and capture the image with imagex. Then i make changes to the image and capture it with WDS (WDS is not making images for non sysprepped machines). This is working now for 1 year and suddenly when i boot a client with the USB key and want to restore the image on the WDS server the image displayes this error. Normally i restore a image with WDS but because WDS does not make images from a non sysprepped machien i must use winpe on the usb key. Someone a idea?

Thx. So it is tru that sysprep isn't needed anymore?

Ok. But i have read somewhere that for unattende installation for Vista / Windows7 you don't need sysprep anymore but a .xml file which you can use to give the answers. IS there documentation somewhere for setting this up thru wds?

We now use Images thru WDS. Starting WINxp machines thru network boot and then install or make images thru WDS server. This goes well. The clients are prepared with sysprep. For the images i make the machines are not sysprepped but i boot then with a usb key with winpe on it. Soon we will step over to Windows 7. I would like a manual or some documentation of how to configure WDS to make and roll out IMAGES with XP and WIndows 7 / Vista. Both must be supported off course and is sysprep still nessecairy on the clients? We have now almost a unattended rollout except for the computer name this is asked in sysprep when i roll the image out. Is there a step to step guide or something available for a unattende roll out for Vista / Windows 7 in combination with XP clients and Windows Deployment Service / Winpe/ Imagex?

I noticed that the sysprep -bmsd does noting anymore nor does buildmassstoragesection=yes, even when [sysprepmassstorage] is empty. The problem lays here i am guessing but how to resolve it, why does sysprep -bmsd builds no massstorage list anymore?

The message is: cannot edit the registry This is very global.. I am now tryiing to remove a lot of mass storage devices out of sysprep and see if it then works. (i have made a lisst of mass storage on a other computer with sysprep -bmsd and copied it in sysprep inf, then added my own masss storage to be sure it works for all my dell machines...) Maybe i better create the list during starting sysprep but then i don't know if all my dell mass storage are in it

Sysprep always has done his job. Now i have new hardware and have made some changes. Running sysprep on a client and sysprep runs for 10 minutes then does noting anymore! doesn;t reboot nor shutdown. The command i gave is start sysprep -reseal -mini -quiet -activated -shutdown When i look at the folder after sysprep stops and exits (but not shutdown) the sysprep folder still excists and i can run it again and again... Someone has i idea what i can do about it? I have replaced sysprep already with a newerversion for Windows Xp pro SP2

After i run sysprep and the system reboots for the first time the administrator is automatically logs in. Then the system finds new hardware and wants to reboot. He keeps doiing that, after six times i take a look at the device manager and see that all hardware is detected, there are no yellow marks in front of any hardware. How can it be that the system keeps automatically logging in all the time and keep finding new hardware? In sysprep i have the option: auto logoncount 2 times. That the administrator logs in automatically is resolved thru the user account sceen, setting the option that the user must use a username and password. But this is before sysprep the normal setting and after sysprep the setting is changed.

I have struggled a lot with wds and began over and over again. Every attempt i came to somthing new with a problem also injecting drivers. What i would do is find the wright boot.wim for you (for me it was on the Windows Vista SP! dvd and not the boot.wim from the windows Vista) the boot.wim is also on the windows server 2008 dvd. Then try to inject drivers with peimg. Try *.inf but also name the name.inf exactly. Find the right drivers for your network card. Try Vista drivers not XP. SOmetimes XP drivers will do sometimes not. Search the internet for problems with your network card. I believe it is in the boot.wim that you use (hell by me it was due to problems 90% at te time..)

Thanks i think i found the problem. Isn't it so that in sysprep.inf the installfilespath is pointing to the path where the cmdlines should be for example: installfilespath=c:\i386 Then cmdlines.txt should be: in c:\i386\$oem$ Now i have installfilespath=c:\ and the cmdlines.txt in c:\sysprep\$oem$ ?? According to the technet from microsoft this is wrong and that is why sysprep is not use the cmdlines. What you said is also in technet. Thx.