Question:

“Could you provide guidance on resolving a persistent issue where, after applying the recommended updates and adding the ‘DeleteUserAppContainersOnLogoff’ DWORD, users are unable to log back into the server? The screen displays ‘Please wait for Remote Desktop Configuration’ indefinitely. The temporary solution has been to remove the DWORD via remote PowerShell through the Azure Console. Is there a known fix to this problem, as manually clearing the firewall rules every few months is not ideal?”

Answer:

In the realm of system administration, particularly when managing Remote Desktop Services (RDS) on Windows Server, applying updates and modifying registry settings are routine tasks that can sometimes lead to unexpected issues. A case in point involves the addition of the ‘DeleteUserAppContainersOnLogoff’ DWORD post-update, which has led to users being unable to log back into the server, with the screen indefinitely displaying “Please wait for Remote Desktop Configuration.”

The problem arises after ensuring that the server has the proper Knowledge Base updates (KB4490481 & KB5010196) and adding the aforementioned DWORD to the registry. This setting is intended to delete user app containers upon logoff, potentially improving system performance. However, an unintended consequence has been that neither the users nor the administrators can log back in, facing a persistent “Please wait” message.

Temporary Workarounds

The interim solution has involved using remote PowerShell through the Azure Console to remove the DWORD, which allows access to the server again. However, this is far from ideal as it requires manual intervention and does not address the root cause of the issue.

Seeking a Permanent Solution

A permanent fix would ideally involve a patch or an update from Microsoft that addresses this specific scenario. Until such a fix is released, system administrators are left with a few options:

1.

Script Automation

: Automate the process of clearing and resetting the firewall rules using PowerShell scripts. This can be scheduled to occur at regular intervals, minimizing manual intervention.

2.

Monitoring Tools

: Implement monitoring tools that can alert administrators when the issue occurs, allowing for quicker response times to reset the DWORD if necessary.

3.

Feedback to Microsoft

: Provide feedback to Microsoft through official channels, detailing the issue and the steps taken, to expedite a resolution in a future update.

Conclusion

While the current situation is not ideal, the community of system administrators can share insights and workarounds on platforms such as Reddit and Microsoft forums. Collaborative problem-solving and sharing experiences can lead to innovative solutions that mitigate the impact of such issues until a permanent fix is available. In the meantime, the focus should be on automating temporary fixes and providing detailed feedback to Microsoft to aid in the development of a comprehensive solution.