Wyse Device Manager 4.9.1 User Guide
I’m doing a new install of WDM 4.9.1 and wishes to use our existing SQL 2008 R2 for the database. I select the option that the database is not already installed and later in the wizard I point to the SQL server using the sa account (much against my wishes!!) to logon and select the option to use default Rapport password. However later in the install process I get an error: “Unable to attach the WDM database” followed by “WDM database mus be running before uninstallation starts” (uninstallation!??? I’m installing!) followed by “Database install table not found. WDM database must be running before uninstallation” (still uninstalling apparently) and then the installer just quits. I have read the installation guide and didn’t find anything pointing out that I should create the database manually? I could start guessing on the DB name and content, but I guess it would take me a while before I got it right!
Administrators Guide Wyse. Configuring Wyse Device Manager Servers 17. WintermTM 1 series, Based on Wyse Thin OS for information on configuring the thin client. Administrators Guide Wyse Device Manager™ Release 4.9.1 Issue: 042012 PN: 883885-01 Rev. Search the Dell Wyse Customer Support Knowledge Base. Get the details on our Dell Wyse cloud clients with user guides, administrator guides, and more. Installation Guide Wyse Device Manager™ Release 4.9.1. Administrators Guide: Wyse Device Manager TM is intended. Information on user forums. Visit the Wyse.
😀 Any suggestions? Well my problems wasn’t over! After installation (without ANY errors AT ALL!) I launched the WDM console only to find a completely empty MMC.
Trying to start Service Log only resulted in an error stating it was not able to get GUI HTTP port. I found an article with a problem similar to mine () and tried reinstalling it (the uninstall also wiped the database – GREAT! 🙁 ) but still to no avail. I ran diagnostics on the WDM server which were all green lights and success (so, everything is working, except it is not – where would I be without that diag util 😕 ) In desperation I did a no-brainer install on a laptop with the default lic code and SQL Express DB (and on the first attempt it failed to mount the DB and it wasn’t until I found a second laptop, it installed – hmmm) and started comparing directories, registry and databases. After hours of searching I saw that on my production DB the license table was empty.
So I entered the information from the laptop install into the production DB which gave me more than an empty MMC! I got a couple of errors on the way to the license config but finally I was able to add my enterprise license and got it activated. Oh, and by the way only enter information in the Sales column (I used the default workgroup key the installer presents during install but without the dashes) in the License table otherwise WDM console thinks you have been tampering with the license and will shut down! Just thought I would let you guys know in case anyone had this issue.
🙂 (and thank you Wyse for wasting so much of my time! Mckesson Pacs Viewer.