[TheWalrus]

I installed a system and got to the point of creating and user and setting a name for the machine. I wanted to enter audit mode, pressed Ctrl-Shift-F3 and... nothing happened. What's wrong? Any ideas?




edit: also, the phase before user creation, I seem to be stuck with "Please wait for the Windows modules installer" message that sits there for LONG time (like 15 mins or so) before the **** screen appears (and then the key combination doesn't work). Totally not looking like working as intended :-O

This post has been edited by TheWalrus: 04 August 2011 - 01:33 PM

[TheWalrus]

Um. How could the key combination work when I wasn't actually at OOBE phase at all! But the question is why! Why would it be skipped? I didn't use any tweaks that would mess around with users.

[Tripredacus]

I don't recommend using the Ctrl+Shift+F3 to enter audit mode unless absolutely necessary. Best place to use it is at the Language selection page in OOBE.

[TheWalrus]

Why don't you recommend it? How else would I enter it?

[ricktendo64]

Let me guess...7lite processed image

[TheWalrus]

Nope not at all.

In fact it was a stupid reg tweak to disable Windows Defender.... Yeah, wtf.

What happened was that the OOBE part was actually completely skipped for some unknown reason. I waited and waited and after a LONG time I got to the standard login screen - but I noticed that much later.

[Tripredacus]

TheWalrus, on 05 August 2011 - 12:55 PM, said:

Why don't you recommend it? How else would I enter it?

I recommend using an answer file to enter Audit Mode, or to pass arguments to be done in Audit Mode.

[TheWalrus]

What are the benefits? It also looks pretty complicated. Why is adding answer file to an image and rebuilding it better than simply installing it straight away and using the key combination? Keep in mind I need to sysprep the system too...

[ricktendo64]

Its simpler, here is mine (the serial is the default one that windows uses when you skip serial)

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <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">
            <InputLocale>0409:00000409</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UserLocale>en-US</UserLocale>
            <SetupUILanguage>
                <UILanguage>en-US</UILanguage>
            </SetupUILanguage>
        </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">
            <Display>
                <ColorDepth>32</ColorDepth>
                <HorizontalResolution>1024</HorizontalResolution>
                <VerticalResolution>768</VerticalResolution>
            </Display>
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>Windows 7 ULTIMATE</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallToAvailablePartition>false</InstallToAvailablePartition>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
            <UserData>
                <AcceptEula>true</AcceptEula>
                <ProductKey>
                    <Key>D4F6K-QK3RD-TMVMJ-BBMRX-3MBMV</Key>
                    <WillShowUI>OnError</WillShowUI>
                </ProductKey>
            </UserData>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <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">
            <Reseal>
                <Mode>Audit</Mode>
            </Reseal>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim:c:/se7en/sources/install.wim#Windows 7 ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

This post has been edited by ricktendo64: 08 August 2011 - 12:52 AM

[TheWalrus]

So I would have to write another unattended file?

I am obviously missing something but I can't understand how is this simplier

[ricktendo64]

Its faster, less hassle, less reboots (BTW watch the OPK videos they talk about how to make the autounattend.xml)

This post has been edited by ricktendo64: 08 August 2011 - 07:44 AM

[TheWalrus]

How do you capture the image then, when it's a part of installation process? I just don't get it. I thought the point of audit mode is to make an image you can use for other machines, so doing a half-install which is then captured and used as a source instead of the default dvd makes much more sense.

What you describe sounds like going into audit mode automatically at some point during the installation. Okay. But then you generalize, leave audit mode... and setup continues. I am missing something.

[ricktendo64]

All the autounattend.xml does is automatically log you into audit mode when installation finishes, no reason it would cause problems capturing and of course you will not use this xml on your final image

[TheWalrus]

Okay. In that case I see absolutely no difference between the two methods