By default, the ProfileUnity Client installs to the NETLOGON share on your domain controller. This path is recommended but is not required. The NETLOGON share is a DFS replicated path that is available on all properly functioning domain controllers. Installing ProfileUnity to this path prevents a single point of failure. ProfileUnity can operate if at least one domain controller is online. Additionally, this path allows ProfileUnity to scale through load distribution across domain controllers.
If you choose to install the ProfileUnity client to an alternative UNC path, you will need to complete the following steps:
- Specify the alternative UNC path when running the Client installer.
- Specify the alternative UNC path when manually configuring the Group Policy. You will need to specify this path for the startup script, the INI File Path, and the logoff script.
Another alternative is to use cloud storage. If you are planning to set up your cloud storage for use with ProfileUnity, this should be done before using the ProfileUnity Management Console. The Using Cloud Storage Guide explains the process in detail. Pay close attention to the cloud storage related instructions throughout this guide, especially when using the Guided Configuration Wizard and using the section on manually configuring your GPO settings.
Note: The Group Policy startup script will execute using the computer’s credentials. The ProfileUnity Client and the Group Policy logoff script will execute using the user’s credentials. The recommended way to set up the alternative UNC path is to allow either Authenticated Users or Everyone read access. This permission setup will allow both the computer and the user to access ProfileUnity.
