Enable Your AppStream 2.0 Users to Configure Their Regional Settings

Note

Enabling users to configure regional settings is currently not supported in Linux-based streaming sessions or streaming sessions powered by multi-session fleets.

Users can configure their Amazon AppStream 2.0 Windows streaming sessions to use settings that are specific to their location or language. In particular, users can configure the following settings:

• Time zone — Determines the system time used by Windows and any applications that rely on the operating system time. AppStream 2.0 makes available the same options for this setting as the Windows Server version used in your fleet.

• Locale (also known as culture) — Determines the conventions used by Windows and any applications that query the Windows culture when formatting dates, numbers, or currencies or when sorting strings. For a list of locales that AppStream 2.0 supports, see Supported Locales.

• Input method — Determines the keystroke combinations that can be used to input characters in another language.

If users change regional settings during their streaming sessions, the changes are applied to any future streaming sessions in the same AWS Region.

Note

For guidance that you can provide your users to help them get started with configuring their regional settings, see Configure Regional Settings.

Supported Locales

AppStream 2.0 supports the following locales:

Locale	Language culture name
Chinese (Simplified, China)	zh-CN
Chinese (Simplified, Singapore)	zh-SG
Chinese (Traditional)	zh-TW
Dutch (The Netherlands)	nl-NL
English (Australia)	en-AU
English (Canada)	en-CA
English (United Kingdom)	en-GB
English (United States)	en-US
French (France)	fr-FR
German (Germany)	de-DE
Italian (Italy)	it-IT
Japanese (Japan)	ja-JP
Korean (Korea)	ko-KR
Portuguese (Brazil)	pt-BR
Spanish (Spain, International Sort)	es-ES
Thai (Thailand)	th-TH

Enable Regional Settings for Your AppStream 2.0 Users

To enable users to configure regional settings for a given stack during their AppStream 2.0 streaming sessions, your stack must be associated with a fleet based on an image that uses a version of the AppStream 2.0 agent released on or after June 6, 2018. For more information, see AppStream 2.0 Agent Release Notes. Additionally, your image must have Windows PowerShell 5.1 or later installed. Images created from AppStream 2.0 base images published on or after June 12, 2018 meet both criteria. Images created from AppStream 2.0 base images published before June 12, 2018 do not have Windows PowerShell 5.1 by default.

To update an existing image to include Windows PowerShell 5.1

1. Launch a new image builder using your existing image as the base image by doing the following:

   1. In the left navigation pane in the AppStream 2.0 console, choose Images.

   2. Choose the Image Builder tab, Launch Image Builder, and then select your existing image.

   3. If you are prompted to update the AppStream 2.0 agent when you launch the image builder, select the check box, and then choose Start.

2. After your image builder is running, connect to it and sign in with an account that has local administrator permissions. To do so, do either of the following:

   • Use the AppStream 2.0 console (for web connections only)

   • Create a streaming URL (for web or AppStream 2.0 client connections)

     Note

     If the image builder that you want to connect to is joined to an Active Directory domain and your organization requires smart card sign in, you must create a streaming URL and use the AppStream 2.0 client for the connection. For information about smart card sign in, see Smart Cards.

3. From the image builder desktop, open Windows PowerShell. Choose the Windows Start button, and then choose Windows PowerShell.

4. At the PowerShell command prompt, type the command $PSVersionTable to determine the version of Windows PowerShell that is installed on your image builder. If your image builder does not include Windows PowerShell 5.1 or later, use the following steps to install it.

5. Open a web browser and follow the steps in Install and Configure WMF 5.1 in the Microsoft documentation, making sure that you download the Windows Management Framework (WMF) 5.1 package for Windows Server 2012 R2. WMF 5.1 includes Windows PowerShell 5.1.

6. At the end of the WMF 5.1 installation process, the installer prompts you to restart your computer. Choose Restart Now to restart the image builder.

7. Wait about 10 minutes before logging in to your image builder, even though AppStream 2.0 prompts you to do so immediately. Otherwise, you might encounter an error.

8. After logging in to your image builder again, open Windows PowerShell and type the command $PSVersionTable to confirm that Windows PowerShell 5.1 is installed on your image builder.

9. Use the image builder to create a new image. This new image now includes the latest versions of the AppStream 2.0 agent and Windows PowerShell.

10. Update your fleet to use the new image by doing the following:

    1. In the left navigation pane in the AppStream 2.0 console, choose Fleets, and then choose the fleet associated with the stack for which you want to enable regional settings.

    2. On the Fleet Details tab, choose Edit.

    3. In Image name, choose the new image to use for the fleet.

For more information about using image builders to create images, see Tutorial: Create a Custom AppStream 2.0 Image by Using the AppStream 2.0 Console.