VPN Client Support

I am writing to verify that this Tuesday's update does NOT fix VPN access on Juniper VPNs either. Microsoft, please fix this!

Another month, another verification that patch Tuesday does NOT fix VPN access on Juniper VPNs.

Will

I'm having a similar issue with my 32GB Surface tablet, running Windows 8.1 with the latest (as of this post) Windows Updates.

When attempting to connect to my corporate SSL VPN using the Microsoft provided Junos VPN client, I received an error message immediately after my credentials have been successfully verified or after selecting a previous session.  The message is simply "invalid parameter".

Reviewing the VPN Client Event Log (as described in the troubleshooting section of the Junos client setup document), I noticed the following 3 events:

<VPN Connection Name> SaveResumpionData: -1671969169

<VPN Connection Name> Invalid parameter.

<VPN Connection Name> RemoveResumptionData: 2622998127

It seems the software is failing on "SaveResumpionData".  It also seems like there's a typo there, as the function is labeled "SaveResumpionData" while its counter part is "RemoveResumptionData" .. note the "t" between mp_ion in the Remove function, that does not exist in the Save_ fucntion.

The Junos Pulse client works flawless on iOS and Android devices with my company's setup.

I use Token based authentication, with an app called MobilePASS from SafeNet.

Our Juniper appliance is a Junos Pulse Secure Access Service, release 7.4 R8.

Any suggestions, feedback, or relevant information would be helpful

A lot of people trying to hack the thing to work unsuccessfully from my research.

http://forums.wpcentral.com/microsoft-surface-windows-rt/233841-8-1-cisco-anyconnect-vpn.html

Cisco has an open issue with MS to offer API access to RT and MS has never responded.

It is tragic, and stunningly ridiculous for the company to do this to this device.

It was nearly the perfect device until they neutered it.

A lot of people trying to hack the thing to work unsuccessfully from my research.

http://forums.wpcentral.com/microsoft-surface-windows-rt/233841-8-1-cisco-anyconnect-vpn.html

Cisco has an open issue with MS to offer API access to RT and MS has never responded.

It is tragic, and stunningly ridiculous for the company to do this to this device.

It was nearly the perfect device until they neutered it.

Agreed, and I posted a quote from Cisco on the linked forum thread.

Limitations to AnyConnect Support for Windows 8

•AnyConnect is not supported on Windows RT. There are no APIs provided in the operating system to provide this functionality. Cisco has an open request with Microsoft on this topic. Customers who want this functionality should contact Microsoft to express their interest.

I've always figured this was the case. The artificial restrictions on the win32 and .NET APIs in Windows RT is infuriating.

Let me say it another way... the APIs are all there! They are just all locked away for anyone and everyone except Microsoft.

That has single-handedly been the downfall of this OS. Apparently Microsoft doesn't read this forum or they would have gotten the message that people want to do more than just simple modern ui apps. All they had to do was provide a way for "power users" to change the signing restrictions (though I would vote to throw them out entirely... make it the same as x86 Windows), and Cisco (and others) could have recompiled their AnyConnect client for ARM years ago. It would have been a non-issue.

Instead Windows RT is being rendered irrelevant. Sad. Windows on ARM could have been soooo much more.

To any forum members or moderators... how exactly do we contact Microsoft as Cisco suggests?? I've posted comments about theses topics many places here and on other forums, and nothing has come of it, nor has anyone ever directed me to any sort of "feature request" contact at Microsoft.