Issue 

• To allocate a shared folder to all domain users using Amazon FSx in AppStream 2.0, a batch file was created and linked to Group Policy so that it would execute uniformly for all users upon logon. 

• However, the shared folder is not immediately connected when all users log on. While some users see the shared folder as soon as the AppStream 2.0 session starts, others do not see it right away and must manually execute the batch file for it to appear. 

Resolution 

There is a 'wait time' that can be configured before user applications launch and the streaming session begins, allowing time for scripts to complete.

If the script completes successfully, the user can load their session and see the shared folder. However, if the user cannot see the folder after the session starts, one possible reason is that the maximum wait time expired before the shared folder mapping was completed.

Even if the script wait time expires, it does not prevent the user from starting their session. This means that running the batch script manually after the application/desktop session begins can still mount the folder as observed in the issue above.

Therefore, it is recommended to increase the wait time value and test again.

(Ex. Change "waitingTime": 30 to 60 seconds.)