![]() New-ItemProperty -Path ‘HKLM:\Software\Microsoft\Flyout\VPN\’ -Name ‘ShowDeviceTunnelInUI’ -PropertyType DWORD -Value 1 -Force ![]() New-Item -Path ‘HKLM:\SOFTWARE\Microsoft\Flyout\VPN’ -Force You can set this registry value using Active Directory group policy preferences or locally by running the following PowerShell command. HKLM\SOFTWARE\Microsoft\Flyout\VPN\ShowDeviceTunnelInUI DWORD = 1 This can be done by setting the following registry value. However, the device tunnel does appear in the classic Network Connections control panel applet (ncpa.cpl).įortunately, there is a simple workaround that allows for the device tunnel connection status to appear in the Windows 10 notification area. Device Tunnel Statusįor those administrators who have decided to deploy the device tunnel exclusively, a common complaint is that the device tunnel connection status does not appear in the Windows 10 notification area like other network or user tunnel connections. While I do not typically recommend this configuration for a variety of reasons, there are some use cases for which using the device tunnel might be acceptable. Although the device tunnel was designed to supplement the user tunnel connection, some administrators have deployed the device tunnel exclusively and use it for general on-premises network access. If you are not familiar with the device tunnel, it is an optional configuration that provides pre-logon connectivity for domain-joined, Enterprise edition Windows 10 clients. I’ve written many articles about the Windows 10 Always On VPN device tunnel over the years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |