For Windows 2003 (32-bit and 64-bit) OS security has been enhanced and as such has the following effects:
Originally Published: 2007-09-12
Article Number
Applies To
Microsoft Remote Desktop
RDP
terminal
service
security
Microsoft Windows
microsoft
Issue
Resolution
The enVision appliance OS using Windows 2003 has been configured to require strong encryption to be negotiated for applications that must use the cryptographic services. Strong encryption may be Federal Information Processing Standard (FIPS)-compliant encryption.
- This setting affects Terminal Services in Microsoft Windows Server 2003. By default, when this setting is not enabled on the client or on the server, the Remote Desktop Protocol (RDP) channel between the server and the client is encrypted by using the RC4 algorithm with a 56-bit key length. After this setting is enabled, the RDP channel is encrypted by using 3DES in Cipher Block Chaining (CBC) mode with a 128-bit key length, if the client supports it. Also, a client must use the RDP client version 5.2 or a later version to connect.
- Encrypting File System (EFS) is also affected by this setting. By default, Windows XP uses the Data Encryption Standard (DESX) algorithm with a 56-bit key length. If the Windows high encryption pack is installed, the key length for this algorithm is Triple-DES (3DES) or 128 bits. By default, on Windows XP Service Pack 1 (SP1)-based and Windows Server 2003-based computers, EFS uses the Advanced Encryption Standard (AES) algorithm with a 256-bit key length. However, if you enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing setting on these computers, the operating system will use 3DES with a 128-bit key length instead.
More information can be found at http://support.microsoft.com/kb/811833 - Installing applications via RDP
Related Articles
RSA Authentication Manager Web Tier installation fails with the following error: The directory already exists! 51Number of Views RSA Identity Governance & Lifecycle 7.0.0 installation fails with the following error: JBAS014653: Composite operation fa… 224Number of Views A parameter cannot be found that matches parameter name Generation when installing RSA Authentication Manager 8.1 SP1 on M… 522Number of Views Workflow variables created in SQL Select Node are not visible in the following node for Review Escalation workflow in RSA … 70Number of Views RSA Identity Governance & Lifecycle installation fails with the following error: <install directory path>/staging/deploy/… 726Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…
Don't see what you're looking for?