This article will explain how to install the Amazon Workspaces Client and how to enter your registration code to access your FCH Workspaces Machine. Installation Go to https://clients.amazonworkspaces.com/ Select the Option for your Machine Most Users will select Download on the Windows 64 bit option The installation should be a straightforward Next, Next Finish type of installation. No further options need to be selected on the installer. Registration Code Amazon Workspaces uses Registration Codes to Connect to environments instead of a URL like Vmware Horizon used in the past. Registration Codes are case Sensitive, so please enter them as you see them. Production Environment Registration Code: WSpdx+CBZSW2 First Launch of Amazon Workspaces Client Upon Registration, select Settings > Manage Login Information Select Remember Registration Code Logging into Amazon Workspaces Username = fch username (Example: nscheetz....astrand...etc) Password = fch login password (Example: SpokaneFCH123$) MFA Code = Type "Push" without quotes to receive a push prompt on Cisco Duo App, or Type in your six digit code from the Cisco Duo App (Example: 523489)

Let the Helpdesk know if you have any questions.

Your AWS thin client will come with: -thin client -thin client power cord -usb hub -usb hub power cord -2 monitor adapters **NOTE: the thin client has two HDMI ports. Only the OUT is used on the thin client for your monitor. Your second monitor is plugged into the HDMI port on the usb hub. Once you get your thin client set up and powered on, it will set up your keyboard and language. Once that is complete, it is going to ask for an activation code. The FCH activation code is: ahx2sjzn Once activated, the thin client will update and then request the registration code. WSpdx+CBZSW2 Once registered, you can log in as you normally would. Let the Helpdesk know if you have any questions.

Everything you need to know from set up to personalizing settings to troubleshooting. Check here first!

If your WorkSpaces Thin Client device is not recognizing the peripherals that you are using, first, verify that they are compatible with WorkSpaces Thin Client. If your peripheral device is compatible with WorkSpaces Thin Client and is still not recognized by the device, do the following: Turn off the WorkSpaces Thin Client device. Disconnect the peripheral device. Reconnect the peripheral device. Check that the USB hub is connected to a power supply with the included hub power adapter. Check that the USB hub is plugged into the WorkSpaces Thin Client device. Turn on your WorkSpaces Thin Client device. Select the Settings gear icon on the toolbar, navigate to Peripheral devices, and verify the peripheral names.

If you are experiencing volume issues with your headset, do the following: Select the toolbar located on the right side of the screen. Go to Settings → Peripheral devices. Scroll down to the Audio section and adjust the output volume. Note After a system restart, WorkSpaces Thin Client resets the volume level for connected USB headsets.

If you're experiencing audio issues with your WorkSpaces Thin Client, try one of the following procedures: Check your WorkSpaces Thin Client device Check that the audio USB headset is connected to the USB hub and that the USB hub is turned ON. Check for supported peripheral devices to ensure that your device is supported. If you are on the login screen of a VDI session Select Settings at the top right of the screen. Locate the device ID. Run a diagnostic check and ensure that the device and advanced logging are both enabled. If you are currently in a VDI session Go to the toolbar on the right side of the screen. Select Settings → Peripheral Devices → Audio. Check that your USB headset is listed and that the volume is set to your desired level. Check that the device is connected to Wi-Fi or Ethernet and that there is no issue with the connection to WorkSpaces. If you are not currently in a VDI session On the WorkSpaces login page, select Settings at the top right of the screen. Locate the device ID. Check that diagnostics and advanced logging are enabled.

If your second monitor goes dark while you are using it, try one of the following procedures: Detect display from Settings Go to Settings then Peripheral devices. Select Detect Extended Display under DISPLAY RESOLUTION. Detect display from VDI toolbar Open your VDI toolbar. Select Detect Displays on the toolbar. After doing either procedure, the secondary monitor should come back on. If the problem continues, restart your WorkSpaces Thin Client device.

The WorkSpaces Thin Client has the following known issues. If you select any link on the VDI login screen, you must return to the login screen. Workaround: Select the Lock/Unlock button. This returns you to the VDI login, and a second monitor will mirror the primary monitor. Using keyboard shortcuts may cause unexpected behavior. Workaround: There is no workaround for this issue. Some peripherals may not be recognized when the device is running. Workaround: Unplug the device and then plug it back in or reboot the device. You cannot view the IP address of the Ethernet network from settings. Workaround: There is no workaround for this issue. Some menu options in the VDI toolbar are displayed but not working. Workaround: These features are not enabled in this release. You cannot find a supported keyboard layout in the OOBE or settings. Workaround: Check that you are using software set 2.2.0 or higher. Check for the most current software set in WorkSpaces Thin Client software releases. You can also use an Ethernet connection if you cannot enter your Wi-Fi password without keyboard layout support. You can select a supported keyboard layout in device settings, but you cannot enter the specific keys within the virtual session. Workaround: Check that the input method within the session is set to the corresponding language. For example, if you want to use an Italian layout keyboard, set the input method to Italian within the session. See the following figure. Toolbar does not expand or collapse when you select it for the first time. Workaround: Make sure the mouse pointer is on the primary monitor and try expanding or collapsing the toolbar again. To expand the toolbar, select the dark area over the collapsed toolbar. To collapse the toolbar, select any area on the primary monitor. On waking up from sleep, WorkSpaces Thin Client device shows the keyboard and mouse setup screen for a few seconds before launching the session. Workaround: The keyboard and mouse setup screen should automatically go away. If the screen remains after a few seconds, unplug the device and then plug it back in or reboot the device. On the restart of a WorkSpaces Thin Client device, end users will see repeated Getting Ready and Checking for updatestransition screens before launching the session. Workaround: None Updates for the WorkSpaces Thin Client device are not taking effect. Workaround: Restart the device after every system update. The webcam is not enabled in WorkSpaces and its icon in the top toolbar remains gray. Workaround: Confirm your webcam is properly connected to your WorkSpaces Thin Client device. Wait 30 seconds after your WorkSpaces session starts. Check to see if your webcam is automatically enabled. If it is still not enabled, restart your WorkSpaces Thin Client device and check again. 4K monitor not at full resolution WorkSpaces Thin Client supports up to 3840x2160 (4K) resolution on the primary monitor. With the scaling factor, you can stream 4K in WorkSpaces. However, WorkSpaces Secure Browser might not support 4k yet. Workaround: None. WorkSpaces Thin Client Packet Loss notification. Workaround: The system may show no Packet Loss even if packet loss is occurring, please ignore the no packet loss message. Keyboard power operation is not correct in device settings If a keyboard is turned on/off using its native power switch, the status may not reflect accurately in the device settings. Workaround: None. Headset volume change not reflected in device settings For headsets with its own amplifier, pressing the volume button on the headset may not change the volume level shown in device settings. Workaround: None. Screen shows multiple updating screen fragments after reset On monitors with 2560 x 1440 resolution and after you reset the WorkSpaces Thin Client device, the monitors display the AWS updating screen tiled across them. Workaround: None. The device reset works as expected and the screen will return to normal. Network icon opening Accessibility settings Selecting the Network Icon on activation code screen may direct users to accessibility settings instead of network settings. Workaround: Enter your activation code to complete setup. The issue will resolve after the device updates to the latest software version. Server error code 1001 during setup Device encounters server error (code 1001) at the end of setup. Workaround: The device needs to be reset and set up again. Select the network icon to open Settings. Select About. Select Reset device. Set up your device. See Setting up your Amazon WorkSpaces Thin Client service.