midiboy

Hi again, ok, the above works for Volume License Enterprise editions but not for Ultimate Versions. With Vista Ultimate (and I guess with other non Volume Licenses also) I always get a message asking for the product key even though I have specified it in WinPE and Specialise phases. I even added the specialise phase to the second xml but it simply won´t work What did Microsoft do with SP1 that makes it so difficult to create a properly working unattended installation !!! Alex

Hi ! Answering my own question here. It works if I do this: netsh firewall set service type = remotedesktop mode = enable scope=ALL profile=ALL When not specifying the profile=ALL command, it is not working for all profiles (work/domain). Bye, Alex

Hi Br4tt3, thanks for that info. Did this with the following script now: This does work during audit phase (I do get an OK as a reply) but after the unattended installation finished and I am back at the desktop (of the same user: administrator) the Remote Desktop firewall exception is again disabled. Any ideas ?? How can I make this setting stick ?? Thanks for any help ! Alex

Hi guys, ok, I have tested this now. Thanks, Wabaunza for the trick with the second unattend.xml. I have attached my two xmls. The first one contains every pass except OOBE. The only entry in there in that pass is the Deployment -> Reseal -> Go into Audit mode configuration. From Audit mode I am going to oobe again using the %WINDIR%\system32\sysprep\sysprep.exe /quiet /oobe /reboot /unattend:%DVDRoot%\Autounattend2.xml entry. This works fine now. OOBE uses all the settings from the second xml and setup does not stop when going to audit mode. However, I have found out that you cannot simply remove all files from the sources dir of the Vista DVD (and keep only the two wim files). If you do, somehow that influences the Vista Setup process and it won´t work reliably anymore (not use settings from xml etc.). Just one question: why do you use the /generalize setting now ? It also works without it. What do you gain by adding this ?? Don´t you have to add the key, computername etc. (which you added in previous passes) again ? Bye, Alex

Hi ! I asked this once sometime last year, trying again now: Is it possible to display the WPI installer window on the right side of the monitor instead of the left side ? I am asking because Windows Setup in audit phase or during runonceex will show that Setup Window in front blocking the WPI window. Any chance for making this somehow adjustable ? Is this possible now in any way ? Thanks for your help ! Alex I have added pictures so you better understand what I mean. How do you guys cope with that ? I agree, you may be able to live with it but it certainly does not look nicely.

Hi Wabaunza, Yeah, please let me know if you find something. I have read that there is something called the oobe.xml that is used to prestage certain oobe settings like logos etc. Maybe that will be a solution ? Have not tried it yet though (so much other stuff to do ) Bye, Alex

Hi Wabaunza, I have attached my xml. Maybe you can try this on those laptops ? This is not a very good situation. If you cannot depend on the install working on all PCs you probably can´t use it. I have not used it on real PCs as of yet, just virtual machines. Bye, Alex

Hi guys, this is really a strange error. I tried it with vmware workstation 6.02 now instead of vmware server but again, the system will shutdown after specialise phase but only with the x64 Windows Vista version. The x32 version runs fine now, no error, no shutdown. You guys are all using 32 bit versions ? Are you all using Vista + SP1 install DVDs ? Are you all using the new WAIK 1.1 for Vista SP1 and W2K8 or the previous version ? By the way: In the technical help file for the WAIK Microsoft recommends to use the following component to go into audit mode: Microsoft-Windows-Deployment\Reseal > oobeSystem ForceShutdownNow = false Mode = Audit Microsoft does not mention the sysprep /quiet /audit command as a recommended way to go into audit mode. So maybe this does not work anymore since SP1 when using that command from specialise phase ? I tried the above in my autounattend.xml instead of using sysprep /quiet /audit but this only works from oobeSystem mode, not from specialise mode. This means that Windows Setup will go from specialise mode to oobe mode and then boot into audit mode. This works fine. However, afterwards, when rebooting to oobe mode again from audit mode, Windows will stop and ask for Computername, user, etc. even though all those settings are already in the autounattend.xml. Seems like Setup only uses those setting for the first oobe pass and not for the second. Does anyone have an idea how to make Windows Setup use the settings for oobe pass in the autounattend.xml for the second oobe pass after Setup went from specialise -> oobe -> audit mode phase ? Bye, Alex

i again, unfortunately, my "solution" did not help with the 64 bit Vista Enterprise edition. Very strange. Wabaunza: I tried removing everything from the specialise phase except for the two synchronous commands but it still does not work. Would you share your autounattend.xml ? Thanks, Alex

Hi again, well, it seems like those files (at least some of them) are important to the installation (at least with Vista + SP1 installations). I have had a strange error lately: before entering audit mode vista would cause a interactive logon error and stop the installation. See this thread: Thread Not having found a solution for days I tried copying the files inside the sources dir back and glady found out that the error was gone. I have no idea which files are that important to the Vista setup process but simply clearing the sources dir seems to be a very bad idea now, at least with integrated SP1 installations (I did not integrate it manually but got the install DVD directly from MS). Bye, Alex

Hi again, I think I found the solution !! @alucke: Did you by any chance clear the sources dir of the Vista DVD and only leave the wim files in there ? In my case I searched days for a solution and tried everything. In the end, the solution was to copy all the files that were in the sources dir of the Vista DVD initially back to the sources dir of my unattended Vista DVD. For some strange reason if only the wim files and the cfg files are in there, the vista installation will cause this error. At least this helped with my x32 unattended DVD, I will check if it works on my x64 installation too. Bye, Alex

Hi ! I am stuck with the same error on a Vista with Integrated SP1 x64 Enterprise version right before the virtual machine should restart into audit mode. Instead it quickly shows the error and then shuts the machine off. Any ideas ?? Cannot find any solution on the net anywhere. edit: Setuperr.log and setupact.log do not seem to show any errors. Any ideas guys ?? Thanks, Alex Here´s my autounattend.xml: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="oobeSystem"> <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>0000043a</InputLocale> <SystemLocale>de-AT</SystemLocale> <UILanguage>de-DE</UILanguage> <UserLocale>de-AT</UserLocale> </component> <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>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>1</LogonCount> <Username>Administrator</Username> </AutoLogon> <Display> <ColorDepth>32</ColorDepth> <DPI>96</DPI> <HorizontalResolution>1024</HorizontalResolution> <RefreshRate>60</RefreshRate> <VerticalResolution>768</VerticalResolution> </Display> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>1</ProtectYourPC> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>QAB1ADUAZwBlADUAcABlAHIAcgB0AFAAYQBzAHMAdwBvAHIAZAA=</Value> <PlainText>false</PlainText> </Password> <Description>Administrator</Description> <DisplayName>Administrator</DisplayName> <Group>Administrators</Group> <Name>Administrator</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <TimeZone>W. Europe Standard Time</TimeZone> <RegisteredOrganization>xxxxxxxxxxxx</RegisteredOrganization> <RegisteredOwner>xxxxxxxxxxx</RegisteredOwner> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> <ShowWindowsLive>false</ShowWindowsLive> <StartPanelOff>false</StartPanelOff> <LogonCommands> <AsynchronousCommand wcm:action="add"> <CommandLine>cmd /c "cmdow @ /HID & %DVDRoot%\sources\$OEM$\cleanup.cmd"</CommandLine> <Description>System bereinigen</Description> <Order>1</Order> </AsynchronousCommand> </LogonCommands> </component> <component name="Microsoft-Windows-Sidebar" 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"> <Gadget4>%PROGRAMFILES%\windows sidebar\gadgets\Notes.Gadget,true</Gadget4> <Gadget5>%PROGRAMFILES%\windows sidebar\gadgets\Weather.Gadget,true</Gadget5> </component> </settings> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" 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"> <SetupUILanguage> <UILanguage>de-DE</UILanguage> </SetupUILanguage> <InputLocale>0000043a</InputLocale> <SystemLocale>de-AT</SystemLocale> <UILanguage>de-DE</UILanguage> <UserLocale>de-AT</UserLocale> </component> <component name="Microsoft-Windows-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"> <DiskConfiguration> <WillShowUI>Always</WillShowUI> </DiskConfiguration> <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows Vista ENTERPRISE</Value> </MetaData> </InstallFrom> <InstallToAvailablePartition>true</InstallToAvailablePartition> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> <UserData> <AcceptEula>true</AcceptEula> </UserData> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Security-Licensing-SLC-UX" 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"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-UnattendedJoin" 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"> <Identification> <JoinWorkgroup>ARBEITSGRUPPE</JoinWorkgroup> </Identification> </component> <component name="Security-Malware-Windows-Defender" 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"> <DisableAntiSpyware>true</DisableAntiSpyware> </component> <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"> <ComputerName>%COMPUTERNAME%</ComputerName> <ProductKey>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</ProductKey> <TimeZone>W.Europe Standard Time</TimeZone> <RegisteredOrganization>xxxxxxxx</RegisteredOrganization> <RegisteredOwner>xxxxxxxxx</RegisteredOwner> </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"> <Order>1</Order> <Path>cmd /c "cmdow @ /HID & FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\DVDRoot.txt SETX DVDRoot %i: -m"</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>2</Order> <Path>%WINDIR%\system32\sysprep\sysprep.exe /quiet /audit</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings> <settings pass="auditUser"> <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"> <Order>1</Order> <Path>cmd /c "%DVDRoot%\sources\$OEM$\checkserver.exe"</Path> <Description>WPI Installation</Description> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>10</Order> <Path>%WINDIR%\system32\sysprep\sysprep.exe /quiet /oobe /reboot</Path> <Description>PC neustarten ...</Description> </RunSynchronousCommand> </RunSynchronous> </component> <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"> <Display> <ColorDepth>32</ColorDepth> <DPI>96</DPI> <HorizontalResolution>1024</HorizontalResolution> <RefreshRate>60</RefreshRate> <VerticalResolution>768</VerticalResolution> </Display> </component> </settings> <settings pass="auditSystem"> <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"> <Display> <ColorDepth>32</ColorDepth> <DPI>96</DPI> <HorizontalResolution>1024</HorizontalResolution> <RefreshRate>60</RefreshRate> <VerticalResolution>768</VerticalResolution> </Display> </component> </settings> <cpi:offlineImage cpi:source="wim://mediaserver/media/installation/Test_base/Test5/Test5_source/base_source/x64/sources/install.wim#Windows Vista ENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>

Well, i have done some tests with this folder. It does work but there are exceptions. First, if the Intel chipset inf files are in there (tried at least a few 8.x versions) Windows PE will stop the setup with a driver installation error. So you cannot add those drivers. Second: if the Intel Matrix Storage driver is added to that folder (isastor.sys), Windows will use that driver even inside a vmware virtual machine and after reboot you will receive an error message saying that the driver (iastore.sys) cannot be loaded. The vmware network drivers are picked up fine, I can´t say much more because I am still testing inside a virtual machine.

Hi MC, actually, some of those files are not that unimportant ! I removed every file in the sources dir except for the two wim files and suddenly Windows Vista Enterprise SP1 (VOL) always required a product key during WinPE phase even though I had specified the correct key in the autounattend.xml. After hours of going through the logs and searching the net, I found the answer in the Microsoft Volume Activation Guide. It says there that Volume License media (enterprise editions) use the temporary PID from the PID.txt file in the sources dir of the root of the DVD during WinPE phase. Only later, in specialise phase, the final PID of the organisation is being used. So if you delete the PID.txt in the sources dir, this won´t work and unattended installation is always interrupted. Worse, the proper key is sometimes not working during WinPE phase: (have a look at this page) So at least the pid.txt file in the sources dir should not be deleted. I hope there´s not more ... Bye, Alex

Hi MC, thanks ! Thats cool ! :-)

Hi guys, has anyone already tried the $WinPeDriver$ folder in Vista SP1 ? From reading the setupact.log file WinPE checks the contents in a folder named $WinPeDriver$ on any accessible drive. I haven´t had a chance to test this on a real machine, just vmware so I can´t say if it really works or not. Has anyone tried it yet ? Alex

Hi guys, I am trying to save space on the unattended DVD and was wondering if all the files in the source directory except for the two wim files are actually needed for a successful unattended installation ? Can I simply delete them and only use the wim files and the boot and efi folders in the root of the Vista DVD ? What do you guys think ? Bye, Alex

Hi Guys, wow, so many replies ! :-) Thanks all for chiming in. I have selected the simplest approach just as Greenmachine, Mhz and Pyrosoft suggested. Thanks all for your help and support ! Alex

Hi Pyrosoft, yeah, thanks. I did this now and it seems to work. Just does not seem very elegant but it is working so thanks ! :-) Have a nice day ! Alex

Hi guys, I do have a special situation here. I would like to check in a cmd if a file was deleted or not (because it was locked by another process for instance). I tried this: if exist D:\Isos\Test.iso DEL D:\Isos\Test.iso If not %Errorlevel% == 0 then ..... However, the errorcode is always 0 no matter if the file was successfully deleted or not. If it was deleted there is no response in the cmd, if the file is locked then the cmd gives a response like "file could not be deleted because it is used by another process". However, this is different in various language versions and this should work on any WinXP/Server/Vista version. Any ideas ??? Hope so ... Thanks a lot for your help ! Alex

Hi again, mhh, does not work with the autoit script either. Now I get an error message right after the Office installation (the office installer still shows the Updating ... screen) saying that an error occured in the script on line 1. Wrong symbol/sign or something (it was shown in german). The scrpit looks like this: ; ----> The Office and reboot.js file error definitive fix! AutoItSetOption("TrayIconHide", 1) AutoItSetOption("WinTitleMatchMode", 4) BlockInput(0) ; ----> Add the name of your .msp file here. (I have mine in the same directory as the setup.exe file) RunWait( @ScriptDir & "\setup.exe", "", @SW_HIDE) ; ----> If you have a SLOW pc and are still getting the error make this number higher (I suggest by 5000 increments) Sleep(12000) RunWait( @ScriptDir & "\officemath.msi /passive /norestart", "", @SW_HIDE) RunWait( @ScriptDir & "\SaveAsPDF.exe /q", "", @SW_HIDE) Exit After I click on either yes or no for entering the debug mode, WPI ends ... Bye, Alex

thats not slipstreaming I have no idea why Microsoft does not support slipstreaming anymore. But maybe there is a way still ? Bye, Alex

Hi guys, there is a new WAIK for Server 2008 / Vista RC1 available on MSDN in case you haven´t realized. However, I think it is available only to MSDN members. It does have an improved oscdimg.exe, one can now create UDF DVDs with that tool. Works great, just tried it. Bye, Alex

Hi again, just found out that the same firewall setting seems to create slightly different registry entries each time. So on another installation the entries in the registry are like this: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Epoch] "Epoch"=dword:00000017 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules] "RemoteDesktop-In-TCP"="v2.0|Action=Allow|Active=FALSE|Dir=In|Protocol=6|Profile=Domain|LPort=3389|App=System|Name=Remot edesktop (TCP eingehend)|Desc=@FirewallAPI.dll,-28756|EmbedCtxt=@FirewallAPI.dll,-28752|Edge=FALSE|" "{7464F2B7-09EC-4DFC-B3F9-F669C74F2C15}"="v2.0|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|LPort=3389|App=System|Name=Remot edesktop (TCP eingehend)|Desc=@FirewallAPI.dll,-28756|EmbedCtxt=@FirewallAPI.dll,-28752|Edge=FALSE|" How do I create a simple firewall rule unattended ? Obviously it does not work like this. Is there a commandline tool or something ?? Thanks for your help ! Alex

Hi ! I understand. Ok, will try this soon :-) edit: No, did not work. So the sleeping alone cannot be the solution. My code is like this: start /wait .\setup.exe ping -n 120 127.0.0.1>nul start /wait .\SaveAsPDF.exe /q if exist .\officemath.msi start /wait .\officemath.msi /passive /norestart I did the same thing for Visio, which installs right after Office. Also, SP1 is in the Updates folder. And thats the reason why I don´t think this will work at all. The problem seems to happen either during the update installation or after the Office and during the Visio installation. So the sleep command (or in my case the ping localhost command comes to late because the problem happens while the script waits for the Office or Visio installation to finish, not after the installation finished. I will now try with the autoit script, however, I doubt that it will behave different from a cmd, unless the solution is using Autoit instead of anything else .... ? Alex