Known Issues

Release 9.1R13 PRs

Symptom:OS check passes on latest Windows 11 machine when checks are configured for "Windows 10-64-Bit".

OS check will pass on Windows 10 machine when checks are configured for latest "Windows 11-64-Bit".

Windows 11 (preview version) returns version string as Windows 10 in the kernel.

Condition: OS check policy for Windows 11 systems.

Workaround: NA

Symptom: Telnet/SSH bookmarks are not working on Windows 11 as IE is deprecated.

Condition: When using Windows 11 as client machine and accessing PCS through browser.

Workaround: Access Telnet/SSH bookmarks using HTML5 solution.

Release 9.1R12.1 PRs

No new known issues found in this release.

Release 9.1R12 PRs

Symptom: In A/P Cluster, users might notice a delay in the VPN session resumption when restart service triggered on cluster by Admin.

Condition: In A/P Cluster, delay in user VPN session resumption happens when Admin does restart services on cluster.

Workaround: It is a delay in session resumption and session shall resume after some time. Admin can restart services during the maintenance window.

Symptom: The image quality needs improvement for advanced HTML5 RDP.

Condition: When a user access advanced HTML5 RDP bookmark.

Workaround: None

Symptom: Downloading files with 6in4 and 4in6 not working properly in PSA hardware whereas 4in4 and 6in6 are working.

Condition: ESP mixed mode configured on HW.

Workaround: Disable “Use ESP tunnel for 6in4 and 4in6 traffic" in Configuration --> VPN Tunneling.

Symptom: VMware tools version shows as Unsupported Older Version.

Condition: When PCS is deployed on ESXi version 7.0.

Workaround: None. Functionalities such as Reboot, Shutdown, Power Off, NTP sync will continue to work without any issues.

Release 9.1R11.5 PRs

No new known issues found in this release.

Release 9.1R11.4 PRs

Symptom: Static IP allocation fails for both single and multi-session enabled users.

Condition: Overlapping IP pools are configured in VPN profile.

Workaround: If the overlapping IP pool is broken up/split up this issue is not seen.

Symptom: Static IP allocation fails for both single and multi-session enabled users.

Condition: Users having multiple preferred IP addresses and/or multiple users assigned same preferred IP address.

Workaround: None.

Symptom: Improper titles for lines on HTML5 dashboard graph and some titles missing in Concurrent users graph.

Condition: This issue appears after upgrading to 9.1R11 even without load.

Workaround: On old UI, for a particular graph, click “Edit” and select “Restore Factory Defaults”.

Symptom: Pulse Desktop Client (PDC) always displays upgrade prompt even when client version on the endpoint and the server are same. Clicking on upgrade prompt performs no action (Cosmetic/UI issue).

Condition: Occurs when the Pulse Desktop Client has Symantec signed binaries and the PCS on which it is hosted (9.1R11.3/ 9.1R10.2/ 9.1R9.2/ 9.1R8.4) is signed by Digicert.

Workaround: Disable End-point upgrade on Pulse Connect Secure (PCS). Enable again only when a higher version of PDC is activated on PCS and let the users trigger the client upgrade through the browser.

Symptom: PSAL fails to launch Java Applets.

Condition: Observed on clean environment (both PDC and PCS) and is not consistent.

Workaround: Re-trigger JSAM by clicking start button.

Symptom: AP cluster fail-over VIP is taking more time for Cluster VIP reachable.

Condition: When clicking Fail-over VIP button from Cluster status page (Cluster setup configured with IPv6 ip address).

Workaround: None.

Symptom: Sometimes back-end resources are not accessible over L7 VPN.

Condition: When both L3 & L7 VPN are connected.

Workaround: Disconnect the L3 VPN & access back-end resources. Connect back to L3 VPN.

Release 9.1R11.3 PRs

Symptom: The PSAL installation prompts for admin credentials on windows 8.1 for Local user.

Condition: On Windows 8.1 Endpoints.

Workaround: Right click on the PSAL msi->Properties and enable Unblock. Click Apply and OK. Then install the PSAL.

Symptom: Upgrade prompts missing on connecting to latest PCS.

Condition: When endpoint has PSIS Installed.

Workaround: Uninstall PSIS.

Release 9.1R11 PRs

Symptom: Pulse client is assigned an IP address from static pool while configuration is to prefer IP from LDAP/Radius attribute.

Condition: LDAP/Radius attribute template and static IP address/range is configured in a single user profile as resources.

Workaround: Split the connection profile into multiple profiles like one Profile with LDAP/Radius attributes/resources and other configuration and another profile with static IP address/range and other configuration. The new profiles can be ordered correctly to maintain the expected order of resources.

Symptom: Enabling “SNMP Diagnostic Logging On” is not working.

Condition: When manually “SNMP Diagnostic Logging On” is enabled.

Workaround: None.

Symptom: HTML5 bookmarks will not be accessible.

Condition: When using IE browser.

Workaround: Use Chrome, MS edge or Firefox browsers.

Symptom: User sessions are not syncing with one of the node in Active-Active cluster.

Condition: LMDB related error messages observed.

Workaround: Clear session data.

Release 9.1R10 PRs

Symptom: Admin URLs are not accessible if administrator logs in with IPv6 address of PCS.

Condition: When the administrator uses IPv6 address for admin login.

Workaround: Use IPv4 address or FQDN address.

Symptom: For advanced HTML5 sessions, on administrator UI shows IP address instead of hostname under virtual desktop sessions page.

Condition: When an advanced HTML5 bookmark is configured with a hostname.

Workaround: None.No functionality impact.

Symptom: When a user access basic html5 bookmark, guacd process may restart.

Condition: When the target machine is configured with NLA & CredSSP options: Force update clients.

Workaround: Use “CredSSP options: Mitigated”.

Symptom: For basic HTML5 connections file transfer is not working on macOS.

Condition: When a basic httml5 bookmark is accessed by using Safari browser.

Workaround: Access basic html5 bookmark using chrome browser.

Symptom: When advanced HTML5 connections are accessed first time, user may see “Failed to connect to gateway” message.

Condition: When advanced HTML5 bookmark is configured with a hostname.

Workaround: Refresh the page or go back to landing page and access the bookmark again.

Symptom: Active user page “Agent Type” shows “Mac OS 10.15" in place of “Mac OS 11.0.1".

Condition: When using Safari on macOS version BigSur 11.0.1.

Workaround: None.

Symptom: For advanced HTML5 connections, graph shows invalid values.

Condition: When user access advanced HTML5 bookmarks.

Workaround: Check the HTML5 session count on the virtual desktop sessions page.

Release 9.1R9.1 PRs

Symptom: For advanced HTML5 bookmarks, when the target machine is configured with hostname resource, may not be available at times.

Condition: When VLAN based source IP is configured under the roles along with the hostname.

Workaround: Configure target machine with IP address.

Symptom: For advanced HTML5 sessions, REST API count displays invalid values.

Condition: When no active HTML5 session is present.

Workaround: Check the HTML5 count on Virtual desktop session page.

Symptom: For unsuccessful HTML5 connection, VDS page displays the entry for advanced bookmarks.

Condition: When user is unable to connect to target machine.

Workaround: None.

Symptom: Ctrl+C (abort) command is not working for advanced html5 sessions.

Condition: When user access Putty SSH session within Windows 10VM through advanced html5 bookmark.

Workaround: None.

Symptom: On the IE browser for the advanced HTML5 intermediate, login page text displays “submit query” instead of submit.

Condition: When NLA encryption is configured without SSO.

Workaround: None.

Release 9.1R9 PRs

Symptom: Web process crashes.

Condition: With new PSAM improvement changes, when PSAM is configured with client application functionality, ACL Deny results are always treated as UDP connection deny request which is causing the issue.

Workaround: Configure resources with WSAM destinations.

Symptom: User column for SNMP traps does not show the username.

Condition: When an SNMP trap is added for v2c and then SNMP version is changed to v3.

Workaround: Delete the trap server and then reconfigure the trap sever with user details.

Symptom: “IP Owned by device with HWADDR” messages at MAJOR level seen in Admin logs after upgrade to 9.1R9.

Condition: These messages are seen during the following sequence:

1. Active Passive Cluster upgrade (Example: Node-1 and Node-2)

2. Upgrade started on Node-1. Node-1 with upgraded version is starting up.

3. Node-2 holds the VIP, till it goes for a reboot.

Workaround: None. These messages do not cause any impact to the cluster functionality.

Symptom: Pull state from server not leasing licenses to all the nodes in cluster. Following event logs are seen:

E.g.: 2020-10-19 17:25:01 - DFS_VA_NODE_115_19 - [127.0.0.1] Root::System()[] - Lease request on behalf of DFS_VA_NODE_115_20 by DFS_VA_NODE_115_19 failed: Not Cluster Member, status code=0x22..

Condition: When, occasionally, both the cluster nodes talk to license server to fetch the license clients.

Workaround:

1. Do XML export of license clients.

2. Delete the affected license clients using admin UI.

3. Re-import the license clients from XML file.

Symptom: For existing HTML5 profiles configuration through REST may not set solution type properly always.

Condition: While updating the existing HTML5 profile solution type.

Workaround: Create new profile through REST API.

Symptom: For Advanced HTML5 user's Zoom sessions, audio stream can be inconsistent.

Condition: When Zoom application is used for meeting session over Advanced HTML5 session.

Workaround: Use Microsoft Teams application.

Symptom: In MAC Safari browser, Advanced HTML5 sessions clipboard is not available.

Condition: When using MAC Safari browser in Advanced HTML5 session.

Workaround: Use Chrome browser for clipboard access.

Symptom: For Advanced HTML5 RDP sessions, Microsoft Teams video call might disconnect the session.

Condition: When making a Microsoft Teams video call in Advanced HTML5 RDP session.

Workaround: None.

Symptom: For Advanced HTML5 sessions, some documents may not invoke print function properly.

Condition: When printing a text document with Notepad++.

Workaround: Use default document mode.

Symptom: For Advanced HTML5 RDP sessions, video quality can be inconsistent at times.

Condition: When accessing high resolution video streaming in an Advanced HTML5 RDP session.

Workaround: None.

Symptom: For Advanced HTML5 sessions, error messages are not displayed.

Condition: When target machine is not reachable.

Workaround: None.

Symptom: REST based import of user role fails with the following error: "/sam/sam-options/wsam-autoinstall] Unsupported attribute type 0".

Condition:

1. User role config obtained from PCS running pre-9.1R9 through REST.

2. Admin uses REST PUT|POST to import the config from Step 1 on PCS running 9.1R9.

Workaround: Replace wsam-autoinstall with wsam-autouninstall and use REST based import.

Symptom: Pulse One fails to sync files Windows ACL policies on Target PCS from Master PCS.

Condition: On Master PCS, when made changes to Windows File ACL policies and tried to push it to targets where the same policies are already present.

Workaround: Manually export those ACL policies from Master PCS and manually import them on Target PCS.

Symptom: PCS is not responding to ping with payload size larger than the MTU size.

Condition: Issue occurs in 4in6 scenario. when pinging a protected resource with large packet size.

Workaround: None.

Symptom: Invalid Admin log shows as “Unable to synchronize time, either NTP server(s) are unreachable or provided symmetric key(s) are incorrect.“ even though NTP servers are reachable and clock is syncing.

Condition: When upgrading to 9.1R8.1 or later builds.

Workaround: None. There is no functionality impact

Symptom: Noticeable slowness seen in upgrade from 9.1R4 to 9.1R8 on AWS platform.

Condition: When the load on data center is high. Also, depends on the network parameters in the given zone.

Workaround: Please plan upgrades with sufficient upgrade window.

Symptom: Remote-program, Multi Monitor, Session recording options are not working for end-user created bookmark.

Condition: When a user tries to access end-user created advanced HTML5 bookmark.

Workaround: User can use admin created bookmarks.

Symptom: Advanced HTML5 graph is not implemented.

Condition: When accessing advanced HTML5 bookmarks.

Workaround: User can check the advanced bookmark count by using REST API/Active Virtual Desktop Sessions page.

Release 9.1R8.2 PRs

Symptom: SAML SLO is not initiated from PCS to its IDP when the user’s browser-based session is ended.

Condition: When user is authenticated using any browser to PCS with SAML authentication method where PCS is SAML SP, user session is ended in browser because of idle timeout or max session timeout or if admin ends the user session from PCS Admin console. Currently only manual sign out from browser session is supported to send SLO request to IDP from PCS side.

Workaround: Close the browser window and launch a new browser window, so that user is prompted for authentication again for security reasons.

Release 9.1R8.1 PRs

No new known issues found in this release

Release 9.1R8 PRs

Symptom: Local proxy PAC file not working in Internet Explorer 11.

Condition: When PAC file resides on a local system.

Workaround: Store the PAC file on an HTTP/HTTPS-accessible server and use that link for Internet Explorer 11 proxy settings.

Symptom: Windows client connecting to PCS using Firefox ESR 68.10 intermittently throws error during Compliance check through Proxy configuration.

Condition: Using Firefox ESR 68.10 version.

Workaround: Once a successful connection is established from the client to the server using Chrome/IE, try connecting to the server using Firefox ESR. This works as expected.

Symptom: Host Checker process tncs crash.

Condition: When user role is configured with 120 HC rules and policy check interval is every one minute and with 8K user load.

Workaround: (Recommended) Increase the Host Checker policy check interval.

Symptom: PCS does not restrict user logins, even though dsagentd crossed 80% CPU utilization.

Condition: Noticed the issue especially with clusters and when changing from Active-Active to Active-Passive cluster or vice versa.

Workaround: Restart of System Services should solve the issue.

Symptom: Pulse collaboration client version is not same in Mac and Windows.

Condition: When user installs 9.1R8 Pulse collaboration client.

Workaround: None.

Symptom: Archiving on AWS S3 storage and Azure is failing when DNS server is not reachable from internal interface.

Condition: When admin trying to Archive using AWS S3 bucket or Azure storage account on management port and DNS server is not reachable through internal port.

Workaround: Admin has to configure internal port for DNS resolution, Archival interface can be internal/management for archiving on AWS S3 bucket or Azure storage account.

Symptom: Hyper-V 9.1R8 upgrade from earlier versions is not supported.

Condition: When upgrading from the earlier versions, say 9.1R5.

Workaround: Install a fresh instance of 9.1R8 and import the config from the earlier version.

Symptom: TOTP Authentication fails for all users.

Condition: After importing TOTP users into the PCS via REST API.

Workaround: Use Export and Import option under TOTP Authentication server in Admin UI.

Symptom: Websocket URL is not accessible.

Condition: When trying to access https://web.whatsapp.com/ URL.

Workaround: None

Symptom: Upgrading Azure images from 9.1R5 to any later releases returns with error message if the factory reset version is 9.1R5.

Condition: When factory reset version is 9.1R5.

Workaround: Export the existing PCS configurations, deploy the new PCS image with the latest version, and import the PCS configurations.

Symptom: Active user page is not displaying node details correctly for the users connected in AA cluster after split and join.

Condition: After cluster split and re-join.

Workaround: Display issue, user sessions will not get impacted. Newly connected sessions are showing the details correctly.

Symptom: Host checker is getting timed out (can be seen on user access log) and user is getting logged out.

Condition: When periodic evaluation is enabled.

Workaround: This issue is not replicable every time, but as a workaround, we have suggested to disable dynamic evaluation or increase the periodic policy evaluation interval.

Symptom: Host Checker installation error found Intermittently while installing Host Checker or Pulse Client [HC enabled] through browser [Chromium Edge/Chrome/Firefox].

Condition: Fresh Installation of Host Checker or Pulse Client [Host Checker enabled] through browser [Chromium Edge/Chrome/Firefox] after uninstalling old Host Checker components

Workaround:

•Uninstall the Host Checker/Pulse Client components manually and reboot the system.

OR

•Manually kill Host Checker process before installing Pulse Client/Host Checker components.

Symptom: Client upload logs fails for Network Connect and JSAM.

Condition: After launching Network Connect and JSAM on Windows 10, client upload log fails.

Workaround: None

Symptom: Update in PSAM Resource policies configuration from Admin portal is not getting applied immediately to existing users with UDP PSAM sessions.

Condition: When Admin changes ACL action from Deny to Allow for a particular UDP based resource (i.e., UDP Server Application) for which user already has UDP PSAM Session active, user will still see access denied and vice-versa. But this condition might occur very rarely in real world scenario.

Workaround: Admin can choose to delete existing UDP PSAM user sessions for which ACL action changes from Deny to Allow and vice-versa.

Alternatively, user can disconnect and connect PSAM UDP based application session.

Symptom: Pulse client is not showing correct error message when there is no bandwidth to allocate for L3 tunnel.

Error message in Pulse client - "Unable to allocate IP address".

Condition: When there is no bandwidth to allocate for L3 tunnel for that specific user.

Workaround: Display issue, correct error message will get displayed in User Access logs.

Error message in User Access logs - "Cannot find a qualified bandwidth management policy for user based on current available bandwidth."

Release 9.1R7 PRs

Symptom: Existing HTML5 active sessions are not displayed under "Active Virtual Desktop Sessions" tab.

Condition: After cluster upgrade, existing HTML5 sessions are not displayed under "Active Virtual Desktop Sessions" tab.

Workaround: User has to re-login and connect to HTML5 session.

Release 9.1R6 PRs

Symptom: Platform page shows hypervisor information as KVM instead of Alibaba-Cloud-KVM or OpenStack-KVM.

Condition: This issue is seen only with PCS deployed on Alibaba Cloud and OpenStack hypervisors.

Workaround: None. There is no functionality loss though. PCS will function without any issues.

Release 9.1R5 PRs

Symptom: Inconsistent upgrade issues seen while upgrading Hyper-V images in clustering and single node.

Condition: Upgrading a Hyper-V image to 9.1R5.

Workaround: If cluster upgrade fails, reboot the node which is not upgraded. If the issue persists, try upgrading the nodes individually and then form cluster.

Symptom: Cannot register the device with Intune to get SCEP profile that has IMEI as common name.

Condition: The devices like Wi-fi only iPad / Wi-Fi only android tablets that do not have IMEI support or do not have IMEI.

Workaround: None.

Symptom: Cluster VIP is not getting migrated to other node when active node's internal interface is not reachable and external port is reachable.

Condition: In AP Cluster configured with both internal and external port, when active node's internal port became unreachable.

Workaround: Reboot the cluster node having issue with internal interface is unreachable.

Symptom: XML import is failing if configuration file has syslog IPv6 settings.

Condition: if one of the devices configured IPv6 syslog server on log settings, the XML import will fail on another device if the same XML is exported from first device.

Workaround: Export the binary system configuration and import on another device.

Symptom: TCPDump fails to capture packets when multiple interfaces are selected.

Condition: When multiple interface - Internal, External and Management are selected.

Workaround: Select individual interface to capture packets using TCPDump.

Symptom: User sessions will be removed for the session logged in at the time of second node upgrade in AP cluster.

Condition: During AP cluster upgrade, when the first node comes up after upgrading newer version, it informs other node to upgrade. During this time if any new user logs in, then all those sessions will be removed after second node goes for upgrade.

Workaround: User needs to re-login.

Symptom: Reliable users may be prompted for secondary authentication despite Adaptive authentication being enabled for the realm.

Condition: Adaptive Authentication feature may not work in some scenarios where nodes are in the cluster setup.

Workaround: None.

Release 9.1R4.3 PRs

No new known issues found in this release

Release 9.1R4.2 PRs

No new known issues found in this release

Release 9.1R4.1 PRs

No new known issues found in this release

Release 9.1R4 PRs

Symptom: Bookmark based access flow for Cloud based apps does NOT support MFA.

Condition: When user tries to access any Cloud apps using Bookmark based flow, MFA based Conditional Access policies does Not work and will Deny the access to user.

Workaround: Access Cloud apps using SP Initiated flow for MFA to work, or do NOT configure MFA for these Bookmark based Cloud apps.

Symptom: License report did not show proper values for older dates (Dec month) after upgrading to 9.1R4 image.

Condition: License report generated from License server running with lesser than 9.1R4 version will have older data (For example: Dec-2019) and after upgrading the license sever to 9.1R4 image, data for older months will not be accurate.

Workaround: None

Symptom: Pulse Collaboration meeting is not getting launched with PSAL in macOS Catalina from the second time.

Condition: In macOS Catalina, Pulse Collaboration meeting can be launched only after the fresh download of the client. If we try to relaunch the meeting, it is getting failed.

Workaround: Delete the Pulse Collaboration client folder and perform a fresh download before launching the meeting.

Symptom: TOTP server, Certificate server and SAML server authentication do not work for MFA based Conditional Access policy settings.

Condition: When TOTP server, Certificate server and SAML server are configured as MFA server for Conditional Access.

Workaround: Any other supported Authentication server can be configured as MFA server.

Symptom: License report doesn't show the software version for one of the members cluster setup.

Condition: When cluster is in license client

Workaround: None (Display issue).

Symptom: HOB launch on CentOS failing when Oracle JDK is installed.

Condition: Oracle JDK installed on CentOS.

Workaround: Install OpenJDK.

Symptom: AliCloud PCS-7K-V: Watchdog restarting cgi-server auth processes (cgi).

Condition: Beyond 20K concurrent users under Pulse ESP and PSAM throughput test.

Workaround: None

Symptom: Hob auto-launch - PSAL failing with error "Failed to contact server".

Condition: When auto-launch is enabled on HOB bookmark.

Workaround: Disable auto-launch.

Symptom: SSH does not work after restarting services in AWS and Azure.

Condition: After performing restart services.

Workaround: SSH works after a reboot.

Symptom: Rewriter issues with SharePoint 2019 – a few buttons and icons does not load and rename file does not work.

Condition: When using PCS web bookmark for the new SharePoint 2019 server.

Workaround: Switch to Classic View in SharePoint 2019.

Symptom: Host Checker error found Intermittently while installing Pulse Client via Chromium Edge browser in presence of Host Checker configured.

Condition: Host Checker configured.

Workaround: Click on Ignore button.

Release 9.1R3 PRs

Symptom: When trying to restart PCS from vCenter, PCS shuts down instead of restart.

Condition: When trying to restart PCS using the Restart Guest option from vCenter.

Workaround: Restart PCS using the PSA-V virtual console.

Symptom: DNS address and domain names are taken from DHCP server when deploying new PCS instance in AWS and Azure.

Condition: When passing DNS address and domain name as parameter for initial configuration, DNS address and domain name are taken from DHCP server.

Workaround: Reconfigure DNS address and domain in network over view page.

Symptom: Not able to enable "copy/paste" option for end user created bookmarks after upgrade from 9.1R2 to 9.1R3.

Condition: After an upgrade, not able to enable "copy/paste" option in the end user created bookmarks.

Workaround: The user has to delete and create the bookmarks to enable "copy/paste" option.

Symptom: Not able to enable "copy/paste" option via RDP launcher URL.

Condition: When trying to enable "Copy/paste" option via RDP launcher URL.

Workaround:

•User should use admin created bookmark.

•User should use end-user created bookmark.

Symptom: AWS or Azure new PCS deployment fails when customer using old templates with admin password is less than 10 characters.

Condition: When the template contains admin password with less than 10 characters.

Workarounds: Customer has to provide admin password length with minimum of 10 characters.

Symptom: Dismiss until next upgrade option is not working for banner related to perpetual licensing.

Condition: Admin clicks on Dismiss until next upgrade.

Workaround: Use the Close button for temporary solution.

Symptom: During peak hours when multiple users try to do browser-based login on PSA5K, a few users might not be able to connect in the very first attempt.

Condition: When PCS is upgraded to 9.1R3 on PSA5K.

Workaround: When the failed user tries to reconnect, the login will happen successfully.

Symptom: Azure PCS - Network interface speed is showing as “Unknown” in the Network Overview page.

Condition: When deploying new PCS instance in Azure, the network interface speed is showing as “Unknown” in the Network Overview page.

Workaround: This is just a display issue.

Symptom: Intermittently, Behavioral analytics dashboard page shows "Unable to connect to database" error.

Condition: Sometimes, when admin navigates to Behavioral analytics dashboard page, "Unable to connect to database" error is seen.

Workaround: Administrator can reload the Behavioral analytics dashboard page after some time to get the details on the page.

Symptom: Sometimes logs are not shown under Log/Monitoring page.

Condition: Not applicable.

Workaround: Refresh the page or click on the Update button on the logs page.

Symptom: When File rule configured for validating a file location using System default Directories <%HOME%> policy evaluation failed on macOS 10.14x or any higher versions.

Condition: If file located at System Directories <%HOME%> and configured a Hostcheck policy with File Rule for macOS 10.14.x or higher versions.

Workaround: Need to add permissions for "Pulse Client" under "Accessibility" and "Full Disk Access" and which can be accessed from "System Preferences" > "Security & Privacy"-> "Privacy

Or without providing permission /tmp location can be used for File validation.

Symptom: Sharing Feature is not working in macOS Catalina.

Condition: When Attendee Joined in Pulse Collaboration meeting via macOS Catalina, Attendee cannot share the Desktop. But Attendee can view the Presenter’s screen.

Workaround: None

Symptom: Pulse collaboration not getting launched in macOS.

Condition: When the Java version above 8 is installed in the macOS, Pulse collaboration will not launch.

Workaround: Use Java version 8 for launching the Pulse collaboration in macOS.

Release 9.1R2 PRs

Symptom: Shutdown of PSA-V deployed on KVM hypervisor does not complete.

Conditions:

•PSA-V is deployed on KVM hypervisor.

•Shutdown is initiated from PSA-V virtual console.

Workaround: None

Symptom: Sometimes end-user is unable to access backend resources.

Conditions:

1.PCS is deployed as an AP cluster.

2.Admin has configured VLAN source IP under User Roles.

3.VIP changes from active node to passive node.

Workaround: Log out and then log back in as an end user.

Symptom: DNS Search Order notes for macOS needs correction as Device only DNS is supported in macOS.

Condition: macOS supports Device only DNS.

Workaround: None

Symptom: Older PSIS is not upgrading to 9.1R2 PSIS version.

Condition: When CTS, WTS and VDI gets upgraded to 9.1R2 in Windows 10 Redstone 5 and later, PSIS is not upgraded to latest version.

Workaround: None. Old PSIS will continue to work and no impact seen.

Symptom: Using REST API - Archiving Schedule settings change from hourly to specified time does not update the hour/minute setting.

Condition: None

Workaround: Apply the same API again the second time.

Symptom: JSAM fails to launch on Mac OS Catalina 10.15.

Conditions:

•Configured a role with Host checker.

•Configured JSAM access with auto-launch.

Workaround: None

Symptom: After single logout with PCS as SP, the SP lands on either IdP page or SP page.

Condition: PCS is configured as IdP and another PCS configured as SP with single logout enable.

Workaround: None.

Release 9.1R1 PRs

Symptom: Named User Remote Repo (NURR) mode does not work when MSSP unlimited license is installed on the License server.

Condition: MSSP Unlimited License installed on License server.

Workaround: Pulse Secure advises MSSP customers with MSSP SKU to not use NURR mode.

Symptom: DNS Port selection will not take any effect. DNS traffic will go through Internal Port only.

Condition: On a PCS Virtual Appliance, when Administrative Network is enabled under Traffic Segregation. This issue is not applicable for PSA Hardware Devices.

Workaround: None

Cloud Secure

Symptom: Blocked ECP users will not be updated if Generic is selected under LDAP server Type.

Condition: LDAP server type selected is Generic.

Workaround: Select the LDAP server type as Active Directory.

Symptom: Blocked ECP users will have a “Blocked till time” of 5 minutes.

Condition: Request count for a particular user is less than 3.

Workaround: None