|
|
 |
Are DameWare Development products compatible with Windows Vista, 2008 Server, and Windows 7?
|
|
Yes. Version 6.x and above of DameWare Development software is compatible with Windows Vista & 2008 Server, and the most current version (v6.9.0.0) is compatible with Windows 7 (both 32-bit and 64-bit). As of the 6.9 release, all of these Operating Systems (Vista, Server 2008, 2008 R2, and Windows 7) are officially supported.
With regard to older versions of the software, even though they may install successfully, and portions of the software may even work, all 5.x and older versions are not compatible with Vista, 2008 Server, or Windows 7. You must upgrade to version 6.x or above to gain compatibility for these newer Operating Systems.
Please also note that at the present time there is no 64-bit version of the DameWare Mirror Driver. The Mirror Driver is currently only supported on 32-bit Operating Systems. However, we are in the process of developing a new version of the Mirrror Driver for 64-bit Operating Systems, which should be available in version 7.x of our software.
|
|
|
|
Back to Top
|
|
|
|
Why do I receive a "Version Registration Number Conflict" message when I try to enter my registration information into the software?
|
|
You are receiving the "Version Registration Number Conflict" message because registration information will only work within the same major version for which it was created. In other words, registration information created for version 4.x products will only work in any 4.x version of the software, regardless of maintenance. Anytime a new major version of the software is released (i.e. 5.x, 6.x, etc.), you will need to contact our sales department for a new set of registration information which is valid for that version of the software. Version 5.x and version 6.x are completely separate products and require a different set of registration information.
Upgrades to the next major version (4.x to 5.x, 5.x to 6.x, etc.) is only provided free of charge if you purchased maintenance with your existing license and that maintenance has not expired. If you did not purchase maintenance or your maintenance has expired, you do not qualify for the free upgrade. However, you can purchase an upgrade at a discounted price.
If you have maintenance on your existing license, then you can request to have your existing license upgraded to the current version of the software online at: https://www.dameware.com/legacy/update/registration or to see if you qualify for the free upgrade. If you run into any problems requesting your upgrade online, please feel free to contact our sales department directly at sales@dameware.com, or at (985) 871-7519 M-F 9:00am-5:00pm CST to obtain a new license that is compatible with your current version of the software.
|
|
|
|
Back to Top
|
|
|
|
Will DameWare Development products work on 64-bit Operating Systems?
|
|
Yes. Version 5.0.1.5 and above of the DameWare Mini Remote Control contains support for 64-bit Operating Systems. However, we are constantly making additional enhancements for 64-bit Operating Systems. Therefore, if you are running an older 5.x version of the software, you may want to consider upgrading to version 6.x of the software (which may or may not be a free upgrade depending on maintenance).
Please also note that even older 4.x versions of the software may be able to connect to 64-bit Operating Systems, provided you manually copy all the DMRC Client Agent Service files to the System32 folder and also the SYSWOW64 folder. Then manually install the Service.
See also:
How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000
Support for Vista (32 & 64-bit) is only included in version 6.x and above, not in any older versions of the software. Support for 2008 Server and Windows 7 (32 & 64-bit) was added back in version 6.8.1.4 and above, and improved in version 6.9.
However, please also note the DameWare Mirror Driver & DameWare Virtual Smart Card Driver are only presently supported on 32-bit Operating Systems. We are currently working on 64-bit versions of each of these Drivers and they should be available in version 7.x of our software.
|
|
|
|
Back to Top
|
|
|
|
How can I use DameWare Development software with Operating Systems other than Microsoft Windows (Unix, Linux, MAC, etc.)?
|
|
At the present time, our software is only supported on Windows Platforms (both the local & remote machines).
However, several users have reported that they were running the DameWare NT Utilities & DameWare Mini Remote Control program on non-Windows platforms such as Linux or MAC under VMWare. Even though we do not directly support our software in this type of environment, it should work.
Unfortunately, if you are wanting to connect to remote machines running these non-Windows Operating Systems, this most likely will not help. In these scenarios the only other possible solution would be to install the appropriate version of the RDP Client Agent on these remote machines. Then you could enable the "Use Remote Desktop (RDP)" option within the DameWare Mini Remote Control software to make an RDP connection to that machine.
|
|
|
|
Back to Top
|
|
|
|
Does DNTU and MRC's RDP functionality support the new /admin switch included in Vista SP1 and XP-SP3?
|
|
Unfortunately, not at the present time, and it will take some time before we can support this new /admin switch. Our software presently only supports the /console switch. Therefore, at the present time if you're running Vista SP1 or XP SP3 locally, then you won't be able to establish a RDP console session from within our software. But you can still connect via RDP (non console) or via a standard MRC connection.
Just FYI, beginning in version 6.1 and above of Microsoft's RDP Client (mstsc.exe), the /console switch has been replaced with /admin. Version 6.1 is included in Server 2008, Vista-SP1 and XP-SP3.
|
|
|
|
Back to Top
|
|
|
|
I receive a "System Error: 1722 - RPC Server is unavailable" when I try to remotely remove the DMRC Client Agent Service. How do I correct this?
|
|
Most likely either File & Printer Sharing is not enabled on the remote machine, or the necessary File & Printer Sharing ports are blocked somewhere between the local and remote machines. File & Printer Sharing is a requirement of Microsoft's APIs used to remotely install, remove, start, or stop the DameWare Mini Remote Control (DMRC) Client Agent Service.
This could be caused by an improperly configured firewall between the two machines, by some type of firewall software on the remote machine, or by File & Printer Sharing not being enabled on the remote machine. Once you correct the configuration issue (network, O/S, etc.) you should then have this ability from within our software as well.
Microsoft defines File & Printer Sharing as the following ports: UDP 137 (Name), UDP 138 (Datagram), TCP 139 (Session), & TCP 445 (Direct Hosting).
|
|
|
|
Back to Top
|
|
|
|
I cannot close the Notification dialog and the SysTray icon appears when I connect to a remote machine using the DMRC program, even though I have disabled these settings in the Client Agent Service. The text "Evaluation" also appears in the Notify Dialog. Why does this happen?
|
|
Actually, this functionality is by design, and it implies that your local copy of the DameWare Mini Remote Control (DMRC) software is still running in Evaluation Mode. It has not been registered properly.
This is a limitation while the software is still running in Evaluation Mode. Until your local copy of the DMRC software has been registered properly, even if you disable those notification features within the Client Agent Service, those settings will be ignored when you connect. Once your local copy of the DMRC software has been registered properly, these features will be available.
Even if you are running the full DameWare NT Utilities (DNTU) suite, and you have already registered DNTU, the DMRC program is still a separate application. Normally, it would automatically pick up DNTU's registration information, however, sometimes that does not happen. Therefore, there may be times when you need to enter the registration information into the DMRC program as well.
When this occurs, open the DMRC program, click on the Help / About DameWare MRC menu, then click on the Registration button. Enter all the registration information into the software and everything should work properly.
|
|
|
|
Back to Top
|
|
|
|
When I connect to a remote machine using the DameWare Mini Remote Control program, I see a small blue or red box in the center of the screen saying I should update the Client Agent Service on the remote machine. How can I update the Client Agent Service once I'm connected?
|
|
If you are running version 5.x or above of the DMRC software, and you are connected to the remote machine using Administrator credentials, you can simply select File / Update Client Agent from the DMRC main menu once you connect.
We always recommend that you update the Client Agent on the remote machine to stay current, because we cannot guarantee all features of the software will work correctly when there is a mis-match in versions locally vs. remotely. However, under certain circumstances, instead of automatically forcing you to update the Client Agent before you can connect, the software will just display the warning dialog letting you know you should update the Client Agent as soon as possible.
If for some reason the Update Client Agent menu is still not shown, then it is possible this behavior is related to not updating the DMRC Toolbar because the File / Update Client Agent was a hidden option in a previous version of the software. The menu entries stored in the Registry are still the old entries, not the new ones.
If this is the case, try deleting the following Registry key:
[HKEY_CURRENT_USER\Software\DameWare Development\NT Utilities\DNTU\MRC Bars]
Restart the software and this issue should be resolved.
|
|
|
|
Back to Top
|
|
|
|
Can the installation of the DameWare Mirror Driver be automated or scripted for mass deployment?
|
|
Yes, but only in version 6.x of the software. For version 6.x, you simply have to install version 6.x of the DMRC Client Agent Service on the remote machine, and the Mirror Driver will automatically be installed the first time you connect to this machine with version 6.x of the DMRC software.
Version 6.3 and above also includes the complete version of the DMRC Client Agent MSI builder, which allows you to build custom MSI packages (including all settings, INI or Registry) to deploy the DMRC Client Agent Service in your environment. These MSI packages can then be sent to your clients (or even distributed via Group Policies within Corporate Environments, etc.) via any of your existing distribution methods.
This is not possible in version 5.x of the software. For version 5.x of the software, you first have to connect to the remote machine and install the Client Agent Service. Next, provided the remote machine is running Windows 2000 or greater, you could select File / Mirror Driver Installation and follow the prompts (may or may not require a reboot of the remote machine).
|
|
|
|
Back to Top
|
|
|
|
When I connect to a remote machine with DMRC version 5, the cursor on the remote machine blinks. This did not happen in version 4. How can I prevent this?
|
|
Support for "Transparent Windows" is enabled by default in version 5, which could possibly cause the mouse cursor to flash/fade in and out. Therefore, you could just toggle it off in the DMRC Toolbar. However, you will not see any transparent windows that are displayed on the remote machine (i.e. ToolTips, etc.). For example, in Windows XP when you hover over an Icon, or the Clock, you see a popup window appear. That is called a tool tip, but you will not see it displayed over the DMRC connection unless you have "View/Hide Transparent Windows" turned on.
Another possible work-around is to install the new DameWare Mirror Driver on the remote machine, then enable the "Use MRC Mirror Driver" setting on the Remote Connect dialog box before you connect.
|
|
|
|
Back to Top
|
|
|
|
How can I speed up a DMRC connection when the remote machine is running a DOS application?
|
|
Try adjusting the "Idle Sensitivity" property of the "_default.pif" MSDos file to as high as it will go. The settings specified in _default.pif file are used by all DOS applications, unless there is an application specific PIF file defined.
The _default.pif file is located in the Operating System installation directory (C:\Windows for XP, C:\WINNT for 2000, etc.). Locate this file, right-click on it and select Properties, then select the MISC Tab. Move the "Idle Sensitivity" slider bar all the way to the right, and select OK. This procedure also applies to application specific PIF files for this DOS application.
Once you have made these changes, open your DOS application and reconnect via DMRC.
Please also note that the DMRC program does not support Full-Screen DOS windows. However, you should be able to press ALT+ENTER to change to a DOS Window.
|
|
|
|
Back to Top
|
|
|
|
How can I be notified when a new release is available?
|
|
Login to the DameWare Forum. Select the topic entitled "DameWare Version 6 Product History." At the bottom of the topic view there will be a link to "Subscribe to Topic." Select this link and you will be emailed when a new release is available and this topic is updated with the details.
|
|
|
|
Back to Top
|
|
|
|
Why do I receive a System Error: 2273 when I try to send a message in DameWare NT Utilities?
|
|
Try issuing a "net send" command from a command prompt. If this fails, then DNTU will also fail. An explanation from Microsoft: The message could not be delivered because the addressee is not logged on, or is not using the name you sent the message to as a computer name or message alias. Here is some additional information from Microsoft's website.
"NET SEND" to Windows 2000-Based Computer May Not Succeed
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q263464
You can also receive this error message if the "Messenger" Service is disabled, or enabled but not started, on the local and remote machines.
Windows XP SP2 has some known issues with regard to the Net Send command.
The NET SEND command may not work correctly on a computer that is running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839018
|
|
|
|
Back to Top
|
|
|
|
What ports are used by DameWare Development software?
|
|
Provided the DameWare Mini Remote Control (DMRC) Client Agent Service is already installed and running on a remote machine, only a single TCP port is used. The default TCP port is 6129, however, you can configure the DMRC program and Client Agent Service to use any one of the 65,000 valid TCP ports.
If you are attempting to connect to this machine over the Internet, we recommend you use an obscure TCP port, something other than 6129, because TCP 6129 is a well known port for the DMRC program.
All the Views in the DameWare NT Utilities (DNTU) program (i.e. Users View, Event Log View, etc.), all the functionality in the DameWare Exporter (DEXP) and DMRC program's ability to remotely install, start, stop, or remove the DMRC Client Agent Service use the Operating System's installed protocols, basically File & Printer Sharing (i.e. 137-139/445).
Microsoft defines File & Printer Sharing as:
UDP 137 (Name)
UDP 138 (Datagram)
TCP 139 (Session)
TCP 445 (Direct Hosting)
For security reasons, we do not recommend that you open these specific File & Printer Sharing ports on any routers/firewalls connected directly to the Internet. It would be much more secure to establish some type of VPN or SSL connection to the remote network first, then use the software over that secure connection.
|
|
|
|
Back to Top
|
|
|
|
Do DameWare Development products work in a Citrix or Terminal Services environment?
|
|
Yes. Our software will work in a Terminal Server/Citrix environment, allowing multiple administrators to use the product. Many customers report using DameWare software in this type of environment without any problems.
For additional information about using our software in Citrix /Terminal Services environments, please see our Citrix/Terminal Service knowledgebase article:
Using DameWare Development software in Citrix or Terminal Services implementations.
http://www.dameware.com/support/kb/article.aspx?ID=300081
|
|
|
|
Back to Top
|
|
|
|
Sometimes when I use the DameWare Mini Remote Control I do not get a response from the keyboard. I type on my keyboard but nothing appears on the remote system.
|
|
When this happens, please try using the DMRC's "Send Refresh" option from the Send Menu. The Send Refresh feature is designed to clear the keyboard state. If it does not work, try pressing the Ctrl key once and the Alt key once to clear the stuck keys.
Verify that the DMRC connection settings are not set to View Only mode.
|
|
|
|
Back to Top
|
|
|
|
How do I blank the monitor on a remote machine when I connect with the DameWare Mini Remote Control program?
|
|
Unfortunately, we do not directly support this feature and we cannot guarantee that it will work properly in every situation (for example when the remote machine is connected through a KVM). However, it is included in version 4.2 and later.
Select a specific host entry and click on the Settings button. Look on the Remote Options tab, and you will see an option called "Enable blank monitor." Note that the "Enable Blank Monitor" checkbox can only be enabled after you enable the "Lock Remote Keyboard & Mouse" setting directly above it.
This functionality is simply a Microsoft API call, and it could possibly fail if the remote machine does not support this functionality. The only way to implement this feature with any certainty is to use Low-Level drivers. This would require a reboot of the remote machine after the Client Agent Service installation, which would defeat the purpose of being able to remotely deploy the Client Agent Service "on the fly." This is why we do not support this feature.
|
|
|
|
Back to Top
|
|
|
|
Why do I need permission to connect to a remote machine using the DameWare Mini Remote Control program?
|
|
This depends on your rights within the remote O/S (Admin vs. Non-Admin) and the Permission Required settings.
This is the behavior when you connect to a remote machine and the "Permission Required" setting is enabled on the Additional Settings tab within the MRC client agent service settings. This applies to Admins and Non-Admins.
Or, you connect to a remote machine and the "Permission Required for these Account Types" setting is enabled on the Access tab within the MRC client agent service settings. This setting applies to Non-Admins.
For additional information please consult the following Knowledgebase article:
Permission Required, Waiting for Client to Accept Connection, and Non-Administrator Mode
http://www.dameware.com/support/kb/article.aspx?ID=300073
|
|
|
|
Back to Top
|
|