Br4tt3

Yap, that would work for a machine that you will install the OS onto... if u already have a OS installed (vista) and forgot to create a second partition for enabling BitLocker, MS has released a tool named BdeHdCfg.exe that will do the trick for you, without having to reinstall the machine. Neet....

Download and install the WAIK tools on ur machine, once done: 1. Open up a cmd prompt (assuming ur admin) 2. Navigate to the imagex.exe tool and issue the following command: imagex /mountrw c:\my_path\my_vista_image.wim 1 c:\mount_folder <-- where u mount imagex index 1 to ur mount folder. 3. Open up a explorer.exe instance, go to the c:\mount directory and the files and folders that u wanna include, once done.... 4. That same cmd console prompt: imagex /unmount /commit c:\mount_folder 5. From now on u have included the custom files and folders into ur my_vista_image.wim file. I have not actually added files to the original install.wim file on the Vista DVD but I rather, install my Vista using an unattend file, sysprep it, then capture the state of the machine into my own custom_install.wim file which I then can edit and add/delete files or folder to using the imagex.exe tool. 6. If u wanna apply that image later on, use WDS or manually run the imagex.exe /apply command.... If u install the WAIK (free of charge, download it from MS) u will automatically obtain the creation "kit" for WinPE 2.0 as well.... once there, then u have all the relevant documentation on how to get up and running with WDS/WinPE/Vista/unattend settings and so on.... Oh, and the default boot.wim (WinPE) file on the Vista DVD contains two images within one single .wim image. So make sure which ID you specify when mounting the image using the imagex command and the index number. U can obtain the index number by running the imagex /info c:\my_custom_image.wim

U might wanna use a tool like dependency walker (depend.exe) that will list all the required .dll's or .ocx's files that needs to be available for ur app to function properly. Trial and error some....

u want to have it loaded automatically when starting WinPE --> Startnet.cmd if u wanna have it loaded as a shell, then of course u can do that as well..... but to answer ur question, I dont know what replaces txtsetup.sif now..... did u just copy the application to a specific path within WinPE using txtsetup.sif earlier or did u actually execute it as well? didnt know u could execute stuff from it.... cool.

I have tried the imageinstall feature as well, and YES, it copied the files within the image (.wim) down or applied them..... but I dont use it right now. For now, I am using BDD to create and deploy one single appliction into my Vista builds which it is performing without any problems (even though there is other problems... ). BDD does this using scripts that are executed from either WinPE or from within full Vista. I would suggest that u download BDD 2007 and try it out, it's free and not that difficult to set up. If u dont wanna use BDD I would suggest that u copy the files down to the machine from within a script that is executed within WinPE 2.0. WinPE 2.0 is free of charge, download it and try it, it's awsome.

Well, I think that there might be one diffrence, I dont execute something external to the Vista machine, I copy the applications down locally before executing them, if u wanna perform the install external to the installing machine I would imagine that u would have to map the network drive prior to executing the .exe file: net use z: \\my_server\my_share /user:domain\my_user my_password and then: z:\my_app /some_switch¨ anyway, here is one example straight out of the BDD box: <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Path>cmd /c net user Administrator /active:yes</Path> <Description>EnableAdmin</Description> <Order>1</Order> </RunSynchronousCommand> </RunSynchronous> </component> Also, r u performing the install as the built in administrator or as another dude with Admin permissions? UAC maby? depending on ur UAC local policies.....

So, i am not really following you! Do you wanna add a single .exe application to your WinPE? Or do you wanna copy over files for an application without installing it into the operating system using the RunSynchronous feature? For #1: Mount your boot.wim (thats the WinPE image on ur Vista DVD) using the imagex.exe command line tool avail in the WAIK (free to download). Once mounted, add ur single .exe application file to ur image. Then unmount the image using the imagex and commit the changes. Should be good to go.... if u wanna invoke it from PE, then startnet.cmd is the place to start messing around. For #2: U can pretty much do anything from the RunSynchronous command section as long as it is CLI based features, such as xcopy, invoke wscript.exe or cscript, msiexec and so on.... or u could also just add the files and folders to ur install.wim image (Vista DVD image file - also on the DVD) using the imagex (WAIK) tool. That way, once the install is finished, the application will be available to install, execute or whatever....

Well, not the AuditUser section, perform it from the specialize section, I have tried adding several commands that are to be executed using the runsynchronous section of the .xml file which all worked out well.. Is it .exe/.msi/scripts that u wanna install or what?

Sure it is.... so it is with all unattended forms of setup using WinXP/2003... just look up the specifc component that matches the thing u wanna add in ur deploy.chm/ref.chm help file below the Components section.

Well, I dont think it is the switch port, but most drivers initalize on auto negotiate, in that case drop the full 1000 and set it to auto.... also, portfast i ON I suppose on the switch? I have seen wiered issues with PortFast when dealing with RIS installations...

Just a suggestion: We solved this issue by creating our own .osc screen that will create a variable within the temp unattend file created for each machine that installs using RIS. Once the machine is in a full win32 environment, it would be easy to script the name of the machine and the move between OUs using the variable earlier in the CIW/.osc screens...

I tired this a coupple of months ago.... I think this mostly comes down to the processor that u r going to run the virtual machine on.... for being able to run x64 virtual machines ontop of a win32 or win64 host, I had to have x86/x64 capable processor + virtualization support instructions in the processor: a.ka Intel VT or AMD Pacifica..... otherwise, the host could install x64 operating systems, but it could not virtualize other x64 machines.... worked out for both VM-Ware server and MS Virtual server...

Make sure u have the file system driver installed (wimfltr.inf - right click and choose install), then the corresponding .sys file is copied to the driver cache and u will be able to mount the boot.wim file using imagex.exe using the /mount or /mountrw command.... I also assume that u have all the dependency software for WAIK installed, MS XML parser, DotNet and so on before trying to use the WSIM application...

Does the answer file need a section where it links it to a particular image? Also which boot loader do you use for booting from PXE boot rom? Thanks Systemsmb There are two seperate .xml files that can be designated for WDS I believe, one for the boot image (WinPE) and one for the main Vista installation. The boot image unattend file is for automating the WDS client behaviour and so on... below u will find my .xml file for handling the drive setup: <DiskConfiguration> <Disk wcm:action="add"> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Extend>false</Extend> <Size>3000</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Type>Primary</Type> <Extend>true</Extend> <Order>2</Order> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>VistaBoot</Label> <Letter>H</Letter> <Order>1</Order> <PartitionID>1</PartitionID> <Extend>false</Extend> </ModifyPartition> <ModifyPartition wcm:action="add"> <Active>false</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>BitLocker</Label> <Letter>C</Letter> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> <WillShowUI>Never</WillShowUI> </DiskConfiguration> hope it helps....

Hi! On the question: That MS looks for an unattend file in seven places! You can open up the WAIK *.chm file and search for "panther" and u will get an option to see "Methods for running Windows setup".... here is what u get! 1. Registry (Prio 1) HKLM\System\Setup!UnattendFile Specifies a pointer in the registry to an answer file. The answer file is not required to be named Unattend.xml. 2. %WINDIR%\panther\unattend (Prio 2) The name of the answer file must be Unattend.xml or Autounattend.xml. 3. %WINDIR%\panther (Prio 3) Windows Setup caches answer files to this location. Important: Do not overwrite the answer files in these directories. 4. Removable read/write media in order of drive letter, at the root of the drive. (Prio 4) Removable read/write media in order of drive letter, at the root of the drive. The name of the answer file must be Unattend.xml or Autounattend.xml, and the answer file must be located at the root of the drive. 5. Removable read-only media in order of drive letter, at the root of the drive. (Prio 5) Removable read-only media in order of drive letter, at the root of the drive. (Prio 5) The name of the answer file must be Unattend.xml or Autounattend.xml, and must be located at the root of the drive. 6. windowsPE and offlineServicing passes: \sources directory in a Windows distribution All other passes: %WINDIR%\system32\sysprep In the windowsPE and offlineServicing passes, the name of the answer file must be Autounattend.xml. For all other configuration passes, the file name must be Unattend.xml. 7. %SYSTEMDRIVE% The answer file name must be Unattend.xml or Autounattend.xml Please read the whole section in this .chm file as it is pretty complex on how it will detect and make use of the supplied answer files... especially if u mix things up with multiple answer files like me... Regarding the custom image and drivers, the anwser is: Yes, it is possible to extend the image to be working on a laptop, just supply the drivers using a $OEM$ folder structure and specify which locations to be added using the unattend.xml using the WSIM application.

Dont really know what u mean..... but my guess is that u wanna run the vista setup using diffrent configurations sets? maby setup.exe /unattend:my_autounattend.xml would work.....

No, there is no supported way off kicking off a Win32 install using RIS from within xp or 2003. What u are looking for is WinPE. Using this software, u can redeploy ur machines even though u r not physical present to perform the installation. Of course, most people buy stuff like altiris or sms to get a "zero-touch" feeling over it, but all u need really, is WinPE and a sh**load of vbscripting... and maby a AD...

Nope, u can do it.... first of all, check out BDD 2007. It is working sweet for creating xp/2003 images that can be deployed using for example WDS. However, vista .wim images uses the .xml format as the native answer file format. For xp or 2003, u would perform an unattended installation, then run sysprep before capturing the image into a wim format. The file that u wanna use to automate sysprep's behaviour is named: sysprep.inf and must always be located in the c:\sysprep directory when creating ur reference image. More or less, create and modify a sysprep.inf until it suits ur needs, place it in the c:\sysprep dir prior to running the actual sysprep.exe command. Then the image will act on those settings once u deploy it.... gl...

hi! If u wanna move the WinPE 2.0 drive letter from X: to B: I think u are up for a big challenge. According to MS the driveletter is hardcoded.... then my guess it is somewhere within some .dll or something binary that u would have to edit. I have not done this but I guess it would be easier to just remodify ur scripts.

Dont buy into what they say.... I dont think they supported ADSI below WinPE based on XP or 2003 either (if I am not mistaken), that does not mean it does not work..... like I said, I have not tried it but I can for example see that they are using some kind of provide within WinPE 2.0 that comes with BDD 2007. For example, they try to use the WinNT provide which is not ADSI but anyway....

Also, when checking the setupact.log file, one can see from the sysprep logs that it first tries the sysprep.xml file but denies, then moves over and snatches an unattend.xml file from the following directory: C:\%windir%\panther\unattend.xml file.... When I compare the unattend.xml with the sysprep.xml file there is one specific setting that is missing in my sysprep.xml file: Unattend.xml <settings pass="generalize" wasPassProcessed="true"> Sysprep.xml <settings pass="generalize"> If I copy that setting over, then I cannot open the sysprep.xml file from within the WSIM application! Any one seen it or know what it stands for?

Hi folks... I am having an issue when I am running the sysprep function from within a BDD capture scenario. When the script is executing it will actually run sysprep.exe but it does accept my custom sysprep.xml file for usage. This is what happens: 1. Executing the following command from the script named: LTISysprep.wsf C:\Windows\System32\sysprep\sysprep.exe /quiet /generalize /oobe /unattend:c:\windows\system32\sysprep\sysprep.xml /quit 2. Once sysprep.exe is exectuted, the c:\Windows\System32\sysprep\panther directory is created which contains the logs for the sysprep command, reading from the setupact.txt, I find the following: [0x0f004d] SYSPRP The time is now 2007-02-03 09:16:12 [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\sysprep\Panther [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine [0x0f0056] SYSPRP ValidateVersion:OS version is okay [0x0f005c] SYSPRP ScreenSaver:Successfully disabled screen saver for sysprep [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIET' [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE' [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE' [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND' [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'QUIT' [0x0f004a] SYSPRP WaitThread:Entering spawned waiting thread [sysprep.exe] UnattendFindAnswerFile: Looking at explicitly provided unattend file [c:\windows\system32\sysprep\sysprep.xml]... [sysprep.exe] UnattendFindAnswerFile: [c:\windows\system32\sysprep\sysprep.xml] meets criteria for an explicitly provided unattend file. SYSPRP SysprepSearchForUnattend: Using unattend file at [c:\windows\system32\sysprep\sysprep.xml]. SYSPRP SysprepSearchForUnattend: [generalize] pass in unattend file [c:\windows\system32\sysprep\sysprep.xml] either doesn't exist or passed validation SYSPRP WinMain:Found unattend file at [c:\windows\system32\sysprep\sysprep.xml]; caching... SYSPRP WinMain:Processing unattend file's 'generalize' pass... SYSPRP Sysprep is running a generalize pass with the following unattend file: [%windir%\panther\unattend.xml] CSI 00000001@2007/2/3:08:16:13.448 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef92ae9d9 @0x7fef4143a7f @0x7fef415c196 @0x7fef412da8c @0x7fef412c9e3 @0xff63d17c) [sysprep.exe] [Action Queue] : GenerateActionQueue begin [sysprep.exe] [Action Queue] : Processing pass = generalize [sysprep.exe] [Action Queue] : Generating queue file to C:\Windows\panther\actionqueue\generalize.uaq [sysprep.exe] [Action Queue] : Identity 0: Microsoft-Windows-Shell-Setup, Culture=neutral, Version=6.0.6000.16386, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS [sysprep.exe] [Action Queue] : Using component order file C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6000.16386_none_63473ad082bcdac6\GlobalInstallOrder.xml CSI 00000001@2007/2/3:08:16:13.588 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef92ae9d9 @0x7fef420ed68 @0x7fef420ddc4 @0x7fef420dbcf @0xff63d497 @0xff63cd8a) [sysprep.exe] [Action Queue] : Found manifest file C:\Windows\Winsxs\Manifests\amd64_microsoft-windows-shell-setup_31bf3856ad364e35_6.0.6000.16386_none_2c42ac33a5128efe.manifest [sysprep.exe] [Action Queue] : GenerateActionQueue finish (hr = 0x0) [sysprep.exe] [Action Queue] : ProcessActionQueue start [sysprep.exe] [Action Queue] : ProcessActionQueue using queue file C:\Windows\panther\actionqueue\generalize.uaq [sysprep.exe] [Action Queue] : ProcessActionQueue finish (hr = 0x0) SYSPRP RunUnattendGeneralizePass: Sysprep unattend generalize pass exits; hr = 0x0, hrResult = 0x0, bRebootRequired = 0x0 NOTE: Please check the entry that states that sysprep does not accept the sysprep.xml [generalize] section of the file... 3. And here is my sysprep.xml file: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Password> <Value>TQB5AFAANAAkACQAdwAwAHIAZAAhAFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </Password> <Domain></Domain> <Enabled>true</Enabled> <LogonCount>2</LogonCount> <Username>Administrator</Username> </AutoLogon> <BluetoothTaskbarIconEnabled>true</BluetoothTaskbarIconEnabled> <ComputerName>*</ComputerName> <CopyProfile>false</CopyProfile> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <DoNotCleanTaskBar>false</DoNotCleanTaskBar> <RegisteredOrganization>Some Department</RegisteredOrganization> <RegisteredOwner>MyCompany IT AB</RegisteredOwner> <ShowWindowsLive>true</ShowWindowsLive> <StartPanelOff>false</StartPanelOff> <TimeZone>W. Europe Standard Time</TimeZone> </component> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>0409:00000409</InputLocale> <SystemLocale>en-us</SystemLocale> <UserLocale>en-us</UserLocale> <UILanguage>en-us</UILanguage> </component> <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <FavoritesList> <FavoriteItem wcm:action="add"> <FavTitle>MinFavorit</FavTitle> <FavURL>http://www.min_favorit.se</FavURL> <FavID>1</FavID> </FavoriteItem> </FavoritesList> <SearchScopes> <Scope wcm:action="add"> <ScopeDisplayName>MinSearch</ScopeDisplayName> <ScopeKey>MinSearchKey1</ScopeKey> <ScopeUrl>http://www.searchochfinn.se</ScopeUrl> </Scope> </SearchScopes> <AllowedSites>http://iwww.mycompany.com</AllowedSites> <BlockPopups>yes</BlockPopups> <CompanyName>MyCompany IT AB</CompanyName> <Home_Page>http://www.myhomepage.nu</Home_Page> <IEWelcomeMsg>false</IEWelcomeMsg> </component> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Path>cmd /c net user Administrator /active:yes</Path> <Description>EnableAdmin</Description> <Order>1</Order> </RunSynchronousCommand> </RunSynchronous> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>c:\mycompany-app\mainhook.exe</CommandLine> <Description>ExecutingMainhook</Description> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> <OOBE> <SkipUserOOBE>true</SkipUserOOBE> <ProtectYourPC>1</ProtectYourPC> <NetworkLocation>Work</NetworkLocation> <HideEULAPage>true</HideEULAPage> </OOBE> <RegisteredOrganization>MyCompany IT AB</RegisteredOrganization> <RegisteredOwner>MyCompany IT AB</RegisteredOwner> <TimeZone>W. Europe Standard Time</TimeZone> <StartPanelOff>false</StartPanelOff> <ShowWindowsLive>false</ShowWindowsLive> <DoNotCleanTaskBar>false</DoNotCleanTaskBar> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <BluetoothTaskbarIconEnabled>true</BluetoothTaskbarIconEnabled> <AutoLogon> <Password> <Value>TQB5AFAANAAkACQAdwAwAHIAZAAhAFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>2</LogonCount> <Username>Administrator</Username> </AutoLogon> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <RefreshRate>60</RefreshRate> <VerticalResolution>768</VerticalResolution> </Display> </component> </settings> <settings pass="generalize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RegisteredOrganization>Some Department</RegisteredOrganization> <RegisteredOwner>MyCompany IT AB</RegisteredOwner> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> </component> </settings> <cpi:offlineImage cpi:source="catalog://bddsehbg-nt6000/distribution$/operating systems/winvista_x64_ent/sources/install_windows vista enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> Anyone know what I am missing in my sysprep.xml file? I cant seem to get around it...

I didn't..... the signature is broken, but at least it is working...

For the BDD 2007 product, there is build in support for enabling BitLocker, however, MS did not deliver one tool within the BDD concept - BdeHdCfg.exe (Disk Preparation Tool). This tool is going to be released on a site named: http://windowsultimate.com/ Seems as some cool stuff in there.... check it out!

In some cases u r able to rename the *.inf and *.sys files and change the references within them... however, the *.cat would of course be broken even if that worked. I am also using two kinds of b57x drivers, that I solved by changing the info/references between them, then adding them to the above stated paths.... Think you would be better of moving over to WinPE 2.0 (based on Vista) that makes better usage of drivers (online) and supports more models from scratch, downside is in memory boot...