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
I was told to disable Active Desktop if I am running Terminal Services on Windows 2000 Server, how do I do this? 

To disable Active Desktop in Windows 2000, two policies and/or registry values are available:

The Disable Active Desktop Group Policy, when enabled:
Removes Active Desktop from the context menu that appears
when the user right-clicks the desktop. Removes the Web tab from Display in
Control Panel.
Disables Enable Web content on my desktop on the General tab of the Folder
Options dialog box.

If the policy is not configured, you can set the NoActiveDesktop value name,
a REG_DWORD data type, to 1 at:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer.

NOTE: The user must logoff/logon for this change to become effective.

NOTE: To disable Active Desktop with the GUI, right-click the desktop,
press Active Desktop and toggle Show Web Content.

The Prohibit changes Group Policy, when enabled:
Removes the Web tab in Display in Control Panel.
Removes Active Desktop from a right-click on the desktop.
If Active Desktop is already enabled, users cannot add, remove, or edit
Web content or disable, lock, or synchronize Active Desktop components.

If the policy is not configured, you can set the NoActiveDesktopChanges value name,
a REG_DWORD data type, to 1 at:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer.

How do I make a local printer available in Remote Desktop? 

This tip comes from Jsiinc.com

To make a local printer available in a Remote Desktop session:
1. Start / All Programs / Accessories / Communications / Remote Desktop Connection.
2. In the Remote Desktop Connection dialog, press Options.
3. Select the Local Resources tab.
4. Press Printers in the Local Devices area.
5. Press Connect.

When you log on to the remote computer, the clients local printer will become the default printer for any programs running on the remote desktop. If there is more than one local printer, all will be available, but the local printer that is the default printer for the remote computer will become the remote desktop default.

NOTE: When you press Connect in step 5, you have established default settings for all new connects. If you use the General tab in the Remote Desktop Connection dialog, you can save groups of settings for connecting

How do I Shadow a Remote Desktop Session in Windows XP Professional?  
This comes from Microsoft Knowledge base article Q279656

HOW TO: Shadow a Remote Desktop Session in Windows XP Professional (Q279656)


The information in this article applies to:

  • Microsoft Windows XP Professional

IN THIS TASK


SUMMARY

Users can connect remotely to a Terminal Services session that is running on a Windows XP Professional-based server. However, in Windows XP Professional you cannot create a shadow session, where a local user and a remote user can control the same session. This article describes how to use Windows .NET Server to create a configuration in which two users can control the same session on a Windows XP Professional-based computer.

back to the top

Connecting to a Windows .NET Server Terminal Services Session

  1. From a separate computer, open a Remote Desktop session to a Windows .NET Advanced or Datacenter-based server. Use this session to host the connection to the Windows XP Professional Desktop session; this is also actually serving as the session to be shadowed.

back to the top

Connecting to the Windows XP Professional Desktop Session

  1. From within the session that you just opened in Terminal Server, open a new Remote Desktop session to the target Windows XP Professional-based computer.
  2. After this step, the original session that you opened in step 1 will appear to be the desktop of the Windows XP Professional-based computer, but in actuality, it is a session to the computer that is nested within the original session to the server. At the same time, the Windows XP Professional-based computer will exhibit the same behavior as if the desktop were connected to any other Remote Desktop session, which means that the console of the Windows XP Professional-based computer will be locked.

back to the top

Connecting to another Terminal Services Session on Windows .NET Server

  1. From yet another computer, open a Remote Desktop session to the same Windows .NET Advanced or Datacenter-based server that you connected to in step 1. This session will be used to shadow the original session.

back to the top

Shadowing the Windows XP Professional Desktop Session

  1. From within the session that you just opened on the Terminal Server, open a command prompt and use the shadow command to shadow the original session from step 1. You can get the session ID from the Terminal Services Manager utility in Administrative tools.
  2. For example, if the original session were given an ID of 2, you would type shadow 2 at the command prompt within the second session that is connected to the Windows .NET Terminal Server.

back to the top

Disconnecting from the Shadow Session

  1. To disconnect the shadow session from the remote side, press CTRL-*(on the numeric keypad), and you will be returned to the original session that you established to the Windows .NET Server. You can then close this session by using logging off from the Start menu.

back to the top

Disconnecting from the Initial Remote Desktop Session

  1. The final step in this procedure is to disconnect from the nested Remote Desktop session that resides in the original session to which you connected on the Windows .NET Terminal Server.
  2. To do this, you use the traditional methods from the Start menu to either log off or disconnect from the session to the Windows XP Professional-based computer, and then use the exact same procedure again to log off or disconnect from the original session to the Windows .NET Terminal Server.

back to the top
How do I put a Comment in the Description Box of a Windows 2000-Based Computer`s Network Identification Properties? 
This comes from Microsoft Knowledgebase #243166

How to Type a Comment in the Description Box of a Windows 2000-Based Computer`s Network Identification Properties (Q243166)


The information in this article applies to:

  • Microsoft Windows 2000 , Advanced Server
  • Microsoft Windows 2000 , Datacenter Server
  • Microsoft Windows 2000 , Professional
  • Microsoft Windows 2000 , Server


SUMMARY

You can type a comment in the Description box of the Network Identification properties of a Windows 2000-based computer. The comment helps to further identify the computer on the network.


MORE INFORMATION

To type a comment in the Description box of a Windows 2000-based computer, use the following steps:

  1. Start the Computer Management Microsoft Management Console (MMC) snap-in.
  2. Right-click Computer Management (Local) , and then click Properties (there may be a slight delay while system information is being polled).
  3. On the Network Identification tab, type the comment you want in the Description box, and then click OK .
NOTE : The changes do not take effect until you restart the target computer. After you restart the computer, the comment is visible when the computer is browsed from the network.

Domain administrators can also add comments to remote systems that are members of the same domain by right-clicking Computer Management (Local) , clicking Connect to another computer , and then typing the name of the remote system or selecting the remote system from the list.

In addition, domain administrators can also change the target computer`s comment field from the command line using the following command:
net config server [/srvcomment:"text"]
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Q231312 Computer Name Missing in the Browsing List When Server Comment More Than 48 Characters
Where do I get the Terminal Services RDP Client from? 

The RDP client software is now installed by default as a subcomponent of Terminal Services.
By default, the various clients are installed in the directory:

%systemroot%\system32\clients\tsclient

There are two options to deploy the client:

Create a file share to do the installation over the network.
Select Terminal Services Client Creation from the Administrative
Tools menu, and make a client image that can be installed with a floppy disk.
You can download the Windows XP Remote Desktop Client from

http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp

How do I delete Temporary Files on Exit in Windows 2000 Terminal Services? 

To delete or retain temporary folders when exiting

Open Terminal Services Configuration
In the console tree, click Server Settings.
In the details pane, right-click Delete temporary folders on exit, and then click Properties.
Click Yes to automatically delete temporary folders when a user logs off from a session,
or No to retain temporary folders.

 Note
To open Terminal Services Configuration, click Start, point to Programs,
point to Administrative Tools, and then click Terminal Services Configuration.

How do I set up a separate Temporary folder for each session in Windows 2000 Terminal Services? 

To use separate temporary folders for each session

Open Terminal Services Configuration
In the console tree, click Server Settings.
In the details pane, right-click Use temporary folders per session,
and then click Properties.
Click Yes to create a separate temporary folder for each new session.

Note:
To open Terminal Services Configuration, click Start, point to Programs,
point to Administrative Tools, and then click Terminal Services Configuration.
Click No if you do not want to create temporary folders per session.

How do I download a full version of Microsoft Internet Explorer 5.5 or 6.0 on my Windows 2000 or Windows XP Machine? 
This comes from Microsoft Technet

Download-Only Setup of Internet Explorer on Windows 2000 and Windows XP (Q257249)


The information in this article applies to:

  • Microsoft Internet Explorer version 6 for Windows XP
  • Microsoft Internet Explorer version 6 for Windows 2000
  • Microsoft Internet Explorer versions 5.01 , 5.01 Service Pack 1 , 5.01 Service Pack 2 , 5.5 , 5.5 Service Pack 1 , 5.5 Service Pack 2 , for Windows 2000


SYMPTOMS

You cannot perform a download-only installation of Internet Explorer in Microsoft Windows 2000 or Microsoft Windows XP.


CAUSE

This behavior is caused by a change in Internet Explorer Setup to allow installation on Windows 2000 or Windows XP. Because Internet Explorer installs only the core browser and scripting files in Windows 2000 or Windows XP, the Install Minimal, or customize your browser option is not available during installation. Therefore, the Component Options dialog box is not available for you to use the Download only option.


RESOLUTION

To perform a download-only installation from the Internet:

  1. On the following Internet Explorer download page, click the appropriate language version to download the Ie5setup.exe or Ie6setup.exe file:

    http://www.microsoft.com/windows/ie/
  2. Click Save to Disk (or Save ), and then save the file in a folder on your computer.
  3. Click Start , and then click Run .
  4. Click Browse , browse to the folder in which you saved the Ie5setup.exe file or Ie6setup.exe file, click to highlight the file, and then click Open .
  5. In the Open box, click at the end of the command, add a space, and then type the following command for Internet Explorer 5, exactly as it appears, with quotation marks:

    /c:"ieXwzd.exe /d /s:""#E"""
    or type the following command for Internet Explorer 6, exactly as it appears, with quotation marks:
    /c:"ie6wzd.exe /d /s:""#E"""
    For example, if you saved the Ie5setup.exe file in the C:\Windows Update Setup Files folder, the command looks like:
    "C:\Windows Update Setup Files\ie5setup.exe" /c:"ie5wzd.exe /d /s:""#E"
    The following is an explanation of the command line switches used:

    • /d - Downloads Internet Explorer for the current platform only. However, if you would like to download all platforms, you can use the /d:1 switch value to get all platforms. There are only two values for this switch, /d and /d:1.

    • /s:""<#e>"" - Designates the source path of Ie5setup.exe. The ""<#e>"" value refers to the full path and name of the .exe file. Note that two pairs of double quotation marks must surround the path.

  6. Press ENTER. Choose the appropriate items for the operating system.
NOTE : To download Internet Explorer to a network drive, you must map the network drive to a drive letter on your computer. You cannot download Internet Explorer to a Universal Naming Convention (UNC) path.

MORE INFORMATION

You can use the command line listed above for all operating systems, but it is designed to assist Windows 2000 and Windows XP users.

To perform a quiet installation for the current operating system, type the following line:

For Internet Explorer 5:

"C:\Windows Update Setup Files\ie5setup.exe" /c:"ie5wzd.exe /d /q /s:""#E"""
To perform a quiet download for all operating systems, type the following command:
"C:\Windows Update Setup Files\ie5setup.exe" /c:"ie5wzd.exe /d /s:" "#E"
For Internet Explorer 6:
"C:\Windows Update Setup Files\ie6setup.exe" /c:"ie6wzd.exe /d /q /s:""#E"""
To perform a quiet download for all operating systems, type the following command:
"C:\Windows Update Setup Files\ie6setup.exe" /c:"ie6wzd.exe /d /s:" "#E"
NOTE : There are only two installation options available: Current and All . There is no way to perform this quiet download for specific operating systems.
How do I use a Windows .NET Server to create a configuration in which two users can control the same session on a Windows XP Professional-based computer? 
Microsoft Knowledge Base article Q279656 contains:

IN THIS TASK


SUMMARY

Users can connect remotely to a Terminal Services session that is running on a Windows XP Professional-based server. However, in Windows XP Professional you cannot create a shadow session, where a local user and a remote user can control the same session. This article describes how to use Windows .NET Server to create a configuration in which two users can control the same session on a Windows XP Professional-based computer.

back to the top

Connecting to a Windows .NET Server Terminal Services Session

  1. From a separate computer, open a Remote Desktop session to a Windows .NET Advanced or Datacenter-based server. Use this session to host the connection to the Windows XP Professional Desktop session; this is also actually serving as the session to be shadowed.

back to the top

Connecting to the Windows XP Professional Desktop Session

  1. From within the session that you just opened in Terminal Server, open a new Remote Desktop session to the target Windows XP Professional-based computer.
  2. After this step, the original session that you opened in step 1 will appear to be the desktop of the Windows XP Professional-based computer, but in actuality, it is a session to the computer that is nested within the original session to the server. At the same time, the Windows XP Professional-based computer will exhibit the same behavior as if the desktop were connected to any other Remote Desktop session, which means that the console of the Windows XP Professional-based computer will be locked.

back to the top

Connecting to another Terminal Services Session on Windows .NET Server

  1. From yet another computer, open a Remote Desktop session to the same Windows .NET Advanced or Datacenter-based server that you connected to in step 1. This session will be used to shadow the original session.

back to the top

Shadowing the Windows XP Professional Desktop Session

  1. From within the session that you just opened on the Terminal Server, open a command prompt and use the shadow command to shadow the original session from step 1. You can get the session ID from the Terminal Services Manager utility in Administrative tools.
  2. For example, if the original session were given an ID of 2, you would type shadow 2 at the command prompt within the second session that is connected to the Windows .NET Terminal Server.

back to the top

Disconnecting from the Shadow Session

  1. To disconnect the shadow session from the remote side, press CTRL-*(on the numeric keypad), and you will be returned to the original session that you established to the Windows .NET Server. You can then close this session by using logging off from the Start menu.

back to the top

Disconnecting from the Initial Remote Desktop Session

  1. The final step in this procedure is to disconnect from the nested Remote Desktop session that resides in the original session to which you connected on the Windows .NET Terminal Server.
  2. To do this, you use the traditional methods from the Start menu to either log off or disconnect from the session to the Windows XP Professional-based computer, and then use the exact same procedure again to log off or disconnect from the original session to the Windows .NET Terminal Server.
My Windows 2000 Terminal Services has Disable Wallpaper checked, but the wallpaper still displays? 

Even though the Windows 2000 Terminal Services computer has the Disable Wallpaper option selected, the wallpaper is displayed on your Terminal Services client desktop?

If the client has enabled the Active Desktop feature, the wallpaper is still displayed.
You can disable Active Desktop for all Terminal Services connections:

1. Log onto the Terminal Services computer with administrator credentials.
2. Start / Programs / Administrative Tools / Terminal Services Configuration.
3. In Server Settings, double-click Active Desktop.
4. Select the Disable Active Desktop check box and press OK.

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