Product: ProfileUnity-FlexApp
Product Version: 5.5+
Expires on: 365 days from publish date
Updated: September 11, 2013
Problem:
ProfileUnity does not run at logon
Symptoms:
You don't see the ProfileUnity splash screen at login.
Possible Resolution(s):
If using Windows 7 or newer:
When installing ProfileUnity using GPO (standard configuration):
1. Open the Group Policy Management Console.
2. Edit the ProfileUnity GPO you are using and go to Computer Configuration -> Policies -> Windows Settings -> Scripts (Startup/Shutdown) -> Startup.
3. Replace this line:
Script Name: %systemroot%\system32\wscript.exe
Script Parameters: \\<domain name>\netlogon\ProfileUnity\startup.vbs //b
with
Script Name: \\<domain name>\netlogon\ProfileUnity\LwL.ProfileUnity.Client.Startup.exe
Script Parameters: (none needed)
4. Go to User Configuration -> Policies -> Windows Settings -> Scripts (Logon/Logoff) -> Logoff.
5. Replace this line:
Script Name: %systemroot%\system32\wscript.exe
Script Parameters: \\<domain name>\netlogon\ProfileUnity\logoff.vbs //b
with
Script Name: \\<domain name>\netlogon\ProfileUnity\LwL.ProfileUnity.Client.Logoff.exe
Script Parameters: (none needed)
2. Check C:\Program Files\ProfileUnity to make sure the client files are there.
3. Run regedit and look in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
vMware environment: The "userinit" value should contain "C:\Program Files\ProfileUnity\userinit.exe"
Example:
Citrix environment: The "AppSetup" value should contain: "C:\Program Files\ProfileUnity\ctxinit.exe"
Example:
4. Go to HKEY_CURRENT_USER\Software\Liquidware Labs\ProfileUnity. Verify if:
a. It exists
b. the ini file path here is correct (Default location is \\domain\netlogon\profileunity)
c. there is a sub-key called Portability (this won't exist if there are no portability settings in your configuration)
5. Check for existence of *.ini and profileunity.lic inpath to ini (4.b)
6. Check if the user is part of the Security Group listed inside profileunity.lic (If time bound unlimited license (rare) this security group is unnecessary).
7. Check if your ProfileUnity configuration has "Require group membership" selected (Open PU console>Configuration Management>Main)
8. Check if there are any GPO policy that could be restricting ProfileUnity.
9. Check Event viewer for GPO time / time mismatch sync issues. If Machine and DC/ESX host is out of time sync GPO's will NOT apply.
10. Verify that the ProfileUnity client is not older version than "Default.ini" Configuration. (Default.ini is downloaded from ProfileUnity Console)
11. Verify that ProfileUnity users are part of "Authenticated Users" Security Group if they are not follow these steps:
Edit ProfileUnity GPO and on first tab (Scope) edit "Security Filtering", add "Domain Users" or "ProfileUnity" Security Group
Example:
12. If the user's are located in separate OU (AD) than there are 2 options:
- Apply ProfileUnity GPO to OU where user's are located (Caution: It will affect all users in OU)
- Turn on "User Group Policy loopback processing mode"
Edit ProfileUnity GPO go to: Computer Configuration>Policies>Administrative Templates>System>Group Policy
"User Group Policy loopback processing mode" Setting= Enabled Mode=Replace
13. KB: How to check if logoff.vbs and startup.vbs scripts settings were pushed down through GPO
14. KB: After upgrade portability is not processing
Related KB: List of GPO security settings which prevent ProfileUnity from functioning properly
Related KB: Startup.vbs fails to install ProfileUnity on the client machine
Related KB: logoff.vbs will not run during logoff thus not saving any settings
0 Comments