Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

M

mafischl

1 Rookie

 • 

56 Posts

2324

September 13th, 2018 10:00

Bad WMS Pro Impressions

So far, my impression is that the extra features within WMS Pro are simply half-baked and does not meet the expectations set in the marketing documents. Coming from WDM Enterprise, WMS feels like a downgrade in terms of functionality and makes it harder to manage clients.

Is everyone else getting the same impression about WMS Pro or are there any counterpoints? My observations are based on WMS Pro 1.2 (as well as an earlier evaluations of 1.0 and 1.1).

Some examples of the "half-baked" Pro features:

  1. Advanced Reporting Tool = A CSV output containing the results table from a MongoDB query. Not presentable to management or a support team.
  2. AD Authentication = It does sync the passwords for a AD user; however, I have to manually import a user ahead and cannot just grant access to a security group (WDM did this in the MMC Console). It is also very slow at querying large ADs.
  3. Mobile Applications = The app is ok but only provides a mobile-optimized experience of the main website with limited features and users testing it often preferred launching the web browser instead of the app. It also did not allow anyone to log in using an AD account to an on-premise instance of WDM Pro. Only manually created accounts work. (AD accounts could log into the domain-credentials log-in page on the web portal)
  4. Advanced Policy Deployment = Worked well except cannot handle errors during the deployment. A method to continue around any step that results in an error would be nice. To be fair, this is the same behavior as a .rsp packages in WDM.

Apologies, if this feels like a rant. Most of this issues were addressed with Dell Premier and CCC Support teams last year and these items are still outstanding.

DELL-Scott H

Moderator

 • 

892 Posts

September 14th, 2018 05:00

Good feedback.

 

I would encourage you to contact your CCC sales team for an update on the enhancement/changes requested and what the non public roadmap for WMS looks like, compared to last year when you brough these items up.

 

DarkIllusion

7 Posts

September 22nd, 2018 11:00

I have had many issues with WMS, but I am using it in production environment despite these issues. Here are a few of my issues.  I have contacted support about all these issues.

  1. Lack of QA.
    1. WYSE Easy Setup for WES clients need WDA 14+ to work but latest version install fails in WMS 1.2 even after ensuring WDA 14+ is installed at a subgroup and WYSE Easy Setup at a higher group, to ensure proper install order. I have found success with advance policy that install lower version of Easy setup and then installing the latest version.
      1. Method outlined above used to work in WMS 1.1, however it just stopped working this week for me out of nowhere.
    2. ThinLinux(Suse) firmware upgrade does not work until you push WYSE components Merlin, WDA, and Platform Tools, however device does not check into WMS when these component are installed. One can use HTTP upgrade instead, but name of devices it not retained post update.
    3. WMS 1.2 has an issue that should have be addressed in QA, where one could not deliver packages to a client in on-off manner.  1.2 HF 1 addressed this  issue
    4. Unmanaged Device Auto Assignment - in WMS 1.2 Destination Group shows blank when you select edit, even after setting it, functionality works but it appears blank, which can be confusing
    5. WMS 1.1 Jobs do not timeout if it has client with the status of pending. I have an image job that is maked as running since 08/18/18 due to one client marked as pending
  2. More roles for users
    1. Want to see a  Group Viewer role .  Only option is Global Admin, Group Admin, and Viewer.  Group admin allows Admin to create new account, would prefer if that was not an option. With a Group viewer you can select what WMS functionalality user would be granted like you can with viewer. Viewer alone give Admin view & WMS functionality granted to all of WMS groups, would prefer to be limited to groups needed by user
  3. Lack of SelectGroup support.  Can be accomplished via Advance tab INI and setting up external web servers.  Would prefer to skip external server need
  4. No built in method to sync files in Repos.  Sync button only syncs meta data.  You can use other methods, but would like some direction from WYSE
  5. Lack of WMS Authentication SAML providers support outside of ADFS. Most companies are moving to third parties providers Ike OKTA
  6. WMS WES language settings do not change language of WES users
  7. Need for additional firewall ports exception for MQQT in public WMS instance.  This is the only way to issue command like restart. It is  extra overhead if you need to keep up with new subnets added all the time.
  8. Lack of the ability to identify client by hostname or hostname wildcard in Unmanaged Device Auto Assignment rules.  This is something INI method was able to do forever with WYSE clients
  9. Lack of Documentation. WMS API Reference Manual is not available after three WMS iterations. This is also true for some additional features of WMS that is not covered in the manual

Was this post helpful?

View All

No Events found!

Top