Follow

Client exe hangs open on XenApp or XenDesktop long after app is opened

Product: ProfileUnity

Product Version: All  (Set to be fixed in v6.7)

Expires on: 365 days from publish date

Updated: December 2, 2016


Problem:

LwL.ProfileUnity.Client.exe and trigger exe stay open for some time after client has completed and the XenApp or XenDesktop has loaded for the user.  Postflight logs will show 0 bytes in size until Client exe exists on its own.  Once the postflight logs are populated after waiting long enough you will see that the delay is likely in the printers postflight log where its retrying to connect to each printer that is already mapped from the client machine by Citrix Print Services.  (Enable debug logging as needed:  https://liquidwarelabs.zendesk.com/hc/en-us/articles/210632143-ProfileUnity-6-5-How-to-enable-debug-logging)

 

Resolution:

Option #1 - Use the DisabledFeature HKCU reg key setting via a User GPO to disable the Client.NET Printers module altogether if its not otherwise in-use: https://liquidwarelabs.zendesk.com/hc/en-us/articles/210637663-List-of-features-that-can-be-disable-with-a-DisableFeature-registry-in-ProfileUnity-registry-module-

Option #2 - Edit LwL.ProfileUnity.Client.exe.config in client.net.zip in NETLOGON or on your master image or on each individual persistent machine and change the following entries:

<setting name="PrintersMaxAttemptsToAdd" serializeAs="String">
        <value>20</value>  <--- This value should be reduced
</setting>
<setting name="PrintersWaitBetweenRetriesInMs" serializeAs="String">
        <value>1000</value>  <--- This value should be reduced
</setting>

How low you set them depends on your environment.  If you want to lower the time taken for the postflight printer work to a minimum, then set each value to 1.

**If you're using a startup GPO to deploy to non-persistent farm, then simply edit the config file in the client.net.zip on the NETLOGON share and then recompose the farm for the change to propagate.  If you have the client installed in your base image, then edit the config file in the install directory and push the new image to the farm.  If you have persistent machines, you will need to make the change on each machine.**

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

0 Comments

Article is closed for comments.