/
FAQ: Windows 10 IoT Enteprise
  • In progress

    • FAQ: Windows 10 IoT Enteprise

    Owned by Anu Selvaraj (Deactivated)
    Last updated: 13. Oct 2023 by Lukas Rosky
    2 min read

    VNC

    This VNC server and client has been tested on Windows 10 IoT Enterprise on Trizeps8Mini (i.MX8M): realvnc-arm64-build-release

    For linux-based VNC client/server refer to this page: Using VNC on Debian 10

    Windows Remote Desktop

    Windows 10 IoT Enterprise comes with the standard Windows remote desktop tool.

    To activate Remote Access on a Trizeps8Mini running Windows 10 IoT Enterprise follow these steps:

    Activate remote access in the control panel: Control panel → System and Security → System → Allow remote access → ('System Properties' window pops up) → Remote tab

    Select 'Allow remote connections to this computer' > Uncheck 'Allow connections only from computers running Remote Desktop with Network Level Authentification → Apply and OK

    Launch 'gpedit' (Launch Group Policy Editor) → Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options

    Disable the „Account: Limit local account use of blank passwords to console logon only“ policy

    run „ipconfig /all“ to display your systems Host Name (e.g. „WINSECO-S0M3C0D3“) and connect to that using the remote desktop tool on your Windows 10 system

     

    SSH

    To install and run an OpenSSH server on Windows 10 IoT Enterprise open an evelated PowerShell window and execute the following commands:

    • Verify OpenSSH.Server is ‘NotPresent’:

      Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*'

    • Install OpenSSH.Server:

      Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0

    • Configure and start OpenSSH.Server:

      Start-Service sshd
      Set-Service -Name sshd -StartupType 'Automatic'
      if (!(Get-NetFirewallRule -Name "OpenSSH-Server-In-TCP" -ErrorAction SilentlyContinue | Select-Object Name, Enabled)) { Write-Output "Firewall Rule 'OpenSSH-Server-In-TCP' does not exist, creating it..." New-NetFirewallRule -Name 'OpenSSH-Server-In-TCP' -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22 } else { Write-Output "Firewall rule 'OpenSSH-Server-In-TCP' has been created and exists." }

    • Open an elevated command prompt window to change the default user account password:

      net user Trizeps8mini 12345

      (In this example we change the password of the user 'Trizeps8mini' to ‘12345’)

    • Restart the device

     

    • Connect to the device via SSH:

      ssh Trizeps8mini@<IpAddress>

      Authenticate with the password ‘12345’

    • You can look up the devices local IP address via command prompt:

      ipconfig /all