We have been using DDM locally with our U3415W monitors (3 of them in our office currently) and it has become critical to efficient workflow. However, we have just moved to a cloud server with remote virtual desktop access. It appears DDM does not work in a virtual desktop environment although I can't find much information on this.
Can someone confirm whether DDM on a virtual desktop will work or not? If not, when will it become supported? Hoping I don't have to dish out even more money for Virtual Display Manager or a similar program on top of the $1,000+/monitor already paid. Especially with a company like Dell that does business in the server space.
Please advise as to my options so my staff and I can get back to working efficiently with a terminal version of DDM or a competitors display manager.
Solved! Go to Solution.
Two different issues here. DDM does not work in your VM for the same reason your Intel, AMD and NVidia graphics drivers and control panel don't work - because your VM has virtualized the hardware and substituted their own virtual drivers. So none of the OSD controls like over brightness and preset modes in DDM can or will work in this kind of environment.
But - correct me if I'm wrong - you seem to be really just interested in the Easy Arrange (screen partitioning) feature in DDM, and that is not hardware dependent and could work in a VM were it not for a different issue - namely, that in DDM Easy Arrange is just a subsidiary feature to monitor OSD control; where there is no OSD control in DDM, there is no screen partitioning either.
So what you really want is stand-alone screen partitioning software; and I'm afraid I don't know if Dell offers anything like that.
Swamped, thanks for your reply. I understand the limitations with the virtual drivers and you are correct that I am simply interested in the screen partitioning. Just seems like something Dell should offer.
I will be proceeding with Virtual Display Manager from iShadow or something equivalent. Hopefully Dell supports this in the future if they are serious about selling these ultra-wide monitors to the business world.
If you are comfortable editing the registry, adding the following switch may enable the Easy Arrange feature inside the VM:
Windows Registry Editor Version 5.00
I tried your suggestion and edited the registry as suggested on the server side. No luck. DDM is in the tray with an "x" over it saying "please connect a supported Dell monitor".
Any other suggestions to try? Thanks again.
I tried it with a Win10 VM under OSX and it works (only the screen partitioning works, not the OSD controls). You may be using a very old version of DDM? The latest version of DDM is b.1800, and I'm not sure when this undocumented support was added, but I tested successfully with b.1739.
Another thing, in case you didn't do this - you may need to restart DDM after adding the registry switch.
Finally, you wrote you made this change on "the server side", and it should be on the client side - in the VM itself.
The private cloud service provider is using Windows Server 2008. Our computers run Win10 but the VM looks like an older version of windows - XP looking.
We are using the latest version 1800. We tried restarting everything after adding the registry switch on all sides, the VM and the server.
Still the same result. Am I missing something here? Thanks again.
Not sure. All that matters is the VM DDM runs inside, not the server. While holding the SHIFT key, right-click on the DDM system tray icon and select "Save diagnostic report" from the popup menu. Then post the content of that report here, maybe it will provide a clue as to what's wrong.
When I try clicking on "Save diagnostic report" nothing happens.
I am getting a new error message on booting up the VM:
"This system does not currently support software control over monitors. Dell Display Manager minimally requires Windows 2000, and a display driver and monitor that supports DDC/CI."
It appears Windows Server 2008 is running Windows NT 6.1.XXX SP1 as the operating system. Could this be an issue?
That error message is normal only if you are running WindowsME or NT4 or earlier. Server 2008 allows you to install a range of different client Windows OSes, from Win8 back but I'm not sure the list goes back that far.
The problem is with the client operating system you are running, not the server. But I'm afraid I can't tell you what the problem is...