how to implement barcode system in c# Figure A-4 The Network Adapter tab of the RDP-Tcp Properties dialog box in .NET framework

Creating QR in .NET framework Figure A-4 The Network Adapter tab of the RDP-Tcp Properties dialog box

A-10

Encryption must be compatible. The default allows any client to connect to a ter minal server without regard to its encryption capability. If you modify the encryp tion requirements for a connection by using the Encryption list on the General tab of the connection properties, as shown in Figure A-5, clients that are not capable of that encryption mode will not be allowed to connect.

Figure A-5

The user must have sufficient connection permissions. As shown in Figure A-6, the Remote Desktop Users group has User Access permissions, which gives the group sufficient permissions to log on to the server. The access control list (ACL) of the connection can be modified to control access in configurations that differ from the default. Refer to the Help and Support Center for more information. If a user does not have sufficient permission to the connection, an error message will appear that indicates that the user does not have access to the session.

Figure A-6

A-11

The user must have the user logon right to log on to the terminal server. Windows Server 2003 separates the right required to log on locally to a server from the right required to log on to a server using a remote desktop connection. The user rights Allow Log On Through Terminal Services, as shown in Figure A-7, and Deny Log On Through Terminal Services can be used to manage this right, using either local policy or Group Policy. On member servers, the local Administrators and Remote Desktop Users groups have the right to log on through Terminal Services. On domain controllers, only Administrators have the right by default. If a user does not have sufficient logon rights, an error message will appear that indicates that the policy of the Terminal Server does not allow logon.

The user must belong to the correct group or groups. Assuming you have managed connection permissions and the right to log on through Terminal Services by assigning rights and permissions to a group, the user attempting to connect to the terminal server must be in that group. With the default configuration of Terminal Server on a member server, users must be members of the Remote Desktop Users group to connect to a terminal server. Allow logon to terminal server enabled. The user account s Terminal Services Profile tab, as shown in Figure A-1, indicates that the user is allowed to log on to a ter minal server. If this setting is disabled, the user will receive an error message indicating that the interactive logon privilege has been disabled. This error mes sage is easy to confuse with insufficient user logon rights; however, in that case, the error message indicates that the local policy of the server is not allowing logon.

A terminal server has one RDP-Tcp connection by default, and can have only one con nection object per network adapter, but if a terminal server has multiple adapters, you can create connections for those adapters. Each connection maintains properties that affect all user sessions connected to that server connection.

A-12

Once a user has successfully connected, Windows Server 2003 and the Remote Desktop client provide a wide array of device redirection options including:

Audio redirection, which allows audio files played within the Terminal Server ses sion to be played by the user s PC. This feature is specified on the Local Resources tab of the Remote Desktop client, as shown in Figure A-2. However, audio redi rection is disabled by default on the Client Settings tab of the RDP-Tcp Properties dialog box, as shown in Figure A-8. Audio redirection can be specified by a GPO.

Figure A-8