CMC power button should work.  This will shut down the CMC and all blades.  This should give the same results as sending the power down command to the CMC via JUNOS. ... View more

These assumption are correct, but you will want to consider if the device support ssl acceleration or not.  If ssl acceleration is enabled, this will offload the encryption and decryption to the hardware acceleration card.  If ssl acceleration is not supported or disabled, this will be done via the software.   The results will differ depending if SSL or ESP mode is utilized and the distribution of packet sizes.  Ideally, ESP with larger packets can pump more data through the SA device than SSL mode with small packets. ... View more

Please open a support ticket so this request is properly tracked.  Please provide the case # once you have it. ... View more

Hello Martin,   Do you have a support ticket open?  If so, please provide the case #. ... View more

There is no current ETA I can provide.  I will send you a PM on who you can contact within Pulse Secure to discuss how to move forward on this request. ... View more

Hello Sameh,   What OS are you running?  Also, the client side debuglog.log would help to understand the issue.  Do you have a support ticket open so I can review the logs? ... View more

Hello Dcvers,   The workaround remains the same for both Per-App and VPN On Demand. ... View more

What issues are we seeing with VOD?  These should be working with the new Pulse Secure client. ... View more

The fix should be in ESAP 2.8.1.  Once a release date has been confirmed, I will update the following thread. ... View more

This is the general error message it could not authenticate the machine to the DC.  However, this could mean an issue with creating the tunnel as well.  Could you open a case with support and provide the pulse logs?  This should give us more detail why this issue is occurring.   Please feel free to provide the case #. ... View more

Hello Matthew,   We are still debugging what changes were made in HTML Access 2.6 and how we can resolve this issue.  Can you please open a support case and provide the case number? ... View more

8.0RX is still the recommended release. ... View more

SA/MAG are now under Pulse Secure.  If you open a SA/MAG case via Juniper case manager, it will be send to Pulse Secure and we can handle your request.  This would be an enhancement request.     If you can provide the case number, I can help move this forward. ... View more

Hello Charlie,   We are definitely working on supporting Linux 64-bit with Pulse client.  At this moment, I cannot provide an ETA.  I would suggest opening a support ticket so we can formal track your request.  This gives us a better idea how many customers are interested in support for a Linux 64-bit VPN client. ... View more

Hello Marc,   VMWare View Horizon 6 will be fully support in 8.2 which is tentative for Q4 of 2015.  Are we talking about HTML access or VDI?   We have had a few cases in regards to HTML access 2.5 with VMWare Horizon View 6.0.1 working with 8.1R2 and 8.0R9.  There is an ongoing issue with HTML access 2.6 with VMWare Horizon View 6.1. ... View more

Here is the general documentation for machine only authentication:   http://www.juniper.net/techpubs/en_US/junos-pulse5.0/topics/task/a-c-c-machine-only-machine-auth-configuring.html ... View more

Can you please try ESAP 2.7.8 or higher?  It should be resolved in the latest release. ... View more

It looks like a quick workaround is to lower the UAC control.  Once I lowered this to 'Never Notify', this is allowing HC to pass. ... View more

Hello Matt,   I was able to replicate this issue in-house as well. Could you please open a support ticket with the oesis diagnostic logs from https://www.juniper.net/support/downloads/?p=esap?   Please let me know what your ticket number is so I can confirm you are running into the same issue. ... View more

If you are making the change on the realm, I would advise against this.  My recommendation would be to create a new realm and role mapping for ldap.  This will give you the option to switch between the two configuration if there is any issues with LDAP.  The main reason is role mapping using group lookup are different between AD vs LDAP.   Another thing to consider are the user records stored on the AD auth server.  Did you allow custom bookmarks to be stored by the end user?  If this is the case, you will need to utilize user record sync to move the user records between AD and LDAP.  If this is not performed, end user will lose their custom bookmarks. ... View more

Thanks, Jack.  I will talk to the current engineer and see what we can do to help move this case to resolution. ... View more

Hello Jack,   Can you please provide the case number?  I will see what I can do to help from our side. ... View more

Hello All,   We are actively fix issues for VMWare 5 & 6 for HTML access.  If you have any open cases, please feel free to PM me. ... View more

Hello Bob,   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. ... View more

After further testing, I am able to see the same results in our lab with only the workaround solution.  If I remove the workaround and apply the MS patch, there are no issues.  We will look into this internally to see what we can do to help prevent this issue in the future, but the recommendation is not to apply the workaround. ... View more

Hello Flip,   When I enabled TLS with AES and AES/DES, it is telling me the following cipher suites will be enabled on the SA.   TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDH_RSA_WITH_AES_256_CBC_SHA TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 TLS_ECDH_RSA_WITH_AES_128_CBC_SHA TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA   When i connect via my client, I am connecting by the last two cipher suites.  I think there is something wrong with my GP. Let me see if I can test this again. ... View more