Solved

Vista keeps auto login in after sysprep is run

Posted on 2007-12-06
3
1,843 Views
Last Modified: 2012-06-21
I am using sysprep for vista and I created a answer file using the step by step guide at http://technet2.microsoft.com/WindowsVista/en/library/12265a2d-e0e6-4ca6-aa02-df4f68a5a8a81033.mspx?mfr=true.  After I run the command sysprep /oobe /generalize /shutdown /unattend:sysprep.xml the system shuts down.  I then boot it up again and the OOBE runs and then reboots.  This time when it comes up it is in audit mode and every time I reboot it after that.  I have narrowed it down to the answer file section for Microsoft-Windows-Deployment and the Reseal mode of Audit.  If I change this to OOBE then I get the Welcome Wizard upon boot up.  What I want is for the system to come up in normal mode and let the user login for the first time.  I am sure my answer file has missing or wrong component that is causing Windows to login in audit mode. I have included my answer file, can someone point out my error?
<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

    <settings pass="windowsPE">

        <component name="Microsoft-Windows-Setup" processorArchitecture="x86" 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>

                <Disk wcm:action="add">

                    <CreatePartitions>

                        <CreatePartition wcm:action="add">

                            <Order>1</Order>

                            <Type>Primary</Type>

                            <Size>16000</Size>

                        </CreatePartition>

                    </CreatePartitions>

                    <ModifyPartitions>

                        <ModifyPartition wcm:action="add">

                            <Active>true</Active>

                            <Extend>false</Extend>

                            <Format>NTFS</Format>

                            <Label>OS_Install</Label>

                            <Letter>C</Letter>

                            <Order>1</Order>

                            <PartitionID>1</PartitionID>

                        </ModifyPartition>

                    </ModifyPartitions>

                    <DiskID>0</DiskID>

                    <WillWipeDisk>true</WillWipeDisk>

                </Disk>

                <WillShowUI>OnError</WillShowUI>

            </DiskConfiguration>

            <ImageInstall>

                <OSImage>

                    <InstallTo>

                        <DiskID>0</DiskID>

                        <PartitionID>1</PartitionID>

                    </InstallTo>

                    <WillShowUI>OnError</WillShowUI>

                </OSImage>

            </ImageInstall>

            <UserData>

                <AcceptEula>true</AcceptEula>

            </UserData>

        </component>

        <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" 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>en-us</UILanguage>

            </SetupUILanguage>

            <InputLocale>en-us</InputLocale>

            <SystemLocale>en-us</SystemLocale>

            <UILanguage>en-us</UILanguage>

            <UserLocale>en-us</UserLocale>

        </component>

    </settings>

    <settings pass="specialize">

        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" 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>Vista</ComputerName>

            <RegisteredOrganization>None</RegisteredOrganization>

            <RegisteredOwner>Nobody</RegisteredOwner>

            <TimeZone>Pacific Standard Time</TimeZone>

            <AutoLogon>

                <Enabled>false</Enabled>

            </AutoLogon>

        </component>

        <component name="Microsoft-Windows-TCPIP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

            <Interfaces>

                <Interface wcm:action="add">

                    <Ipv4Settings>

                        <DhcpEnabled>false</DhcpEnabled>

                    </Ipv4Settings>

                    <Identifier>Local Area Connection</Identifier>

                    <Routes>

                        <Route wcm:action="add">

                            <Identifier>0</Identifier>

                            <NextHopAddress>192.168.100.1</NextHopAddress>

                            <Prefix>0.0.0.0/0</Prefix>

                        </Route>

                    </Routes>

                    <UnicastIpAddresses>

                        <IpAddress wcm:action="add" wcm:keyValue="0">192.168.100.10/24</IpAddress>

                    </UnicastIpAddresses>

                </Interface>

            </Interfaces>

        </component>

        <component name="Microsoft-Windows-DNS-Client" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

            <Interfaces>

                <Interface wcm:action="add">

                    <DNSServerSearchOrder>

                        <IpAddress wcm:action="add" wcm:keyValue="0">192.168.100.2</IpAddress>

                        <IpAddress wcm:action="add" wcm:keyValue="1">192.168.100.4</IpAddress>

                    </DNSServerSearchOrder>

                    <Identifier>Local Area Connection</Identifier>

                </Interface>

            </Interfaces>

        </component>

    </settings>

    <settings pass="oobeSystem">

        <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" 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>

                <ForceShutdownNow>false</ForceShutdownNow>

            </Reseal>

        </component>

        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

            <OOBE>

                <ProtectYourPC>1</ProtectYourPC>

                <NetworkLocation>Work</NetworkLocation>

            </OOBE>

        </component>

    </settings>

    <cpi:offlineImage cpi:source="wim:c:/temp/vista/install.wim#Windows Vista ENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

Open in new window

0
Comment
Question by:randeffects
3 Comments
 

Author Comment

by:randeffects
ID: 20429124
I solved this on my own.  I removed the Microsoft-Windows-Deployment component and added the component Microsoft-Windows-Shell-Setup under oobeSystem using the following elements:
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>

Since I have already set all the entries OOBE in the answer file I believe that it is ok to skip the OOBE process.
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 20591255
PAQed with points refunded (250)

Computer101
EE Admin
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Hi All Just a quick one for everybody. I was recently looking into setting the default User Account Picture for all my vista clients within the network but on closer inspection the group policy setting only allows you to set the default pictur…
I'm a big fan of Windows' offline folder caching and have used it on my laptops for over a decade.  One thing I don't like about it, however, is how difficult Microsoft has made it for the cache to be moved out of the Windows folder.  Here's how to …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now