Parallels Secure Workspace 5.6.0 is a major release containing important changes, bug fixes, performance improvements, and security updates.
Awingu is rebranded as Parallels Secure Workspace starting Oct 31. As a part of the rebranding, our users will see changes to the logos, naming conventions, and the default color scheme. The overall user experience will remain the same as Awingu 5.5.
In-product Licensing Terms
EULA in Awingu will be replaced with Licensing Terms and will be available as an in-product feature for both new installations and upgrades.
Default branding is updated
When creating a new domain after an upgrade, the branding will have a new look.
The following documentation is available for this release:
Mind that some internal URLs have changed. In case you previously only allowed the appliance(s) to connect to specific IPs or hosts, make sure to update your firewall configuration to allow Parallels Secure Workspace to connect to awg.parallels.com and psw.parallels.com .
You can upgrade to Parallels Secure Workspace 5.6.0 from Awingu 5.5.1:
Sign in to Awingu with an administrator account (of an administrative Awingu domain) and make sure that all services on Dashboard are green.
Make sure the host (hypervisor) is not in a stressed state (CPU and disk I/O) and that the memory is not ballooning.
At this point, it is highly recommended to back up the Awingu environment:
Create an environment backup in Awingu.
Shut down the appliance(s) cleanly and make a snapshot/backup.
Make a backup of the database if you are using an external database.
Start up the appliances(s), sign in to Awingu with an administrator account (of an administrative Awingu domain), and wait until all services in Dashboard are green again.
Make sure all Awingu appliances in your environment have internet connectivity (access to https://repo-pub.awingu.com).
Open System Settings.
On the General Information page, in the section Upgrade Version, select 5.6.0 and click Upgrade.
The upgrade can take up to 60 minutes per appliance, depending on the disk and network speed.
Don't refresh the System Settings page.
Do not reboot your appliance(s) during the upgrade.
When the upgrade is completed, Close System Settings and log out. Refresh your browser before you re-login.
It is highly recommended to reboot the appliances(s) after a successful upgrade.
- The redirection to the external IdP when using pre-auth or SSO is not working for environments that started on 4.2 or older.
- Users with a different sAMAccountName but the same UPN are unable to log in using SSO.
- Users using a recreated Active Directory account are unable to log in using SSO even if the user account is removed from the Workspace.
- In some cases, the failover of application sessions is not working correctly.