![windows nt 6.4 user agent windows nt 6.4 user agent](https://docs.checkmk.com/latest/images/agent_linux_rules_agent_plugins.png)
- Windows nt 6.4 user agent mac os#
- Windows nt 6.4 user agent plus#
- Windows nt 6.4 user agent windows#
The default SPN is: HTTP/, where is the canonical DNS name of the server. When a server or proxy presents Chrome with a Negotiate challenge, Chrome tries to generate a Kerberos SPN (Service Principal Name) based on the host and port of the original URI. Unfortunately, the server does not indicate what the SPN should be as part of the authentication challenge, so Chrome (and other browsers) have to guess what it should be based on standard conventions. The SPN generated will use the CNAME name if that exists, so better to use an A record with an IP address. This link from the Chromium page also mentions the SPN issue I encountered previously. Chrome, and Chromium based browsers (such as Vivaldi, Edge, etc.) will use this list so WIA will work for them automatically. Under the HKCU hive you can push out a key “S oftware\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains\adfs.fqdn\” (or replace adfs with a * if you want *.fqdn to be matched), with a value of https and data of DWORD 00000001 in hex.
![windows nt 6.4 user agent windows nt 6.4 user agent](https://img.it610.com/image/info8/2249803c9544483a9bcfe63d5fb2e027.jpg)
Best to use Group Policy Preferences for this, pushing out a registry key. You must add your ADFS site to the Local Intranet zone of IE. Some more things to be done for WIA to work.
Windows nt 6.4 user agent windows#
Matching on “Windows\s*NT.*Chrome” (which I think is regex and so should translate to the string Windows followed by zero or more spaces, followed by NT, followed by zero or more characters, followed by Chrome) will thus only pick the last User Agent String.
Windows nt 6.4 user agent mac os#
![windows nt 6.4 user agent windows nt 6.4 user agent](https://i.stack.imgur.com/rq8ax.png)
Windows nt 6.4 user agent plus#
This is based on this & this Microsoft Docs plus some other blog posts I read over the years.