Administrator Guide

Solution: Refresh the browser to see the login page.
Issue While logging in to WEB UI
Problem: Login to WDM Web UI is not possible, If the WDM server is joined to the Windows Server 2012 domain controller.
Solution: The GetAuthorizationGroups() function fails on groups (SIDs) which are added to you by default, when a 2012 domain controller
is involved.
Installing KB2830145 on the WDM server will resolve the issue.
EMSDK fails to start due to port number
Problem: EMSDK component uses port number 49155 by default for its communication. If the startup of EMSDK fails due to non-
availability of the mentioned port, then user shall manually stop the EMSDK server which is running in the console of the machine where
software is installed, and provide a available port number in the following les:
Solution:
1 Go to Program les path where EDM le is installed \Wyse\WDM\Teradici\EMSDK, open the emsdk.properties le in notepad and
assign the available port number in the eld emserver.serverPort=49155, For example, 49159.
2 Set the new port number in the le C:\inetpub\wwwroot\ThreadXApi\Web.cong, by opening the same le in the text editor and
replace the port number under the following tag:
• <appSettings><add key=”EmSdkPort” value=”49155”/></appSettings>
3 Restart the machine.
Domain user login and HApi Log Failure
Problem : Domain user login failure. The following HApi Log error message is displayed:
An error (1301) occurred while enumerating the groups. The group's SID could not be resolved.
Solution:: Install the Microsoft hotx from the link and then try using WDM: www.support.microsoft.com/en-us/kb/2830145
Problem: Web UI login error occurs, if you prex machine name to user credentials name.
Solution: Enter the user name and log in credentials.
Problems with accessing Device Page
Problem: You are having problem while accessing the device page. It gets logged out when you try to access the page.
Solution: Clear the cookies and cache of the system and try to login again.
OSD Logo Conguration or Firmware Push Failure on
ThreadX 5.X Devices
Problem: Failed to push OSD logo conguration or rmware upgrade.
Solution: Make sure Software repository test connection for CIFS is successful.
Add the following accounts to rapport folder sharing permissions:
• System account of the server where ThreadX 5.X is installed.
Troubleshooting
117