Tech Trends and Insights

  Microsoft recently introduced Remote Help Unattended Support with Remote Sign-In , allowing IT administrators and helpdesk staff to remotely access Intune-managed Windows devices without requiring an end user to be present. This guide documents a complete lab-tested deployment , including setup, configuration, troubleshooting, and lessons learned during real-world testing. Disclaimer This guide is based on a manual proof-of-concept deployment . For production environments, Microsoft recommends deploying the required Azure Virtual Desktop components through Intune as Win32 applications. What is Remote Help Unattended Support? Traditional Remote Help requires a signed-in user to approve the support session. With Unattended Support with Remote Sign-In , administrators can: Connect to a managed Windows device when no user is present Sign in using their own credentials Work in a separate Windows session Perform maintenance after business hours Support kiosk devices, public computers, ...

Introduction Microsoft recently introduced the ability to collect Windows Registry data using Device Inventory and the Properties Catalog in Intune. While most examples focus on application inventory and configuration validation, I wanted to explore a different use case. Many security-related events leave traces in the Windows registry. For example, enabling Remote Desktop, configuring a proxy server, or installing remote access software often results in registry changes that can be monitored. Traditionally, identifying these changes required PowerShell scripts, remote access tools, or dedicated security products. With Registry Inventory, administrators can collect selected security-related registry values directly from managed devices and review them centrally in Intune. This provides an additional layer of visibility without connecting to the endpoint. Why This Matters Security teams are often asked questions such as: Has Remote Desktop been enabled on any devices? Are users configur...

Introduction Microsoft recently introduced the ability to collect Windows Registry data using Device Inventory and the Properties Catalog in Intune. While most examples focus on application-specific registry data, I wanted to explore a practical use case for Windows kiosk devices. In environments such as libraries, schools, and public-access workstations, kiosk devices often rely on specific registry settings for automatic sign-in and user experience configuration. When these settings change unexpectedly, troubleshooting can become time-consuming and often requires remote access, PowerShell scripts, or manual registry inspections. With Registry Inventory, administrators can now verify these settings directly from Intune and gain visibility into device configurations without connecting to the endpoint. Why This Matters One of the most common support issues for kiosk devices is that: Automatic sign-in stops working The wrong local account is configured A device is rebuilt incorrectly Reg...