This is our ARCHIVE site. This site contains content that was on our community site "amset.info" and is no longer maintained. However as there are large numbers of links to the content on the internet, it has been retained on this site so that people who find that information of use, can still access it. However it cannot be guaranteed to be up to date, or accurate, particularly with regards to modern best practises. Most of the content was originally written between 1998 and 2008.

Image watermarks refer to the old url of amset.info, which is another domain under control of Sembee Ltd.

Our Exchange Server related content can be found at http://exchange.sembee.info/ and is actively maintained. Other sites from Sembee include: dosprompt.info - loginscripts.info - office-recovery.com - wuauclt.info - statuspages.co.uk

Windows

Using Microsoft NetMeeting for Remote Control

One of the relatively unknown features of Microsoft NetMeeting is the ability to remote controls ystems that have been configured to run the software. This uses the existing application sharing feature, with the added bonus of full control over the system, secure connections and auto answer ability on the machine you are connecting to. It is also fairly fast, allowing you to use it over a LAN, WAN or dial up connection in near real time (depending on the speed of your connection) as long as you are running TCP/IP over that connection.

It's use in Windows 2000 Server and Windows XP is now limited as the built in terminal services capability makes a better job. However on Windows 2000 Professional and older operating systems where terminal services is not available, it is still a valuable tool.
More info on terminal services with Windows 2000 Server and Windows XP.

It is an ideal tool for network administrators. 

Although NetMeeting does not offer the same functions and features of the big applications (such as pcAnywhere) if all you want is simple remote control over a desktop it is ideal. Set it up on all of your desktops and you are able to control any system from your own desk, without the overhead and licensing of packages like pcAnywhere or Microsoft's Systems Management Server. With it's low resources overhead, cost (free), user security and the ability to stop users from closing the application down with a registry change, it is an ideal tool to have on every machine on your network. It takes a few minutes to set up and then it is ready to go.

Furthermore you could have it setup on your own system, then if you are working elsewhere on the network and you need to reset a password or do some other task that can only be carried out from your own system, or even just check your email, you can connect back to your own machine without having to walk back to your desk or a server and without having to grant the user any additional rights.

Availability

This functionality is only available on Microsoft NetMeeting version 3.x or higher. 3.x is supplied with Windows 2000 and Windows XP as standard and is available as a free download separately or as part of Internet Explorer 5.x (or higher) for other Windows operating systems.

In Windows XP it is hidden away and needs to be activated. Use the help system to find the "installation" for it and once complete you should find it on the start menu.

Security

With an application of this type, security is very important. You do not want to give someone without physical access to a system remote control access that compromises the network. There are a number of ways that this software overcomes security concerns.

Access Control
On Windows NT, Windows 2000 and XP systems, the software uses the local or domain user manager for authentication. In order to connect to a system you must be a local administrator of the system. This can be set via either a local or domain username.
On Windows 9x and ME systems, a separate password is set within the software. This can make managing the application in these environments a little more complex, but with preset procedures these can be worked around.

Secure Connections
The application has an option to ensure that only secure connections can be made. This can be either via an internal security system which ensure privacy or with external certificates. This means that highly secure connections are possible over the Internet, if your firewall permits them. The security settings are made within the application options.

Stopping and Starting
With NT based systems (NT4 (Server and Workstation) and Windows 2000/XP (Professional and Server) the application can be controlled either via the icon in the system tray or as a service. There are three states:

1. Not running at all (no icon in system tray and service stopped),
2. Application started but not able to receive "calls" (icon in system tray and service paused)
3. Application started and able to receive "calls" (icon in system tray and service started).

This means that some control can be achieved over the application to ensure that only those authorised can use the remote access capability.

Setting up the software

When setting up the software, a reboot will be required on all operating systems except Windows 2000. This should be considered, especially if you are working on a server.

1. If you haven't already, ensure that NetMeeting version 3.x is installed on your system. If downloaded and installed as a separate application from Microsoft it does not usually require a reboot.
2. Start the application. If it is the first time you have started NetMeeting on this system, you will be taken through a wizard. Enter the information you a prompted for. You may want to use the server's name instead of your own name for example. In most cases you will not want to be listed in any of the directory services, so these options should be unselected.
3. You should set the security options first. Click Tools, Options and choose the security tabs. Both the top two options should be selected to ensure maximum security. Here you canreview and use any certificates that you already have on your system.
4. While still in the options menu you may want to verify and enable the setting on the first screen about not logging in to a directly service and not adding your name to the directory. Of course if you are in a corporate environment where NetMeeting is used with an internal ILS (Internet Locator Server) then you should verify these settings with your network admin.
5. On the Tools menu, you should have a option "enable Remote Desktop Sharing..."). Choose it and you will be taken through a wizard. If the wizard has already been run, then you will see the option "Remote Desktop sharing".
6. At the end of the wizard, you may be asked to reboot. If you can, do so. You will not be able to use the feature until teh system has been rebooted. 
7. Once your machine has restarted, return to NetMeeting. From the Call menu there will be a further option, "Exit and Activate Remote Desktop Sharing". Choose this optionand the main NetMeeting application will close. You are now ready to start using the software.

Making the Connection

Making the actual connection to the machine is very easy.

1. Start NetMeeting on the machine you wish to control from (the client).
2. In the top box in the application, you can type either the machine's name or IP address. On a corporate or home network, the name should work. On the Internet, the IP address will have to be used, unless the machine has it's own dedicated DNS entry.
3. Once you have entered the information, click connect and NetMeeting will attempted to "call" the name or IP address you have specified.
4. When the initial connection is made, you should be prompted for username, domain (on NT host systems) and password. Enter the information and you are connected.
5. After establishing the session you will be presented with a summary that informs you that can use the file transfer feature to copy file to and from each machine and that all other NetMeeting features (whiteboard, chat and sharing) are disabled.

Working with the Connection

Most of the capabilities that you need are easily accessible.

Use the Control Menu to send the CTRL-ALT-DELETE command to the host machine.
Use Alt Enter to switch between full screen and window mode on the client machine.
Use the main NetMeeting application on the client to send file. Use the system trayicon on the host machine to do the same thing.

Ending the Connection

Use the main NetMeeting application on the client (your) machine to close the connection (hang up the "call"). On the host machine, the screensaver will be started immediately. If this screen saver is password protected then that function will also be enabled, ensuring maximum security.

Secure the NetMeeting Remote Control Feature

When using this feature of NetMeeting, it can be annoying if your users shut the application down. This registry hack disables that functionality. Add a new key to the following location:

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Conferencing \ Mcpt

It should be of the following:

Value Name: Nx
Data Type: REG_DWORD
Data: 1

Windows 2000 Server and Windows XP/2003 Server

Microsoft have brought in some remote control capabilities as part of the operating system in their latest versions.

Windows 2000 Server

Windows 2000 server has a facility called terminal services. On NT 4, this was a different product, but it is built in to the newer version. However unlike NetMeeting remote control, you do not actually see the desktop on the server.
In turn, there are two versions of terminal services.

Application Sharing Mode is designed for lots of users to connect to the server and actually run applications from it - such as Office and Internet Explorer. A license server must be available on the network and if they are using thin clients licenses will have to be bought. A server being used for this kind of service should not be used for admin tasks.

Remote Administration Mode uses the same client software as the full application sharing mode, but is probably the closest replacement to the Net Meeting remote control. It only allows two connections to the server at any one time. The overheads are very limited and you can run any application or tool installed on the server. This is almost a "must-have" part of the install on any Windows 2000 Server. No additional licences are required. 

Both modes have to be installed from Add/Remove programs, Windows Components. You will be asked which version you want to install as part of the process.

Windows XP and Windows 2003 Server

With the latest version of Windows, Microsoft have made improvements in remote control and remote assistance which makes them a lot more useful in day to day use.
There are two versions. Remote assistance is designed for a user to ask another person for assistance and to allow the helper to view or take control of a desktop. Assistance can be summoned in a number of ways, but the best way is via Windows Messenger. However, both parties must have Windows XP.

The other mode is "Remote Desktop". This allows you to connect to your own machine and take control of your own desktop. While you are controlling it, the standard "Workstation Locked" dialogue box is shown on the screen, then your normal screensaver. This is useful for network administrators who can use any machine that has the client installed (Windows 9x, NT can all have the client software installed). It can even be used over the Internet, if the relevant port (3389) is opened. On Windows XP only one connection can be made at a time.

For both modes, you don't have to install anything, just enable the feature. In System Properties (quickest way --> Right click on My Computer and choose properties), choose the "Remote" tab. You can also control who can access the computer remotely.
For Windows XP, the functionality is available on both Windows XP Home and Professional. 

If you are connecting to a Windows 2003 server and want to view the actual desktop - the "console", then you need to start the client software with the right switch. On the run menu enter the following:

mstsc /console

This will start the client software and will connect to the console instead of a new session on the server. This can be invaluable if you want to see if there is an error message on the screen, or you have left the server processing something and want to check it's progress remotely.