Amazon WorkSpaces Application Manager
Administration Guide

User Account Issues

The following are possible issues user account issues that you might have when packaging an application.

My roaming user accounts and folder redirection does not work

Amazon WorkSpaces Application Manager Studio allows the HKEY_CURRENT_USER registry settings and the %appdata% folder contents for roaming profile support. Any limitations with Windows roaming profiles still apply.

If you are using folder redirection to a network share through a mapped drive or a UNC path, set the disposition of the folder and the files to the recommended Installed-permanent (layer 1) or Installed-temporary (layer 2). The application will not start if the files or folders are set to Virtual-integrated (layer 3) or Virtual-isolated (layer 4).

For example, if the %appdata% folder is being redirected to \\fileshare\user1\appdata\, the template folder ?roamingappdata? must only contain files and folders with Installed-permanent (layer 1) or Installed-temporary (layer 2) disposition. Redirection to another local disk supports files set to the Virtual-integrated (layer 3) or Virtual-isolated (layer 4) disposition.


With folder redirection, the network folder must exist prior to activating the application. For example, if %appdata% is mapped to n:\{username}\appdata, the appdata folder must already exist on the server.

To enable roaming profile support

  1. In Amazon WorkSpaces Application Manager Studio, choose the Project tab on the top of the project pane.

  2. Under 3. Optional settings, choose Settings.

  3. In the Settings dialog box, choose Sandboxing, Allow Windows to roam application settings under Application settings, and OK.

How do I create unique user accounts?

Some applications create a special user account when you install them. Amazon WorkSpaces Application Manager Studio cannot capture user accounts because they are not transferable between operating systems. You need to create a Configurable AppEvent to replicate the user accounts and password on the host computer programmatically when Amazon WorkSpaces Application Manager Studio installs the application.


User accounts may appear as a security identifier (SID) in the registry. For example, S-1-5-18 is the local system account. For more information, go to Well-known security identifiers in Windows operating systems in the Microsoft Knowledge Base.