My testers have been reporting back some weird behaviour with the beta agent, this may be due to only testing the beta agent with using MIRC 12.04
chatting text in common applications from remote machine is not appearing on local machine
Crashing on remote computer
I wanted to try test the 12.1 beta agent with using MRC 12.1. Problem is to test this properly in our environment we want to be able to install MRC 12.1 in centralized mode to connect to our centralized server through AD accounts
I dont see this option anywhere. Usually this asks you upon the install process like our precious version
Is there another way to get this to install so when you launch it it pops up with centralized server authentication?
It seems I can only test this with evaluation mode
Even if the evaluation mode works flawlessly its useless to us unless we can get it to connect to our centralized server
This is what I mean by not seeing any option to install in Centralized mode:
Since the Beta1 launch, we have added multi-monitor support to the new mirror driver, added different bit modes, fixed security vulnerabilities and fixed FIPS mode.
We're now working on 4k resolution support and TLS1.2 support for the over-the-internet connections.
pguerrisi, I am not allowed to communicate timelines. Since the Beta1 launch, we have fixed most of the issues present in Beta1 and finalizing features, that were not present in Beta1. I'd like to give you stable Beta2 build.
So coming across an issues in our test group here at the office. 12.1 responds great with Windows 10 and I notice the difference from each software version but unfortunately, 12.1 Beta 1 seems to lock up the screen on my end while it still displays my mouse moving on the end-users computer. Disconnecting and reconnecting will allow the connection to be reestablished. This is caused but using the 12.1 Beta 2 on my desktop and 12.1 Beta 1 on the end users.
If we setup 12.1 Beta 2 on my desktop and the end users, we get an issue where the screen freezes on "Initializing Desktop, please wait."
We never had this I issue with 12.0.5 on our old systems so I figured it may still be a bug that's being worked on.
I've got the same problem with version 12.1 beta 2 connecting Computer with Windows 10, but not all the Windows 10 were freeze at "initializing" screen. which is still confused me.
when i trying to remote a computer after installed the DMRC 12.1 Beta 2 on my laptop, there is a selection popped up that you can choose whether you want to install some update on your remote computer.
if you choose not to install the update, the performance would remain slow. and when you choose to install the update, the Freeze at "Initializing" happens.
here is the findings from the test I've just been done minutes ago.
there are 2 computers with Windows 10 that i had chose for the test.
Computer A: Frozen at the "initializing"
OS Build: 16299.611
Amount of items existing in the folder C:\Windows\dwrcs\: 97
Has been connected by other versions of DMRC Previously?: Yes, DMRC 12.0.5.
Computer B: not frozen at the "Initializing.
OS Build: 16299.309
Amount of items existing in the folder C:\Windows\dwrcs\: 43
Has been connected by other versions of DMRC Previously?: No.
after i had copied and replaced the folder C:\Windows\dwrcs\ from B to A, and tried to remote Computer A using DMRC, it's worked as expected, the refresh rate is acceptable.
apparently I am not sure how these software works internally, that is why it is still confused me, hope the input helps you to figure out and fix the problem. Thank you.
and it is appreciated that if you could send me an update when there's any useful updates or any beta/official version released.
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.