IoT edge runtime not installing on Windows version 1809 when using TPM DPS mode

Attempted to install latest 1.0.7 of IoT edge runtime on Windows 10 enterprise version 1809 Build 17763.503. Using TPM as the attestation method.

Expected Behavior

IoT edge runtime should be successfully install

Current Behavior

followed the documentation on https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-windows.

However tried several times and keep erroring out when the ps script tries to start the iotedge service

Steps to Reproduce

Context (Environment)

Device (Host) Operating System

Windows 10 enterprise version 1809 build 17763.503

Architecture

amd64

Container Operating System

Windows

Runtime Versions

iotedged

1.0.7

Edge Agent

Edge Hub

Docker

Logs

PS C:\WINDOWS\system32> . {Invoke-WebRequest -useb aka.ms/iotedge-win} | Invoke-Expression; `

Install-SecurityDaemon -ContainerOs Windows -Dps

ModuleType Version Name ExportedCommands

---

Script 0.0 IoTEdge {Deploy-IoTEdge, Get-IoTEdgeLog, Initialize-IoTEdge, Insta…

cmdlet Install-IoTEdge at command pipeline position 1 Supply values for the following parameters: ScopeId: XXXXX RegistrationId: XXXXX The container host is on supported build version 17763. WARNING: One or more batteries were detected on this device.

A known Windows operating system issue prevents transition to sleep and hibernate power states when IoT Edge modules (process-isolated Windows Nano Server containers) are running. This issue impacts battery life on the device.

As a workaround, use the command “Stop-Service iotedge, iotedge-moby -Force” to stop any running IoT Edge modules before using these power states.

Confirm Do you want to continue with installation? [Y] Yes [N] No [S] Suspend [?] Help (default is “Y”): Y Skipping VC Runtime installation because it is already installed. Downloading IoT Edge… Using IoT Edge from C:\Users\sakovvu\AppData\Local\Temp\microsoft-azure-iotedge.cab The container host is on supported build version 17763. Generating config.yaml… Configured device for DPS provisioning. Configured device with hostname ‘MININT-HPDSUR6’. Configured ProgramData directory. Configured device with Moby Engine URL ‘npipe://./pipe/iotedge_moby_engine’ and network ‘nat’. Updated system PATH. Start-Service : Service ‘Azure IoT Edge Daemon (iotedge)’ cannot be started due to the following error: Cannot start service iotedge on computer ‘.’. At line:1328 char:9

•     Start-Service $EdgeServiceName
  

•     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service], ServiceCommandException
  • FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand

Additional Information

Verified the hyper-v and containers windows features are enabled. Am i missing an environment variable. ? Using TPM as the attestation method.

[saikovvuri]

@veyalla actually I was not using the old cmdlets. Below are the tests I did -

1st iteration Followed instructions from https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-windows#option-2-install-and-automatically-provision TEST FAILED - that is when i logged the issue

2nd Iteration Just to validate if my windows environment had all the prequisites, I tried to install a previous stable version of Iotedge using - https://raw.githubusercontent.com/Azure/iotedge/1.0.6/scripts/windows/setup/IotEdgeSecurityDaemon.ps1 TEST SUCCEEDED

3rd Iteration Based on your suggestion, changed the aka.ms link to https://aka.ms/iotedge-wininstall-dps107 TEST SUCCEEDED

Hope this clarifies

[saikovvuri]

verified the fix in latest release 1.0.7.1