Revision history [back]

Hello,

We have just made a patch in order for cloudbase-init to continue its execution, even if the serial port for logging becomes unavailable. You can use the nightly cloudbase-init installer build to create a new Windows image.

But this won't solve you the real issue you are having. When you join a domain, the cloudbase-init user under which the cloudbase-init service runs will become a local administrator for that computer and it might not have the rights to open a com port. Can you jchange the cloudbase-init user password, log in as that user an try to open a com port?

Thank you,
Adrian Vladu

Hello,

We have just made a patch in order for cloudbase-init to continue its execution, even if the serial port for logging becomes unavailable. You can use the nightly cloudbase-init installer build to create a new Windows image.

But this won't solve you the real issue you are having. When you join a domain, the cloudbase-init user under which the cloudbase-init service runs will become a local administrator for that computer and it might not have the rights to open a com port. Can you jchange the cloudbase-init user password, log in as that user an try to open a com port?

[Update] I tried to reproduce the error using a Windows 2012 R2 Standard instance added to a newly created AD and I did not get any error related to the COM ports. What version of CloudBase-Init are you using?

Thank you,
Adrian Vladu