Troubleshooting issues with container locked or in use
Clean up invalid sessions
In some configurations, user sessions are signed out and a process or application prevents a proper sign out operation. This can leave artifacts on the file system or registry. During a sign in operation, these artifacts prevent the container from detaching and new sign ins are blocked. This can also occur if the session is terminated abruptly.
Recommendations
- There could be an operational issue in the environment. Prioritize any environmental or system issues that help solve the root cause versus the symptom.
- Setting: Enable
CleanupInvalidSessions
Concurrent or multiple connections to a single container
The default configuration of FSLogix prohibits a user from using their container in more than a single connection. When this situation is paired with the PreventLogonWithFailure setting, users can't sign in and receive an error from the FSLogix shell (frxshell.exe). FSLogix maintains an exclusive lock on the user's container while they're connected to a virtual machine and concurrent connections is disabled. Concurrent or multiple connections are supported in some configurations.