New Question

Revision history [back]

click to hide/show revision 1
initial version

Hello Daniel,

If possible, can you put in a pastebin the cloudbase-init and cloudbase-init-unattend logs, for further debugging this issue?

Thanks.

Hello Daniel,

If possible, can you put in a pastebin the cloudbase-init and cloudbase-init-unattend logs, for further debugging this issue?

Edited: This is a known issue of Windows 10, which causes a SetComputerName function to run during the OOBE step, that changes the computer name to DESKTOP-<random string="">. As we run our cloudbase-init-unattend during specialize(which is before oobe), the hostname plugin execution becomes irrelevant.

A quick solution would be to change the cloudbase-init-unattend run in Unattend.xml from "specialize" step to "oobesystem" step -> http://pastebin.com/LNy0D0mC . The downside with this approach is that the login screen appears, then the hostname reboot is executed(after of course, the time taken to find and consume a valid metadata service).

We are currently investigating the options to mitigate this issue and will be back with a fix on this(either the installer or cloudbase-init).

Thanks.

Hello Daniel,

If possible, can you put in a pastebin the cloudbase-init and cloudbase-init-unattend logs, for further debugging this issue?

Edited: This is a known issue of Windows 10, which causes a SetComputerName function to run during the OOBE step, that changes the computer name to DESKTOP-<random string="">. As we run our cloudbase-init-unattend during specialize(which is before oobe), the hostname plugin execution becomes irrelevant.

A quick solution would be to change the cloudbase-init-unattend run in Unattend.xml from "specialize" step to "oobesystem" step -> http://pastebin.com/LNy0D0mC https://pastebin.com/xLATygNd [edited] . The downside with this approach is that the login screen appears, then the hostname reboot is executed(after of course, the time taken to find and consume a valid metadata service).

We are currently investigating the options to mitigate this issue and will be back with a fix on this(either the installer or cloudbase-init).

Thanks.