FAQ Terminal Server related Print E-mail
Written by Administrator, Wednesday, 12 May 2004

Updated 25 July 2008

Q: Every time I logon to a terminal server I have to provide a password.

A: Check the RDP-Tcp snapin (Logon Settings) the box "Always prompt for password" should not be marked. Also if you have several domains or loggin in to another domain make sure to select the right domain!

Q: When a user logs on a popup occurs prompting for password although the user has set the credentials while loging on

A: Go to Administrative Tools > Terminal Server Configuration\Connections (TSCC) and open the RDP-Tcp snapin by double cliking on it. Now go to the tab "Logon Settings" and uncheck "Always prompt for password".

Q: Can I remotely enable Remote Desktop for administration.

A: Yes you can make a administrative mapping to the target server then open registry editor. Add the server and browse to HKLM\System\CurrentControlSet\Control\Terminal Server change the value of "fDenyTSConnections" to 0 this will enable Remote Desktop. You do not have to reboot this change will take effect immediately

Q: Do you guys have a adm to set the "Enable remote desktop" on multiple servers.

A: Yes we do :) it's downloadable at the download section

 

 

Q: Do I have same cpu and memory in Remote Desktop the a Terminal Server in application mode?

 

A: No you have less cpu power and memory resources available, this is buildin by design because Remote Desktop is for Administrative tasks only.

Q: What maximum colors are available in terminal server 2003.

A: Maximum available is 24bits color.

Q: How long are temporarily terminal server licenses valid

A: The temporarily terminal server licenses are valid for 120 days, then you have to aquire a tscal license pack. 

Q: How can I troubleshoot applications that will only launch with administrative privilage's

A: www.sysinternals.com has filemon.exe and regmon.exe which are execelent tools to see what happens on file and registry level. Both tools are freeware.

Q: Can you hardcode the location of the license server in the registry

A: Any Enterprise license servers or Domain license servers that are specified in the registry.

In Windows Server 2003, the relevant registry key is LicenseServers , and it is located under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters.

In Windows 2000, the relevant registry key is DefaultLicenseServer, and it is located under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters.

In Windows Server 2003, you can specify multiple license servers in the registry. In Windows 2000, you can only specify one license server

Now add a new key  and enter either netbios name, ip address or FQDN name of the license server.

Updated thanks to Jiboom (brain madden forum)

Q: Can I stop Point and print on a terminal server 2003

A: There are a few ways to acomplish disabling the download from client to server.

  • Group Policy.  There is a setting under Computer Configuration->Windows Settings->Security Settings->Local Policies->Security Options called "Devices: Prevent users from installing printer drivers"  Enable it and apply it to your Terminal Server GPO
  • Registry hack.  Edit the value named AddPrinterDrivers located at HKLM\SYSTEM\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers and set it to 1 instead of 0
  • NTFS Security.  Edit the security ACL on NTPrint.Inf to only allow users to have Read Access to the file (not modify)

thanks to Shawn Base

Q: I cannot change file Association in terminal server 2000 /2003

A: Read this article provided by Microsoft link

Q: Can I release terminal server cal's for general use after I removed a client from the domain (so the cal is no longer used)

A: No this cannot be done, you have to wait until the license server releases the cal again.

Q: If you add programs after the user profile has been created all new additions are placed
at the bottom of the start menu. Is there any way to sort these elements automatic ?.

A:The first way is by loading your default profile into the registry and deleting some registry keys and changing permissions on a key.

To do this, Open regedit and select the HKEY_USERS key. From the file menu, select load hive and then browse to you default user profile and select the ntuser.dat.  When prompted for the "key name" call it anything you want, I called my “temp”.

Browse to this key…
HKEY_USER\temp\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder
...and then delete all the keys under it. To fix it so it always sorts, change the permissions on it so the “everyone” group only has read permissions. You will need to turn off inheritance and remove the full control permission for the “everyone” group.

The other way to do it for users that already have profiles is to just delete all of the keys under the “MenuOrder” key, which can be automated via logon script.

source: brain madden forum credts: oneill3

note: Use this at own risk datacrash has not tested this yet!

Q: Can I use shortcut key's like ctrl+alt+del in a rdp sessions.

A: These are all options in a RDP session

CTRL+ALT+END (Open the Microsoft Windows NT Security dialog box)
ALT+PAGE UP (Switch between programs from left to right)
ALT+PAGE DOWN (Switch between programs from right to left)
ALT+INSERT (Cycle through the programs in most recently used order)
ALT+HOME (Display the Start menu)
CTRL+ALT+BREAK (Switch the client computer between a window and a full screen)
ALT+DELETE (Display the Windows menu)
CTRL+ALT+Minus sign (-) (Place a snapshot of the active window in the client on the Terminal server clipboard and provide the same functionality as pressing PRINT SCREEN on a local computer.)
CTRL+ALT+Plus sign (+) (Place a snapshot of the entire client window area on the Terminal server clipboard and provide the same functionality as pressing ALT+PRINT SCREEN on a local computer.)

Q: How to change the file assiociation on a terminal server

A: You can use the FTYPE and ASSOC command from a command line

[code]

Displays or modifies file types used in file extension associations

FTYPE [fileType[=[openCommandString]]]

  fileType  Specifies the file type to examine or change
  openCommandString Specifies the open command to use when launching files
                    of this type.

Type FTYPE without parameters to display the current file types that
have open command strings defined.  FTYPE is invoked with just a file
type, it displays the current open command string for that file type.
Specify nothing for the open command string and the FTYPE command will
delete the open command string for the file type.  Within an open
command string %0 or %1 are substituted with the file name being
launched through the assocation.  %* gets all the parameters and %2
gets the 1st parameter, %3 the second, etc.  %~n gets all the remaining
parameters starting with the nth parameter, where n may be between 2 and 9,
inclusive.  For example:

    ASSOC .pl=PerlScript
    FTYPE PerlScript=perl.exe %1 %*

would allow you to invoke a Perl script as follows:

    script.pl 1 2 3

If you want to eliminate the need to type the extensions, then do the
following:

    set PATHEXT=.pl;%PATHEXT%

and the script could be invoked as follows:

    script 1 2 3

[/code]

Q: How to change the terminal server listening port

A: Read this document it's all descripted in here

Q: Can you grant non administrators access to the remote desktop of a windows 2003 server in remote desktop mode

A: No only members of the local administrator group can connect to a remote desktop on a 2003 server running in remote desktop mode

Q: Can you disable automaticly install of printer drives when people connect to RDP of a 2000/2003 server

A: Yes modify the permissions to the following 2 folders %systemroot%\system32\spool\drivers\w32x86\2  AND  %systemroot%\system32\spool\drivers\w32x86\3

Also modify permissions on following 2 registry hives HKLM\System\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-2
HKLM\System\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3

Q: When connecting to a terminal server the connection stops at Negotiating Capabilities.

A: One of the most found solutions is removing the license000 folder. It can be located at HKLM\Software\Microsoft\MSLicensing\Store\License000 (Remove only the license000)

Q: Is there a way to turn of the multiple toolbars in the taskbar see figure

Multiple toolbars in taskbar

 A: There is no hotfix but a workarround: Turn off advanced text services in "regional and language options". (thanks to Vera Noest) update: KB932039

Q: Can I remotely see who is logged on to a terminal server and what session the user(s) are in?

A: Yes you can with Quser /server:servername and with logoff sessionid: /server:servername you can actually log them off (thanks to Michel Buis)

Q: Can I build up a Terminal Server on a stand alone server with local policies in place.

A: Yes you can also read this  KB 325351 howto apply policies without effecting the administrator(s)

Q: Can you link one specifiek application to use one version of for example Oracle

A: Yes make a entrie in HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths. There are already entries so simply use those as an example.

Q: Is there a tool to automaticly created a list of printers that are not mapped corectly

A: Yes Terminal Server Printer Redirection Wizard Tool

Q: Can I match the input language of the  terminal server client to the terminal server session

A: Yes read KB322042

Q: Can I manually create a rdp file using notepad orso?

A: Yes you have to save the file as a *.rdp file but follow this link for RDP5.x settings. Mind settings in RDP6.x have been changed

Q: Do I need a Windows CAL if we connect with Linux based thin clients

A: Yes then also you need a Windows CAL

Q: I have a HP 2600N Color Laserjet is this printer suitable for a terminal server environment

A: Yes and No. As long as it's a client printer it will print. If you install it on a printserver it will not work.

Q: My usb printer is not redirected to a remote desktop session.

A: Follow KB302361 to edit your registry. Mind editing the registry is at your own risk.

Comments
Add NewSearchRSS
Only registered users can write comments!
 
< Prev   Next >