Our company is rolling out windows 7 and now I get a System Error 5 when trying to connect to a XP or even a Win 7 computer. Any way to solve this?
↧
System 5 error. Access Denied
↧
Is DMRC compatible with Windows 10?
I use Dameware Mini Remote Control to remote into my servers from home. My home PC is WIN 7. I have the free upgrade to Win 10 but do not want to install until I verify DMRC will be compatible with the new OS. I have version 11.1 64bit
↧
↧
Dameware remote control is slow to connect.
When Windows Firewall is enabled stealth mode is enabled by default and there is no supported method to turn this off.
Is there any way to fix this problem on the client side without installing dameware on every single computer.
So what happens is you connect to a computer with dameware the connection spends several very noticable seconds before it promts you to install the client. This is because it seems to assume the client is always installed. And this is why stealth mode causes a problem.
Is there any way for the dameware client to do a check for the client service first and then connect or install the client?
Is this problem solved in any of the recent versions of the software? I belive we are a few versions behind.
↧
Dameware MRC V 9.0 64 Bit And Windows Server 2012
Good Afternoon,
I recently tried installing the Dameware Mini Remote driver onto a Windows Server 2012 machine and it continues to report back "The Operating System has reported that a reboot of the remote machine is required to complete the Mirror Driver installation/update". Once you click ok, it lets you in. But, everytime you remote in with Dameware, it pops up this message. The system has been rebooted multiple times and tried installing the driver multiple ways with no success. How do I get around this? Thanks
↧
RECOMMEND DameWare MRC ON SPREAD THE WORD FOR A $25 AMAZON GIFT CARD!
Let the community know how impressed you are with DameWare MRC and earn a $25 Amazon gift card! Simply post your review in Spread The Word with the questions answered below:
- What was life like before using SolarWinds? (Include what you were using and why you decided it was time for a change)
- Which SolarWinds product(s) saved your bacon?
- Did you consider other options, and why did you choose SolarWinds?
- How has life been since you've rolled out SolarWinds in your environment?
↧
↧
host list conversion mrc.dbf (v6.9) to mrccv2.db (v10)
Need help with host list conversion mrc.dbf (v6.9) to mrccv2.db (v10)
My mrccv2.db is always blank. I have tried deleting and the conversion dialog appears for a moment, but the end result is always a blank host list.
↧
NON-ADMIN USE OF MRC V11
I would like to request help/walk-through/guide to having non-admins use DameWare Mini Remote Control v11 without having someone on the remote end that needs to accept the incoming connection request. The non-admin users may granted Remote Desktop User rights but may not have local admin rights permanently. We have many Processor Engineers, amongst other areas and users, that require a way to remote into systems but cannot use RDP. Due to audit reasons we cannot add them as administrators.
FYI - I entered this as a feature request, but I am starting to think this should not be a request as it should all ready be part of the software functions.
I have already add the user/s to the Remote Desktop Users group on the remote PC's I am using to test.
The case I sited in the Discussion Title is closed but was opened end of August in 2013. At that time we had been using version 8 and we went a different route but it has come up again and I need to find a solution. Below you will find what I was asked to try by Solarwinds to get this working.
Try this settings for Non- Admin. But this requires permission of the remote machine.
- On the DMRC Remote Connect window Click on the Settings
- Under Properties, look for Install Options Tab
- Click on Configure button
- There you will see the Additional Settings Tab
- It will need to tick on Permission required then Ok
I made these changes well logged in as a administrator. I then went to my non-admin account for testing and I receive the following error:
"The remote machine reported the following error:
The remote system is currently at the Logon Desktop.
Your credentials do not allow for access at the current desktop state."
Next I gave my non-admin account admin rights to check if the settings actual transfer between accounts; they do not. I changed them and tried again (after removing the local admin rights) but still received the error message. So next I changed the following settings under my non-admin account with local admin rights.
Under Additional Settings tab:
- checked Permission Required
- unchecked On Disconnect Logoff
Under Access tab
- unchecked All three boxes at the bottom
I logged off, removed the local admin rights, tried again; but still receive that same error message. If I am logged in to the remote PC as the user I do not receive the error message. Someone on the remote end still needs to accept the incoming connection request though.
So basically what I have going on is it only works if the user is logged in and the PC is not in a locked state. But not just that; someone on the remote end also has to accept the incoming connection request. I need to be able to have a non-admin account remote into the PC without requiring someone on the remote end. That user may be granted Remote Desktop User rights but may not be granted local admin rights.
Any and all help would be greatly appreciated.
↧
Dameware Mini Remote Control - Question
Can the Mini Remote software be configured so that a specific Computer Name access only specific other computers within the LAN?
↧
Dameware 12.0 is now Available!
I’m thrilled to announce that Dameware 12.0 is now publicly available. In this release we focused all our efforts to finalise the remote support story with unattended over the internet sessions. Dameware now allows to assist remotely without presence of the end-user, who is not in the intranet but travelling. Technicians can now support end-user in company network as well as in Internet anytime.
This release brings several bigger and smaller improvements, so let me highlight a few of them:
- Over the Internet (OTI) unattended sessions for Dameware Centralized users
- Allows you to remotely support users on the move, and assist remotely without the presence of the end user
- Deploy agents with OTI unattended support to end-points
- Manage agents for OTI unattended sessions to maintain high security and control
- Search Hosts in Mini Remote Control
- Support for Windows 10
- Ability to switch between the Standalone and Centralized versions without reinstallation
- And many other improvements and bug fixes
Dameware 12.0 is available for download on your customer portal for those customers under current maintenance.
If you are not a Dameware user yet, now go and download new version from www.dameware.com now!
↧
↧
v10 Reverse Connection not working
I am trying to connect to remote sites using the reverse connection option, and am running into a wall.
We have multiple public I.P. addresses available to us at our technical support site, so I have configured our SonicWall to forward requests sent to one of these address (xxx.xxx.xxx.xxx:6130) to the local I.P. address of my workstation. I then set my local DMRC to accept incoming connections on port 6130.
On the remote workstation, I have installed the DMRC client using an MSI created with the MSI builder. The settings on the client are as shown in the attached document.
When I try to connect form the remote workstation, to the public I.P. address and port 6130, I get the error listed in the attached document.
I have stopped and started the service on the remote system, with no effect.
What am I missing?
↧
Dameware MRC Version 11 Warning Border is disabled
Since upgrading to Damware Version 11 using the Centralized server the option to turn on the warning border is disabled.
↧
Dameware Centralized Server - Useless?
Hi all,
i am sorry but i have to say i really expected more from Dameware Centralized Server. I installed the Centralized Server today (no proxy, no gateway), but this tool is just useless in my opinion.
Installation was easy yes, but after an hour i have to say: It is only usefull for centralized license management, thats all! If you have just a few licenses, dont waste your time and manage them manually.
Things i am really missing (and i think i am not alone requesting such features)
- only AD User Import, no real AD integration. Hence you have to manage your users manually.
- no Rights Managment - only admin or no admin
- no centralized config management
- no autologin with DRMC or DRMS
Global host list:
- No rights management (user only should have access to a few hosts / folders)
- no centralized and advanced settings for hosts entries (only connect with RDP to a specific host) settings will be ignored if you connect via DRMC
- its just a list of your favourites, not more not less.
Is there a wishlist for product improvement? When is the next update planned?
Thanks
Peter
↧
Dameware 10 Mini Remote Control Tool - Admin Cert on CAC
Hello,
I am setting up Dameware 10 Remote Control Tool on a few systems and am having an issue getting connected to remote systems using my CAC. We have both admin and regular certs on the CAC but will be using the admin cert to do the remote control assistance.
Ill give you a rundown of what I am doing:
Right click DameWare Mini Remote Control > Run as (choose my admin Cert from CAC)
Fill in all information needed (Select Smart Card logon and fill in PIN)
Click connect and get error, after a few moments of waiting
Error:
DameWare Mini Remote Control
Smart Card Logon Failed (5.2).
System Error: 1326
System Message: Logon failure: unknown user name or bad password.
After inspecting the security logs on the client system I see that the error is because its attempting to use my regular user account, not my admin account. Even tho we are running the MRC tool using admin cert credentials.
Security Logs on client system shows the attempted connection and failure:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: %COMPUTERNAME%$
Account Domain: %DOMAIN%
Logon ID: 0x3e7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: %REMOVEDINFO%
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0x380
Caller Process Name: C:\Windows\dwrcs\DWRCS.exe
Network Information:
Workstation Name: %Computername%
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: DWMRC3
Authentication Package: Kerberos
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
I am a local admin on remote system and can confirm this with username and password, so we know the authentication is there. For some reason it keeps defaulting back to the regular user cert.
Any thoughts on it?
↧
↧
DameWare Centralized Server 12 RC--How can I import host from AD OU?
I'm wanting to try out the centralized server to see if it's more useful than the first time we tried it over a year ago. I am wanting to import hosts from one of our workstation OUs, but that doesn't seem to be possible. When trying to import, my only option is to import computers from a group. None of our machines are in a group other than the default Domain Computers group, and I do not want to import that. We have our workstations broken out into different OUs. Is this possible? Without this ability, the centralized server is useless to us. Thanks.
↧
damewareminicontrolsettings.ini settings for administrator and non-admin users
Hi,
How could I configure damewareminicontrolsettings.ini so that administrators should not need permission to take over and that a certain group (on domain) needs permission to take over on remote ?
So Admin no need for permission
certain group - need permission
all others who try to connect - no allowance at all
↧
license manager from cmd line?
Are there any command line swtches for License Manger so that one can script out the deactivation of the license?
↧
Dameware MRC V 9.0 64 Bit And Windows Server 2012
Good Afternoon,
I recently tried installing the Dameware Mini Remote driver onto a Windows Server 2012 machine and it continues to report back "The Operating System has reported that a reboot of the remote machine is required to complete the Mirror Driver installation/update". Once you click ok, it lets you in. But, everytime you remote in with Dameware, it pops up this message. The system has been rebooted multiple times and tried installing the driver multiple ways with no success. How do I get around this? Thanks
↧
↧
Pushing settings out as easy as importing registry keys?
We just rolled out Dameware 11 (we were on 9 before). This is standalone, not the centralized server model yet. I noticed even though I used the MSI builder and configured the settings, they didn't seem to apply to everyone. For example we have just started testing removing "Domain Admins" from our IT support people and in order to still be able to use Dameware we had to push out settings for only allow these specific groups to connect to not only DOMAIN\Domain Admins, but also DOMAIN\Information Technology. At least one person's dameware was asking them for permission and even when granted we couldn't take control (view only). A few others we could not connect at all with our windows credentials unless I ran MMC as a domain admin, managed that particular computer and put Information Technology in as a local admin.
So I did some digging with Regshot and found all the settings seem to be saved at HKLM\Software\DameWare Development\Mini Remote Control Service. So I got all the settings how I want them, tested them and then exported this branch in regedit. I imported it into Dell Desktop Authority so these registry keys are imported to the PC if the dwmrc.exe file version is equal to 11.0 or greater. So far it seems to work. Are there any caveats to doing this? Again it seems to be working fine but I wanted to post it out there just as an FYI.
↧
My Dameware MiniRemote 11.1 is not installing
When I run the DameWareMRC32-St-v11.1.exe or DameWareMRC64-St-v11.1.exe, It appears to "unpack the binaries" then just quits.
I had it installed and working before the holidays.When I returned I ran a PC cleaner. Afterwards, Dameware claimed that the licence had expired. I uninstalled the software at the request of IT and attempted to re-install with the results above. Any Ideas??
The PC cleaner may or may not have had any influence in the situation. I did not run DWMRCS before the cleaner. So, I don't know if it worked directly before. I mention it only to provide a clear picture of the situation.
Mark A Conway
Director - Applied Technology
Gilmore & Associates
↧
Dameware remote control is slow to connect.
When Windows Firewall is enabled stealth mode is enabled by default and there is no supported method to turn this off.
Is there any way to fix this problem on the client side without installing dameware on every single computer.
So what happens is you connect to a computer with dameware the connection spends several very noticable seconds before it promts you to install the client. This is because it seems to assume the client is always installed. And this is why stealth mode causes a problem.
Is there any way for the dameware client to do a check for the client service first and then connect or install the client?
Is this problem solved in any of the recent versions of the software? I belive we are a few versions behind.
↧