DameWare NT Utilities requires Windows NT 4.0, Service Pack 1 or
greater (including Windows 2000, XP, 2003, Vista, 2008, Windows7).
The APIs used by DNTU also require the user to have the ability to
authenticate to this remote machine over the network. In other
words, it may require the Server Service, the NetLogon Service
(Domain environments), and possibly the Remote Registry Service as
well (Event Log View, Properties View, Processes View, Registry
View, Services View, & Software View. Because these views also
require access to the Registry).
Please also note that the Remote Registry Service is turned off by default in Vista, Server 2008, and Windows 7.
The following informational message will be displayed whenever DameWare NT Utilities is executed on machines that do not have version 4.71 or later of the Microsoft COMCTL32.DLL file:
This version of DameWare NT Utilities requires a newer version of COMCTL32.DLL (Version 4.71 or later) than what is installed on this machine (Version x.xx)*. A newer version of this DLL can be obtained from Microsoft and is shipped with NT SP4 and IE 4.x or higher.
*Note: x.xx will be changed to show the version on the machine receiving this message.
When this message is encountered, DameWare NT Utilities will still function however, it is recommended that the COMCTL32.DLL file be revised to a later version. This file is not re-distributable by third party software developers but you can download it from Microsoft and install it. At the time of this writing, two versions are available for download from Microsoft, 4.21 with a file name of 401COMUPD.EXE and 5.80 with a file name of 50COMUPD.EXE. These files can be found at the following URL: http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp
DNTU’s Active Directory functionality is only supported on machines running Windows 2000 and above. However, even though it is not directly supported, many of DNTU’s Active Directory features will still work on machines running Windows NT4 SP-6a, provided you also installed Microsoft’s Active Directory Client Extensions (DSClient.exe) for Windows NT4. For more information about Microsoft’s Active Directory Client Extensions, please refer to Microsoft’s website.
Active Directory Client Extensions for Windows 95/98 and Windows NT 4.0
Support for Exchange 5.5 was dropped back version 5.x of the NT Utilities software.
Exchange 2000/2003 support is only supported in version 4 and above, and only within DNTU's Active Directory Users & Computers portion of the Browser (and it does not require the Exchange Admin Tools nor User Manager Extensions). Exchange 2000/2003 functionality is not available within the Microsoft Windows Network portion (i.e. Users View, etc.) or Favorite Machines (formerly non-Browsable) portion of DNTU.
When you open DNTU's Active Directory Users & Computers section on a Domain Controller, the only way DNTU's Exchange Tasks (right-click context menu) will be enabled is if DNTU also detects that Exchange 2000 or greater is installed on this specific AD site. If this specific machine where you opened the Active Directory Users & Computers section is not your Exchange Server (i.e. you have another machine in your Domain that is running your Exchange Server), then you will need to right-click on DNTU's Active Directory section, then select Add Active Directory Site, then add the IP-Address of your Exchange Server. However, DNTU also requires that your Exchange Server also be running Active Directory. In other words, your Exchange Server must also be an Active Directory Domain Controller for this Domain. If you Exchange Server is not running AD (i.e. Domain Controller), then DNTU's Exchange Tasks menu will not function properly and you will receive an error.
If everything is setup correctly in your environment, then you should be able to right-click on an AD object (i.e. User, Group, Contact...) under AD Users & Computers (or in an OU), then select the Exchange Tasks context menu. Then selecting your desired Task (i.e. Create Mailbox, Move Mailbox, Delete Mailbox, Establish Email Addresses, Delete Email Addresses, or Update now). Or you can also access other Exchange settings via the Exchange General, Email-Addresses, or Exchange Advanced Tabs, on the User Properties GUI. Just make sure the "View Advanced Properties" setting is enabled.
For the MRC Program:
The MRC program requires the TCP Protocol.
MRC Application (Installed on the Local Machine):
Version 7 of the MRC program is officially supported on all Microsoft Windows Operating Systems beginning with Windows 2000. The local machine, where the MRC application is installed, must be running one of the following Microsoft Windows Operating Systems: Windows 2000, XP, Server 2003/2003 R2, Vista, Server 2008/2008 R2, Windows 7. All service pack levels for these Operating Systems are supported. Both 32-bit and 64-bit versions of these Operating Systems are supported.
***It is possible that older Operating Systems will still be able to run the MRC application, however DameWare Development cannot guarantee it can be done without issues
MRC Client Agent Service (Installed on the Remote Machine):
Version 7 of the MRC client agent service can be installed and run on machines running all Microsoft Windows Operating Systems beginning with and including Windows 95, 98, ME, NT 4.0, XP, Server 2003/2003 R2, Vista, Server 2008/2008 R2, and Windows 7. All service pack levels are supported with these Operating Systems except where noted in parentheses. Both 32-bit and 64-bit versions of these Operating Systems are supported. For 64-bit remote machines, the new 64-bit MRC Client Agent Service can be used.
***Note: To connect to a Windows 95 machine it must
have Winsock2 as well as upgraded Comctl32.dll (to version 4.70)
and the upgraded Unicode layer. The following downloads are
available from Microsoft:
Com32upd.exe for Windows 95 (Upgrades Comctl32.dll to version 4.70):
Windows Sockets 2.0 (Winsock2) for Windows 95:
Platform Software Development Kit Redistributable: Microsoft Layer for Unicode on Windows 95, 98, and Me Systems, 1.1.3790.0:
***The MRC Mirror Driver is supported on Windows 2000 or higher.
The video card of the remote machine must support the following raster capabilities:
Transferring bitmaps (RC_BITBLT)
Supporting the Windows APIs, SetDIBits and GetDIBits functions (RC_DI_BITMAP)
Support only one color plane.