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 the prerequisites you need except where noted.
Management Console Requirements
The ProfileUnity Management Console requires the following for installation:
| Component | Requirements |
|---|---|
| Platforms Supported | Windows Server 2016/2019/2022/2025. Only 64-bit versions 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 |
Note: 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 considered best-practice. Note: Do not install the packaging console on the same machine where the ProfileUnity Management Console was installed. |
| Additional Software |
Note: All additional software is included with the installer. |
| CPU | 4 CPUs at 2 gigahertz (GHz) or faster. |
| Memory | 8 GB RAM |
| Storage | 40 GB available hard disk space. |
Client Requirements
The ProfileUnity Client requires the following for installation:
| Component | Requirements |
|---|---|
| Platforms Supported |
|
| Additional Software |
Note: .NET Framework 4.6.2 is no longer included in the Client installer because it is already included with all currently-supported operating systems. |
| CPU | 2 CPUs at 2 gigahertz (GHz) or faster |
| Memory | 4 GB RAM minimum. Increase to 6 GB RAM if using FlexApp. |
| Storage | 20 GB available hard disk space |
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 to that location. 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 VHDX files. Generally, VHDX files have less overhead and work great for many organizations, while VMDKs are faster and more stable than VHDXs in certain environments. The ProfileUnity FlexDisk technology requires the following for installation:
| Component | Requirements |
|---|---|
| Desktops Supported |
|
| Additional Software | VMware vSphere vCenter and ESXi versions 6.5 to 8.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 or other directory service
ProfileUnity Console would typically use Active Directory to deploy its client files to the desktop and point the user to its configuration file. ProfileUnity now also offers integration with Microsoft Entra ID (formerly Azure Active Directory Services) and other Identity Providers via SAML integration.
-
For Hybrid AD environments, an Active Directory-based Service Account can be used to access to Domain-based resources.
-
For environments not using Active Directory at all, cloud storage can be utilized, negating the need for a directory services-based Service Account.
-
Full, Hybrid and Entra ID-joined-only endpoints and end-users account types are supported. AD-based logons can utilize AD-based Context Filters like AD User Groups and Entra ID-joined-only logons can utilize Entra ID-joined-based Context Filters like Entra ID Groups.
Note: For more information on SAML see Configuring SAML Authentication for the ProfileUnity Console. For more information on Microsoft Entra ID see Configuring Microsoft Entra ID for Use with Security Group-Based Filters.
(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.
