Product Version: 6.7.x
Expires on: 365 days from publish date
Updated: December 14, 2018
Using ProfileUnity as a Service when Parent image is not on the Domain
Install of this component (process) will fail as we can't grant the ProfileUnity Service account (domain account) user rights for logon as a service when machine is not in the Domain
You can follow similar process to install the Client tools as see in this KB
but without the .creds file used for ProfileUnity as a service. In this case for new install the Process would look like this
1. On netlogon or share where client tools reside and where your installing the ProfileUnity client tools from, copy out or rename the LwL.ProfileUnity.Client.Service.exe.creds file
2. Run the installer for ProfileUnity on Parent image
3. Rename the LwL.ProfileUnity.Client.Service.exe.creds back
4. Make sure the LwL.ProfileUnity.Client.Startup.exe is defined in the Computer GPO as part of normal ProfileUnity GPO settings
Once machines are created via the Pool (Citrix or Horizon View) the startup is set to look fir the .creds file and add the requisite components needed.
The normal process for upgrades can be found here:
The steps for upgrades is similar in respect to following Steps 1-4 above for handling the ProfileUnity as a Service creds file during install.