Follow

Startup.vbs or LwL.ProfileUnity.ClientStarup.exe fails to install ProfileUnity

Product: ProfileUnity-FlexApp

Product Version: 5.5

Expires on: 365 days from publish date

Updated: June 19, 2013

 

Problem:

I would like to install ProfileUnity on the Windows 7 base image (Gold) for my VMware Pool and when I run startup.vbs it is not installing. No ProfileUnity folder is created in Program Files. 

Note: Similar behavior may apply if launching startup.vbs using GPO (Group Policy Object)

 

Symptoms:

Missing files in "C:\Program Files\ProfileUnity after running startup.vbs and/or ProfileUnity is not launching when user is logging in. Startup.vbs is only for WIndows XP clients

 

Possible Resolution(s):

Note:  "LwL.ProfileUnity.Client.Startup.exe" does not work with Widnows XP clients.

In some environments do to security or other environmental/info structure settings, executing startup.vbs does not install ProfileUnity in base image or it does not install ProfileUnity when startup.vbs is executed using GPO when machine is booted up.

Perform list of following steps:

 

 

Note: "LwL.ProfileUnity.ClientStarup.exe" is usually located in "\\server\netlogon\profileunity" Directory.

Step 1 - A. Gold Image: Run "LwL.ProfileUnity.Client.Startup.exe" as Administrator (Check if "c:\Program FIles\ProfileUnity" directory was created and files within)

OR Step 2 - B. Edit the ProfileUnity GPO, Startup Script,

10.20.20.jpg

 

Step 3. Recompose/Reset/Restart your VDI desktops

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.