Software Requirements for Installing ProfileUnity
ProfileUnity is available as a standalone product and consists of three parts:
- Management Console —Provides one central location where administrators can configure persona management and user and machine policies.
- FlexApp Packaging Console —Provides the ability to capture applications as FlexApp packages. Administrators can then assign these packages to groups of users.
- Client Tools —Manages each user’s settings and persona during their session.
The ProfileUnity standalone installer guides you through the setup of the Management Console. The FlexApp Packaging Console and the Client are installed from the Administration screen of the Management Console. Installation is straightforward and merely requires an administrator to answer a few simple prompts. The installer, ProfileUnity-Net_vX.X.X.exe, contains the ProfileUnity software and all of the prerequisites you need, including the Microsoft .NET Framework, Erlang OTP, RabbitMQ Server, and MongoDB Server.
Management Console Requirements
The ProfileUnity Management Console requires the following for installation:
| Component | Requirements |
|---|---|
| Platforms Supported | Windows Server 2012/2012 R2/2016/2019/2022. Only 64-bit versions where applicable are supported. Both physical and virtual instances are also supported. |
| Additional Software |
|
| Browsers Supported | Chrome 22.x, Firefox 12.x, and Internet Explorer 9.x or higher versions of these browsers. If you are using Internet Explorer 9, disable enhanced security. |
| CPU | 2 CPUs 1 gigahertz (GHz) or faster |
| Memory | 4 GB RAM |
| Storage | 20 GB available hard disk space |
The ProfileUnity Management Console requires your user account to have administrative privileges on the local machine for installation.
FlexApp Packaging Console
The ProfileUnity FlexApp Packaging Console requires the following for installation:
| Component | Requirements |
|---|---|
| Platforms Supported | Windows 10/11 and Windows Server 2012/2012 R2/2016/2019/2022. Both 32-bit and 64-bit versions where applicable are supported. The packaging console should be on a Windows operating system that can be reset after each package is created. Using a non-persistent pool or a virtual machine with a snapshot that can be rolled back is fully acceptable. Do not install the packaging console on the same machine where the ProfileUnity Management Console was installed. |
| Additional Software | Microsoft® .NET Framework 4.6.2 or higher |
| CPU | 2 CPUs at 1 gigahertz (GHz) or faster |
| Memory | 8 GB RAM |
| Storage | 200 MB available hard disk space (32-bit) or 20 GB (64-bit) |
The FlexApp Packaging Console has an additional bit-level requirement. The bit-level of the operating system on which you package applications with the FlexApp Packaging Console needs to match the operating system of the desktop to which you deploy applications. If you are packaging applications to be used in a 32-bit environment, you must use the Packaging Console on a 32-bit OS. If you are packaging applications to be used in a 64-bit environment, you must use the Packaging Console on a 64-bit OS.
Client Requirements
The ProfileUnity Client requires the following for installation:
| Component | Requirements |
|---|---|
| Platforms Supported | Windows 10/11, Windows Server 2012/2012 R2/2016/2019/2022, and Terminal Server or RDSH. Citrix Virtual Apps and Desktops 6.5-7 2109 (XenApp & XenDesktop), VMware Horizon 5.2.x-8.3 (2106), and VMware Horizon RDSH 8.3 (2106). Both 32-bit and 64-bit versions where applicable are supported. Both physical and virtual instances are also supported. |
| Additional Software | Microsoft® .NET Framework 4.6.2 or higher for use with ProfileDisk or FlexApp DIA |
| CPU | 2 CPUs at 1 gigahertz (GHz) or faster |
| Memory | 2 GB RAM minimum. Increase to 3GB RAM if using FlexApp. |
| Storage | 200 MB available hard disk space (32-bit) or 20 GB (64-bit) |
The ProfileUnity Client is dependent on a Microsoft domain infrastructure. Machines running the ProfileUnity Client must be members of the domain.
Any client machines making use of ProfileUnity’s FlexApp features must have Windows 10 or higher installed. The clients can be deployed as physical desktops or as either persistent or non-persistent virtual desktops.
Additionally, write permission to the NETLOGON share on your domain controller is required to install the ProfileUnity Client. Ensure your user account has the necessary privileges prior to continuing. If you are not using the NETLOGON share on your domain controller, refer to Appendix A, Not Using NETLOGON? for more information.
(Optional) FlexDisk Requirements
FlexDisk is a VMDK distribution technology that can be used with ProfileUnity’s FlexApp and ProfileDisk features as an alternative to using VHDs with these features. Generally, VHDs have less overhead and work great for many organizations, while VMDKs are faster and more stable than VHDs in certain environments. The ProfileUnity FlexDisk technology requires the following for installation:
|
Component |
Requirements |
|---|---|
| Desktops Supported | Windows 10/11, Windows Server 2012 R2/2016/2019/2022 as a desktop, Citrix Virtual Apps and Desktops 6.5-7 2109 (XenApp & XenDesktop), VMware Horizon 5.2.x-8.3 (2106), and VMware Horizon RDSH 8.3 (2106). Both 32-bit and 64-bit versions where applicable are supported. |
| Additional Software | VMware vSphere vCenter and ESXi versions 5.5x-7.x |
| Other Requirements | VMDKs need to be on storage that is visible to the desktops. VMware vSphere licensing that supports HOTADD |
Additional Requirements
Active Directory
ProfileUnity requires Active Directory to deploy its client files to the desktop and point the user to its configuration file. Users also must use Active Directory to log in to their physical or virtual desktops.
(Optional) Using Cloud Storage with ProfileUnity
For those planning to utilize cloud storage with ProfileUnity, the Using Cloud Storage Guide walks you through the process of setting up your cloud storage for use with ProfileUnity. The configuration of your cloud storage should be performed before using the ProfileUnity Management Console.
