Note: If the OS uses the Windows Embedded Compact Standard Shell, you must instead configure these user preferences by using the corresponding keywords located in the.rdp file. See for more information. Name Type Description Default Value alternate shell REGSZ Specifies the path to the server program that starts automatically when you connect to the server with Remote Desktop Protocol (RDP), for example, 'C: ProgramFiles Office Word.exe.' In the Remote Desktop Connection dialog box, on the Programs tab, corresponds to the Program path and file name box ' ' audioMode REGDWORD Indicates where audio plays. Set to 0 (zero) to play audio on the host server. Set to 1 to play audio on the device. Set to 2 to prevent playing audio.
In the Remote Desktop Connection dialog box, on the Local Resources tab, corresponds to the Remote audio Settings button. 0 authentication level REGDWORD Defines the server authentication level.
Set to 0 (zero) to establish a connection to a Terminal Server without authenticating the connection to the server. Set to 1 to require a valid Transport Layer Security (TLS) certificate from the Terminal Server to authenticate the connection to the server. Set to 2 to try to use TLS to authenticate the connection to the server. If either the server or the device does not support TLS, the device still establishes a connection.
2 autoReconnection Enabled REGDWORD Indicates how the device and server automatically try to reconnect if the connection is lost. Set to 0 (zero) for the device to try to reconnect to the server. Set to 1 for the server to try to reconnect to the device. 1 bitmapCacheSize REGDWORD The size, in KB, of the bitmap cache in memory. The system attempts to allocate approximately twice this amount of memory.
If the allocation attempt fails, the system disables persistent caching for bitmaps and uses RAM caching instead. 1500 bitmapPersistCacheLocation REGSZ The location of the bitmap cache. Temp compression REGDWORD Enables file and directory compression. Set to 1 to enable compression. Set to 0 to disable compression. 1 connect to console REGDWORD Enables the host console session to connect from the command line.
Set to 0 (zero) for the command line to connect to a Terminal Services session. Set to 1 for the command line to connect to the host console session. This setting only works when you connect to a computer running Windows Server 2003. Windows XP Professional does not respond to this setting because it always connects the user to the console. Windows NT 4.0 Terminal Server Edition and Windows 2000 Server with Terminal Services do not support this setting.
0 desktopheight REGDWORD The height of the display, in pixels. This value can range from 200 to 2048. 0 When set to 0 (zero), the default value becomes the height value of the resolution dimensions that the OS uses when it starts. Desktopwidth REGDWORD The width of the display, in pixels. This value can range from 200 to 4096. 0 When set to 0, the default value becomes the width value of resolution dimensions that the OS uses when it starts. Disable cursor setting REGDWORD Indicates whether cursor blinking is enabled during a Terminal Services session.
Set to 0 (zero) to enable cursor blinking. Set to 1 to disable cursor blinking. 0 disable full window drag REGDWORD Indicates whether the contents of a window are visible while the user drags it in a Terminal Services session. Set to 0 (zero) to display the contents of the window. Set to 1 to not display the contents of a window. In the Remote Desktop Connection dialog box, on the Experience tab, corresponds to the Show contents of window while dragging check box 1 disable menu anims REGDWORD Indicates whether menu and window animations are enabled. Set to 0 (zero) to enable animations.
Set to 1 to disable animations. In the Remote Desktop Connection dialog box, on the Experience tab, corresponds to the Menu and window animation check box. 1 disable themes REGDWORD Indicates whether themes are permitted when you log on to a remote server. Set to 0 (zero) to enable themes.
Set to 1 to disable themes. In the Remote Desktop Connection dialog box, on the Experience tab, corresponds to the Themes check box.
0 disable wallpaper REGDWORD Indicates whether wallpaper is enabled. Set to 0 (zero) to disable wallpaper. Set to 1 to enable wallpaper. In the Remote Desktop Connection dialog box, on the Experience tab, corresponds to the Desktop background check box. 1 displayconnectionbar REGDWORD Indicates whether the connection bar is displayed on the remote desktop when in full-screen mode. Set to 0 (zero) to remove the connection bar.
Set to 1 to display the connection bar. In the Remote Desktop Connection dialog box, on the Display tab, corresponds to the Display the connection bar when in full-screen mode check box.
1 EnableCredSspSupport REGDWORD Enables support for Credential Security Support Provider protocol (CredSSP) if it is present on the Remote Desktop device. Set to 0 to disable support. Set to 1 to enable support.
1 keyboardhook REGDWORD Indicates whether Windows key combinations will work on the server. Set to 0 (zero) to disable support for Windows key combinations on the server. To enable Windows key combinations, set to one of the following:. Set to 1 to enable support for Windows key combinations on the server. Set to 2 to enable support for Windows key combinations on the server only while in full-screen mode.
In the Remote Desktop Connection dialog box, on the Local Resources tab, corresponds to the Keyboard drop-down list. 2 redirectclipboard REGDWORD Indicates whether the clipboard is automatically redirected during a Terminal Services session. Set to 0 (zero) to disable clipboard redirection.
Set to 1 to enable clipboard redirection. 1 redirectdrives REGDWORD Indicates whether disk drives are automatically redirected when the user logs on to a remote server. Set to 0 (zero) to disable drive redirection.
Set to 1 to enable drive redirection. In the Remote Desktop Connection dialog box, on the Local Resources tab, corresponds to the Disk Drives check. 0 redirectcomports REGDWORD Indicates whether COM ports are automatically redirected when the user connects to a remote server.
Set to 0 (zero) to disable COM port redirection. Set to 1 to enable COM port redirection. In the Remote Desktop Connection dialog box, on the Local Resources tab, corresponds to the Serial Ports box. 0 redirectprinters REGDWORD Indicates whether printers are automatically redirected when the user logs on to a remote server.
Set to 0 (zero) to disable printer redirection. Set to 1 to enable printer redirection. In the Remote Desktop Connection dialog box, on the Local Resources tab, corresponds to the Printers check box. 1 redirectsmartcards REGDWORD Indicates whether the device redirects Smart Cards during server authentication. Set to 0 (zero) to disable redirection of Smart Cards.
Set to 1 to enable redirection of Smart Cards. In the Remote Desktop Connection dialog box, on the Local Resources tab, corresponds to the Smart cards check box. 1 Screen Mode Id REGDWORD Indicates whether the device displays the remote desktop in full-screen mode or normal mode. Set to 0 (zero) to display it in full-screen mode. Set to 1 to display it in normal mode, in which it is displayed inside a window on the desktop. 0 session bpp REGDWORD Defines the bits per pixel (bpp) depth for an RDP session. Set to one of the following:.
15 15 bpp. 16 16 bpp. 24 24 bpp. Serial number for nitro pdf pro 7.
32 32 bpp Corresponds to the color depth that you select in Colors on the Display tab of the Remote Desktop Connection client. Uses the bit depth of the local system shell working directory REGSZ If an alternate shell was specified, this value indicates a valid path of the folder in which the startup application is located.
In the Remote Desktop Connection dialog box, on the Programs tab, corresponds to the Program path and file name. ' ' Span Monitors REGDWORD Enables monitor spanning. Set to 0 (zero) to disable monitor spanning. Set to 1 to enable monitor spanning.
Drive redirection redirects the path of a drive on a remote server to a new location on the local device. You can configure drive redirection by using the following registry entry, located in the key HKEYCURRENTUSER Software Microsoft Terminal Server Client. Name Type Description Default value EnableDriveRedirection REGDWORD Set to 1 to enable drive redirection. Set to 0 (zero) to disable drive redirection. 1 If drive redirection is enabled, you can configure the folder redirection filter by using the following entry, located in the key HKEYLOCALMACHINE System StorageManager AutoLoad FilterFsd.
Name Type Description Default value RootPath REGSZ The root directory that is available within the RDP session. Set to ' ' to make all of the file system available. ' ' Terminal Server Client Configuration. You can configure the Terminal Services Client by using the following registry entries, located in the key HKEYLOCALMACHINE Software Microsoft Terminal Server Client. Name Type Description Default value BitmapPersistCacheLocation REGSZ The path of the folder where the cache file is stored.
Temp CEConfig REGSZ Indicates whether Terminal Services Client runs in the Windows Thin Client Shell. Set to one of the following:. WBT to run the Terminal Services Client in a Windows Thin Client Shell. This value is set when SYSGENWBTSHELL = 1.
When WBT is set: Windows Embedded Compact disables file change notifications through protected server library (PSL) calls. Windows Embedded Compact disables keyboard hooks for the Windows Thin Client Shell. Additional registry migration occurs for Windows Thin Client OS designs because the connections are started through registry settings and not through.rdp files. Maxall to run the Terminal Services Client in a program other than the Windows Thin Client Shell. The following list describes issues that a Windows Thin Client might encounter if this value is set to Maxall:. The Filesys.exe may stop responding when drive redirection is enabled and an attempt is made to copy a file by using the clipboard. The Windows Embedded Compact Terminal Services Client CETSC user interface appears in the Windows Thin Client Shell when the user closes the dialog box to enable drive redirection.
Keyboard shortcut messages might be sent to remote sessions. Maxall CEDisableRFXDecoder REGDWORD Explicitly disables RemoteFX on a RemoteFX-enabled device. Set to 0 (zero) to enable the RemoteFX decoder.
Set to 1 to disable the RemoteFX decoder. 0 DisableFileAccess REGDWORD Indicates whether the user has access to the local file system. Set to 0 (zero) to enable access to the local file system. Set to 1 to disable access to the local file system and to hide the Save As and Open options on the context menus of the UI of the client device OS. 1 DisableRDP7BitmapCompression REGDWORD Disables the support for Remote Desktop Protocol 7.0 bitmap compression on RDP Client. When establishing a RemoteFX session, the server may send non-RemoteFX data to the client in addition to RemoteFX data. Non-RemoteFX data may use an RDP 7.0 bitmap codec for compression, which requires support for the Streaming SIMD Extensions 2 (SSE2) instruction set in the processor.
If a platform does not support the SSE2 instruction set, the RDP 7.0 bitmap codec will not be used. Set to 0 (zero) to enable the codec. Set to 1 to disable the codec. 0 FullScreenRFXOnly REGDWORD Enables full-screen-only mode for hardware-assisted RemoteFX and disables the Graphics Device Interface (GDI) (or windowed) mode. The FullScreenRFXOnly setting is not used in software decoding in RemoteFX. If this setting is used with software decoding, the contents of the device display screen might not update. When FullScreenRFXOnly is enabled, the RDP client does not call the ESCAPECOPY2BMP escape function.
When this key is enabled, the RDP client will not present any RemoteFX data on screen and it becomes the responsibility of the display driver to handle the display of decoded RemoteFX data. When this key is enabled the blue connection bar will be hidden in RemoteFX sessions. Set to 0 (zero) to disable support.
Set to 1 to enable support. 0 FullScreenAlways REGDWORD Indicates whether the RDP session runs in full-screen mode or windowed mode. Set to 0 (zero) to run in windowed mode. Set to 1 to run in full-screen mode. The user does not have the option to select a remote desktop size in the Remote Desktop Connection dialog box, on the Display tab. In the Standard Shell, the default is 0.
In the Windows Thin Client Shell, the default is 1. Redir0 REGDWORD Indicates whether smart cards are automatically redirected when the user logs onto a remote server. Set to 0 (zero) to disable smart card redirection. Set to 1 enable to smart card redirection. 1 Redir1 REGDWORD Indicates whether drives are automatically redirected when the user logs on to a remote server. Set to 0 (zero) to disable drive redirection.
Set to 1 enable drive redirection. 1 Redir2 REGDWORD Indicates whether serial ports are automatically redirected when the user logs on to a remote server. Set to 0 (zero) to disable serial port redirection.
Set to 1 to enable serial port redirection. 1 Redir3 REGDWORD Indicates whether printers are automatically redirected when the user logs on to a remote server. Set to 0 (zero) to disable printer redirection. Set to 1 to enable printer redirection. 1 Redir4 REGDWORD Indicates whether audio playback is automatically redirected when the user logs on to a remote server.
Set to 0 (zero) to disable audio playback redirection. Set to 1 to enable audio playback redirection.
1 Redir5 REGDWORD Indicates whether the clipboard is automatically redirected when the user logs on to a remote server. Set to 0 (zero) to disable clipboard redirection. Set to 1 to enable clipboard redirection. 1 Redir6 REGDWORD Indicates whether audio recording is automatically redirected when the user logs on to a remote server.
Set to 0 (zero) to disable audio recording redirection. Set to 1 to enable audio recording redirection. 1 RightMouseForALT REGDWORD Indicates the effect of pressing the Alt key while clicking the left mouse button.
Set to 0 (zero) to send an Alt plus left mouse click to the server when the user presses the Alt key. Set to 1 to send a right mouse click to the server when the user presses the Alt key. 1 Static Virtual Channel Plug-in. When you include SYSGENAUTHNTLM in a run-time image, you can ensure that the Negotiate security package selects the Windows NT LAN Manager (NTLM) Security Support Provider (SSP) instead of Kerberos as the security provider. NTLM SSP prevents a 15-second delay during authentication over an RDP connection to a computer running Windows Vista. Use this registry entry, located in the key HKEYLOCALMACHINE Comm SecurityProviders Negotiate Packages.
Name Type Description Default value Packages REGSZ Specifies the order of security providers that Simple and Protected GSS-API Negotiation (Negotiate SSP) chooses, as a comma-separated string. Set to 'NTLM' so that Negotiate SSP selects NTLM first.
Vga Port
Hello Gerber, Thanks for your feedback. Based on my research on your case, this is possibly a known issue due to application design and the redirected serial printers. In detail, each WriteFile request on the virtual RDP serial port on the server will result in an RDP packet sent to the client; while each ReadFile request on the server will result in 2 RDP packets.
As the result, if the application reads or writes 1 byte at a time by design, so each byte transferred will create one or two RDP packets. This is the underlying cause that serial communications to be significantly slower. In your case, I am not sure if this is the exact reason, as the issue is only occurring in WAN environment and you didn’t mention if only specific software meets the issue. I recommend you to test if the issue persists in all the applications you have, and if the problematic software encounter much slower printing performance in LAN environment too (which may be quicker than WAN, but slower than local printing and non-serial printer). Lionel Chen in forum If you have any feedback on our support, please contact This posting is provided 'AS IS' with no warranties, and confers no rights. Hello Gerber, Thanks for your post.
From your description, I understand that one of your redirected serial printer is working in Terminal Services / Remote Desktop Services environment. When the remote session occurs in LAN, the printer works fine; but if it is a WAN connection, the serial port between the server and the communication is very slow.
The information you provided is currently not enough for us to dig into the issue. Please help us collect the following information step by step: 1.
What operating systems are used by the server and client computers? What kind of printer redirection is used?
Is it a driver redirection or Easy Print feature? Is the issue occurring on only one printer and one client? Have you tried other clients and printers in the similar environment? What method is used for the WAN environment? Is it static public IP address, VPN or TS/RD Gateway?
How’s the general network bandwidth for the WAN connection? When the slow performance issue occurs, check the Windows Logs – Application category of the Event Viewer (eventvwr.msc) on both the client and server sides. If there is any logs recorded, please let us know them. As a general suggestion, I recommend you to update the printer drivers on both sides. Lionel Chen in forum If you have any feedback on our support, please contact This posting is provided 'AS IS' with no warranties, and confers no rights. Hi Lionel, Thank you for your answer.
The terminal server runs on Windows Server 2008 (But I have checked with a Server 2003, and the problem is the same). The client runs on Windows 7 (I have also checked with a XP client) 2. The printer is a POS printer (it uses a Serial Port (com)).
So there is no driver 3. I have tried with several clients (Windows 7 and XP pro) 4. The method used for the WAN is a static IP address.
The wan bandwith is 8Mbit download / 1Mbit upload. There is nothing logged in the application log about the serial (com) port neither on the server, neither on the client. Many thanks, Gerber Systems.
Hello Gerber, Thanks for your feedback. Based on my research on your case, this is possibly a known issue due to application design and the redirected serial printers. In detail, each WriteFile request on the virtual RDP serial port on the server will result in an RDP packet sent to the client; while each ReadFile request on the server will result in 2 RDP packets. As the result, if the application reads or writes 1 byte at a time by design, so each byte transferred will create one or two RDP packets. This is the underlying cause that serial communications to be significantly slower.
In your case, I am not sure if this is the exact reason, as the issue is only occurring in WAN environment and you didn’t mention if only specific software meets the issue. I recommend you to test if the issue persists in all the applications you have, and if the problematic software encounter much slower printing performance in LAN environment too (which may be quicker than WAN, but slower than local printing and non-serial printer).
Lionel Chen in forum If you have any feedback on our support, please contact This posting is provided 'AS IS' with no warranties, and confers no rights. Hello Gerber, Do you get any update on this issue?
If you need further assistance from us, please don't hesitate to follow up here. Lionel Chen in forum If you have any feedback on our support, please contact This posting is provided 'AS IS' with no warranties, and confers no rights. I am facing the same problem as Gerber, but in my case is a seriel barcode scanner. When i read your previous reply to Gerber, i understand that this is by design, and that there are no fix for this problem? Best regards Michael Louis Jensen. Hello Gerber, Do you get any update on this issue?
If you need further assistance from us, please don't hesitate to follow up here. Lionel Chen in forum If you have any feedback on our support, please contact This posting is provided 'AS IS' with no warranties, and confers no rights. I am facing the same problem as Gerber, but in my case is a seriel barcode scanner. When i read your previous reply to Gerber, i understand that this is by design, and that there are no fix for this problem? Best regards Michael Louis Jensen Hello, I've got the same problem - But its a serial port signature capture device. It worked fine on 2003, but now com port redirection is extremely slow.
The application even stops running. Was there a way to solve this issue? Pro Source Irrigation.
I have a barcode scanner CipherLab 8300. Serial ports are visible through 'change port' in windows server 2003.
I run the program for reading from the device of the information, and she writes 'time out'. Freerdp version of the 21.11.11. /usr/local/freerdp/bin/xfreerdp -u xxx -d xxx -a 16 -g 1024x768 -x l -plugin cliprdr -plugin rdpdr -data printer:'HP-LaserJet-4050' serial:COM1:/dev/ttyS0 serial:COM2:/dev/ttyUSB0 - hostname loading plugin cliprdr loading plugin rdpdr connected to hostname:3389 connected to hostname:3389 connected to hostname:3389 null server certificate registered device: PRN1 (type=4 id=1) registered device: COM1 (type=1 id=2) registered device: COM2 (type=1 id=3) When referring to the serial port of a in console is nothing. When the session ends in Windows the console output: unfinished.
killed by SIGSEGV P.S. In xfreerdp version 0.8.2 everything works fine. In order to help solving this issue, we ask you to compile both versions of FreeRDP enabling rdpdr debug. In FreeRDP-1.0: cmake -DWITHDEBUGSVC=ON In old FreeRDP, you must edit the source channels/rdpdr/rdpdrtypes.h: diff -git a/channels/rdpdr/rdpdrtypes.h b/channels/rdpdr/rdpdrtypes.h index 9bce305.0bebd83 100644 - a/channels/rdpdr/rdpdrtypes.h b/channels/rdpdr/rdpdrtypes.h @@ -25,7 +25,7 @@ #include 'config.h' -#define LOGLEVEL 1 +#define LOGLEVEL 11 #define LLOG(level, args) Please paste here the output of both debugs.
This article contains information about Remote Desktop Services COM port redirection for Windows Server 2008 R2, 2012 and 2012 R2. Table of Contents:. Windows client computers sometimes require COM port redirection when using Remote Desktop Services (RDS) provided by Windows Server 2012 and Windows Server 2012 R2. An example would be the use of a serial attached smart card reader on the client computer. This article addresses enabling COM port redirection on on the server and ensuring it's not disabled in Remote Desktop Session Host Configuration or Group Policy. Follow the steps below to achieve this goal. Steps:.
Press Windows Logo, type Windows PowerShell, right-click on Windows PowerShell and click Run as administrator to open Windows PowerShell. Type Set-RDVirtualDesktopCollectionConfiguration -CollectionName Name -CustomRdpProperty 'redirectcomports:i:1' where Name is the actual name of the RDS Collection. Type ' ' around the collection name if there are spaces in the name. For example type 'My Collection Name'. Use tsconfig.msc on a server running Windows Server 2008 R2 by performing the following steps:.
Press Windows Logo+R, type tsconfig.msc and press Enter to open Remote Desktop Session Host Configuration. Right-click RD Session Host Configuration: ServerName where ServerName is the actual name of the Windows Server 2008 R2 server, click Connect to Remote Desktop Session Host Server. Click Another computer, type the name of the Window Server 2012 or Windows Server 2012 R2 server and click OK. Right-click RDP-TCP in the center, click Properties and select the Client Settings tab. Ensure COM Port isn't checked in Redirection Disable the following. Steps:.
Press Windows Logo+R, type gpedit.msc, and press Enter. Click the arrow next to Computer Configuration under Local Computer Policy to expand it. Click the arrow next to Administrative Templates to expand it. Click All Settings to show all group policy settings. Scroll down to Do not allow COM port redirection and double-click on it to view the setting. Ensure the policy isn't enabled and click OK.
I have a business that has a small branch office about 20 miles from it's HQ. They have a VPN (router to router) to connect the two, but due to the latency between the two, in order to make the application they use run (AVIMark veterinary software) we use Remote Desktop.
That works great with one hiccup. They have lab equipment in the branch office that needs to send results to the software. I can use putty within the remote desktop and connect to the com ports assigned on the local machine they are using. The data is getting through the RD session from the local machine the lab equipment is connected to. However the AVImark software looks for actual com ports on the computer it's running on (in this case the RD session). Since RD isn't actually creating a com port which can be seen in device manager it isn't working. Long story short.
Is there any way to make the com ports from the local/host machine actually show up in a remote desktop session? (Serial ports is checked in the RD options, but that doesn't actually create the ports in device manager).
VS - Thanks for those links, I'll check them out. MD0221 - Yeah, that's the 'work around' but it takes about 45 minutes to load. AVImark as you know is an outdated software but also what almost everyone uses (although that is changing). VS - They do have a client server connection but it still has to pull everything over the network. The way the software works is you create a shortcut to the exe file on the desktop and run it from there. So instead of it just sending data over the network it has to run the whole program over the network. Justin, That's intriguing.
Can you only re-direct one user/computer (RDS Session) to Server 2012 or is it an all or nothing? Zacharryw - I'd love to see what your using.
CCWTech wrote: Justin1250 wrote: That PS command turns on com port redirection globally on the server. I believe it is disabled by default in 2012 So each session would be re-directed but would be session specific, am I understanding that correctly? Don't quote me on this but if I remember correctly they are redirected by name and are globally accessible. So each port on each computer would have to have a unique number associated with it. But it is easy to change to change the COM port number in device manager. Go into the properties of the COM port.
Then under port settings hit advanced. You should be able to change the com port number here. Edited Jun 9, 2015 at 6:12 UTC.