We used globalprotect vpn to connect to our corporate network. We are upgrading to windows 10. Our windows 7 computers using VPN do not have any problems mapping to our DFS folders. We receive red X and share not available when accessing with windows 10. The drive never gets mapped no matter how long the user waits. I use preferences in the group policy to map the drives to the DFS folder(update). Map using UNC.
As a test, I added the following to item level targeting on the group policy using wmi:
Select * from Win32_Pingstatus Where address="server.horizon.hbc" and StatusCode=0
nameSpace Root\cimv2
The windows 10 user was able to access the drive after I added the server name. Can someone tell me why this worked. I did not configure the VPN, so I do not know how it is setup. I do not want to hard code the server name in a group policy.
How can I fix the drive mapping for Windows 10 and VPN?
Any help would be appreciated. Thanks.