Highlighted
rtwright68
Bronze

On-premise Dell Wyse Management Suite issues

We have the on-premise WMS installed and configured, can access the login page externally and internally using a fully signed SSL certificate (it is our corporate wildcard certificate).  

The problem occurs when we try to configure the Wyse thin client to connect to the correct address.

We see an error message 7512.  We also sign up for a demo account of the hosted version of WMS and configuring it with the options as outlined permits the thin client to connect to it immediately.

I'm suspecting that there is some kind of redirection issue happening with the WMS on-premise installation, because the setting is configured and adds a :443 at the end (can't see a way to modify that), which when we attempt to bring up the page from a browser, gives us an HTTP status 404 error.

I'm hoping someone can give some insight on this issue.  Not sure if some settings need modified in the Tomcat configuration to properly route the requests? 

6 Replies
bbattle
Copper

RE: On-premise Dell Wyse Management Suite issues

We are having an issue getting the software to run at all. Get the same 404 error when going to http://{servername.domain.tld}/ccm-web, type Status report, message /ccm-web, description The requested resource is not available. Cannot connect locally, or outside of the server. We've installed this on 2 Windows Server 2012 servers, attempting to get something to work, and fails with the same error. Tomcat is running, as we can hit http://localhost:8080, and grant rights to the management views through the XML.

0 Kudos
JK-PBA
Copper

RE: On-premise Dell Wyse Management Suite issues

I have the exact same problem, except I don't understand where you are getting the 404 error.   Do you mean when you point a browser to WMShost.yourdomain.com:443?    I get a default Tomcat is installed page for that. 

Did you find a solution for this?

0 Kudos
bbattle
Copper

RE: On-premise Dell Wyse Management Suite issues

Yes, I ended up finding the solution for Dell on this one. They have a bug in their installer code, when creating the Tomcat application for WMS. If you choose the default options, (do not choose custom install), it will install without a problem. I installed this on 2 different servers, one of which was a clean install of Windows Server 2012 R2 and had the same problem. On a whim, I decided to take the defaults on the install and the WMS site popped up. I have other problems with WTOS communications, but that's unrelated to this installation problem.

JK-PBA
Copper

RE: On-premise Dell Wyse Management Suite issues

Thank you!   That worked for me too.

0 Kudos
Moderator
Moderator

RE: On-premise Dell Wyse Management Suite issues

I ran into this with another customer.  WMS was installed on Server 2016 using Default settings.  Customer added their own certificate which was valid.  WTOS device had valid time and certificate information.

Error messages were:

SSL: error ERR_SSL_NO_CIPHER_MATCH! 

SSL: unable to setup connection, (err=-7512)

CCM agent open http error! errno:7512

Issue was resolved by upgrading the WTOS firmware from 8.1.x to 8.4.108.

Tags (3)
0 Kudos
SCSIgate
Copper

RE: On-premise Dell Wyse Management Suite issues

Thanks bbattle. 

Was having the same 404 troubles with WMS 1.1 install as I initially did the custom install option but selected all embedded databases. Uninstalled it and selected the typical install and the ccm-web console was available after the install.

Cheers,

0 Kudos