Product Version: 5.7
Expires on: 365 days from publish date
Updated: Mar 10, 2014
startup.vbs or LwL.ProfileUnity.Client.Startup.exe launched by GPO fail to install ProfileUnity on Physical (Persistent) Machine.
All or some of the symptoms might occur:
No ProfileUnity client installed on the desktop (s) after multiple restarts.
No ProfileUnity directory in c:\Program FIles
No ProfileUnity userinit values: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon is set to C:\windows\system32\userinit.exe
ProfileUnity's splash screen is displaying old version.
Last alternative way to deploy (after all other options fail - Startup.vbs fails to install ProfileUnity on the base image.) is to install ProfileUnity on client machines using "Task Scheduler" to run LwL.ProfileUnity.Client.Startup.exe under with specific Domain Admin rights.
Steps to follow to schedule a Task:
Edit current ProfileUntiy GPO (Group Policy Management Editor) and go to: Computer Configuration>Preferences>Control Panel Settings> Scheduled Tasks>New Task
- Action: Replace
- Name: PU Install
- Run: \\domain.com\netlogon\ProfileUnity\LwL.ProfileUnity.Client.Startup.exe
- Start in:
- Run as (Enabled)
- User Name: domain.com\Administrator (domain admin would be best account to use for this)
- Enabled (scheduled task runs as a specified time)
- Scheduled Task: At Logon
Save and close Group Policy Management Editor
Note: The scheduled task will not launch until next (subsequent) logon. Other task "options" may work also, and yield same end result.
Optional: With some user accounts additional settings might be required for script to execute properly.
"Log on as batch job" setting: Edit GPO>Computer Configuration>Policies>Windows Settings>Security Settings>Local Policies>User Rights Assignments.
Related KB: ProfileUnity does not run at logon