A desktop reset and a missing user-state path
A fictional pool assigns an available desktop to each user under a documented nonpersistent image-reset policy. One user stores a report in a location that the design expected to preserve through a profile container, but the supplied attachment log shows that the container was not mounted during that session. The desktop image is later reset, and the report is unavailable from the new session. A colleague says every pooled catalog is defective, while another proposes deleting the remaining user container so the next sign-in is clean. The task is a written review of assignment, reset timing and state ownership. No container is deleted and no recovery is attempted. The team must protect the existing evidence and determine the actual supported storage and recovery path.
1. Which distinct conditions must be considered?
Read the worked answer
Random assignment, the stated reset policy and successful user-state attachment are separate. The supplied failure is consistent with data being placed outside the intended persistent path; a pooled label alone does not diagnose every mechanism.
2. What should be checked before an authorized remedy?
Read the worked answer
Preserve the existing state, inspect the actual user identity, path, permissions, locks, attachment result and backup/recovery evidence, then test a narrow supported fix. Deleting the container can destroy useful data or evidence.