Need help with win7 TimeZone and activation

[grabby]

For the life of me I can't get the time zone to work or figure out how to make it activate on first start up. I've tried a bunch of different stuff for both but I can't seem to get it to work.

<?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="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>0409:00000409</InputLocale>
      <UserLocale>en-US</UserLocale>
      <UILanguage>en-US</UILanguage>
      <SystemLocale>en-US</SystemLocale>
    </component>
    <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">
      <UserData>
        <Organization>School Info</Organization>
        <AcceptEula>true</AcceptEula>
      </UserData>
      <ImageInstall>
        <OSImage>
          <InstallFrom>
            <MetaData wcm:action="add">
              <Key>/IMAGE/NAME</Key>
              <Value>Windows 7 PROFESSIONAL</Value>
            </MetaData>
          </InstallFrom>
          <InstallToAvailablePartition>false</InstallToAvailablePartition>
          <WillShowUI>OnError</WillShowUI>
        </OSImage>
      </ImageInstall>
    </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">
        <ProductKey>key</ProductKey>
        <TimeZone>Eastern Time</TimeZone>
    </component>
  </settings>
  <settings pass="oobeSystem">
    <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">
      <AutoLogon>
        <Password>
          <Value>password</Value>
        </Password>
        <Enabled>true</Enabled>
        <LogonCount>1</LogonCount>
        <Username>Administrator</Username>
      </AutoLogon>
      <OOBE>
        <HideEULAPage>true</HideEULAPage>
        <NetworkLocation>Work</NetworkLocation>
        <SkipMachineOOBE>true</SkipMachineOOBE>
        <SkipUserOOBE>false</SkipUserOOBE>
      </OOBE>
      <UserAccounts>
        <AdministratorPassword>
          <Value>password</Value>
        </AdministratorPassword>
      </UserAccounts>
      <FirstLogonCommands>
           <SynchronousCommand wcm:action="add">
              <CommandLine>cmd /q /c for %i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %i:valueadd\wpi\wpi.exe start %i:valueadd\wpi\wpi.exe</CommandLine>
              <Description>Windows Post Install Wizard</Description>
              <Order>1</Order>
              <RequiresUserInput>false</RequiresUserInput>
           </SynchronousCommand>
           <SynchronousCommand wcm:action="add">
              <CommandLine>slmgr /ato</CommandLine>
              <Description>activate windows</Description>
              <Order>2</Order>
           </SynchronousCommand>
      </FirstLogonCommands>
    </component>
  </settings>
  <cpi:offlineImage cpi:source="wim:C:/Users/wmayes/Documents/work/iso/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

If anyone could help me out with some tips or ideas it would be much appreciated.

Edited April 12, 2010 by grabby

[johnhc]

grabby, according to unattend.chm, the Eastern time zone is "Eastern Standard Time", without the quotes and is defined as (GMT-05:00) Eastern Time (US and Canada). Sorry, can't help with the activation question. Enjoy, John.

[grabby]

grabby, according to unattend.chm, the Eastern time zone is "Eastern Standard Time", without the quotes and is defined as (GMT-05:00) Eastern Time (US and Canada). Sorry, can't help with the activation question. Enjoy, John.

I've tried it both ways, but i'll give it another shot.

[johnhc]

grabby, I get lots of hits here on slmgr, including this:

cscript %systemroot%\System32\slmgr.vbs -ato

So, perhaps you need the cscript part. I also find "SkipAutoActivation" in the unattend.chm. Perhaps that means you don't need to activate, but do need to skip it if you don't want it done automatically. The several threads I found via search of slmgr indicates that some are using it to activate. Therefore, I am confused on this issue. Enjoy, John.

[grabby]

grabby, I get lots of hits here on slmgr, including this:

cscript %systemroot%\System32\slmgr.vbs -ato

So, perhaps you need the cscript part. I also find "SkipAutoActivation" in the unattend.chm. Perhaps that means you don't need to activate, but do need to skip it if you don't want it done automatically. The several threads I found via search of slmgr indicates that some are using it to activate. Therefore, I am confused on this issue. Enjoy, John.

that worked like a charm for activation, after tho it started giving me problems with wpi in the vm, testing it now on a real pc tho. thanks a ton

[johnhc]

grabby, I have used WPI on XP and it runs fine in VMware Server VM. I assume you have used the W7 $OEM$ code found here. Enjoy, John.

[grabby]

grabby, I have used WPI on XP and it runs fine in VMware Server VM. I assume you have used the W7 $OEM$ code found here. Enjoy, John.

I ran it on a pc and it worked great, now my questions for activation would i change the code on a 64 bit machine to

cscript %systemroot%\System64\slmgr.vbs -ato

or leave it as System32?

thanks again, you've been very helpful.

[myselfidem]

I ran it on a pc and it worked great, now my questions for activation would i change the code on a 64 bit machine to

cscript %systemroot%\System64\slmgr.vbs -ato

or leave it as System32?

Hello!

If you want to preserve the activation for Windows 7 x64, you can find help here:

http://www.mydigitallife.info/2009/09/24/how-to-backup-and-restore-windows-7-and-server-2008-r2-activation-status-activate-offline-on-reinstall/

At fist you need to activate your copy and after save the files: tokens.dat and pkeyconfig.xrm-ms (for Windows 7 x64)

Make a batch file and put this one inside: $OEM$\$$\SETUP\SCRIPTS\

like this:

net stop sppsvc

DEL /F /Q "%SystemDrive%\Windows\ServiceProfiles\NetWorkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\Tokens.dat"

COPY /Y "%~dp0tokens.dat" "%SystemDrive%\Windows\ServiceProfiles\NetWorkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\"

DEL /F /Q %SystemDrive%\Windows\SysWOW64\spp\tokens\pkeyconfig\pkeyconfig.xrm-ms

COPY /Y "%~dp0pkeyconfig.xrm-ms" %SystemDrive%\Windows\SysWOW64\spp\tokens\pkeyconfig\pkeyconfig.xrm-ms

net start sppsvc

cscript %systemroot%\System32\slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (your key)

cscript %systemroot%\System32\slmgr.vbs -dli

cscript %systemroot%\System32\slmgr.vbs -ato

EXIT

Put all files inside: $OEM$\$$\SETUP\SCRIPTS\

That works fine for me with Windows 7 x86 (without "pkeyconfig.xrm-ms" needed)!

You can see the same "slmgr.vbs" inside "System32" and "SysWOW64"

You have the same result and you can use also:

cscript %systemroot%\SysWOW64\slmgr.vbs -dli

I hope that will help you!

Edited April 19, 2010 by myselfidem

[johnhc]

grabby, I run XP x64 but have no experience with W7 yet. I think its structure is the same, however. My answers are for XP x64, though. There is no System64. Strangely, all 64 bit executables go into System32 and 32 bit executables are in SysWoW64. The WoW stands for "Windows on Windows" and is the 32 bit emulation on the 64 bit platform. I use one VBS script in my installation of XP x64 and it is in System32 folder. Enjoy, John.

[cluberti]

I ran it on a pc and it worked great, now my questions for activation would i change the code on a 64 bit machine to

cscript %systemroot%\System64\slmgr.vbs -ato

or leave it as System32?

There is no system64 - system32 is the native (aka 64bit) system folder, and syswow64 is the WoW64 subsystem system folder, containing the 32bit binaries. You would always run slmgr.vbs from system32, whether on a 32 or 64bit installation.