I am also experiencing this with Windows 10 1709 computers. I also noticed that there was only one monitor in the monitor list even though the computer had 3 screens in display settings. In display settings I changed the main display to another monitor and after doing that all of the monitors listed in Dameware's drop down list. After switching the main display back to the original display I could still see all of the monitors and switch to them. I followed Milan's above suggestion to change Default Host Properties and it helped for a minute but after switching monitors I started experiencing screen refresh issues again.
A majority of our computers are on Windows 10 1703 and there is no issue between the machines and Dameware.
Quick and dirty workaround is to disable MRC's mirror driver. When you launch DMRC, fill your user ID and credentials and right under credentials is a checkbox saying "Use MRC's Mirror Driver if available" - simply uncheck and connect.
Minimal difference. Still a lag with Windows 10. I just talked our whole department into purchasing Dameware! Didn't realize there would be this issue with Windows 10.
Hi- what's the best way for me to get an update on this? Is there a newsletter or support bulletin I can subscribe to? Our organization would like to be notified as soon as a new release that fixes this is out.
It would be good to know if will takes weeks, months or years to get this fixed.
In April we are deploying 1709 to 5000+ computers.
If this is not fixed by then we have to find Another alternative.
This is something we dont want to do because we Think that dameware is a good Product but this bug makes it useless.
We have a super strict "do not promise timelines" policy.
I am glad, that you like the product and agree, that this is a serious issue, that needs to be fixed ASAP.
Dealing with this issue since 5 months is not what i call "fixing it ASAP".
Just ridiculous that its taking so long.
Every software development company should test their software with insider preview builds early to avoid such problems.
I don't want to think about what new problems will come with build 1803 & DameWare...
We have lost our trust to Solarwinds, if they at least could show some proof that they are working on it.
They could present some kind of beta
With this silence maybe they will never fix this issue.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.