We are actively testing with the preview builds from Microsoft. If you know of any issues, please feel free to let us know via the forum or a case.
There appears to have been some change to the Windows 10 side of things that prevents it from being the target of a terminal session. It looks like the issue is on the Windows side of the equation and not the Juniper side, because Windows 10 will not accept RDP connections from either my Guacamole server or the Microsoft RDP client on a Mac.
Network level authentication is NOT activated on the Windows 10 PC. I have also tested from an XP box that did not have the regedits needed to make XP do NLA, and it was able to connect.
Yes. I have disabled the native Windows firewall and install my local antivirus that includes a firewall (Trendmicro) and then set it to allow RDP from any source. I am able to successfully get to it from Win81, Win7, Vista, and XP. And it would be in character for Microsoft to do something to try to break interoperablity with non-Microsoft products.
The the client you are using is not supported.
For OSX you can download the latest version of the Microsoft Remote Desktop from the app store. Version 8.0.15 is the latest. I have no windows 10 here so I'm unable to test it for you.
For linux you have to have a look
the client you are using is not supported.
Correct. And since the client in this case happens to be the MAG 2600, I thought that it was appropriate to report that to everyone on the Juniper forums so that no one else wastes time trying to make it work when Microsoft appears to have followed their old habits and prevented it from working.
And I've got a fix. There are two parts, one that is due to changes in the most recent build (10074) which should be helpful information but is not Juniper specific, and the one that will trip up the VPN appliance. The most recent build put a change to the Login UI, but that caused a problem for RDP when my test box was joined to my domain. The fix is to change the value for Threshold from 1 back to 0 (that's the number zero).
The part that trips up the VPN appliance is that previous Windows settings on RDP accepted lower levels of encryption. Now, the default on Windows is to force TLS encryption. Since there is no corresponding setting within the VPN appliance, for now the way to fix this has to be on the Windows side. Change the SecurityLayer setting from 2 back to 1.
Note that this SecurityLayer setting is not the same as what is in the remote settings to force NLA.
I am unable to install Pulse Secure on the latest Windows 10 Build (10074). The installer (ps-pulse-win-5.1r2.0-b54585-64bitinstaller.msi) gets about half way through the 'copying files' step and then rolls back. I found the following error in a .log file. This is on clean install of Windows 10 so there should not be any old Juniper drivers to be found. I also searched the registry for 'jnprTdi', and there is nothing there.
00159,09 2015/05/05 21:13:56.618 1 SYSTEM MsiExec.exe jnprTdi p1292 t1978 jnprTdiInstDLL.cpp:204 - 'jnprTdi' deletion of driver file jnprTdi_812_54585 failed, error 2
00149,09 2015/05/05 21:13:56.618 1 SYSTEM MsiExec.exe jnprTdi p1292 t1978 jnprTdiInstDLL.cpp:223 - 'jnprTdi' deletion of driver key jnprTdi_812_54585 failed
Has anyone else gotten Pulse Secure to install on the latest Windows 10 build?