Revision history [back]

Hi all,

I would like to know the usage differences between theses two files as they can host the same settings. When each of them are interpreted ? At first boot ? At every boot ?

I made my first Windows 2016 instance. Then I reboot it and I notice 2 log files just written :

• cloudbase-init.log
• cloudbase-init-unattend.log,

So AFAIK the 2 configuration file were interpreted by cloudbase-init. Why ?

Here is how I build the image

• I install Windows as our standards in my company (antivirus, ntp, registry settings...)
• At the end of setupcomplete.cmd, I added the silent installation of CloudbaseInitSetup0911x64.msi
• Put settings on cloudbase-init.conf and/or (?) cloudbase-init-unattended.conf
• Launch sysprep specifying the unattend.xml provided by cloubaseinit installation.
• System shutdown, ready to copy on openstack

And the code :

msiexec /i CloudbaseInitSetup__0__9__11__x64.msi /qn /l*v "C:\Logiciels\CloudInit.log" LOGGINGSERIALPORTNAME=COM1
copy personnalized cloudbase-init.conf "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf"
ipconfig /release  
cd "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf"
\Windows\System32\Sysprep\Sysprep.exe" `/generalize `/oobe `/shutdown `/unattend:Unattend.xml
 /generalize  /oobe  /shutdown  /unattend:Unattend.xml

Thanks !

Hi all,

I would like to know the usage differences between theses two files as they can host the same settings. When each of them are interpreted ? At first boot ? At every boot ?

I made my first Windows 2016 instance. Then I reboot it and I notice 2 log files just written :

• cloudbase-init.log
• cloudbase-init-unattend.log,

So AFAIK the 2 configuration file were interpreted by cloudbase-init. Why ?

Here is how I build the image

• I install Windows as our standards in my company (antivirus, ntp, registry settings...)
• At the end of setupcomplete.cmd, I added the silent installation of CloudbaseInitSetup0911x64.msi
• Put settings on cloudbase-init.conf and/or (?) cloudbase-init-unattended.conf
• Launch sysprep specifying the unattend.xml provided by cloubaseinit installation.
• System shutdown, ready to copy on openstack

And the code :

msiexec /i CloudbaseInitSetup__0__9__11__x64.msi /qn /l*v "C:\Logiciels\CloudInit.log" LOGGINGSERIALPORTNAME=COM1
copy personnalized cloudbase-init.conf "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf"
ipconfig /release  
cd "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf"
\Windows\System32\Sysprep\Sysprep.exe"  /generalize  /oobe  /shutdown  /unattend:Unattend.xml

Thanks !

Hi all,

I would like to know the usage differences between theses two files as they can host the same settings. When each of them are interpreted ? At first boot ? At every boot ?

I made my first Windows 2016 instance. Then I reboot it and I notice 2 log files just written :

• cloudbase-init.log
• cloudbase-init-unattend.log,

So AFAIK the 2 configuration file were interpreted by cloudbase-init. Why ?

Here is how I build the image

• I install Windows as our standards in my company (antivirus, ntp, registry settings...)
• At the end of setupcomplete.cmd, I added the silent installation of CloudbaseInitSetup0911x64.msi
• Put settings on cloudbase-init.conf and/or (?) cloudbase-init-unattended.conf
• Launch sysprep specifying the unattend.xml provided by cloubaseinit installation.
• System shutdown, ready to copy on openstack

And the corresponding code :

msiexec /i CloudbaseInitSetup__0__9__11__x64.msi /qn /l*v "C:\Logiciels\CloudInit.log" LOGGINGSERIALPORTNAME=COM1
copy personnalized cloudbase-init.conf "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf"
ipconfig /release  
cd "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf"
\Windows\System32\Sysprep\Sysprep.exe" /generalize /oobe /shutdown /unattend:Unattend.xml

According Unattend.xml, at first boot, the following will be run : cmd.exe /c ""C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Scripts\cloudbase-init.exe" --config-file "C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init-unattend.conf

So, does it mean the cloudbase-init-unattend.conf is used only once at fist boot. So this file should init the user : according theses entries using the pluging : cloudbaseinit.plugins.windows.createuser.CreateUserPlugin username=Admin groups=Administrators As all plugin are executed by defaut, no need for a pluings entry in this ini file

If cloubase-init.conf has also the username/groups entries, it will change the password of the admin user at each reboot ? The only way to automaticaly change this password and be able to get it vith the nova command

If one want to keep the provided password at first boot, one have to remove these entries and specify la limited set of plugin in the plugins= entry ?

Thanks !

Hi all,

I would like to know the usage differences between theses two files as they can host the same settings. When each of them are interpreted ? At first boot ? At every boot ?

I made my first Windows 2016 instance. Then I reboot it and I notice 2 log files just written :

• cloudbase-init.log
• cloudbase-init-unattend.log,

So AFAIK the 2 configuration file were interpreted by cloudbase-init. Why ?

Here is how I build the image

• I install Windows as our standards in my company (antivirus, ntp, registry settings...)
• At the end of setupcomplete.cmd, I added the silent installation of CloudbaseInitSetup0911x64.msi
• Put settings on cloudbase-init.conf and/or (?) cloudbase-init-unattended.conf
• Launch sysprep specifying the unattend.xml provided by cloubaseinit installation.
• System shutdown, ready to copy on openstack

And the corresponding code :

msiexec /i CloudbaseInitSetup__0__9__11__x64.msi /qn /l*v "C:\Logiciels\CloudInit.log" LOGGINGSERIALPORTNAME=COM1
copy personnalized cloudbase-init.conf "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf"
ipconfig /release  
cd "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf"
\Windows\System32\Sysprep\Sysprep.exe" /generalize /oobe /shutdown /unattend:Unattend.xml

According Unattend.xml, at first boot, the following will be run : cmd.exe /c ""C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Scripts\cloudbase-init.exe" --config-file "C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init-unattend.conf

So, does it mean the cloudbase-init-unattend.conf is used only once at fist boot. So this file should init the user : according theses entries using the pluging : cloudbaseinit.plugins.windows.createuser.CreateUserPlugin cloudbaseinit.plugins.windows.createuser.CreateUserPlugin

username=Admin
groups=Administrators

As all plugin are executed by defaut, no need for a pluings entry in this ini file

If cloubase-init.conf has also the username/groups entries, it will change the password of the admin user at each reboot ? The only way to automaticaly change this password and be able to get it vith the nova command

If one want to keep the provided password at first boot, one have to remove these entries and specify la limited set of plugin in the plugins= entry ?

Thanks !

Hi all,

I would like to know the usage differences between theses two files as they can host the same settings. When each of them are interpreted ? At first boot ? At every boot ?

I made my first Windows 2016 instance. Then I reboot it and I notice 2 log files just written :

• cloudbase-init.log
• cloudbase-init-unattend.log,

So AFAIK the 2 configuration file were interpreted by cloudbase-init. Why ?

Here is how I build the image

• I install Windows as our standards in my company (antivirus, ntp, registry settings...)
• At the end of setupcomplete.cmd, I added the silent installation of CloudbaseInitSetup0911x64.msi
• Put settings on cloudbase-init.conf and/or (?) cloudbase-init-unattended.conf
• Launch sysprep specifying the unattend.xml provided by cloubaseinit installation.
• System shutdown, ready to copy on openstack

And the corresponding code :

msiexec /i CloudbaseInitSetup__0__9__11__x64.msi /qn /l*v "C:\Logiciels\CloudInit.log" LOGGINGSERIALPORTNAME=COM1
copy personnalized cloudbase-init.conf "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf"
ipconfig /release  
cd "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf"
\Windows\System32\Sysprep\Sysprep.exe" /generalize /oobe /shutdown /unattend:Unattend.xml

According Unattend.xml, at first boot, the following will be run : cmd.exe /c ""C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Scripts\cloudbase-init.exe" --config-file "C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init-unattend.conf

So, does it mean the cloudbase-init-unattend.conf is used only once at fist boot. So this file should init the user : according theses entries using the pluging : cloudbaseinit.plugins.windows.createuser.CreateUserPlugin

username=Admin
groups=Administrators

As all plugin are executed by defaut, no need for a pluings plugins entry in this ini file

If cloubase-init.conf has also the username/groups entries, it will change the password of the admin user at each reboot ? The only way to automaticaly change this password and be able to get it vith the nova command

If one want to keep the provided password at first boot, one have to remove these entries and specify la limited set of plugin in the plugins= entry ?

Thanks !

Hi all,

Sorry this post is quite long. Today

I would like to know the usage differences between theses two files as they can host the same settings. When each of them are interpreted ? At first boot ? At every boot ?

I made my first Windows 2016 instance. Then I reboot it and I notice 2 log files just written :

• cloudbase-init.log
• cloudbase-init-unattend.log,

So AFAIK the 2 configuration file were interpreted by cloudbase-init. Why ?

Here is how I build the image

• I install Windows as our standards in my company (antivirus, ntp, registry settings...)
• At the end of setupcomplete.cmd, I added the silent installation of CloudbaseInitSetup0911x64.msi
• Put settings on cloudbase-init.conf and/or (?) cloudbase-init-unattended.conf
• Launch sysprep specifying the unattend.xml provided by cloubaseinit installation.
• System shutdown, ready to copy on openstack

And the corresponding code :

msiexec /i CloudbaseInitSetup__0__9__11__x64.msi /qn /l*v "C:\Logiciels\CloudInit.log" LOGGINGSERIALPORTNAME=COM1
copy personnalized cloudbase-init.conf "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf"
ipconfig /release  
cd "%ProgramFiles%\Cloudbase Solutions\Cloudbase-Init\conf"
\Windows\System32\Sysprep\Sysprep.exe" /generalize /oobe /shutdown /unattend:Unattend.xml

According Unattend.xml, at first boot, the following will be run : cmd.exe /c ""C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Scripts\cloudbase-init.exe" --config-file "C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init-unattend.conf

So, does it mean the cloudbase-init-unattend.conf is used only once at fist boot. So this file should init the user : according theses entries using the pluging : cloudbaseinit.plugins.windows.createuser.CreateUserPlugin

username=Admin
groups=Administrators

As all plugin are executed by defaut, no need for a plugins entry in this ini file

If cloubase-init.conf has also the username/groups entries, it will change the password of the admin user at each reboot ? The only way to automaticaly change this password and be able to get it vith the nova command

If one want to keep the provided password at first boot, one have to remove these entries and specify la limited set of plugin in the plugins= entry ?

Thanks !