MSFN Forums > Not booting Audit mode during Vista Setup

alucke

Feb 13 2008, 04:57 PM

i created an unattend.xml file with WAIK. When i run Vista Setup, I get an Interactive Logon error when entering Audit Mode. I followed FireGeier's unattended guide. Can't figure out why its not working. I attached my autounattend file. Hopefully i can get some insight to why Vista is giving me error when booting to Audit mode, during Vista Setup.

midiboy

Feb 23 2008, 09:20 AM

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:

CODE

<?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>

midiboy

Feb 25 2008, 03:15 AM

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

Wabaunza

Feb 25 2008, 09:05 AM

I have the same problem with Vista Enterprise with SP1 slipstreamed from Microsoft:
If you use the OEM disk files WIM unmodified and use your current XML then it works.
If you use the OEM files then modify the install.wim and in the specialize area of the xml it only works with the two runsynchornous commands only in there. I found anything else in specialize phase will hang the install throwing out the error message and shutting the machine down. Think I am going to burn the OEM Vista Enteprise Disk Tomorrow and see if it shutsdown during the sysprep screen where the I used to get the interactive logon error.

midiboy

Feb 25 2008, 01:25 PM

i again,

QUOTE

I will check if it works on my x64 installation too.

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

Wabaunza

Feb 25 2008, 04:50 PM

I started from scratch this morning right after my previous post. Extracted the Vista Enterprise SP1 ISO to my iso folder, copied my install folder, appsroot file and my autounattend.xml from my previous (Pre-SP1 working Enterprise build) to this iso folder. I executed WSIM selected my autounattend.xml, selected the install.wim from sources and saved it. then ran my script to make an iso and loaded up a new vm with this. The interesting this is it still shutsdown where it has always crashed, but I launched it again and it then goes through the rest of the passes from the autounattend.xml. This is a Microsoft Virtual PC bug I am guessing because I have made three new builds modifying the install.wim and it continues to shutdown but when restarted continues as it should. Guess autoreboot does not always work (Microsoft Product) I attached my XML hope this helps.

Wabaunza

Feb 25 2008, 10:13 PM

I created a DVD and the shutdowns are not just in the VM's its also from the disk. Anyone experiencing this? I start the machine back up and it continues from the DVD and evenutally completes and everything works. Maybe the SP1 install requires a shutdown?

alucke

Feb 26 2008, 01:14 AM

I tried it with VM and computer. Either way, I get it to shutdown. Then i restart setup, it says a critical error has occured and is unabled to continue.

midiboy

Feb 26 2008, 04:40 AM

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:

CODE

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

alucke

Feb 26 2008, 06:02 AM

I am using Vista + SP1 DVD and WAIK 1.1

Wabaunza

Feb 26 2008, 09:16 AM

QUOTE (midiboy @ Feb 26 2008, 06:40 AM)

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:

CODE

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

Midiboy, Yes I am using 32bit version with sp1 integrated from Microsoft and WAIK 1.1 2008 version. In specialize phase Windows-Deployment one of my RunSyncronous Commands has %WINDIR%\system32\sysprep\sysprep.exe /quiet /audit - I noticed I had the WillReboot Option set to never in WSIM. Hmnnn Changing this to Always to see what happens. I'll let you guys know my results.

Wabaunza

Feb 26 2008, 10:21 AM

Midiboy can you post your working xml for 32bit version. I am getting the Interactive logon error on fujitsu and panasonic model laptops not on Dells. I have not made the changes to the build yet that i was going to test.

midiboy

Feb 26 2008, 11:02 AM

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

Wabaunza

Feb 26 2008, 02:30 PM

Midiboy I removed the sysprep /quiet /audit command and added the deployment\reseal oobe option forceshutdown mode - audit and it installed fine on my Fujistu going to try on other models. I as well got the OS version, license terms agreement, username prompts as well so I will be seeing if I can figure that out. Least the OS installs so far.

midiboy

Feb 26 2008, 02:47 PM

Hi Wabaunza,

QUOTE

I as well got the OS version, license terms agreement, username prompts as well so I will be seeing if I can figure that out. Least the OS installs so far.

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

Wabaunza

Feb 27 2008, 08:51 AM

Midiboy still no luck, I looked into the OOBE.xml this is really for branding and customization for if you want the windows visible. I created a new Unattend.xml which I am pointing to in the last audituser pass runsynchronous pass with %WINDIR%\system32\sysprep\sysprep.exe /generalize /quiet /oobe /reboot /unattend:%AppsRoot%Install\Unattend.xml. Trying to tweak this to work and have it read at the end. See if you can do anything with this as well.

Wabaunza

Feb 28 2008, 12:04 PM

Midiboy I got the OOBE prompts to go away so far using %WINDIR%\system32\sysprep\sysprep.exe /generalize /quiet /oobe /reboot /unattend:C:\Temp\Unattend.xml and adding the unattend.xml to C:\Temp when mounting the install.wim For some reason from the CDROM it didn't like it but it works on my Fujitsu and some Panasonics.

alucke

Feb 28 2008, 12:27 PM

I will have to try that.

Wabaunza

Feb 28 2008, 02:58 PM

All I am getting inconsistent results now, it works on previously not working Fujistus but Dells and some Panasonics that were working now do not work lol. This is crazy.

alucke

Feb 29 2008, 07:11 AM

I created unattend.xml and put it in the root of the DVD. I used this setting %WINDIR%\system32\sysprep\sysprep.exe /generalize /quiet /oobe /reboot /unattend:%DVDRoot%\Unattend.xml in the last audit user pass runsyncronuous command of the Autounattend.xml. I ran Vm 2 times to test the above settings and they work perfectly for me. I uploaded a copy of my basic unattend file below. Thanks to Wabaunza for pointing the the settings in a previous post.

Wabaunza

Feb 29 2008, 10:06 AM

QUOTE (alucke @ Feb 29 2008, 09:11 AM)

I created unattend.xml and put it in the root of the DVD. I used this setting %WINDIR%\system32\sysprep\sysprep.exe /generalize /quiet /oobe /reboot /unattend:%DVDRoot%\Unattend.xml in the last audit user pass runsyncronuous command of the Autounattend.xml. I ran Vm 2 times to test the above settings and they work perfectly for me. I uploaded a copy of my basic unattend file below. Thanks to Wabaunza for pointing the the settings in a previous post.

Alucke,

Glad to help but the real test is on a physical machine. Can you give this a shot and see if it still works. Thanks

alucke

Feb 29 2008, 05:49 PM

I will give it a shot tomorrow., and i will post the results.

alucke

Mar 1 2008, 11:42 AM

I installed Vista SP1 unattended using the generalized setting as previously posted. For me, it ran without any problems. I am posting this reply while using Vista SP1.

midiboy

Mar 1 2008, 04:49 PM

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

CODE

%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

midiboy

Mar 2 2008, 12:47 PM

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

Wabaunza

Mar 2 2008, 09:13 PM

Midiboy, I feel your pain. I have escalated this to Microsoft since we have some reps where I work and they hopefully have been looking at it this weekend and can have an answer as to why the SP1 slipstreamed build is so jacked up and a solution. As a backup plan, I am going to use my 100% functional Pre SP1 build with my XML that has been working on all vendors hardware for months now. I am going to install SP1 standalone silently after OOBE at login screen, adding a runonce reg key to install using setupcomplete.cmd to execute and using one more autologon launching a VB window up about the install and forcing a restart after the first part of the install. lol this sounds like the best way to go, it's only 444MB so not to bad. I'll let you guys know if these Micorosft guys come up with anything. Does anyone know if it is suggested to install after OOBE or is it better during audituser phase or another phase?

midiboy

Mar 4 2008, 01:02 AM

Hi Wabaunza,

any news on this from MS ?

I did some more tests. It works in Windows Vista Ultimate if I use the /generalize switch after audit mode as you suggested. However, I cannot use that because I am running a script in Windows PE (before setup starts) that will ask for the Computer name and then adds that value to the unattend.xml in the C:\Windows\panther directory (thats where Setup copies the autounattend.xml) where I have a variable %COMPUTERNAME%.
I read about this trick in a Microsoft forum somewhere (cannot find it anymore).

Now, if I use the /generalize switch, that name will be reset again and Setup will stop again during OOBE pass to ask for the key. Unless there is a way to somehow transfer the computername from the first passes to OOBE pass during generalisation I cannot use /generalize.

Anyway, thanks for your help,
Alex

SKiNNiEH

Mar 6 2008, 06:38 AM

Removed my entry, i have the same problems no matter what bios setting i make

Wabaunza

Mar 7 2008, 02:13 PM

I still have not heard anything from the Vista deployment team. I am guessing they have not come up with a solution yet?

exhaler

Apr 23 2008, 08:26 AM

thanks you very much for the sysprep solution, finally i can install software during audit. but i still have one more thing to fix.
Before logon the "enter key" message shows up, i tried putting in the second xml file but no luck. I don't want to skipuserOOBE since i want the user to put in his username, password, and computer name

here my xml files:

Pasha

May 3 2008, 03:25 PM

Two Unattended files work just fine, thanks everybody for an idea. Now the question what Microsoft thinks? What's there guidline on the question?

SonyXP

Jun 16 2008, 04:40 PM

Hello everyone

I am new "creating" an unattended setup XML file. As you, I came accross the problems discussed in here.
Could one of you elaborate this technique behind "using 2 unattend.xml files" ? Which passes have to be
entered into each of them / how to seperate / split up "the one" file I have now?

Every reply is much appreciated

hannubys

Jun 16 2008, 05:03 PM

i had a look on technet, i'll try to do it using the distribution method $oem$ for application

SonyXP

Jun 16 2008, 05:23 PM

That's exactly what I am looking for atm

I tried the $oem$ method on WinXP (RunOnceEx), worked flawlessly.
However, in Vista, I could not get it to work.

Do you (or anyone else) have a sample Autounattend.xml showing how to deal that (how to install let's say "firefox" during Vista Setup ?) with Vista SP1 ?
It worked for me using the normal Vista RTM, but as y'all found out, with SP1 there's some probs.

Update:
I finally got it to work. Thanks to hannubys and exhaler

http://www.msfn.org/board/Install-applicat...tml#entry773690

NobleSir

Jul 30 2008, 09:28 PM

Another solution:

Settings to Use for Automating Windows Welcome

In order to not see the all that stuff after the final reboot make sure you have the following in your XML file. This webpage has all the information needed.

Yes this page has more than what the dude's guide has.

maxXPsoft

Nov 13 2008, 10:56 AM

Finally I am using the 2 xml method with ver 5.0 or later and I am installing all the software I want in Audituser pass, thanks to all gave me the guidelines where I could interpret this to my own things and my app and do this.
Best Vista install I ever had with SP1, Dreamscene on final desktop and all
My Adventures: http://veegertx.com/forums/index.php?showt...&#entry3563