AWS appstream2 documentation change
Summary
Renamed all instances of 'AppStream 2.0' to 'WorkSpaces Applications' throughout the documentation, including client names, URLs, and configuration references.
Security assessment
The changes appear to be a rebranding effort from 'AppStream 2.0' to 'WorkSpaces Applications' without altering security configurations or introducing new security features. No vulnerabilities, mitigations, or security enhancements are mentioned in the diff.
Diff
diff --git a/appstream2/latest/developerguide/install-client-configure-settings.md b/appstream2/latest/developerguide/install-client-configure-settings.md index 684bc3f88..d6030658f 100644 --- a//appstream2/latest/developerguide/install-client-configure-settings.md +++ b//appstream2/latest/developerguide/install-client-configure-settings.md @@ -3 +3 @@ -[Documentation](/index.html)[Amazon AppStream 2.0](/appstream2/index.html)[Administration Guide](what-is-appstream.html) +[Documentation](/index.html)[Amazon WorkSpaces Applications](/appstream2/index.html)[Administration Guide](what-is-appstream.html) @@ -5 +5 @@ -Download the Enterprise Deployment ToolInstall the AppStream 2.0 Client and USB DriverAccessing AppStream 2.0 with the AppStream 2.0 ClientSet the StartURL Registry Value for AppStream 2.0 Client UsersSet the TrustedDomains Registry Value to Enable Other Domains for the AppStream 2.0 Client Create the AS2TrustedDomains DNS TXT Record to Enable Your Domain for the AppStream 2.0 Client Without Registry ChangesDisable DNS TXT Record Lookup for Trusted DomainsChoose Whether to Disable Automatic Client UpdatesChoose Whether to Disable On-Demand Diagnostic Log UploadsChoose Whether to Disable Native Application ModeChoose Whether to Disable Local Printer RedirectionChoose Whether to Disable Smart Card RedirectionConfigure Additional AppStream 2.0 Client Settings for Your UsersUsing Group Policy to Customize AppStream 2.0 Client Experience +Download the Enterprise Deployment ToolInstall the WorkSpaces Applications Client and USB DriverAccessing WorkSpaces Applications with the WorkSpaces Applications ClientSet the StartURL Registry Value for WorkSpaces Applications Client UsersSet the TrustedDomains Registry Value to Enable Other Domains for the WorkSpaces Applications Client Create the AS2TrustedDomains DNS TXT Record to Enable Your Domain for the WorkSpaces Applications Client Without Registry ChangesDisable DNS TXT Record Lookup for Trusted DomainsChoose Whether to Disable Automatic Client UpdatesChoose Whether to Disable On-Demand Diagnostic Log UploadsChoose Whether to Disable Native Application ModeChoose Whether to Disable Local Printer RedirectionChoose Whether to Disable Smart Card RedirectionConfigure Additional WorkSpaces Applications Client Settings for Your UsersUsing Group Policy to Customize WorkSpaces Applications Client Experience @@ -7 +7 @@ Download the Enterprise Deployment ToolInstall the AppStream 2.0 Client and USB -# Tutorial: Install the Amazon AppStream 2.0 Client And Customize the Client Experience for Your Users +# Tutorial: Install the Amazon WorkSpaces Applications Client And Customize the Client Experience for Your Users @@ -9 +9 @@ Download the Enterprise Deployment ToolInstall the AppStream 2.0 Client and USB -The following sections describe how to install the AppStream 2.0 client and customize the client experience for your users. If you plan to download and install the client for your users, first download the Enterprise Deployment Tool. You can then run PowerShell scripts to install the AppStream 2.0 client and configure client settings remotely. +The following sections describe how to install the WorkSpaces Applications client and customize the client experience for your users. If you plan to download and install the client for your users, first download the Enterprise Deployment Tool. You can then run PowerShell scripts to install the WorkSpaces Applications client and configure client settings remotely. @@ -13 +13 @@ The following sections describe how to install the AppStream 2.0 client and cust -Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not supported. +Using the Enterprise Deployment Tool with the WorkSpaces Applications macOS client is not supported. @@ -19 +19 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not - * Install the AppStream 2.0 Client and USB Driver + * Install the WorkSpaces Applications Client and USB Driver @@ -21 +21 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not - * Accessing AppStream 2.0 with the AppStream 2.0 Client + * Accessing WorkSpaces Applications with the WorkSpaces Applications Client @@ -23 +23 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not - * Set the StartURL Registry Value for AppStream 2.0 Client Users + * Set the StartURL Registry Value for WorkSpaces Applications Client Users @@ -25 +25 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not - * Set the TrustedDomains Registry Value to Enable Other Domains for the AppStream 2.0 Client + * Set the TrustedDomains Registry Value to Enable Other Domains for the WorkSpaces Applications Client @@ -27 +27 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not - * Create the AS2TrustedDomains DNS TXT Record to Enable Your Domain for the AppStream 2.0 Client Without Registry Changes + * Create the AS2TrustedDomains DNS TXT Record to Enable Your Domain for the WorkSpaces Applications Client Without Registry Changes @@ -41 +41 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not - * Configure Additional AppStream 2.0 Client Settings for Your Users + * Configure Additional WorkSpaces Applications Client Settings for Your Users @@ -43 +43 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not - * Using Group Policy to Customize AppStream 2.0 Client Experience + * Using Group Policy to Customize WorkSpaces Applications Client Experience @@ -50 +50 @@ Using the Enterprise Deployment Tool with the AppStream 2.0 macOS client is not -The Enterprise Deployment Tool includes the AppStream 2.0 client installation files and a Group Policy administrative template. +The Enterprise Deployment Tool includes the WorkSpaces Applications client installation files and a Group Policy administrative template. @@ -52 +52 @@ The Enterprise Deployment Tool includes the AppStream 2.0 client installation fi - 1. To download the Enterprise Deployment Tool, on the bottom right of the [AppStream 2.0 supported clients](https://clients.amazonappstream.com) page, select the **Enterprise Deployment Tool** link. This link opens a .zip file that contains the required files for the latest version of the tool. + 1. To download the Enterprise Deployment Tool, on the bottom right of the [WorkSpaces Applications supported clients](https://clients.amazonappstream.com) page, select the **Enterprise Deployment Tool** link. This link opens a .zip file that contains the required files for the latest version of the tool. @@ -56 +56 @@ The Enterprise Deployment Tool includes the AppStream 2.0 client installation fi - * AppStream 2.0 client installer (AmazonAppStreamClientSetup_<version>.msi) — Installs the AppStream 2.0 client. + * WorkSpaces Applications client installer (AmazonAppStreamClientSetup_<version>.msi) — Installs the WorkSpaces Applications client. @@ -58 +58 @@ The Enterprise Deployment Tool includes the AppStream 2.0 client installation fi - * AppStream 2.0 USB driver installer (AmazonAppStreamUsbDriverSetup_<version>.exe) — Installs the AppStream 2.0 USB driver that is required to use USB devices with applications streamed through AppStream 2.0. + * WorkSpaces Applications USB driver installer (AmazonAppStreamUsbDriverSetup_<version>.exe) — Installs the WorkSpaces Applications USB driver that is required to use USB devices with applications streamed through WorkSpaces Applications. @@ -60 +60 @@ The Enterprise Deployment Tool includes the AppStream 2.0 client installation fi - * AppStream 2.0 client Group Policy administrative template (as2_client_config.adm) — Lets you configure the AppStream 2.0 client through Group Policy. + * WorkSpaces Applications client Group Policy administrative template (as2_client_config.adm) — Lets you configure the WorkSpaces Applications client through Group Policy. @@ -65 +65 @@ The Enterprise Deployment Tool includes the AppStream 2.0 client installation fi -## Install the AppStream 2.0 Client and USB Driver +## Install the WorkSpaces Applications Client and USB Driver @@ -67 +67 @@ The Enterprise Deployment Tool includes the AppStream 2.0 client installation fi -After you download the AppStream 2.0 client installation files, run the following PowerShell script on users' computers to install the AppStream 2.0 client installation file, AppStreamClient.exe, and the USB driver silently. +After you download the WorkSpaces Applications client installation files, run the following PowerShell script on users' computers to install the WorkSpaces Applications client installation file, AppStreamClient.exe, and the USB driver silently. @@ -78 +78 @@ To run this script, you must be logged in to the applicable computer with Admini -After you install the Enterprise Deployment Tool on a user's computer, the AppStream 2.0 client is installed as follows: +After you install the Enterprise Deployment Tool on a user's computer, the WorkSpaces Applications client is installed as follows: @@ -80 +80 @@ After you install the Enterprise Deployment Tool on a user's computer, the AppSt - 1. The AppStream 2.0 client installation file is copied to the following path on the user's computer: C:\Program Files (x86)\Amazon AppStream 2.0 Client Installer\AppStreamClient.exe. + 1. The WorkSpaces Applications client installation file is copied to the following path on the user's computer: C:\Program Files (x86)\Amazon WorkSpaces Applications Client Installer\AppStreamClient.exe. @@ -82 +82 @@ After you install the Enterprise Deployment Tool on a user's computer, the AppSt - 2. The first time the user logs on to their computer after the Enterprise Deployment Tool is installed, the AppStream 2.0 client is installed. + 2. The first time the user logs on to their computer after the Enterprise Deployment Tool is installed, the WorkSpaces Applications client is installed. @@ -86 +86 @@ After you install the Enterprise Deployment Tool on a user's computer, the AppSt -If the Enterprise Deployment Tool detects that the AppStream 2.0 Client folder, **AppStreamClient** , already exists in **%localappdata%** , the tool does not install the client. +If the Enterprise Deployment Tool detects that the WorkSpaces Applications Client folder, **AppStreamClient** , already exists in **%localappdata%** , the tool does not install the client. @@ -91 +91 @@ If the Enterprise Deployment Tool detects that the AppStream 2.0 Client folder, -If a user uninstalls the AppStream 2.0 client, the client isn’t installed again until you update the AppStream 2.0 Enterprise Deployment Tool. +If a user uninstalls the WorkSpaces Applications client, the client isn’t installed again until you update the WorkSpaces Applications Enterprise Deployment Tool. @@ -93 +93 @@ If a user uninstalls the AppStream 2.0 client, the client isn’t installed agai -## Accessing AppStream 2.0 with the AppStream 2.0 Client +## Accessing WorkSpaces Applications with the WorkSpaces Applications Client @@ -95 +95 @@ If a user uninstalls the AppStream 2.0 client, the client isn’t installed agai -By default, when users launch the AppStream 2.0 client, they can connect only to URLs that include the AppStream 2.0 domain or domains that include a DNS TXT record that enables the connection. You can let client users access domains other than the AppStream 2.0 domain by doing any of the following: +By default, when users launch the WorkSpaces Applications client, they can connect only to URLs that include the WorkSpaces Applications domain or domains that include a DNS TXT record that enables the connection. You can let client users access domains other than the WorkSpaces Applications domain by doing any of the following: @@ -108 +108 @@ By default, when users launch the AppStream 2.0 client, they can connect only to -The AppStream 2.0 client and DNS TXT record configuration do not prevent users from using other connection methods to access the domains or URLs that you specify. For example, users can access specified domains or URLs by using a web browser, if they have network access to the domains or URLs. +The WorkSpaces Applications client and DNS TXT record configuration do not prevent users from using other connection methods to access the domains or URLs that you specify. For example, users can access specified domains or URLs by using a web browser, if they have network access to the domains or URLs. @@ -110 +110 @@ The AppStream 2.0 client and DNS TXT record configuration do not prevent users f -## Set the StartURL Registry Value for AppStream 2.0 Client Users +## Set the StartURL Registry Value for WorkSpaces Applications Client Users @@ -112 +112 @@ The AppStream 2.0 client and DNS TXT record configuration do not prevent users f -You can use the `StartUrl` registry value to set a custom URL that is populated in the AppStream 2.0 client when a user launches the client. You can create this HKLM registry key while installing the client so that your users don’t need to specify a URL when they launch the client. +You can use the `StartUrl` registry value to set a custom URL that is populated in the WorkSpaces Applications client when a user launches the client. You can create this HKLM registry key while installing the client so that your users don’t need to specify a URL when they launch the client. @@ -114 +114 @@ You can use the `StartUrl` registry value to set a custom URL that is populated -After the AppStream 2.0 client is installed, you can run the following PowerShell script to create this registry key, or you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After the WorkSpaces Applications client is installed, you can run the following PowerShell script to create this registry key, or you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -128 +128 @@ To run this script, you must be logged in to the applicable computer with Admini -## Set the TrustedDomains Registry Value to Enable Other Domains for the AppStream 2.0 Client +## Set the TrustedDomains Registry Value to Enable Other Domains for the WorkSpaces Applications Client @@ -130 +130 @@ To run this script, you must be logged in to the applicable computer with Admini -You can configure the AppStream 2.0 client to connect to URLs in trusted domains that you specify. For example, you might want to let users connect to any URL in your organizational domain or to any URL in one or more of your IdP domains. When you specify the URL, use the following format: *.`example`-`idp`.`com`. +You can configure the WorkSpaces Applications client to connect to URLs in trusted domains that you specify. For example, you might want to let users connect to any URL in your organizational domain or to any URL in one or more of your IdP domains. When you specify the URL, use the following format: *.`example`-`idp`.`com`. @@ -132 +132 @@ You can configure the AppStream 2.0 client to connect to URLs in trusted domains -You can specify a list of trusted domains in a comma-separated format. Add this list as a registry value to the AppStream 2.0 `TrustedDomains` HKLM registry key. We recommend that you create this registry key and specify the list of trusted domains when you install the AppStream 2.0 client or, if you are using Microsoft Active Directory, through Group Policy. That way, your users can connect to a URL in any trusted domain immediately after the client is installed. +You can specify a list of trusted domains in a comma-separated format. Add this list as a registry value to the WorkSpaces Applications `TrustedDomains` HKLM registry key. We recommend that you create this registry key and specify the list of trusted domains when you install the WorkSpaces Applications client or, if you are using Microsoft Active Directory, through Group Policy. That way, your users can connect to a URL in any trusted domain immediately after the client is installed. @@ -134 +134 @@ You can specify a list of trusted domains in a comma-separated format. Add this -After the AppStream 2.0 client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After the WorkSpaces Applications client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -158 +158 @@ The following are requirements and considerations for formatting trusted domain - * The * applies to the subdomain level that includes the *, and to all the subdomains of that subdomain. For example, if an entry is named *.example.com, the AppStream 2.0 client allows zenith.example.com, acme.zenith.example.com, and pinnacle.acme.zenith.example.com. + * The * applies to the subdomain level that includes the *, and to all the subdomains of that subdomain. For example, if an entry is named *.example.com, the WorkSpaces Applications client allows zenith.example.com, acme.zenith.example.com, and pinnacle.acme.zenith.example.com. @@ -163 +163 @@ The following are requirements and considerations for formatting trusted domain -## Create the AS2TrustedDomains DNS TXT Record to Enable Your Domain for the AppStream 2.0 Client Without Registry Changes +## Create the AS2TrustedDomains DNS TXT Record to Enable Your Domain for the WorkSpaces Applications Client Without Registry Changes @@ -173 +173 @@ For more information about setting up the DNS record, see [Enable your organizat -When you create DNS TXT records, any users can stream from enabled domains that are not included in the `StartURL` or `TrustedDomains` registry values. The AppStream 2.0 client and DNS TXT record configuration do not prevent users from using other connection methods to access the domains or URLs that you specify. For example, users can access specified domains or URLs by using a web browser, if they have network access to the domains or URLs. +When you create DNS TXT records, any users can stream from enabled domains that are not included in the `StartURL` or `TrustedDomains` registry values. The WorkSpaces Applications client and DNS TXT record configuration do not prevent users from using other connection methods to access the domains or URLs that you specify. For example, users can access specified domains or URLs by using a web browser, if they have network access to the domains or URLs. @@ -177 +177 @@ When you create DNS TXT records, any users can stream from enabled domains that -The following is an example of a DNS TXT record configuration. With the configuration for this example, users can launch the AppStream 2.0 client and connect to appstream.example.com or appstream-dev.example.com. However, they cannot connect to example.com. +The following is an example of a DNS TXT record configuration. With the configuration for this example, users can launch the WorkSpaces Applications client and connect to appstream.example.com or appstream-dev.example.com. However, they cannot connect to example.com. @@ -204 +204 @@ Keep in mind the following requirements and considerations for creating a DNS TX - * The * applies to the subdomain level that includes the *, and to all the subdomains of that subdomain. For example, if an entry is named *.example.com, the AppStream 2.0 client allows connections to the following domains: zenith.example.com, acme.zenith.example.com, and pinnacle.acme.zenith.example.com. + * The * applies to the subdomain level that includes the *, and to all the subdomains of that subdomain. For example, if an entry is named *.example.com, the WorkSpaces Applications client allows connections to the following domains: zenith.example.com, acme.zenith.example.com, and pinnacle.acme.zenith.example.com. @@ -211 +211 @@ Keep in mind the following requirements and considerations for creating a DNS TX -By default, when users launch the AppStream 2.0 and specify a URL that is not an AppStream 2.0 domain, the client performs a DNS TXT record lookup. The lookup is performed on the second-level domain of the URL so that the client can determine whether the domain is included in the `AS2TrustedDomains` list. This behavior lets users connect to domains that are not specified in the `StartURL` or `TrustedDomains` registry keys, or AppStream 2.0 domains. +By default, when users launch the WorkSpaces Applications and specify a URL that is not an WorkSpaces Applications domain, the client performs a DNS TXT record lookup. The lookup is performed on the second-level domain of the URL so that the client can determine whether the domain is included in the `AS2TrustedDomains` list. This behavior lets users connect to domains that are not specified in the `StartURL` or `TrustedDomains` registry keys, or WorkSpaces Applications domains. @@ -213 +213 @@ By default, when users launch the AppStream 2.0 and specify a URL that is not an -You can disable this behavior by setting the value for the `DnsTxtRecordQueryDisabled` registry key to `true`. You can create this registry key when you install the AppStream 2.0 client. That way, the client connects only to URLs that are specified by the `StartURL` or `TrustedDomains` registry keys. +You can disable this behavior by setting the value for the `DnsTxtRecordQueryDisabled` registry key to `true`. You can create this registry key when you install the WorkSpaces Applications client. That way, the client connects only to URLs that are specified by the `StartURL` or `TrustedDomains` registry keys. @@ -215 +215 @@ You can disable this behavior by setting the value for the `DnsTxtRecordQueryDis -After the AppStream 2.0 client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After the WorkSpaces Applications client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -229 +229 @@ To run this script, you must be logged in to the applicable computer with Admini -By default, when a new version of the AppStream 2.0 client is available, the client updates automatically to the latest version. You can disable automatic updates by setting the value for the `AutoUpdateDisabled` registry key to `true`. You can create this registry key when you install the AppStream 2.0 client. That way, the client is not updated automatically whenever a new version is available. +By default, when a new version of the WorkSpaces Applications client is available, the client updates automatically to the latest version. You can disable automatic updates by setting the value for the `AutoUpdateDisabled` registry key to `true`. You can create this registry key when you install the WorkSpaces Applications client. That way, the client is not updated automatically whenever a new version is available. @@ -231 +231 @@ By default, when a new version of the AppStream 2.0 client is available, the cli -After the AppStream 2.0 client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After the WorkSpaces Applications client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -245 +245 @@ To run this script, you must be logged in to the applicable computer with Admini -By default, the AppStream 2.0 client allows users to upload diagnostic logs and minidumps on demand to AppStream 2.0 (AWS). In addition, if an exception occurs or the AppStream 2.0 client stops responding, users are prompted to choose whether they want to upload the minidump and associated logs. For more information about on-demand diagnostic logging, see [Automatic and On-Demand Diagnostic Log Uploads](./feature-support-diagnostic-log-upload.html). +By default, the WorkSpaces Applications client allows users to upload diagnostic logs and minidumps on demand to WorkSpaces Applications (AWS). In addition, if an exception occurs or the WorkSpaces Applications client stops responding, users are prompted to choose whether they want to upload the minidump and associated logs. For more information about on-demand diagnostic logging, see [Automatic and On-Demand Diagnostic Log Uploads](./feature-support-diagnostic-log-upload.html). @@ -247 +247 @@ By default, the AppStream 2.0 client allows users to upload diagnostic logs and -You can disable these behaviors by setting the value for the `UserUploadOfClientLogsAllowed` registry key to `false`. You can create this HKLM registry key when you install the AppStream 2.0 client. +You can disable these behaviors by setting the value for the `UserUploadOfClientLogsAllowed` registry key to `false`. You can create this HKLM registry key when you install the WorkSpaces Applications client. @@ -249 +249 @@ You can disable these behaviors by setting the value for the `UserUploadOfClient -After the AppStream 2.0 client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After the WorkSpaces Applications client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -264 +264 @@ To run this script, you must be logged in to the applicable computer with Admini -By default, the AppStream 2.0 client can run in either classic mode or native application mode. You can disable native application mode by setting the value for the `NativeAppModeDisabled` registry key to `true`. You can create this HKLM registry key when you install the AppStream 2.0 client. If the value is set to `true`, the client runs in classic mode only. For information about native application mode, see [Native Application Mode](./feature-support-native-application-mode.html). +By default, the WorkSpaces Applications client can run in either classic mode or native application mode. You can disable native application mode by setting the value for the `NativeAppModeDisabled` registry key to `true`. You can create this HKLM registry key when you install the WorkSpaces Applications client. If the value is set to `true`, the client runs in classic mode only. For information about native application mode, see [Native Application Mode](./feature-support-native-application-mode.html). @@ -266 +266 @@ By default, the AppStream 2.0 client can run in either classic mode or native ap -After the AppStream 2.0 client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After the WorkSpaces Applications client is installed, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -280 +280 @@ To run this script, you must be logged in to the applicable computer with Admini -By default, the AppStream 2.0 client enables users to redirect print jobs from their streaming applications to a printer that is connected to their local computer. You can disable local printer redirection by setting the value for the `PrinterRedirectionDisabled` registry key to `true`. You can create this HKLM registry key when you install the AppStream 2.0 client. If the value is set to `true`, the client does not redirect print jobs from users’ streaming applications to a printer that is connected to their local computer. +By default, the WorkSpaces Applications client enables users to redirect print jobs from their streaming applications to a printer that is connected to their local computer. You can disable local printer redirection by setting the value for the `PrinterRedirectionDisabled` registry key to `true`. You can create this HKLM registry key when you install the WorkSpaces Applications client. If the value is set to `true`, the client does not redirect print jobs from users’ streaming applications to a printer that is connected to their local computer. @@ -282 +282 @@ By default, the AppStream 2.0 client enables users to redirect print jobs from t -After you install the AppStream 2.0 client, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After you install the WorkSpaces Applications client, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -296 +296 @@ To run this script, you must be logged in to the applicable computer with Admini -By default, smart card redirection is enabled for the AppStream 2.0 client. When this feature is enabled, users can use smart card readers that are connected to their local computers and their smart cards during AppStream 2.0 streaming sessions without USB redirection. During AppStream 2.0 streaming sessions, users' smart card readers and smart cards remain accessible for use with local applications. The client redirects the smart card API calls from users’ streaming applications to their local smart card. You can disable smart card redirection by setting the value for the `SmartCardRedirectionDisabled` registry key to `true`. You can create this HKLM registry key when you install the AppStream 2.0 client. +By default, smart card redirection is enabled for the WorkSpaces Applications client. When this feature is enabled, users can use smart card readers that are connected to their local computers and their smart cards during WorkSpaces Applications streaming sessions without USB redirection. During WorkSpaces Applications streaming sessions, users' smart card readers and smart cards remain accessible for use with local applications. The client redirects the smart card API calls from users’ streaming applications to their local smart card. You can disable smart card redirection by setting the value for the `SmartCardRedirectionDisabled` registry key to `true`. You can create this HKLM registry key when you install the WorkSpaces Applications client. @@ -298 +298 @@ By default, smart card redirection is enabled for the AppStream 2.0 client. When -If the value is set to `true`, your users can't use their smart card readers and smart cards during an AppStream 2.0 streaming session without USB redirection. In this case, users can't sign in to their streaming applications by using a smart card that is connected to their local computer unless you [qualify the device](./qualify-usb-devices.html). After you qualify the device, users must [share the device with AppStream 2.0](./client-application-windows-how-to-share-usb-devices-user.html). When smart card redirection is disabled, during users' AppStream 2.0 streaming sessions, their smart card readers and smart cards are not accessible for use with local applications. +If the value is set to `true`, your users can't use their smart card readers and smart cards during an WorkSpaces Applications streaming session without USB redirection. In this case, users can't sign in to their streaming applications by using a smart card that is connected to their local computer unless you [qualify the device](./qualify-usb-devices.html). After you qualify the device, users must [share the device with WorkSpaces Applications](./client-application-windows-how-to-share-usb-devices-user.html). When smart card redirection is disabled, during users' WorkSpaces Applications streaming sessions, their smart card readers and smart cards are not accessible for use with local applications. @@ -300 +300 @@ If the value is set to `true`, your users can't use their smart card readers and -After you install the AppStream 2.0 client, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the AppStream 2.0 client Enterprise Deployment Tool to configure the client through Group Policy. +After you install the WorkSpaces Applications client, you can run the following PowerShell script to create this registry key. Or, you can use the administrative template that is included in the WorkSpaces Applications client Enterprise Deployment Tool to configure the client through Group Policy. @@ -312 +312 @@ To run this script, you must be logged in to the applicable computer with Admini -## Configure Additional AppStream 2.0 Client Settings for Your Users +## Configure Additional WorkSpaces Applications Client Settings for Your Users @@ -314 +314 @@ To run this script, you must be logged in to the applicable computer with Admini -The AppStream 2.0 client uses registry keys to configure the following additional client settings: +The WorkSpaces Applications client uses registry keys to configure the following additional client settings: @@ -316 +316 @@ The AppStream 2.0 client uses registry keys to configure the following additiona - * AppStream 2.0 client End-User License Agreement (EULA) acceptance + * WorkSpaces Applications client End-User License Agreement (EULA) acceptance @@ -318 +318 @@ The AppStream 2.0 client uses registry keys to configure the following additiona - * AppStream 2.0 client EULA version accepted + * WorkSpaces Applications client EULA version accepted @@ -320 +320 @@ The AppStream 2.0 client uses registry keys to configure the following additiona - * Automatic diagnostic log uploads for the AppStream 2.0 client + * Automatic diagnostic log uploads for the WorkSpaces Applications client @@ -322 +322 @@ The AppStream 2.0 client uses registry keys to configure the following additiona - * Automatic updates for the USB driver that is used to pass USB drivers to AppStream 2.0 + * Automatic updates for the USB driver that is used to pass USB drivers to WorkSpaces Applications @@ -324 +324 @@ The AppStream 2.0 client uses registry keys to configure the following additiona - * Enabling hardware rendering in the AppStream 2.0 client + * Enabling hardware rendering in the WorkSpaces Applications client @@ -326 +326 @@ The AppStream 2.0 client uses registry keys to configure the following additiona - * Setting custom folder paths for file system redirection in the AppStream 2.0 client + * Setting custom folder paths for file system redirection in the WorkSpaces Applications client @@ -333 +333 @@ The AppStream 2.0 client uses registry keys to configure the following additiona -The following table summarizes the registry values for additional client settings that you can use to customize the AppStream 2.0 client experience for your users. +The following table summarizes the registry values for additional client settings that you can use to customize the WorkSpaces Applications client experience for your users. @@ -341,5 +341,5 @@ Value | Registry path | Type | Description | Data -`EULAAccepted` | `HKCU\Software\Amazon\Appstream Client` | String | Set this value to `true` to accept the AppStream 2.0 client EULA on behalf of your users. | `true`/`false` -`AcceptedEULAVersion` | `HKCU\Software\Amazon\Appstream Client` | String | The version of EULA that is accepted. If the current version of the AppStream 2.0 client EULA is different from the version of the EULA that is accepted, users are prompted to accept the current version of the EULA. | `1.0` -`DiagnosticInfoCollectionAllowed` | `HKCU\Software\Amazon\Appstream Client` | String | Set this value to `true `to enable AppStream 2.0 to automatically send diagnostic logs from the AppStream 2.0 client to AppStream 2.0 (AWS). | `true`/`false` -`USBDriverOptIn` | `HKCU\Software\Amazon\Appstream Client` | String | Set this value to `true` to enable AppStream 2.0 to automatically update the USB driver that is used to pass USB drivers to AppStream 2.0. | `true`/`false` -`HardwareRenderingEnabled` | `HKCU\Software\Amazon\Appstream Client` | String | Set this value to `true` to enable hardware rendering in the AppStream 2.0 client. | `true`/`false` +`EULAAccepted` | `HKCU\Software\Amazon\Appstream Client` | String | Set this value to `true` to accept the WorkSpaces Applications client EULA on behalf of your users. | `true`/`false`