Follow

Elevation rules do not get updated on persistent desktops ( 6.0 and 6.0 U1 )

Product: ProfileUnity          

Product Version: 6.0 and 6.0 U1

Expires on: 365 days from publish date

Updated: September 30, 2014

 

Problem: 

Elevation rules do not get updated on persistent desktop.

 

Symptoms:

After making changes to elevation the INI file is updated, but lwl_elevation_service.xml does not resemble changes made to the INI file.

In the example below the INI file does not include an elevation rule, but the XML file still has the cmd.exe entry from previous configuration.

 

NOTE: The issue occurs when User goes from having 1 or more elevation entry, and then attempting to use zero entries. In other words, the lwl_elevation_service.xml is updated correctly, as long as there is 1 or more entries.

 

 

Possible Resolution(s):


There are several workarounds to this problem.

 

SOLUTION 1 - use for individual desktops (requires elevation service restart).

 

Update individual XML files by deleting undesirable entries.

1. Log in to the desktop as a an administrator.

2. Stop the elevation service

3. Go to "C:\Program Files\ProfileUnity\Elevation" and open "lwl_elevation_service.xml" and edit that file (image 1).

( image 1 )

 

4. Remove the undesired entries - in this case it will be a command line.

( image 2 )

 

 

 

SOLUTION 2 -For all users executing ProfileUnity (requires log-off)

1. Log in to the desktop as a an administrator.

2. Go to "C:\Program Files\ProfileUnity\Elevation" and open "lwl_elevation_service.xml" and edit that file (see image 1 above).

3. Remove the undesired entries - in this case it will be a command line (see image 2 above).

4. Once edited, copy the file to a share that can be accessed by all users. This file will later be used to update the existing outdated XML 

5. In order to copy/update the "lwl_elevation_service.xml" please create a App Launcher rule.

 

Filespec: xcopy.exe

Arguments: xcopy "\\server\path\lwl_elevation_service.xml" "C:\Program Files\ProfileUnity\Elevation\" /d /y /r /k

NOTE: Please change the server path in the Arguments line.

Timing: During configuration execution

Frequency: One Time (User)

UID: elevationXMLupdate

Tracking: Your storage path

 

Example shown below (image 3)

 

( image 3 )

6. Update the INI file.

7. Log off and log back in to see the updated XML file.

 

 

 

SOLUTION 3 - Alternatively (for all users - requires reboot)

1. Log in to the desktop as a an administrator.

2. Go to "C:\Program Files\ProfileUnity\Elevation" and open "lwl_elevation_service.xml" and edit that file (see image 1 above).

3. Once edited, replace the the existing lwl_elevation_service.xml usually located in "\\Server\netlogon\ProfileUnity\elevation.zip\" with the updated XML edited in point 2.

4. If startup.vbs is used in a Profile Unity logon script, it is possible to force update of the xml file with the increment of the version # in client.net.vbs in the same location as client.net.zip by editing the file client.net.vbs in an elevated text editor:

            ClientDotNET_Version="5.7.298-2014-02-13_15-30-10"

            Change to:

            ClientDotNET_Version="5.7.299-2014-02-13_15-30-10"

   Then save the file to it's original location. This setting change will force startup.vbs to reinstall the client on the desktop pool AFTER the Desktops restart.

2. Reboot all desktops

 

SOLUTION 4 - Alternatively (for all users - requires reboot)

1. Edit LwL.ProfileUnity.Client.Startup.exe.config that is usually located in a ProfileUnity folder on netlogon.

For example, %logonserver%\Profileunity\LwL.ProfileUnity.Client.Startup.exe.config

2. Edit the configuration with a notepad or any other tool and change the shown value (picture 4)

from

<value>6.0.5305-e331c1d</value>     

to

<value>6.0.5368-e331c1d</value>

NOTE: The values might be different depending on a version of ProfileUnity. If the values are different then shown here, please make sure that the original values are lower the the changed values. This will ensure the elevation files are reset with a "new version" files.

 

( picture 4 )

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

0 Comments

Article is closed for comments.