Applies to: Nerdio Private Cloud (NPC) and Nerdio For Azure (NFA) customers/managed service partners (MSPs)
Nerdio view agents have been frequently reporting an issue that an open application is preventing previous user sessions from logging off. Some agents have observed that few users are able to logoff from their desktops. However, when they try to access the Nerdio Admin Portal (NAP) to reset their account, they get an error message "sorry something went wrong, we are unable to process your request". Please advise.
There's some application running on your VMware desktop which is preventing your user session from logging off. Generally, when you log off from a Windows desktop, it attempts to close all open user applications. If an application is either hung or presents a dialogue box requesting user input, the default behavior of Windows is to prompt the user how to handle the application. However, this behavior can cause the user session to hang or prevent the desktop from logging off, thus creating a deadlock situation.
Refer the link below for more details:
In order to resolve this issue, you need to update the Windows registry to force your user's desktop to shut down even if there are few open applications and no response from the user. You need to change your Windows registry setting to automatically end all open tasks. So next time when the user initiates a desktop logoff/shut down request, the OS will not wait for user response and allow the system to shut down, thus preventing a deadlock situation.
If you are an IT admin, you can update the Windows registry of the domain controller server (DC01) so that it applies to all desktops within the domain. This can be achieved by updating the Group Policy Object (GPO).
To enable auto-end tasks via GPO
This GPO will update/add a registry entry to auto end tasks when a user logs off or shuts down. There is still a small wait time where the user will be prompted to close open programs before logging off, but this setting will cause those programs to auto-close if no user input is given.
1. This policy can be applied to the existing "WS Computer GPO" if you want to apply for all machines. Otherwise, you can use GPO filtering to apply for specific machines as needed. Edit the existing policy or add a new one as needed:
2. The registry change can be made via "Computer Configuration \Preferences \Windows Settings \Registry"
a. Right click "Registry" then choose "New"→ "Registry Item"
3. Fill out the below options:
- Action: Update (this will create the entry for those that don’t have or update the value for those that do)
- Hive: HKEY_USERS
- Key Path:.DEFAULT\Control Panel\Desktop
- You can use the Key Path“ ...” button to specify the matching path from the registry of the machine you are logged into
- Value Name: uncheck default and specify ‘AutoEndTasks’
- Value Type: REG_SZ (string.DWORD will not work)
- Value Data:1
4. Once the GPO is configured and filtered as needed, run the command gpupdate/force from the server and the workstation to apply immediately. Logoff from the workstation may be required to complete.
This update to the GPO will prevent a deadlock and ensure that users can log off from their desktops in spite of open applications running on their desktops.