Whenever TPM is to be initialized, the client must be restarted because the security hardware
must be initialized. Since the security hardware must be initialized, a BIOS screen immediately
displays prompting the user for confirmation.
Upon accepting, the security hardware is initialized. Then the TPM ownership must be taken by
providing a password. It is recommended that once a TPM is initialized, it is best not to change the
state or disable it. Leaving the TPM initialized is not an issue with imaging.
The options available for BitLocker Drive Encryption depend on the policy set. Since the Allow
BitLocker without a compatible TPM is not set/selected, the following BitLocker startup preferences
are displayed when TPM is enabled, initialized and owned.
If TPM is not enabled, initialized and owned, then the following dialog box displays when BitLocker is
To view and configure the Wyse SCCM components installed on your thin client, use the Configuration
To open Configuration Manager Properties dialog box, go to Start → Control Panel → Configuration
For more information, refer Dell Wyse SCCM Guide at http://www.dell.com/wyse/manuals
Device Manger: Bluetooth Wireless Connections
You can access Bluetooth- enabled devices on your thin client device, if your thin client has optional
Wireless Bluetooth capability.
1. To manage an existing Bluetooth device :
a. Go to Start → Control Panel → Device Manager
b. Click Bluetooth Radios.
c. To manage an existing Bluetooth device, double-click on the Bluetooth icon
You can update drivers using the Driver tab
2. To add Bluetooth- enabled device:
a. Go to Start → Control Panel → Devices and Printers
Devices and Printers window is displayed
b. Click Add a Device.
c. Turn on the Bluetooth — enabled devcie and ensure that the device is discoverable.
d. When the device is discoverable by the thin client device, click Next and follow the wizard.
NOTE: Be sure to disable the File Based Write Filter and to configure NetXClean to refrain from
clearing up your settings. For more information, see Before configuring your thin clients