Terminal Services and WAFS

This method applies to MS NetMeeting, RDP, and similar remote Agent software.

To log on to the remote computer using the Console of Microsoft Terminal Services

mstsc /v:<servername> /admin

Note that there is a space before /v and /admin. <servername> is the server you want to manage. Type its IP address or server name.

As of Windows XP Service Pack 3, Windows Vista Service Pack 1, and Windows Server 2008, the /console switch for the Windows Remote Desktop Connection Tool is not available. Use the /admin option instead.

To log off from the Terminal Services Console on Windows Server 2003

  1. Click Start > Run, type tsadmin, then press ENTER.

  2. On the server, on the right side is the account you are logged in as.

  3. Right-click and choose log off.

In Microsoft Terminal Services for Windows 2000, remote users can log in to see ONLY those resources to which they have been provided access. The software runs under the System account. You typically log on through Terminal Services under an administrator account, which does not allow you access or view SYSTEM activities. If you use Terminal Services to access a Windows 2000 computer running the software, you must stop the service, then start the software as an application. You cannot manage it while it runs as a Windows Service.

PCAnywhere, CarbonCopy, RealVNC (free www.realvnc.com), DAMEWARE, GOTOMYPC etc. are not limited like Microsoft Terminal Services for Windows 2000. If using Windows 2000, we recommend the use of one of these products to help manage this functionality.

Configuration Notes

  1. When connecting via Terminal Services to the Windows computer running an Agent, you must log on to the computer using the highest possible access levels. Otherwise, your changes may not be saved when you set it to operate as a Service. Check the owner status of files/folders before making permission security changes.

  2. Microsoft Terminal Services does not allow you to view activity on a remote computer; it shows only a portion (a session specific to your administrator login). Many items that are visible on the actual screen are not displayed. This includes icons, warnings on shutdown, progress bars, status, etc. When you run the Agent as a Windows Service, Terminal Services will not display the icon or menu. You cannot perform Agent management functions while it is running as a Windows Service if you use Terminal Services. You must stop the service and restart it as a program.

  3. Shutdown messages are not displayed, so you must wait for the Agent service to shut off. It may take a minute for the warning screens to timeout.

  4. When logged on via Terminal Services and now running the software as a program (not as a Service), Terminal Services displays all the icons and you can do all Agent management. Note that you do not have access to your files while running as a program instead of a service. Finish making your changes, then restart as a service. Either log on with Terminal Services and run as a program and manage it, or run it as a Service and you can access the files. Perform your management from Terminal Services, and then restart as a Windows Service. (Preferences, Run as NT Service check box.)

  5. If the Agent is running as a Service, and you attempt to start the Agent from the Start menu, you will receive a message that the Agent is already running. It is even possible that another user session started the Agent, and Terminal Services does not show the Windows Service. Look in Task Manager for AANTS, which is the service. Make sure that show processes from all users is selected.

  6. To check on local users' file access, go to Network Neighborhood on your computer (not using Terminal Service), and browse to the files just as a user does. You will be seeing the files exactly as your users do.

  7. Set directory permissions when running as a service. Otherwise, upon a reboot, Windows may not automatically reapply the share setting.

  8. If you do decide to use a different product, such as VNC, shut off the Agent before you log out of Terminal Services. Otherwise, upon connect the Agent will be running, and you may not be able to tell, not even in Task Manager. This will be quite confusing as you start and stop the service but nothing happens and nothing shows up in Task Manager.

  9. Terminal Services has limitations for remote management in Windows 2000. It has more functionality in Windows 2003 and XP when using the console command.

To Manage a Remote Agent with Terminal Services

  1. Login to the remote computer using Terminal Services.

  2. Go to services and stop the Agent. Wait at least 30 seconds.  

  3. Start the Agent as a program.

  4. Perform your management.

  5. When complete, click the icon once, click Preferences > run as NT Service. It needs to run as a Service to provide local user access to the files, and is the best method for share and security setting.