surfertje

In the c:\sysprep\i386\$oem$ there is a cmdlines.txt. This file contains 2 commands: [commands] "c:\sysprep\sysprep -clean" "oeminf.cmd" The file öeminf.cmd" is in the same folder (...\i386\$oem$\ Oeminf.cmd contains a dos menu where the user must choose on which pc the image must be placed. When i restore a image sysprep runs but nothing happens with the cmdlines.txt, or i don't see anything happen. No menu appears etc? Is the path wrong for the file? or what can i do about this problem?

When i make a new image with the same name on a client and upload this image to the WDS server, the orginal image is not overwritten in the explorer. WDS displays the image only one's but on the disk there are 2 .wim's. One with the given name and one with a number on it like name1.wim. Is there any way to avoid this? When i start the client and want to restore the image i see the image also double with the same name!

Can sombody pleasy tell me how i know which lines to add to sysprep.inf mass storage section for the chipset and mass storage drivers? I have a lot of dell machines and want to automate the image for several Dell pc and laptops. Now i am copiing all iastor and other files for the chipset and massstorage to one folder but this doesn't work because the newest iastor for example doesn't contain the lines for the older chipset. I have read that for the mass storage i must copy all lines with pci/dev into the sysprep.inf for the mass storage drivers and then with the path where the files are. This must be different paths for the files because if i have 5 different massstorage devices there must be 5 paths, am i wright? But how can i tell which lines to add to sysprep.inf for the chipset? There are many files with Dell machines in the chipset folder like: ich6 ich4 ich9 etc. Which files and which lines do i add to sysprep.inf and different folders? I keep getting the bsod's after restoring a image to a different machine, and it looks like a mass storage problem or maybe a chipset problem...

Shortly i have created a unsysprepped image with winpe and a sysprepped image with wds. There are 4 images on the wdsserver. One of the images is a image from a D630 machine sysprepped. When i boot a D600 machine and choose to restore a image from wds, i selekt the language and then a scree appears where you can select your images. But i can only see 1 image and that is a unsysprepped VISTA image. This is the only vista image i have made. The winxp images i cannot see. Somebody has a idea why i don't see the windows xp pro sp2 images? Maybe a driver problem? Has it something to do with sysprep?

I am sorry. Never heard of winnt.sif. I am using sysprep and startnet.cmd for the booting images. Can you tell me a little more of the procedure with winnt.sif? Read your life away @ the unattended.xp guide: http://unattended.msfn.org/unattended.xp/ Ok. I have read the document. But so i understand: i can use either winnt.sif and/ or sysprep.inf to make a unattended installation. I use sysprep wih success except where to put all the driverfiles so that they will be automatically install with new hardware. In the document link says that winnt.sif is when install from cd/dvd etc. but this isn't the case. What is the advantage of using winnt.sif and not sysprep.exe? Or am i wrong?

I am sorry. Never heard of winnt.sif. I am using sysprep and startnet.cmd for the booting images. Can you tell me a little more of the procedure with winnt.sif?

But must i point out somewhere that windows (sysprep) should look in that folder? is it c:\$oem$\$1\drivers Must it contain subolders or all files in that folder?

I want to automate the deployment of windowsxp with WDS and winpe method. When i have a new system from Dell i put the inf files in the c:\dell folder. Then i start a tool called spdrv from vernalex which puts the dell folder in the registry so that sysprep uses that settings and adds the drivers so they will be installed automatically when sysprep runs. With Dell machines there are drivers which containes .inf files but also other files like iss, ini, cab, dll etc. For example video and audio drivers is a whole folder from Dell. The question is: driver scanner scan's only for .inf files but don't i need the other files to be on the system? Where must i put thes files? in the windows folder or in the c:\i386 folder (installpath in my sysprep)? Or is it not nesseairy to put these driver on the client machines? I believe it or all OEM drivers.

I am having trouble to image a wim image with imagex. The command i give: imagex /mountrw d:\wds\mount\naamwimimage.wim 1 d:\temp Vervolgens verschijnt de foutmelding: error mounting: Either the path was not found or the parth contains critical system files. The image was created on a dell optiplex 755 machine with all the software installed on windowsxp2. What can i do? The reason that i am mounting is because i want to edit the boot.ini in the image. The image cannot be restored because during the installation there is a disc configuration error. I think this is because the boot.ini is wrong. The image is made on a Dell 755 and there are two partitions on the Dell. Windows is at the second partition. SO when i made the image and want to restore it gives me a discconfiguration error. The unattend.xml for the winpe part is wiping the disc and making 1 partiton so windows in the image is tryiing to install on the second parttition.

Kleine toevoeging: De unattend.xml doet wel iets want als ik de unattend uit de ..remoteinstall\wdsclientsunattend verwijder kan ik helemaal geen image meer terugzetten! Boot ik de client dan en kies voor terugzetten dan verschijnt er even later kan de WDS server niet bereiken. Dit kan toch niet aan de unattend.xml liggen, die heb je toch alleen maar als toevoeging?

I want to automate the first part of the winpe on restoring and capturing a image with wds-winpe etc. I have created a unattend.xml (that is: copieed from the internet) and opened in systemimage manager from WAIK. I cannot open a wim file in the system image manager, then there are errors cannot create catalog file. But i have read on the internet that it is not nessecary to open a image file within the unattend.xml. Now i put the unattend.xml in the \remoteinstall\wdsclientunattend. But nothing is automated when i boot a client. Everything like keyboard and name, password must be entered. So i think the unattend.xml doesn't work. The most imported thing i want to do with unattend is that the winxp machine which te image must apply, is that the disk (2 partitions)is formatted and that 1 partition is created. What am i doiing wrong that the unattend.xml is doeiing nothing? <?xml version="1.0" ?> - <unattend xmlns="urn:schemas-microsoft-com:unattend"> - <settings pass="windowsPE"> - <component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86"> - <WindowsDeploymentServices> - <Login> <WillShowUI>OnError</WillShowUI> - <Credentials> <Username></Username> <Domain></Domain> <Password></Password> </Credentials> </Login> - <ImageSelection> <WillShowUI>OnError</WillShowUI> - <InstallImage> <ImageName></ImageName> <ImageGroup>ImageGroup1</ImageGroup> <Filename></Filename> </InstallImage> - <InstallTo> <DiskID>2</DiskID> <PartitionID>1</PartitionID> </InstallTo> </ImageSelection> </WindowsDeploymentServices> - <DiskConfiguration> <WillShowUI>OnError</WillShowUI> - <Disk> - <CreatePartitions> - <CreatePartition> <Order>1</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> - <ModifyPartitions> - <ModifyPartition> <Active>true</Active> <Format>NTFS</Format> <Label></Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration> </component> - <component name="Microsoft-Windows-International-Core-WinPE" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86"> - <SetupUILanguage> <WillShowUI>OnError</WillShowUI> <UILanguage>en-US</UILanguage> </SetupUILanguage> <UILanguage>en-US</UILanguage> </component> </settings> </unattend>

When i boot a client thru winpe / pxe and choose for Image capture (name i have given it in wds) there appears no volume to choose for capturing. I have read that this is because sysprep hasn't run. This is correct when i run sysprep there is a volume. But my problem is then: how do i maintain a image to add drivers and software e.d.? A this moment with ghost, i make a master image with no sysprep run and one image with sysprep run. When i want to add aoftware i restore the master unsysprepped and make the changes. Then i make from that machine a new unsysprepped image and a sysprepped image. How must i do that now when i have no master image unsysprepped? I mean how to add drivers / software to a image that is sysprepped because when i restore that image it runs sysprep and then it is connecting to the domain and gets a pcnumber etc..

With mounting to d"\wds\mount i mean: the image is mounted with imagex. I have read that i must mount the image to edit startnet.cmd and diskpart. When i don't mount the image the startnet.cmd cannot be edited? But on a article on the internet i saw it is also possible to use Unattend.xml fot automating like formatting etc. in the windowsPE phase, in combination with windowsXP. Can i use unattend.xml instead of startnet.cmd? Because this unattend can be edited with WAIK which makes it easyer. I have tried it already but unattend doesn't do anything when i make use of it with windowsxp..

You do not "add" FILE.TXT to startnet.cmd you add the line: inside startnet.cmd, with notepad or other "pure text" editor. this invokes diskpart using the FILE.TXT as a series (or batch) of commands that will be executed automatically. FILE.TXT, with the contents of the previous post or your custom ones, must obviously be in the same directory of startnet.cmd. jaclaz Ok. The part of file.txt and diskpart is clear to me, but the startnet.cmd not yet. I have read that startnet.cmd is in the windows\system32 folder on every image. What must i do to add the command diskpart etc to startnet.cmd? Mount a image and then? or make a startnet.cmd of my own with notepad but how to add it to a image? Can you help me with this, i can't really find how to edit / make the startnet.cmd and how to add it etc? I think i know a little more. I am mounting the boot.wim. ype in: edit d:\wds\mount\startnet.cmd (path where i mounted boot.wim). After the wpinit i put in the rule: diskpart /s diskpart.txt (this is a little confusing: diskpart.txt must excist but where do i put the diskpart.txt, must i also choose in the mounted boot.wim: edit c:\diskpart.txt and put in the lines?) And must i do this also voor the install image? Must i then add the boot.wim and install.wim to the wds first remove then add or is replace enough?

You do not "add" FILE.TXT to startnet.cmd you add the line: inside startnet.cmd, with notepad or other "pure text" editor. this invokes diskpart using the FILE.TXT as a series (or batch) of commands that will be executed automatically. FILE.TXT, with the contents of the previous post or your custom ones, must obviously be in the same directory of startnet.cmd. jaclaz Ok. The part of file.txt and diskpart is clear to me, but the startnet.cmd not yet. I have read that startnet.cmd is in the windows\system32 folder on every image. What must i do to add the command diskpart etc to startnet.cmd? Mount a image and then? or make a startnet.cmd of my own with notepad but how to add it to a image? Can you help me with this, i can't really find how to edit / make the startnet.cmd and how to add it etc?

You do not "add" FILE.TXT to startnet.cmd you add the line: inside startnet.cmd, with notepad or other "pure text" editor. this invokes diskpart using the FILE.TXT as a series (or batch) of commands that will be executed automatically. FILE.TXT, with the contents of the previous post or your custom ones, must obviously be in the same directory of startnet.cmd. jaclaz Ok. The part of file.txt and diskpart is clear to me, but the startnet.cmd not yet. I have read that startnet.cmd is in the windows\system32 folder on every image. What must i do to add the command diskpart etc to startnet.cmd? Mount a image and then? or make a startnet.cmd of my own with notepad but how to add it to a image?

Thx, but how do i add the textfile to a startnet.cmd?

Because i wan't to automate as much as possible by restoring or making a image and want to delete a disk with all partitions and then off course create a new partition NTFS with use of Winpe and WDS/WAIK etc for windowsxp SP2 clients. Reading thru google says that i best use diskpart for the partitions and startnet.cmd to start diskpart. But i don't understand how to edit startnet.cmd to start a diskpart file and how to make a diskpart file to wipe out the disk and create new partition for restoring to that partition. I have read that i must mount a image with imagex but how do i edit the startnet.cmd then? Must i make a startnet.cmd in every image i got?

After installing WDS on a windows2003 SP2 server and WAIK i want to get started with deploying windows XP pro sp2 machines and Vista. The clients are Dell machines. The documentation is talking about boot, capture images e.d.. I have following the manual for WDS and booted a client. On a other post on this forum i state that the client cannot connect to the WDS server. I believe that this comes because the network driver aren't up to date in the standard image... I am asking myself what does WDS do? is it using WindowsPE, Imagex? etc. When i boot a client and choose F12 PXE boot what is beiing used to boot? When i want to add drivers to a image that is for booting how do i add the new drivers, like the manual in windowsPE says? command prompt and imagex commands etc? I like to know more of the details what is goiing on when booting from PXE/ WDS server...

I wan't to step over from ghost 7 to WDS for client deployment. I have read a document where people speak about sysprep.ini. I am using with ghost for years: sysprep.inf. I want to deploy, winxp pro and vista with wds. Must i use sysprep.ini or sysprep.inf of is it version depended?

I have installed and configured a WDS server windows 2003 sp2. Installed Vista WAIK (downloaden from microsoft). Booted a client Dell with network PXE on. The client comes with a menu to boot are capture a image. I want to capture a image. A screen appears to set the location for the image to save. I choose the C drive. Then a screen appears to upload the image to a WDS server. This is the problem. I have put the name from the WDS server in and also tried the IP from the server. But the client cannot connect to the WDS server. It says: cannot reach the network location..... What can be the problem. The wds server can be pinged, reached with remote desktop etc. There are no firewalls on the WDS server so this cannot be the problem. Anyone has a idea? I am just beginning to deploying thru a new envirement, but the first problem arrives. The client is a Dell optiplex 755.

Thx. But this is not in combination with a server? I think the best way i wan't to do it is use a server for the images and start the pc with a usb stick or better thru network and then choose a image from the server and restore.

I am searching for a new method of imaging deploying pc's on a network. Using windowsxp and Vista. Now i am using Ghost 7 and Ghostcastserver. Every new system that i buy, rstoring the image woth ghost 8 on the machine. Not the best solution however because i have 12 images. To many different systems on our network. I have read on this website tools like: WDS, WINDOWSPE, IMAGEX, WAIK etc that can deploy windows. Also read about something like a complete microsoft solution for deploying for free... Can some one explain to me what do i need for deploying windowsxp(vista) with free tools like above. Which tools i need excactly? Is there a manual from beginning to setup those tools on a server to the end (restoring it to a client)? Freddie

No i mean SMS 2003. I believe SMS is a package of System centre essentials and you can also use it apart. I think there are nog many people using sms because there is no much response. I must use it though so searching and searching is what i am gonna do.

I am sorry. I mean SBS 2003!