Problem:
When using the option to 'Force users to logoff' during recompose, the logoff process of ProfileUnity is interrupted - e.g. logs are cut short.
Symptoms:
When recomposing, possibly during refresh as well, and the option 'Force users to logoff' is selected as shown below, View provides a grace period of 60 seconds for remaining tasks to complete.
If the logoff process for ProfileUnity exceeds 60 seconds within an environment, it's halted due to what is essentially the equivalent of a power-off command being sent to the desktop.
In certain scenarios where the ProfileUnity logoff process does not exceed 60 seconds, interruption has been observed as well. This issue applies to disconnected sessions and active sessions where no message is provided to users, allowing them to gracefully logoff prior to the recompose initiating.
Possible Resolution(s):
This can be mitigated by selecting the alternative option, 'Wait for users to logoff, which will delay the recompose process for active until users logoff gracefully. For disconnected sessions, it's more a matter of session management - e.g. forcing disconnected sessions to logoff after a certain amount of time.
This can be implemented through Remote Desktop Session group policy or client settings available through the View administration console when creating or editing a desktop pool itself.
Option A - Group Policy
Enable and define an amount of time within the policy below:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits
Option B - View Desktop Pool Settings
Product: ProfileUnity
Product Version: 6.7.x and newer