[Help] Unattended Seven and WPI

[ricktendo]

If you run regshot or installwatch before and after you install VirtualBox and choose to always trust the unsigned driver you will get the reg entry that you can apply before you run the installer next time so you dont get that popup

[easly89]

If you run regshot or installwatch before and after you install VirtualBox and choose to always trust the unsigned driver you will get the reg entry that you can apply before you run the installer next time so you dont get that popup

thats what i've doen and now its all good

the only thing to take care of is the request of reboot

Thanks for your answer,

Carlo

[myselfidem]

Check if you have selected this option with WPI

[easly89]

Check if you have selected this option with WPI

the request of reboot comes from win7, because it just pops out before WPI starts.. anyway in the wpi option this one is disabled (not checked!)

[myselfidem]

Could you send as attachment your "Autounattend.xml" - and delete your personnal key inside before?

[easly89]

here it is Autounattended.xml

and in the code:

<?xml version="1.0" encoding="utf-8"?>
<!--This answer file generated by RT Seven Lite-->
<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">
      <SetupUILanguage>
        <UILanguage>it-IT</UILanguage>
      </SetupUILanguage>
      <InputLocale>0410:00000410</InputLocale>
      <UserLocale>it-IT</UserLocale>
      <UILanguage>it-IT</UILanguage>
      <SystemLocale>it-IT</SystemLocale>
    </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">
      <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>
        <ProductKey>
          <Key>xxxxxxxx</Key>
          <WillShowUI>OnError</WillShowUI>
        </ProductKey>
        <Organization>Easly s.p.a.</Organization>
        <FullName>Carlo Ruggiero</FullName>
        <AcceptEula>true</AcceptEula>
      </UserData>
    </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">
      <UserAccounts>
        <LocalAccounts />
      </UserAccounts>
      <OOBE>
        <NetworkLocation>Home</NetworkLocation>
        <HideEULAPage>true</HideEULAPage>
        <HideWirelessSetupInOOBE>false</HideWirelessSetupInOOBE>
        <SkipMachineOOBE>false</SkipMachineOOBE>
        <SkipUserOOBE>false</SkipUserOOBE>
      </OOBE>
      <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
      <TimeZone>W. Europe Standard Time</TimeZone>
      <StartPanelOff>true</StartPanelOff>
      <Display>
        <ColorDepth>32</ColorDepth>
        <RefreshRate>60</RefreshRate>
      </Display>
      <Themes>
        <WindowColor>Sky</WindowColor>
      </Themes>
      <FirstLogonCommands>
        <SynchronousCommand wcm:action="add">
          <CommandLine>cmd /C start /wait %systemdrive%\APPSX64\FirstLog.cmd</CommandLine>
          <Description>FirstLogonScript</Description>
          <Order>1</Order>
        </SynchronousCommand>                        
      </FirstLogonCommands>   
    </component>
  </settings>
  <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">
      <ComputerName>Admin-PC</ComputerName>
      <Themes>
        <WindowColor>Sky</WindowColor>
      </Themes>
    </component>
    <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>
  </settings>
</unattend>

[myselfidem]

Thanks!

I think you can delete inside "Autounattend.xml":

<SkipMachineOOBE>false</SkipMachineOOBE>

It's deprecated and a window ask to choose the type of Network location!

Maybe reboot appends with your "Firstlog.cmd"!

Edited November 19, 2010 by myselfidem

[easly89]

i'll try

i didn't got the thing of the "append".. what do you mean?

[myselfidem]

I mean that I must modded my "Autonattend.xml" file made with RT Se7en Lite if I want an fully unattended installation for my Windows 7 Ultimate x86.

I've made these changes and I keep these lines inside OOBE section:

<OOBE>

<HideEULAPage>true</HideEULAPage>

<NetworkLocation>Home</NetworkLocation>

<ProtectYourPC>1</ProtectYourPC>

</OOBE>

If not appends to you, nice!

*Edit:

You don't have create an local account! Maybe you don't want create an user account?

Edited November 19, 2010 by myselfidem

[easly89]

this autounattended was created by RT7 so i don't know

i want to create a local account but i want to choose the name (this part is not automated i know )

anyway i've just removed the line in the autounattended but i'm issuing some BSOD in the vitualPC (weird.. never got them)

so i''ve added it again and making a new iso, i'll try that and check if they are gone

oh and i've added a reboot request in the runonceex so that before the desktop first load there is the reboot so ther will not be another request on first login.. hope to be right

i'll let u know asap

thx in advance for the answers

Carlo

Edited November 19, 2010 by easly89

[myselfidem]

this autounattended was created by RT7 so i don't know

i want to create a local account but i want to choose the name (this part is not automated i know )

You can choose the option: click on "Add more users" with RT Se7en Lte 1.6.0 and you can create one or more user accounts!

[easly89]

Resolved

The reboot after RunOnceEx works, so no more reboot, and no more BSODs

so everything goes in th e right way now just some more things i can't get rid of

- When the script of FirstLog.cmd is launched other then the WPI also a Command Windows will appear and the Win7 installation will not go on if i don't close Manually the window.. how can i get rid of this?

- Daemon Tools asks to install the gadget, how can i avoid that screen? (there is an Open file security warning exactly)

- VrtualBox still asks if I want to install USB Drivers (coz of the Signin Policy i suppose) how can i get rid of it?

- Windows live essentials installs but only manually, what are the silent switches for this prog? (i have downloaded the standalone installer)

thanks in advance for the answers,

Carlo

[myselfidem]

Have you write: Exit

at the end of your FirstLog.cmd?

Edited November 19, 2010 by myselfidem

[easly89]

Have you write: Exit

at the end of your FirstLog.cmd?

yes, the cmd itself is good (if i start it now it do what it has to do and when finishes it closes)

maybe there is something wrong in the way i call to it in the autounattended.xml?

[myselfidem]

You want start FirstLog.cmd before WPI.exe (with SetupComplete.cmd) or after?

Unattended Windows Setup Reference for Windows 7.chm

SynchronousCommand

SynchronousCommand specifies a command to run the first time a user logs on to the computer, its description, and the order in which it is run. FirstLogonCommands are run after logon but before the user sees the desktop.

If you create a user account that does not include administrative privileges, the following commands may not be executed:

If User Account Control is enabled, then when that user logs in for the first time, a dialog box appears, prompting the user with an option to allow an administrator to apply the commands. If the user selects Cancel, these commands are not executed.

If User Account Control is disabled, these commands are not executed.

Edited November 19, 2010 by myselfidem