Message appears after upgrade: “Upgrade Migrations have failed. Please reboot to try again”.

Workaround: This is expected behaviour. For an upgrade to Pulse One 2.0.2004.1, the system will need to be rebooted 2-3 times for the infrastructure upgrades to complete.

The Group validation status is updated to “Invalid” if a group is added while the LDAP server is not available.

Workaround: Manually initiate the verification process once the LDAP server is available again.

The Pulse One domain UI does not accurately display a locked account.

The Publish operation fails when a Pulse One group contains appliances with different versions.

The ‘Logins in Past 24 Hours’ endpoint compliance widget in the ‘Overall System Health’ dashboard does not display the ‘non-compliant reason’ information correctly. After 24 hours, the data from the previous 24 may still be visible.

Search for users based on LDAP group while adding a policy lists all users instead of just LDAP group policy users.

Workaround: Save the policy and re-open the edit screen to see the changes.

Pulse One supports the ability to aggregate up to 90 days of syslogs from Pulse Connect Secure and Pulse Policy Secure appliances that are configured to send their Syslog data to Pulse One. However, an admin is not prevented from configuring more days.

Workaround: Please specify a maximum of 90 days when configuring this capability.

Pulse One does not prevent an admin from running the ‘system destroy’ command when an NFS directory is mounted.

Workaround: Remove the NFS mount before running ‘system destroy system-config’ on the CLI.

When not successfully mounted, ‘log-aggregator show’ does not indicate any errors with the mount process.

Workaround: Please check the NFS share to ensure that the logs are being written there. If not, please retry to mount.

The ‘system destroy system-configs’ command does not immediately disconnect interfaces.

Workaround: After using the ‘system destroy system-configs’ command on the serial console of a Pulse One Appliance, reboot the appliance.

Removed appliance names are no longer displayed in the appliance activities trail.

Send Logs does not upload logs on to the Pulse Workspace server.

Workaround: Do send log using email address.

A few settings – Licenses, NTP, and so on – are not synched from Active node to Passive node after a cluster is successfully set up.

The ‘cluster add’ command returns ‘ERROR: list index out of range’ if the IP address being added is invalid.

If the Active node is shut down and you attempt to run ‘cluster status’ command on the Passive node, it might take up to 5 minutes for the Passive node to provide a status message.

An admin user having a custom-defined role with delete privileges at the “User” level can edit/delete admins with custom permissions higher than itself. That is, Super Admins, and so on.

Workaround: Do not give edit/delete privileges to custom roles with permissions lower than a Super Admin’s unless specifically intended.

When the use of the time-range selector returns more than a 100 data points, the graph may not display correctly.

The ‘system destroy system-config’ command also deletes all entered licenses when it deletes all other configuration and data. You can re-enter licenses only after the provisioning step has been successfully completed.

Workaround: Perform ‘services restart’ after re-entering licenses to make them effective.

Login failure due to a short password configured for the user authentication causes an inaccurate “User Login Failure” count in the User Syslogs Reports feature.

After performing the ‘cluster demote’ command, the internal interface is disabled, and its IP address removed from the configuration. You need to configure internal interface again prior to invoking subsequent clustering commands.

In the first few minutes after a service start, the ‘log-collector’ service makes a number of outbound attempts to reach https://versioncheck.graylog.com to check for the newest version available.

The message presented when a ‘cluster join’ command is run before the external interface is configured is not user friendly: “AttributeError: ‘NoneType’ object has no attribute ‘network for joining the cluster’”.

IP subnet 192.170.0.0/24 is used internally by Pulse One. These addresses cannot be used to configure external nor internal interface of the appliance.

“Space name” is showing “Unregistered” even after the Space state is up-to-date.

Workaround: If the admin refreshes the Workspace page, Space name will show correctly.

Applying a group config to the non-leading node of an AA cluster target or to the passive node of an AP cluster target, causes the group to remain in an infinite publishing state.

Workaround: Click to ‘Apply Group Config’ on the leader or the Active node of the target cluster. This should automatically get the group back into sync once complete.

A group that has no target appliance may sometimes go into an unknown state.

Workaround: Make changes to the configuration of the master appliance. This should trigger a re-render and update the status of the group to ‘In-sync’.

Connectivity issues when an interface with DHCP configuration overlaps with the static IP subnets of other interfaces.

Workaround: If using DHCP, ensure all interfaces are on different subnets. If using static, use only static IPs for all interfaces; do not mix DHCP assigned IPs with static IPs.

SSH connections are not gracefully closed when the IP address of the management interface is modified.

Workaround: Enter “~.” To cleanly exit out of SSH and return to the command prompt.

Appliance groups sometimes display a continual rendering state after an upgrade from Pulse One 2.0.1649 to Pulse One 2.0.1834.

Workaround: Remove appliance from the associated group(s) and add back.

After performing “Verify Group” for LDAP users, a new policy is not pushed in client.

Workaround: Refresh the policy from the client or push the workspace in the server to update the newly added group policy.

Cluster promotion command fails with ‘log-indexer’ timeout error after ‘system destroy data’.

Upgrade fails with ‘log-indexer’ error when no licenses were added to the system prior to upgrade.

Apps are not installed on BYOD device that use Google Accounts method if “Enforce EMM policies on Android devices” is enabled in the Google Admin console.

When ‘services logs’ is running in one SSH session, another duplicate SSH session will not be able to kill the first session.

After destroying its config, on-premise appliance gets stuck in MSSP mode.

When a failed Active node comes back online, the Pulse One cluster suffers a split brain.

Workaround: Once an Active node has suffered outage, remove the IP entry from the DNS to prevent it from hitting this scenario.

Managed appliances will not fail over if an appliance was registered in a release using the registration URL: api.pulseone.domain (pre-1743) which is upgraded to a release (post 1723) using registration URL: hostname.pulsonedomain.com.

Workaround: All appliances affected have to be re-registered.

Before an Active/Passive upgrade, you demote both nodes to standalone. If the cluster’s FQDN resolves to both addresses, managed PCS/PPS appliances might connect to either node. This is a split-brain condition. Data will be lost.

After issuing a Full Device Wipe, the UI does not show the Space state info.

The Pulse Client “Workspace Apps” page locks and displays “Error Occurred” for a long time after Corporate-Owned Provisioning is completed.

After issuing “Wipe Workspace”, an error appears if the profile has been removed.

The upgrade software option remains enabled when a group is upgrading. If an admin attempts the upgrade again, a conflict message is displayed.

Scheduling an install task with a package version that is not the staged package version initiates the installation on the appliance and upgrades the appliance to the staged package version.

Active/non-leader node of cluster shows an unclear error message when the upgrade of a group of clusters fails.

After Volume Purchase Program (VPP) apps are installed on an iOS device, it could take up to 45 mins for the license count to be updated to reflect the app usage.

When an admin enters an incorrect location API key, the location map displays no image or visible errors.

Lost Mode options are not hidden for unsupervised devices.

Even after the workspace is wiped, Space Actions show “Force Update Cert” button as highlighted. It should be made unavailable (greyed out).

Certificate Based authentication for ActiveSync does not work a certificate generated by the PWS in-built CA Server is used. This affects both iOS and Android devices.

Workaround: Use an external PKI Server for generating ActiveSync certificate using SCEP or CAWE.

Policy publish button is not enabled when OnDemand rules are configured.

Workaround: After configuring the VPN On-Demand rules, again toggle the VPN OnDemand ‘Enabled’ property and then publish the policy.

After deleting all the rules/criteria/action parameters, Selected value is still showing ‘1’.

Profiler data is not received on Pulse One for up to 24 hours after running a ‘system destroy data’ command.

A user may get an “Unauthorized error” if they try to change their Pulse One password using a browser tab that was previously used for the SDP workflow.

Workaround: Delete the cached DSID cookie from the browser’s cookie settings.

Syslogs are not received on Pulse One for up to 24 hours after running a ‘system destroy data’ command.

Out of Memory error prevents admin from SSH-ing into the Pulse One appliance.

Workaround: Reboot the appliance.

Workspace device UI should add the ability to display the enrolled workspace as Managed client or Managed Device.

In the Google App search window, each page does not consistently show ten apps in the search results.

Even after supporting pagination for Google App search and removing duplicate search results, I.T. admins cannot search and add the required apps to the App Catalog.

Workaround: Add the Android apps directly from the Google Play after logging in using the AFW registration account.

For a custom-created policy, web clips present in the Global policy are not shown.

Workaround: Configure the Web clips in the custom policy also.

'Coverage By Policy' widget details are not part of the Workspace Dashboard report, when user tries to download the Workspace dashboard report or send the the report via e-mail.

Workaround: 'Coverage By Policy' widget report can be downloaded individually.

PCS appliances with IP addresses in range 172.17.0.0/16 do not register on Pulse One OnPrem appliances. This is because Docker uses the same IP subnet.

Workaround: Consider moving managed appliances to a different subnet.