This post is more than 5 years old
8 Posts
0
13686
U3415W, DDM not supported in a Virtual Desktop
We have been using DDM locally with our U3415W monitors (three 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, will it ever 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.
Thanks!
swamped1
234 Posts
0
January 23rd, 2017 06:00
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.
swamped1
234 Posts
0
January 23rd, 2017 11:00
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
[HKEY_CURRENT_USER\Software\EnTech\DDM]
"EULA"=dword:00002070
jhatch78
8 Posts
0
January 23rd, 2017 09:00
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.
Thanks again.
jhatch78
8 Posts
0
January 24th, 2017 08: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.
jhatch78
8 Posts
0
January 24th, 2017 11:00
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.
swamped1
234 Posts
0
January 24th, 2017 11:00
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.
swamped1
234 Posts
0
January 24th, 2017 12:00
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.
jhatch78
8 Posts
0
January 24th, 2017 14:00
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?
swamped1
234 Posts
0
January 24th, 2017 14:00
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...
jhatch78
8 Posts
0
September 26th, 2017 12:00
Hi Swamped,
Further to our previous thread above, my IT provider has upgraded our remote server to Windows Server 2016. I had them install the latest DDM and I made the suggested regedits above. Happy to report the easy arrange feature works....but then stops after a minute or two. DDM still shows in the tray as being active but is unresponsive. The easy arrange will feature will then sometime startup again after a while but then stops shortly after again. If I log off the remote desktop and relog back on, the easy arrange feature will work again for a minute and then stop again.
I have been working with my IT support team but they don't know what's causing it to intermittently stop and start. Any thoughts on what might be causing this to occur or suggestions to try?
Thanks again for the assistance with this.
swamped1
234 Posts
0
September 27th, 2017 03:00
Close and restart DDM and then wait for DDM to stop working at least one time. Then: 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 happening.
jhatch78
8 Posts
0
October 3rd, 2017 16:00
Here's a copy of the diagnostic report:
Diagnostic Report, generated 2017-10-03 (10.0.14393)
Copyright (c) 1995-2017, EnTech Taiwan.
Version = 1.31.0.1895
OS = 10.0.14393.2 x64
Mechanism = 3
Account = Standard
Command line = "C:\Program Files (x86)\Dell\Dell Display Manager\ddm.exe"
////////////////////////////////////////
GridType.{184C9720-4972-45FE-88C6-ED5F159AA2B7} = 0x00000005
GridType.{CEA1DEE8-2F29-4A21-927D-2374A57BF4FD} = 0x00000005
GridType.{E3A2B645-4AF2-40E3-BC07-82A4F777B0EF} = 0x00000005
UseDesktopforEA = 0x00000001
GridType.{5D689283-F932-4E0E-BC0E-6B11E65FA06C} = 0x00000005
GridType = 0x00000005
GridType. = 0x00000005
GridType.{4BE54F38-B53E-46F0-978E-319DFEF803AB} = 0x00000005
AppScan. = 0x00000004
AppFlags = 0x00002070
AutoRestoreWindowLayout = 0x00000000
LastCheck = 0x0000A802
EnumErrorCount = 0x00000000
HintShown = 0x00000001
C:\Program Files (x86)\Dell\Dell Display Manager\ddm.d3d = 0x00000000
C:\Windows\SysNative\ApplicationFrameHost.exe*Microsoft Edge = 0x00000000
C:\Program Files (x86)\Microsoft Office\Root\Office16\OUTLOOK.EXE = 0x00000000
C:\Program Files (x86)\Microsoft Office\Root\Office16\WINWORD.EXE = 0x00000000
C:\Program Files (x86)\Microsoft Office\Root\Office16\POWERPNT.EXE = 0x00000000
C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE = 0x00000000
C:\Program Files\Windows NT\Accessories\WORDPAD.EXE = 0x00000000
C:\Windows\system32\mspaint.exe = 0x00000000
C:\Program Files (x86)\Windows Media Player\wmplayer.exe = 0x00000000
C:\Program Files\Internet Explorer\iexplore.exe = 0x00000000
C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe = 0x00000000
C:\Windows\SysNative\ApplicationFrameHost.exe = 0x00000000
C:\Program Files (x86)\Dell\Dell Display Manager\ddm.exe = 0x00000000
Metro. = 0x00000000
D3D. = 0x00000000
\C:\Program Files (x86)\Dell\Dell Display Manager\ddm.d3d = 0x00000000
\C:\Windows\SysNative\ApplicationFrameHost.exe*Microsoft Edge = 0x00000000
\C:\Program Files (x86)\Microsoft Office\Root\Office16\OUTLOOK.EXE = 0x00000000
\C:\Program Files (x86)\Microsoft Office\Root\Office16\WINWORD.EXE = 0x00000000
\C:\Program Files (x86)\Microsoft Office\Root\Office16\POWERPNT.EXE = 0x00000000
\C:\Program Files (x86)\Microsoft Office\Root\Office16\EXCEL.EXE = 0x00000000
\C:\Program Files\Windows NT\Accessories\WORDPAD.EXE = 0x00000000
\C:\Windows\system32\mspaint.exe = 0x00000000
\C:\Program Files (x86)\Windows Media Player\wmplayer.exe = 0x00000000
\C:\Program Files\Internet Explorer\iexplore.exe = 0x00000000
\C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe = 0x00000000
\C:\Windows\SysNative\ApplicationFrameHost.exe = 0x00000000
\C:\Program Files (x86)\Dell\Dell Display Manager\ddm.exe = 0x00000000
\Metro. = 0x00000000
\D3D. = 0x00000000
////////////////////////////////////////
09:53:55.771...User session disconnect
10:09:27.781...User session connect
11:13:55.968...User session disconnect
11:25:38.302...User session connect
11:32:02.265...User session disconnect
11:37:34.770...User session connect
11:53:11.661...User session disconnect
11:54:41.576...User session connect
13:09:14.827...User session disconnect
13:13:41.338...User session connect
13:33:18.062...User session disconnect
13:33:19.938...User session connect
13:39:41.238...User session disconnect
13:40:36.777...User session connect
13:46:39.340...User session disconnect
13:55:15.327...User session connect
14:15:58.634...User session disconnect
14:21:11.273...User session connect
14:36:14.115...Display powered ON
14:41:30.553...Display powered OFF
14:47:23.099...User session disconnect
14:50:29.182...User session connect
15:07:56.397...User session disconnect
15:14:20.693...User session connect
15:23:09.047...\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
15:23:09.047...Dump: complete Windows device enumeration
15:23:09.048...1.DeviceName = \\.\DISPLAY1
15:23:09.048.....DeviceFlags = 05000005
15:23:09.048.....DeviceString = RDPUDD Chained DD
15:23:09.049.....DeviceID =
15:23:09.049.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.049...2.DeviceName = \\.\DISPLAY2
15:23:09.050.....DeviceFlags = 05000000
15:23:09.050.....DeviceString = RDPUDD Chained DD
15:23:09.051.....DeviceID =
15:23:09.051.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.051...3.DeviceName = \\.\DISPLAY3
15:23:09.051.....DeviceFlags = 05000000
15:23:09.060.....DeviceString = RDPUDD Chained DD
15:23:09.060.....DeviceID =
15:23:09.061.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.061...4.DeviceName = \\.\DISPLAY4
15:23:09.061.....DeviceFlags = 05000000
15:23:09.062.....DeviceString = RDPUDD Chained DD
15:23:09.062.....DeviceID =
15:23:09.062.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.062...5.DeviceName = \\.\DISPLAY5
15:23:09.062.....DeviceFlags = 05000000
15:23:09.063.....DeviceString = RDPUDD Chained DD
15:23:09.063.....DeviceID =
15:23:09.063.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.063...6.DeviceName = \\.\DISPLAY6
15:23:09.063.....DeviceFlags = 05000000
15:23:09.064.....DeviceString = RDPUDD Chained DD
15:23:09.064.....DeviceID =
15:23:09.064.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.065...7.DeviceName = \\.\DISPLAY7
15:23:09.065.....DeviceFlags = 05000000
15:23:09.065.....DeviceString = RDPUDD Chained DD
15:23:09.065.....DeviceID =
15:23:09.065.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.066...8.DeviceName = \\.\DISPLAY8
15:23:09.066.....DeviceFlags = 05000000
15:23:09.072.....DeviceString = RDPUDD Chained DD
15:23:09.073.....DeviceID =
15:23:09.073.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.073...9.DeviceName = \\.\DISPLAY9
15:23:09.073.....DeviceFlags = 05000000
15:23:09.074.....DeviceString = RDPUDD Chained DD
15:23:09.074.....DeviceID =
15:23:09.074.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.074...10.DeviceName = \\.\DISPLAY10
15:23:09.075.....DeviceFlags = 05000000
15:23:09.075.....DeviceString = RDPUDD Chained DD
15:23:09.075.....DeviceID =
15:23:09.075.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.075...11.DeviceName = \\.\DISPLAY11
15:23:09.076.....DeviceFlags = 05000000
15:23:09.076.....DeviceString = RDPUDD Chained DD
15:23:09.076.....DeviceID =
15:23:09.076.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.077...12.DeviceName = \\.\DISPLAY12
15:23:09.077.....DeviceFlags = 05000000
15:23:09.077.....DeviceString = RDPUDD Chained DD
15:23:09.077.....DeviceID =
15:23:09.077.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.077...13.DeviceName = \\.\DISPLAY13
15:23:09.078.....DeviceFlags = 05000000
15:23:09.078.....DeviceString = RDPUDD Chained DD
15:23:09.078.....DeviceID =
15:23:09.107.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.107...14.DeviceName = \\.\DISPLAY14
15:23:09.108.....DeviceFlags = 05000000
15:23:09.111.....DeviceString = RDPUDD Chained DD
15:23:09.119.....DeviceID =
15:23:09.119.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.119...15.DeviceName = \\.\DISPLAY15
15:23:09.119.....DeviceFlags = 05000000
15:23:09.120.....DeviceString = RDPUDD Chained DD
15:23:09.120.....DeviceID =
15:23:09.120.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.121...16.DeviceName = \\.\DISPLAY16
15:23:09.121.....DeviceFlags = 05000000
15:23:09.122.....DeviceString = RDPUDD Chained DD
15:23:09.122.....DeviceID =
15:23:09.122.....DeviceKey = \REGISTRY\Machine\System\CurrentControlSet\Services\RDPUDD\Device0
15:23:09.122...Total number of monitors enumerated = 0
15:23:09.123...\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
15:23:09.128...Dumping VCP table on
15:23:09.128......VCP table dumped
swamped1
234 Posts
0
October 3rd, 2017 18:00
I don't see anything amiss in that - no indication that EasyArrange ever stopped working. You are using an older version of DDM though - before anything else try updating to the latest version here: delldisplaymanager.com/ddmsetup.exe
jhatch78
8 Posts
0
October 12th, 2018 16:00
Thanks Swamped1! Thanks to you I got it working great a few months ago.
I confirm that it required a current Windows Server upgrade (2016 works) and the registry edit was required. Now my staff and I can all use the Easy Arrange feature inside the VM. Awesome!
Thanks again!
Ady_c
1 Message
0
November 9th, 2018 03:00