Terminal Services - Frequently Asked Windows Terminal Services Questions!

[12] Frequently Asked Asp Questions!
Updated: Jun 07, 2000
[188] Frequently Asked Citrix Questions!
Updated: Oct 10, 2006
[3] Frequently Asked Sco Tarentella Questions!
Updated: Aug 16, 2002
[260] Frequently Asked Windows Terminal Services Questions!
Updated: Aug 03, 2006
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [16] 17 18 19 20 21 22 23 24 25 26
Can the Lotus Notes user`s work files be mapped back to the connected user`s local drive? 

No, in most cases the Terminal Server session cannot handle the access load of the concurrent file transfer of the Notes session. The user`s work files must be accessed directly by the system running the Notes client application and hosted on the same system`s local storage or a local file server mapped drive that meets the Terminal server farm configuration requirements

Users keep getting the error message: "This page provides potentially unsafe information to an ActiveX Control". How do I fix this? 

If you receive:

      This page provides potentially unsafe information to an
      ActiveX Control. Your current security settings prohibit
      running controls in this manner. As a result, this page
      may not display correctly.

when you start Internet Explorer version 4.0, and/or An ActiveX Control on this page is not safe.  Your current security settings prohibit running controls on this page.
As a result, this page may not display as intended.
when you click on a drive in My Computer or in NT Explorer, you are probably running Office 97 and you used the Eraser97.exe/2000 utility at one time or another.

To fix this problem, reinstall Comcat.dll:
1. Copy Comcat.dll from the \\System folder of the Office 97 CD to
   %Systemroot%\System32.   
2. Start / Run: Regsvr32 c:\winnt\system32\comcat.dll
3. Click OK. You should receive DllRegisterServer in c:\winnt\system32\comcat.dll
   succeeded.

Are there any compatibility issues between MetaFrame XPe System Monitoring and Analysis component (Resource Manager) and Microsoft Data Access Components (MDAC)? 

This note discusses compatibility between MetaFrame XPe System
Monitoring and Analysis component (Resource Manager) and Microsoft
Data Access Components (MDAC). MDAC 2.5 SP1 is recommended for
MetaFrame XP and Resource Manager.
The original English version of the System Monitoring and Analysis CD
included with MetaFrame XPe contains an error in the
Resource_Manager_Readme.txt file. The file recommends installing
Microsoft Data Access Components (MDAC) Version 2.5 and then 2.6, but
MDAC 2.6 may cause problems with MetaFrame XP and should not be
installed. MDAC compatibility issues can cause the IMA Service to
terminate. If MDAC 2.6 is used, you must also install the Microsoft
Jet 4.0 Service Pack 3. The server MUST be rebooted after installing
the Jet service pack.

MDAC 2.5 SP1 is currently the recommended version for MetaFrame XP
and Resource Manager.

Important! Disregard the following in the Resource_Manager_Readme.txt.

"Error message: Failed to load plugin `RMAnalysisSS.dll` after
installation."
======================================================================

"If you are installing Resource Manager on Windows NT 4.0 Server,
Terminal Server
Edition, you will see this error if your system does not include the
correct
MDAC drivers.

"You need to install the Microsoft Data Access Components (MDAC)
Version 2.5,
AND THEN UPGRADE TO Version 2.6 before you can use the Citrix
Management Console
(both MetaFrame XP and Resource Manager components).

"To download the MDAC drivers:

1. Go to www.microsoft.com/downloads.
2. Select `Keyword Search`
3. Search for Keyword `MDAC` and OS `Windows NT 4.0`
4. Among the downloads available will be MDAC 2.5 and 2.6.

"To install the MDAC drivers:

1. Stop the Terminal Server Licensing service.
2. Empty the event log.
3. Install MDAC 2.5 and restart the server.
4. Install the MDAC 2.6 upgrade and restart the server.
5. Restart the Citrix Management Console."

MetaFrame XP is known to expose this issue in MDAC 2.6 when used with
clustered SQL servers. For more information, see Microsoft Technet
Article Q280294:

FIX: SQL Server ODBC Driver Reuses Incorrect Parameter Length
http://support.microsoft.com/support/kb/articles/Q280/2/94.ASP
MDAC 2.5 SP1 components are included with Windows 2000 SP1. To
download this version of MDAC for Windows NT 4.0 servers or for
Windows 2000 servers without SP1, please visit the following URL:

Release Manifest for MDAC 2.5 SP1
http://www.microsoft.com/data/MDAC25Info/MDAC25SP1Manifest.htm

NOTE: According to Microsoft, MDAC 2.6 cannot be uninstalled or
rolled back to MDAC 2.5 without reinstalling the server operating
system. For more information about MDAC, including a component
checker utility, please visit http://www.microsoft.com/data/.

How do I prevent Internet Explorer Temporary files and personal settings from being stored in the users Profile? 

To simply exclude temp files from being saved, use Regedt32 to navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

On the Edit menu, Add Value name ExcludeProfileDirs as a type REG_SZ,
nd set the string data to the names of the folders, relative to the profile root,
that you wish to exclude. If entering more than one, they must be separated by
semicolons.

Example:

Temporary Internet Files;Personal;etc

How can I keep Temporary Internet Files, favorites, and History out of a user profile using the registry? 

Create a folder for each of these objects in the users home
directory or anywhere. Then, navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

The Temporary Internet Files are pathed at the Cache value name, a
type REG_SZ entry. Add Value or double click Cache and type:
%Homedrive%%Homepath%\cache
This will put the temp files in a folder called cache in the
users home directory specified in user manager.

To change the History folder, Add Value or double click the History
value name which is also a type REG_SZ entry and set it to
%Homedrive%%Homepath%\history
This will put the history files in a folder called history in the
users home directory specified in user manager.

To change the Favorites folder, Add Value or double click the Favorites
value name which is also a type REG_SZ entry and set it to
%Homedrive%%Homepath%\Favorites
This will put the favorites files in a folder called favorites in the
users home directory specified in user manager

You can use the %homedrive%%homepath% variable with the users Personal files
setting under this key also.
(This controls the listbar pick personal for My Documents or
default office save path sttings)
%homedrive%%homepath%\personal

If these Value Names exist at:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
make the changes there also

How do I get rid of The System event log on error Event ID 1100 on my Windows 2000 Terminal Server? 

Your System event log contains:
Event Type: Error
Event Source: TermServDevices
Event Category: None
Event ID: 1100
Date: mm.dd.yyyy
Time: hh:mm:ss
Description: Initialization of Notify Failed.
This is caused because the Spooler service has stopped.
To fix the problem, either

Start the Spooler service

                OR

prevent the error by using Regedt32 to navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TerminalServer\Wds\rdpwd

On the Edit menu, Add Value name fEnablePrint RDR, as a REG_DWORD data type.
Set the data value to 0.

How do I remove Help from the Windows 2000 Start menu? 

To remove Help from the Windows 2000 Start menu, use Regedt32 to navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

On the Edit menu, Add Value name NoSMHelp as a REG_DWORD data type. Set the data value to 1.

Log off and log on for the setting to take effect.

NOTE: If you subsequently set the data value to 0, Help appears without the need to logoff.
NOTE: NoSMHelp stands for No Start Menu Help.

How do I print to a Terminal Server client`s local printer? 

To print to the client`s local printer when conected to a Terminal Server using RDP4.0 or RDP5.0:
1. The windows NT print driver for the client`s local printer must be installed on the Terminal Server, even if the client is running another O/S.
2. The Terminal Server must have NetBIOS name resolution to the client, either via WINS or a LMHOSTS entry.
3. If the client connects via RAS or VPN, they must logon to the domain.
4. The client`s printer must be shared.

How do I allow non-administrators to use Terminal Services Remote Administration mode? 

When a user who is NOT an administrator, tries to use Terminal Services Remote
Administration mode, they receive:
You do not have access to logon to this Session.
Only 2 simultaneous members of the Administrators group are allowed to log on
in Remote Administration mode.
You can grant other users, such as Server Operators, the right to use Terminal
Services Remote Administration mode. These groups are NOT included in the default
RDP-TCP permissions, and cannot log on until they are authorized.

NOTE: The System account has permission but can NOT be used to log on.

To grant addition user or groups permission:
01. Start Terminal Services Configuration in the Administrative Tools folder.
02. Press Connections in the left-hand pane.
03. Press the RDP-TCP connection in the right-hand pane.
04. Press Properties on the Action menu.
05. Select the Permissions tab.
06. Press Add.
07. Select the users or groups you wish to add and press Add to place them in the bottom pane.
08. Press OK.
09. Check the User Access box, for just basic tasks, or both User Access and Full Control to completely manage the server.
10. Press Apply.
11. Press OK.
12. Test the logon of a newly added user or group.

NOTE: Only 2 simultaneous logons are allowed, regardless of how many users and
groups you add.

How do I use Terminal Services to remotely administer a Windows 2000 Server? 

This comes from http://www.jsiinc.com.

The linked white paper at the bottom of this tip is a usage guide for IT professionals who are new to Terminal Services and/or its` Remote Administration mode.
There are two modes to choose from when enabling Terminal Services. Application Server mode is similar to the Windows NT® Server 4.0, Terminal Server Edition. It is designed to supply multiple users with Windows-based applications run from a server.

Remote administration mode allows two (2) concurrent Administrator connections, without installing a license on the client.

When run in Remote administration mode, Terminal Services does NOT implement any changes to CPU and memory utilization, and does NOT implement any application compatibility settings.

The Terminal Services component of Windows 2000 Server is tightly integrated into the kernel. It only requires about 2 MB of server memory and has minimal impact on server performance.

Microsoft recommends enabling Terminal Services in Remote Administration mode on every Windows 2000 Server.
Download the Whitepaper.

The below is from MS KB Article Q300847


SUMMARY

This step-by-step instruction guide describes how to configure Terminal Services in Windows 2000 Server for Remote Administration mode, which allows you to manage all of your computers remotely. This document describes how to install and configure Terminal Services, how to install and run the client, and briefly describes how to make Terminal Services work over firewalls.

Installing Terminal Services

You can install Terminal Services in two modes: Application Server mode and Remote Administration mode. Application Server mode is used for thin-client environments in which users have lightweight PCs and run programs remotely on the server instead of locally. Application Server mode requires a license for each connected user.

Remote Administration mode allows two low-resource simultaneous connections that are ideally suited for remote administration. No additional licenses are necessary, and the limit cannot be increased. This document describes Remote Administration mode.

To Install Terminal Services

  1. Insert the Windows 2000 Server CD-ROM into the CD-ROM or DVD-ROM drive.
  2. If a dialog box appears automatically after you insert the CD-ROM, click Install Add-on Components. If no dialog box appears, click Start, point to Settings, and then click Control Panel. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.
  3. In the list of components, click to select the Terminal Services check box.
  4. Click to clear the Terminal Services Licensing check box if it is selected. You do not need this service for Remote Administration mode. Click Next.
  5. Click Remote Administration Mode, and then click Next.
  6. The Terminal Services Wizard runs and installs Terminal Services. Close the wizard when it is finished, and then reboot your computer if you are prompted to do so.

Connecting to Terminal Services

To connect to Terminal Services running on a server, you must use a Terminal Services client. The client is available on the server on which you installed Terminal Services, in the following folder:
%SystemRoot%\System32\Clients\Tsclient\Net\Win32
Create a share on your server so that you can easily install the client on any computer.

To Create a Share on Your Server

  1. Use Windows Explorer to locate the %SystemRoot%\System32\Clients\Tsclient\Net\Win32 folder. Note that %SystemRoot% may be the C:\Winnt folder.
  2. Right-click the Win32 folder, and then click Sharing.
  3. On the Sharing tab, click Share this folder.
  4. Change the share name to TSClient.
  5. Click Permissions.
  6. Click to clear the Full control and Change check boxes. Only the Read permission should be selected.
  7. Click OK, and then click OK.
Follow the next steps on the computer from which you want to perform remote administration. The Terminal Services client runs on any 32-bit version of Windows, including Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows Millennium Edition (Me), Microsoft Windows NT 3.5x and 4.0, Microsoft Windows 2000 Professional, and various server versions. Connect to the share you created earlier. The share is named \\Servername\TSClient, where Servername is the name of the computer on which you installed Terminal Services. You do not have to follow the uppercase and lowercase convention that is used in this article.

To Install the Terminal Services Client

  1. Connect to the \\Servername\TSClient share that you created earlier.
  2. Double-click Setup.exe.
  3. Click Continue in the dialog box that appears, and then type your name and organization in the next dialog box.
  4. Click I agree (if you agree) when you see the license agreement.
  5. Click the large button in the next dialog box. You can change the installation path first, if you want to.
  6. Click Yes when you are prompted whether you want all users to have the same initial settings.

Using the Terminal Services Client

Before you can manage your Terminal Services servers remotely, you must create a connection to these servers. This procedure uses the Client Connection Manager tool to create icons for all of the Terminal Services servers you want to manage.

To Create a Connection to the Terminal Services Server

  1. Click Start, point to Programs, point to Terminal Services Client, and then click Client Connection Manager.
  2. When the Client Connection Manager Wizard starts, click Next.
  3. In the Connection name box, type a descriptive name for the connection.
  4. In the Server name or IP address box, type the server`s name or IP address, or click Browse to search for the server. When you are done, click Next.
  5. Leave all automatic logon information blank. Using automatic logon information might present a security problem if a non-administrator has access to the computer from which you run the client. Click Next.
  6. Click a screen resolution that is appropriate for you. It is best to use the largest area you can select (the client does not let you select an area that is larger than your local screen can display). Do not select Full screen at this time; you can toggle between windowed and full screen modes later. Leaving the initial connection in a window helps reinforce the fact that you are working on a remote computer rather than your local workstation. Click Next.
  7. Leave the Enable data compression and Cache bitmaps check boxes clear. They are useful only if you are working over a slow dial-up link. Click Next.
  8. Leave the Start the following program check box clear. You want the client to display the server`s desktop. Click Next. Change the icons if you want to. Click Next. Click Finish to complete the wizard.
This process creates an icon for your server. Double-clicking the icon connects you to the server. You can also right-click the icon to change the connection properties if you need to.

To Connect to the Server Using Terminal Services

  1. Double-click the server icon in Client Connection Manager.
  2. The Terminal Services client window appears and displays the server`s logon dialog box. You might need to double-click the window`s title bar to see it all.
  3. Type an appropriate set of credentials to log on to the server. Typically, you will log on as some kind of administrator (local, domain, or enterprise).
  4. If you use correct credentials, you see the server`s desktop.
Note that this is very different from using a remote-control product. You are not manipulating the keyboard, mouse, and screen at the server. Instead, you are logged on to the computer and have created a new session, but this session is displayed remotely, over Terminal Services, rather than locally at the computer. You do, however, have full access to the computer`s programs just as if you were working at its local console.

Disconnecting the Terminal Services client

There is an important distinction between disconnecting from a session and logging off. If you only close the Terminal Services client window, your session remains active on the server. When you connect again, Terminal Services reconnects you to that session. Any programs that you left running in the session are still available. To end the session, you need to log off by using the remote computer`s Start menu. Note that this logs you off and ends the remote session. It does not log off the user at the computer`s local console.

Useful Client Shortcut Keys

Key combination Function Similar local keys
CTRL+ALT+END Opens the Windows Security dialog box CTRL+ALT+DELETE
CTRL+ALT+BREAK Toggles the Terminal Services client display from window to full screen
ALT+INSERT Cycles through running programs on the remote computer ALT+TAB
ALT+HOME Displays the remote computer`s Start menu
ALT+DELETE Displays the remote window`s Control menu ALT+SPACE BAR
You can take screenshots with these shortcuts:
Key combination Function Similar local keys
CTRL+ALT+NUMBER PAD MINUS Places an image of active window onto the TS clipboard ALT+PRINT SCREEN
CTRL+ALT+NUMBER PAD PLUS Places an image of the entire Terminal Services client on the Terminal Services clipboard PRINT SCREEN

Pitfalls

Cannot Connect Because of a Firewall Between the Client and the Server

Terminal Services operates over TCP port 3389. If a firewall is protecting the server to which you want to connect, that firewall must permit inbound connections to the server`s TCP port 3389. If you are running the client from behind a firewall, that firewall must permit outbound connections to TCP port 3389. Check with your firewall administrator for assistance.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [16] 17 18 19 20 21 22 23 24 25 26

Featured Links