 |
|
Answer File = Unattend.txt
The [TerminalServices] section contains entries for configuring Terminal Services features (Terminal Server and Remote Desktop) in Windows XP and the Windows Server 2003 family.
Terminal Server applies only to Windows Server 2003, Enterprise Edition, Windows Server 2003, Datacenter Edition, and the
To install and enable Terminal Server (also called Terminal Services in Application Server mode), use the TerminalServer entry in the [Components] section. To change the permissions settings for a Terminal Server installation, use the PermissionsSetting entry in the [TerminalServices] section.
Windows XP Professional and the Windows Server 2003 family install Remote Desktop (also called Terminal Services in Remote Administration mode), but display it by default. To enable Remote Desktop during unattended Setup, set AllowConnections to 1. Windows XP Home Edition does not provide the Remote Desktop feature.
| Entry | Description |
|---|---|
| AllowConnections | Specifies whether Remote Desktop (also called Terminal Services in Remote Administration mode) enables connections from other computers. |
| LicensingMode | Configures how Terminal Services manages its Client Access Licenses (CALs). |
| PermissionsSetting | Enables administrators to choose the security mode for Terminal Server users during terminal server sessions. |
This sample demonstrates one use of the [TerminalServices] section of Unattend.txt.
[TerminalServices] AllowConnections = 0 LicensingMode = PerUser PermissionsSetting = 1
Specifies whether Remote Desktop (also called Terminal Services in Remote Administration mode) enables connections from other computers.
| Syntax | AllowConnections = 0 | 1 |
|---|---|
| Values | 0 Disables Remote Desktop on the computer. 1Enables Remote Desktop during unattended Setup. |
| Default Value | 0 |
| Example | AllowConnections = 0 |
| Comments | Any member of the Windows Server 2003 family installs Remote Desktop (also called Terminal Services in Remote Administration mode) and enables it by default. If you set TerminalServer to On in the [Components] section of the answer file, setting AllowConnections to 0 installs Terminal Server without enabling it.
Windows XP Professional and Windows XP Home Edition install the Remote Desktop feature by default but do not enable it. |
Configures how Terminal Services manages its Client Access Licenses (CALs).
| Syntax | LicensingMode = PerDevice | PerUser |
|---|---|
| Values | PerDevice Configures Terminal Server to require that each connected device has a valid Terminal Server Client Access License (CAL). If the client has a Terminal Server CAL, it can access more than one Terminal Server. PerUserConfigures Terminal Server to provide one Terminal Server CAL for each active user. |
| Default Value | PerDevice |
| Example | LicensingMode = PerDevice |
| Comments | For more information, see "Terminal Services Licensing" in the Windows Server 2003 Help.
Important
|
Enables administrators to choose the security mode for Terminal Server users during terminal server sessions.
| Syntax | PermissionsSetting = 0 | 1 |
|---|---|
| Values | 0 Grants Terminal Server users the same permissions as the users of Windows 2000, Windows XP, or the Windows Server 2003 family. Note that some applications written for Windows NT 4.0 or earlier operating systems might not run correctly in this security mode. 1Grants Terminal Server users the same permissions as the users of Terminal Server 4.0. End users can continue running previous application versions that might require additional user permissions. Note, however, that using this option bypasses some of the security enhancements in Windows XP and the Windows Server 2003 family, and grants end users access to critical registry and system file locations. |
| Default Value | 0 |
| Example | PermissionsSetting = 1 |
| Comments | By default, Setup enables Terminal Server in Full Security mode, which grants Terminal Server users the same permissions as members of the User group and provides the most secure environment in which to run applications. However, some applications not certified for Windows 2000, Windows XP, or the Windows Server 2003 family require write access to certain parts of HKLM and to certain system directories. Granting these additional permissions may enable end users to delete or change vital settings under HKLM and/or system files.
Important
|
