1 | initial version |
For "cloudbase-init screen" you mean the black command line window that shows up during the first boot?
Regarding licensing, to activate the current Windows instance you can add the following option in the configuration file:
activate_windows = true
2 | No.2 Revision |
For "cloudbase-init screen" you mean the black command line window that shows up during the first boot?
The short answer is yes, we'll add a feature to hide the console window in the next release (max 2 weeks).
If you prefer, you can also change the following line in the unattend.xml available in teh CLoudbase-init conf folder, after install but BEFORE sysprep:
<Path>"%INSTALLDIR%Python27\Scripts\cloudbase-init.exe" --config-file "%CLOUDBASEINITCONFFOLDER%cloudbase-init-unattend.conf"</Path>
With a script that will hide the window, e.g.:
<Path>PowerShell.exe -windowstyle hidden "%INSTALLDIR%Python27\Scripts\cloudbase-init.exe" --config-file "%CLOUDBASEINITCONFFOLDER%cloudbase-init-unattend.conf"</Path>
Regarding licensing, to activate the current Windows instance you can add the following option in the configuration file:
activate_windows = true
3 | No.3 Revision |
For "cloudbase-init screen" you mean the black command line window that shows up during the first boot?
The short answer is yes, we'll add a feature to hide the console window in the next release (max 2 weeks).
If you prefer, you can also change the following line in the unattend.xml available in teh CLoudbase-init conf folder, after install but BEFORE sysprep:
<Path>"%INSTALLDIR%Python27\Scripts\cloudbase-init.exe" --config-file "%CLOUDBASEINITCONFFOLDER%cloudbase-init-unattend.conf"</Path>
With a script that will hide the window, e.g.:
<Path>PowerShell.exe -windowstyle hidden "%INSTALLDIR%Python27\Scripts\cloudbase-init.exe" --config-file "%CLOUDBASEINITCONFFOLDER%cloudbase-init-unattend.conf"</Path>
Regarding licensing, to activate the current Windows instance you can add the following option in the configuration file:
activate_windows = true