Looking at your description, we are already performing similar steps, when in the cloudbase-init installer the user chooses to sysprep. Here's the content of SetSetupComplete.cmd:
mkdir "%SYSTEMROOT%\Setup\Scripts"
sc config cloudbase-init start= demand
echo sc config cloudbase-init start= auto ^&^& net start cloudbase-init > "%SYSTEMROOT%\Setup\Scripts\SetupComplete.cmd"
Here's how the same script is called during the automated generation process:
Hi Curt,
Looking at your description, we are already performing similar steps, when in the cloudbase-init installer the user chooses to sysprep. Here's the content of SetSetupComplet e.cmd:
mkdir "%SYSTEMROOT% \Setup\ Scripts" \Setup\ Scripts\ SetupComplete. cmd"
sc config cloudbase-init start= demand
echo sc config cloudbase-init start= auto ^&^& net start cloudbase-init > "%SYSTEMROOT%
Here's how the same script is called during the automated generation process:
https:/ /github. com/cloudbase/ windows- openstack- imaging- tools/blob/ master/ UnattendResourc es/Logon. ps1#L77
Would you be available for a chat on IRC or Skype? My nick is alexpilotti (FreeNode) on #openstack-dev
Thanks,
Alessandro