Administrator Guide
Table Of Contents
- Windows 10 Enterprise 2019 LTSC for Dell Wyse Thin Clients Administrator’s Guide
- Contents
- Introduction
- Getting started
- Accessible applications
- Browsing with Internet Explorer
- Using the Dell Thin Client Application
- Using VMware Horizon Client to connect to virtual desktop
- Citrix Workspace app
- Configuring remote desktop connection session services
- Using Ericom Connect and WebConnect client
- Using Ericom PowerTerm Terminal Emulation
- Windows Media Player
- Wyse Easy Setup
- Overlay Optimizer
- Cisco Jabber Softphone for VDI
- Administrative features
- Using Administrative tools
- Using TPM and BitLocker
- Configuring Bluetooth connections
- Configuring wireless local area network settings
- Using custom fields
- Configuring RAM disk size
- Enabling auto logon
- System shortcuts
- Viewing and configuring SCCM components
- Devices and printers
- Configuring multi-monitor display
- Managing audio and audio devices
- Additional language support
- Setting region
- Managing user accounts
- Using Windows Defender
- Windows Defender Advanced Threat Protection
- Threat Defense
- Endpoint Security Suite Enterprise
- C-A-D tool
- Wyse Device Agent
- Citrix HDX RealTime Media Engine
- Viewing and exporting operating system image manifest files
- Additional administrator utility and settings information
- Automatically launched utilities
- Utilities affected by log off, restart, and shut down
- Unified Write Filter
- Application Launch Manager
- xData Cleanup Manager
- Capturing logfiles
- Saving files and using local drives
- Mapping network drives
- Participating in domains
- Using the Net and Tracert utilities
- Managing Users and Groups with User Accounts
- Changing the computer name of a thin client
- Removing language and feature on demand packages
- Language codes
- Adding languages to LTSC 2019 (RS5)
- Windows 10 IoT enterprise language packages
- Imaging using Dell Application Control Center
- System administration
- Network architecture and server environment
- Installing firmware using USB Imaging Tool
- Frequently asked questions
- How to install Skype for Business
- How to set up a smart card reader
- How to use USB Redirection
- How to prepare a Windows 10 IoT Enterprise operating system image for capture
- Using Wyse Management Suite
- How to capture and push Windows 10 IoT Enterprise operating system image
- How to update Windows 10 IoT Enterprise 2016 LTSB to Windows 10 IoT Enterprise 2019 LTSC
- Troubleshooting
- Keyboard customization issues
- Resolving memory issues
- CADMAP tool interfering with published application shortcut keys
- WiFi settings configured from Wyse Management Suite are not persistent across multiple Wyse 5070 thin clients
- Wyse Management Suite registration information is not cleared after the Sysprep process
Table 8. Examples to configure nodes using xDCM (continued)
Scenario Command
\Windows\Security\database, C:\Windows\logs"
-Event: USER_LOGOFF -CleanType:DIR_EMPTY -
CleanFrom:Disk
Deleting a file cleanup node under OverlayCleanup element
Notepad in XdataCleanupConfig.xml.
XDCM.exe -Remove -CleanupType:File -
Name:Notepad -CleanFrom:Overlay
NOTE:
● If you log off from the thin client when UWF is disabled, the folder cleanup node is used by ClientServiceEngine service
to clean up the contents inside the directory C:\Windows\Security. Also, when the contents of this directory is
deleted, the contents in the folders C:\Windows\Security\database and C:\Windows\logs are deleted as
they are added in the excluded paths.
● You must provide unique names to add a new application entry to the XdataCleanupConfig.xml using XDCM.exe.
● When you are running the command to add an entry, the folder path is compared with the existing entries. If the path is
already available, only the exclusion paths are added to the existing folder entry.
Capturing logfiles
You can configure DebugLog.xml file to collect different types of logs for an application. You can modify the log levels to
obtain specific type of logs. The logs files are created at C:\Windows\Logs\<Application name>\Logs.
NOTE: By default, no logs are created for an application.
Configuration of DebugLog XML file
You can use the Debug Configuration Editor (DCE) console application to configure the debug configuration XML file. This tool
can be used to commit, exclude, or modify the debug configuration file.
To commit, exclude, or modify the debug configuration file, enter the following commands on the Debug Configuration Editor:
● To commit the file and obtain the logfiles—DebugConfigEditor.exe -CommitLog -Path "DebugLog.xml". This
command commits the file present in the path that is mentioned in Debug.xml.
● To exclude the collection of logs from a folder mentioned in the Debug.xml—DebugConfigEditor.exe -
ExcludeLog -Path "DebugLog.xml".
● To configure the Debug.xml file to collect different types of logs—DebugConfigEditor.exe -UpdateConfig -
Path "DebugLog.xml" -LogPath "Path of Log File" -LogFileName "Name of log File" -LogLevel
"logLevel".
The following table describes the different LogLevel values that can be used:
Table 9. LogLevel values
Value Description
0 Logs are not captured.
1 Error logs are captured.
2 Warning logs are captured.
3 Error and warning logs are captured.
4 Information logs are captured.
7 All logs are captured.
Additional administrator utility and settings information 37