Standalone Client Installer
The ProfileUnity Client Tools are also available as a self-contained, standalone installer in both EXE and MSI format. A standalone installer allows for installation on non-domain joined endpoints and simpler job creation when using various deployment solutions, such as Microsoft Intune. Refer to the ProfileUnity Client Deployment with Microsoft Intune Guide for more information and the required steps to deploy the standalone client through Microsoft Intune.
Note: Only the standalone EXE installs the required .NET Core Hosting and Windows Desktop Runtimes. The standalone MSI installer does not contain these runtimes and must be installed and managed separately.
Core settings required for ProfileUnity to not only install on a workstation but properly initialize when a user logs in are reliant upon either domain or local policies to be configured, allowing the respective registry entries to be created. The standalone installer supports both interactive and CLI-based installations.
When using the standalone client installer, many of the settings configured through domain or local policies, along with certain startup configuration values, can be set by passing different arguments at the time of installation. This allows the client to fully install and have all relevant settings configured by passing a single command. Below is a table outlining the different arguments and associated settings or configuration values.
| Argument | Description |
|---|---|
| ACCEPTEAULA=1 | Accept EULA (Required to perform client install) |
| E=<1|0> | Enable ProfileUnity for all machine users |
| LOGOFF=<1|0> | Create the ProfileUnity logoff script within the local policy |
| USERINI | User configuration INI path at the system level (overrides value at the user level) Example: USERINI="\\userpath, s3://, s3:\\, az://, az:\\, gs://, gs:\\" |
| LICSTR="<LicString>" | License Server Connection String |
| SYSINI | System INI path used by the Client Service Example: SYSINI="\\syspath, s3://, s3:\\, az://, az:\\, gs://, gs:\\" |
| SVCCRED | Location of the Client Service credentials file Example: SVCCRED="\\credpath, s3://, s3:\\, az://, az:\\, gs://, gs:\\" |
| SYSSVCCRED=<1|0> | Client Service runs as the SYSTEM account |
| CLIENTXML | Location of the Client Settings XML file Example: CLIENTXML="\\xmlpath, s3://, s3:\\, az://, az:\\, gs://, gs:\\" |
| PDUSESVC=<1|0> | ProfileDisks are handled by the Client Service |
| PDUSESYS=<1|0> | ProfileDisks are handled by the SYSTEM account |
| S3CRED="<CredsString>" | AWS S3 encrypted credentials |
| AZCRED="<CredsString>" | Azure encrypted credentials |
| AZCRED2="<CredsString>" | Secondary Azure encrypted credentials |
| GSCRED="<CredsString>" | Google Cloud Service encrypted credentials |
| SECPATH | Secondary paths for configurations, Client Settings, and Client Service credentials Example: SECPATH=“s3://b1/f1 > s3://b2/f1, gs://b3/f1 | \\n1\f2 > \\n2\f2, gs://b5/f2” |
| PROFSVC=<1|0> | Install the Profile Cleanup Service |
| ISOLATE=<1|0> | Installs the Windows Sandbox for FlexApp Isolation |
