Authenticating WIN 10 Clients with NTLM against WGW 126.96.36.199
so i found something strange which could have a multitude of root causes, so i just want to know is someone else encountered the problem.
I am using the webgateways with a few different domains, some of them using NTLM1, some NTLM2. With Win7/8/8.1 we had no problems so far, but testing with WIN 10 revealed that no userinformation is forwarded to the Webgateways (no proxygroup, no username).
As said, that could be caused by a lot of things, but has anyone else encountered this?