The naming and casing of hostname of provisioned EFLOW VM.

[jamesclu]

Describe the bug
Deploy-Eflow seems to always append “-EFLOW” to Windows hostname. In my case, I have my Windows hostname in lowercase and the provisioned EflowVm actually has my Windows hostname changed to uppercase with “-EFLOW” appended to it!?

To Reproduce
Steps to reproduce the behavior:
$msiPath = $([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))
$ProgressPreference = 'SilentlyContinue'
Invoke-WebRequest "https://aka.ms/AzEflowMSI" -OutFile $msiPath
Start-Process -Wait msiexec -ArgumentList "/i","$([io.Path]::Combine($env:TEMP, 'AzureIoTEdge.msi'))","/qn"
Deploy-Eflow

Expected behavior
Assuming a Windows 10 with hostname 'mywindows', after running Deploy-Eflow command, the provisioned EFLOW VM, when using Connect-EflowVm, should have the hostname as 'mywindows-eflow', instead of what it is - MYWINDOWS-EFLOW.

Screenshots
If applicable, add screenshots to help explain your problem.

Windows Host OS (please complete the following information):

• Edition: [e.g. Professional, IoT Enterprise, Server, etc]
• Version: [e.g. build 17763]
• Virtual Machine: [eg. Azure VM, Local VM, None]

Additional context
Add any other context about the problem here.

[johnsonshih]

deploy-eflow gets host computer name from the environment variable $env:COMPUTERNAME and appends '-EFLOW' to the host computer name as eflow vm hostname. You can change your environment variable to lower case if you want. for the '-EFLOW ' suffix, it's in upper cases by design.

[jamesclu]

Okay, but it can create a problem for your samples, such as interop-textmsg-consoleapp. Specifically, in Step 4 – Create Certificates for Authentication where self-signed certificates are generated with CN (hostname) in lowercase, which invalidates the cerificates! Thanks, ____ __ / / / / /_ / / /__ \___/____ / James Lu ||| Director, Software Development Aspen Technology, Inc. ||| +1 781-221-6463 ||| www.aspentech.com<http://www.aspentech.com/> Developing Microsoft Azure Solutions ***@***.***D77D82.529B2A00] From: Johnson Shih ***@***.***> Sent: Tuesday, July 20, 2021 3:51 PM To: Azure/iotedge-eflow ***@***.***> Cc: Lu, James ***@***.***>; Author ***@***.***> Subject: Re: [Azure/iotedge-eflow] The naming and casing of hostname of provisioned EFLOW VM. (#52) deploy-eflow gets host computer name from the environment variable $env:COMPUTERNAME and appends '-EFLOW' to the host computer name as eflow vm hostname. You can change your environment variable to lower case if you want. for the '-EFLOW ' suffix, it's in upper cases by design. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [github.com]<https://urldefense.com/v3/__https:/github.com/Azure/iotedge-eflow/issues/52*issuecomment-883651470__;Iw!!ApAMwfxt6g!u_9QO9pWr27WuhF6cam9Io2dGpr4vFDX08rw8tNlacLJG7iADoSe15MiNRYZsN5Nuw$>, or unsubscribe [github.com]<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ADBBMW6GWZ266QJ6WPJATGLTYXHRXANCNFSM5AWIONVQ__;!!ApAMwfxt6g!u_9QO9pWr27WuhF6cam9Io2dGpr4vFDX08rw8tNlacLJG7iADoSe15MiNRbecxF0-Q$>.

[fcabrera23]

Thanks @jamesclu,

We will update the documentation to make sure the user is aware of the naming scheme used.

Thanks,
Francisco