Agent connectivity on Windows 10 IoT Enterprise

[gmileka]

coreypottebaum wrote:

I am attempting to connect a Windows 10 IoT Enterprise VM with the device agent and am running into issues (or I am just misunderstanding the documentation). Am I correct to create a device in the IoT Hub, copy the connection string, then modify the AzureDeviceManagementClient.json file with the connection string in the "debugConnectionString" variable? The devices we will be using do not have TPM so we cannot use that method.

I have performed these steps but the device has no connectivity in the IoT hub. I have already enabled embedded mode.

Thanks in advance.

Copied from #13.

[gmileka]

Hi coreypottebaum,

The steps you've done look right to me. Can you please attach the log? How did you get the binaries? from the zip file on the repo or did you build them yourself?

Passing the connection string through the configuration file works only with debug builds. We have not enabled it in release builds because connection strings should not be stored in plain text on the device. The configuration file connection string is there only for testing and development purposes - but not production.

[gmileka]

Hi coreypottebaum,

Given that there hasn't been recent activity on this bug, I'm closing it. Please, feel free to re-open if you still see issues.

thanks, george

[coreypottebaum]

Sorry for the lack of replies. I am still having this issue with device.agent.2.0.0.1.x64. My logs are attached.

The files came directly from the repo and I added the device connection string to the AzureDeviceManagementClient.json file in field "connectionString".

I understand that passing the connection string in the configuration file is only for testing but I'm trying to simply set this up for a PoC. Thanks in advance for the help! logs.zip