Apparently did MS do several breaking changes here so my unattend files
never runs, ie:

<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>REG ADD "HKLM\SOFTWARE\Microsoft
\Windows NT\CurrentVersion\Winlogon" /v AutoAdminLogon /t REG_SZ /d 1
/f</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<CommandLine>REG ADD "HKLM\SOFTWARE\Microsoft
\Windows NT\CurrentVersion\Winlogon" /v DefaultUserName /t REG_SZ /d
Homer /f</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>3</Order>
<CommandLine>REG ADD "HKLM\SOFTWARE\Microsoft
\Windows NT\CurrentVersion\Winlogon" /v DefaultPassword /t REG_SZ /d
Lisa</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>%SystemRoot%
\System32\WindowsPowerShell\v1.0\powershell.exe -Command &quot;&amp;
{set-executionpolicy RemoteSigned -Force}&quot;</CommandLine>
<Description>Set exec policy for
scripts</Description>
<Order>4</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>%SystemRoot%
\System32\WindowsPowerShell\v1.0\powershell.exe -Command "C:\Setup
\setup1.ps1"</CommandLine>
<Description>Run setup script</Description>
<Order>5</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>

Anyone successfully kicked off a script in sysprep? The registry
entries are being set, but scripts do not run.

- Anders