Question 450
In the Northgate Collaboration pilot environment, a controlled verification is required for: A session host logs FSLogix profile attach failures because the configured VHDLocations value points to a nonexisting network folder. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
The FSLogix log records the intended VHDX attached and a user profile persists across a host change. This is an independently observable result of the targeted change: Configure the correct FSLogix Profile Container path and validate SMB resolution and share permissions on every host. It closes the specific Northgate Collaboration failure: A session host logs FSLogix profile attach failures because the configured VHDLocations value points to a nonexisting network folder.
Incorrect Answers
Users in the allowed group can launch the app while unauthorized users cannot see or open the masked application. This is evidence for a DIFFERENT remediation: Use supported FSLogix application masking rules and assignments to present authorized applications to the intended user groups. That remediation addresses: A pooled desktop hosts licensed applications that only certain groups may see, but all users find every app shortcut in the Start menu. It does not establish resolution of the Northgate Collaboration problem: A session host logs FSLogix profile attach failures because the configured VHDLocations value points to a nonexisting network folder. The required outcome here is: The FSLogix log records the intended VHDX attached and a user profile persists across a host change.
A recovered login attaches the authorized existing profile rather than creating an unrelated empty profile. This is evidence for a DIFFERENT remediation: Review concurrent session design, the profile container locking behavior, and proper session logoff or supported reattachment configuration. That remediation addresses: A pooled user experiences a temporary profile whenever their profile disk is already mounted to a disconnected host and lock handling is ignored. It does not establish resolution of the Northgate Collaboration problem: A session host logs FSLogix profile attach failures because the configured VHDLocations value points to a nonexisting network folder. The required outcome here is: The FSLogix log records the intended VHDX attached and a user profile persists across a host change.
A controlled storage-endpoint outage permits the approved profile workflow and the replicas reconcile after recovery. This is evidence for a DIFFERENT remediation: Design supported FSLogix Cloud Cache providers for the chosen locations and test failover and write consistency behavior. That remediation addresses: A remote branch must continue attaching profiles during a temporary outage of the primary FSLogix file share, but only one provider is configured. It does not establish resolution of the Northgate Collaboration problem: A session host logs FSLogix profile attach failures because the configured VHDLocations value points to a nonexisting network folder. The required outcome here is: The FSLogix log records the intended VHDX attached and a user profile persists across a host change.