A path-based RemoteApp starts from its valid executable on every host but cannot find a configuration file referenced with a relative path. The same user can read the file and the app works when started with its expected local working folder. Which publication setting should be corrected?

✓ Correct answer

• The RemoteApp working directory.

The working directory controls where relative file references are resolved. The executable, user access and app behavior in the correct folder are already verified. Option explanations: A. The Windows App organizational account.: The app has already launched as the intended user, so discovery identity is not the reported problem. B. The user’s Azure subscription Owner assignment.: An Azure management role does not supply the missing process working directory. C. The RemoteApp working directory.: Setting the expected working directory addresses the specific relative-path difference. D. The host pool’s preferred application-group type.: Presentation preference does not change relative-path resolution inside a launched application. Sources: Publish applications with RemoteApp — https://learn.microsoft.com/azure/virtual-desktop/publish-applications-stream-remoteapp

Read the source reference