Wyse Device Manager 4.9.1 User Guide

Wyse Device Manager. SQL Server 2008 R2 External Database Support. I'm trying to configure WDM 4.9. Patch A Pool With Plastered on this page. 1 to connect up to my standalone SQL 2008 R2 server.

I recently installed a fresh copy of WDM (v. 5.0) on a Windows Server 2008 R2 vm. I had been running v. 4.9.1, and had about 15 WYSE P25 zero clients and 3 WYSE D90D7 thin clients in my device list. After installing the new version, my P25s immediately showed up (without a device scan) but my thin clients did not. I ran a couple of device scans but got nothing. After some searching online, I saw where numerous people were stating that the thin client HAgents needed to be upgraded to the most recent version.

From what I can see, that is 6.1.0.39 (I have 6.1.0.25 installed). After downloading the package and extracting it on one of the thin clients locally, I cannot figure out how to install the thing (my clients are running Windows 7 Embedded). There was a 'Install' bat file extracted, but that did nothing after running.

The ReadMe gives no install information. Can someone help me get this done? Thanks for the reply RMontalvo, but this does not work. After running both PortRegToIni.exe and Install.bat, I see no Rapport entry in the registry.

Also, there is nothing that talks about replacing the old.ini file with the new one. I did this manually after following all the steps (and saw that nothing happened) and ran both the.exe and.bat again, and nothing. Is there possibly a newer document that shows how to install version 6.1.0.39, or perhaps a document on just wiping the whole thing and installing HAgent fresh? Darkknight - can I call you mr. wayne:) When you installed the new WDM server (you mentioned 4.9.1 previously used) did you upgrade in place or install on new server? If truly fresh install, did you reuse the same servername/IP as the old server the previous devices were communicating with? If not did you update the DHCP option tags or DNS records to reflect the new server values? As far back as 2009 there was a change on WES/WES7 devices that made manual discovery optional during security hardening.

They added the local discovery check boxes to enable and disable various discovery options around the same time. The default behavior is upon discovery in WDM 4.9.1 to disable all other discovery options to prevent rogue servers from finding and attempting mgmt. This is configurable globally within WDM preferences >dvc mgr prefs >discovery. Its possible your devices are still holding onto the old WDM servername/IP and since the new one is different its ignoring the manual discovery request.

This is why autodiscovery is important with these devices. My experience has DHCP OTs being the most widely supported method (they all support it) followed by DNS A record 'wdmserver' pointed to the server IP (important to note IP and not FQDN). Newer HAgents can also use DNS SRV or DNS CNAME if FQDN is important. Manual discovery for security reason is largely depreciated in production usage due to security concerns and networking limitations. As for discovery with WDM 5.0 - with few exceptions - if it checked into 4.9.1 it'll checkin to 5.0. The only real caveat is whether the Hagent in question is old enough to only support HTTP (WDM 5.0 installs with HTTPS) or in rare cases the very old HAgents may not yet support IIS7+ on win2008+. The HTTPS one is easy to resolve as you can just go to IIS and enable HTTP as a binding for the website and uncheck the require SSL option.

I suspect this may be your issue rather than needing to manually upgrade hagents on each box before discovery. Stepping through the install.bat its copying over files and settings from the registry. Some core pieces being the registry settings (if present) and the hagent.exe. Can you check whether the hagentsettings.ini is created?

Missing the registry /Rapport isn't important as that was a legacy option and is no longer required. The portregtoini.exe just copies those values over if present when converting to the new hagentsettings.ini.

If that's present then check the Hagent.exe version under properties details. Is it the new one or old one? Install Mcboot Using Usb.

Since youre already here open 'CMD' and navigate to that WDM directory. Once there you can manually remove the hagent service using 'hagent.exe -remove'. Go ahead and copy over the newer hagent.exe from the installer and then use the 'hagent.exe -install' command to add it back. Try starting the hagent service and see if it works again.

Once its back up check the WDM control panel applet to see where the device is looking for WDM server and what discovery options are enabled. Thanks for the reply karaziel, you MAY call me Mr. I did create a fresh Windows Server 2008 R2 vm and install WDM 5.0. All this local stuff is VERY convoluted to say the least. I never could get the HAgent to install locally, no matter what I did. I did, however, download the WYSE USB Firmware Tool and was able to install the most recent image (BDB0_0858_8192) on the 3 thin clients. After that, I was able to connect to these machines on WDM and remotely deploy the new HAgent (which turned out to be version 6.3.2.54).

I am still having quite a few other issues with WDM, due to to its convoluted nature, lack of relevant documentation, and bad Dell support, but at least this part is done. I will be creating at least 3 other posts, so if you would like to help out on any of them it would be greatly appreciated.

We are currently on WDM 4.9 version and would like to upgrade it to 5.7.1 or to the latest available. Below is the infra. We have a single server, configured for ~4000 devices. Database Rapport is local to the server.

What would be the upgrade process with low risk and impact and what precautions should be considered for an upgrade. I am planning to have a clone of existing server and perform an upgrade there, test it and then move to original server, But could not find any documentation on the website. Please suggest Thanks Datta.