Changes in Functionality from Windows Server 2003 with sp1 to Windows Server 2008



Download 1.83 Mb.
Page20/35
Date26.04.2018
Size1.83 Mb.
#46827
1   ...   16   17   18   19   20   21   22   23   ...   35

Additional references


For information about other new features in Terminal Services, see the Terminal Services Role topic.

Terminal Services Printing


Terminal Services printing has been enhanced in Windows Server® 2008 by the addition of the Terminal Services Easy Print printer driver and a Group Policy setting that enables you to redirect only the default client printer.

The Terminal Services Easy Print driver is a feature that enables users to reliably print from a RemoteApp program or from a terminal server desktop session to the correct printer on their client computer. It also enables users to have a much more consistent printing experience between local and remote sessions.

The Redirect only the default client printer policy setting allows you to specify whether the default client printer is the only printer that is redirected in Terminal Services sessions. This helps to limit the number of printers that the spooler must enumerate, therefore improving terminal server scalability.

Are there any special considerations?


To use the Terminal Services Easy Print driver in Windows Server 2008, clients must be running both of the following:

 Remote Desktop Connection (RDC) 6.1



Note

The RDC 6.1 (6.0.6001) client supports Remote Desktop Protocol 6.1.

 Microsoft .NET Framework 3.0 Service Pack 1 (SP1)

Windows Server 2008 and Windows Vista® with Service Pack 1 (SP1) Beta or Windows Vista with SP1 Release Candidate (RC) include both of the required components. By default, Windows Vista with SP1 supports the Terminal Services Easy Print driver with no additional configuration.

Windows XP with Service Pack 3 (SP3) Beta or Windows XP with SP3 RC also supports the Terminal Services Easy Print driver. However, you must install .NET Framework 3.0 SP1 separately. (RDC 6.1 is included with Windows XP SP3.)

To use the Terminal Services Easy Print driver on a Windows Server 2008-based server (that is acting as the client), you must first add .NET Framework 3.0 SP1. The .NET Framework 3.0 SP1 component is available as an installable feature. For more information, see the "Terminal Services Printing" topic in the "What's New in Terminal Services for Windows Server 2008" guide (http://go.microsoft.com/fwlink/?LinkId=87440).


What new functionality does this feature provide?


The Terminal Services Easy Print driver offers the following functionality:

 Increased reliability of Terminal Services printing for both RemoteApp and remote desktop sessions.

 Support for legacy and new printer drivers without the necessity of installing these drivers on the terminal server.

 Scalability improvements over Windows Server 2003 in terms of printer enumeration performance. During the Winlogon process, the spooler only enumerates printers that are available for a user in a particular session instead of enumerating all redirected printers. Therefore, printers are enumerated on a per-session basis, instead of on a per-user basis.

 Enhanced available printer capabilities. The Terminal Services Easy Print driver provides rich and complete printer capabilities in remote sessions. All of the physical printer driver's capabilities are available for use when a user views the printing preferences.

The Redirect only the default client printer Group Policy setting allows you to control whether the default client printer is the only printer redirected in a Terminal Services session, or whether all printers are redirected in a session.


What existing functionality is changing?


The terminal server fallback printer driver is not included with Windows Server 2008. Although the Specify terminal server fallback printer driver behavior Group Policy setting still exists, it can only be used for Windows Server 2003 with SP1-based computers.

How should I prepare for this change?


By default, the Terminal Services Easy Print driver is enabled in Windows Server 2008. To use the Terminal Services Easy Print driver, client computers must meet the requirements that are outlined in the "Are there any special considerations about these features" section.

If there are client computers that do not support the Terminal Services Easy Print driver, and the printer driver is not already available on the terminal server, you must do either of the following to support client printing:

 Ensure that client printer drivers for both local and network printers are installed on the terminal server. If you are installing a third-party driver, make sure that the driver is a Windows Hardware Quality Labs (WHQL) signed driver.

 Add the client printer drivers for both local and network printers to a custom printer mapping file on the terminal server. For more information about how to create a custom printer mapping file, see the "Resolution" section of article 239088 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=82784).


What settings have been added or changed?

Group Policy settings


The following Group Policy settings have been added for Terminal Services printing:

Use Terminal Services Easy Print printer driver first

This policy setting is located in the following node of the Local Group Policy Editor:

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection

The possible values are:

Enabled or Not configured: If this policy setting is enabled or not configured, the terminal server will first try to use the Terminal Services Easy Print driver to install all client printers. If for any reason the Terminal Services Easy Print driver cannot be used, a printer driver on the terminal server that matches the client printer will be used. If the terminal server does not have a printer driver that matches the client printer, the client printer will not be available for the Terminal Services session. By default, this policy setting is not configured.

Disabled: If you disable this policy setting, the terminal server will try to find a suitable printer driver to install the client printer. If the terminal server does not have a printer driver that matches the client printer, the server will try to use the Terminal Services Easy Print driver to install the client printer. If for any reason the Terminal Services Easy Print driver cannot be used, the client printer will not be available for the Terminal Services session.

Redirect only the default client printer

This policy setting is located in the following node of the Local Group Policy Editor:



Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection

The possible values are:

Enabled: If you enable this policy setting, only the default client printer is redirected in Terminal Services sessions.

Disabled or Not configured: If you disable or do not configure this policy setting, all client printers are redirected in Terminal Services sessions. By default, this policy setting is not configured.


Additional references


For information about other new features in Terminal Services, see the Terminal Services Role topic.

TS RemoteApp


Terminal Services RemoteApp™ (TS RemoteApp) enables organizations to provide access to standard Windows-based programs from virtually any location to users of any Windows Vista®–based or Windows Server® 2008–based computer, or to users of Windows® XP with Service Pack 2 (SP2)–based or Windows Server 2003 with Service Pack 1 (SP1)–based computers that have the new Remote Desktop Connection (RDC) client installed.

Note

See the "Are there any special considerations?" section for information about client requirements for accessing RemoteApp programs through Terminal Services Web Access (TS Web Access).

TS RemoteApp is installed as part of the Terminal Server role service in Windows Server 2008.

What does TS RemoteApp do?


RemoteApp programs are programs that are accessed remotely through Terminal Services and appear as if they are running on the end user's local computer. Users can run RemoteApp programs side by side with their local programs. A user can minimize, maximize, and resize the program window, and can easily start multiple programs at the same time. If a user is running more than one RemoteApp program on the same terminal server, the RemoteApp programs will share the same Terminal Services session.

Users can run RemoteApp programs in a number of ways. They can:

1. Double-click a Remote Desktop Protocol (.rdp) file that has been created and distributed by their administrator.

2. Double-click a program icon on their desktop or Start menu that has been created and distributed by their administrator with a Microsoft® Windows Installer (.msi) package.

3. Double-click a file whose extension is associated with a RemoteApp program. (This can be configured by their administrator with a Windows Installer package.)

4. Access a link to the RemoteApp program on a Web site by using Terminal Services Web Access (TS Web Access).

The .rdp files and Windows Installer packages contain the settings needed to run RemoteApp programs. After opening the RemoteApp program on a local computer, the user can interact with the program that is running on the terminal server as if it were running locally.

Who will be interested in this feature?


TS RemoteApp can reduce complexity and reduce administrative overhead in many situations, including the following:

 Branch offices, where there may be limited local IT support and limited network bandwidth.

 Situations where users need to access applications remotely.

 Deployment of line-of-business (LOB) applications, especially custom LOB applications.

Environments, such as "hot desk" or "hoteling" workspaces, where users do not have assigned computers.

 Deployment of multiple versions of an application, particularly if installing multiple versions locally would cause conflicts.

You should review this topic, and the additional supporting documentation on TS RemoteApp, if you are in any of the following groups:

 IT planners and analysts who are technically evaluating the product.

 Enterprise architects.

 IT professionals who deploy or administer terminal servers, LOB programs, or programs that can be more efficiently deployed with TS RemoteApp.


Are there any special considerations?


To access RemoteApp programs that are deployed as .rdp files or as Windows Installer packages, the client computer must be running Remote Desktop Connection (RDC) 6.0 or RDC 6.1. (RDC 6.1 [6.0.6001] supports Remote Desktop Protocol 6.1.) A supported version of the RDC client is included with Windows Vista and Windows Server 2008.

Note

The RDC version 6.0 software is available for use on Windows XP with SP2 and Windows Server 2003 with SP1. You can download the installer package from article 925876 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=79373).

To access RemoteApp programs through TS Web Access, the client computer must be running RDC 6.1. RDC 6.1 is included with the following operating systems:

 Windows Server 2008

 Windows Vista with Service Pack 1 (SP1) Beta or Windows Vista with SP1 Release Candidate (RC)

 Windows XP with Service Pack 3 (SP3) Beta or Windows XP with SP3 RC


What new functionality does this feature provide?

Ability to run programs remotely


Users can run programs from a terminal server and have the same experience as if the programs were running on the end user's local computer, including resizable windows, drag-and-drop support between multiple monitors, and notification icons in the notification area.

Why is this functionality important?


TS RemoteApp improves the user's experience, opens new avenues for program deployment, and reduces the amount of administrative effort required to support these programs.

What works differently?


Instead of being presented to the user in the desktop of the remote terminal server, the RemoteApp program is integrated with the client's desktop, running in its own resizable window with its own entry in the taskbar. If the program uses a notification area icon, this icon appears in the client's notification area. Popup windows are redirected to the local desktop. Local drives and printers can be redirected to appear in the RemoteApp program. Many users might not be aware that the RemoteApp program is any different than a local program.

How do I fix these issues?


Because TS RemoteApp is an enhancement to existing Terminal Services technologies and uses the same technology and protocols, it does not introduce any new issues.

How should I prepare for this change?


You should evaluate your programs to see which ones might be suited to being run as a RemoteApp program, and then test the programs. To test your programs, follow the procedures described in the TS RemoteApp Step-by-Step Guide to configure your terminal server to support RemoteApp programs, and to distribute the programs to users.

Do I need to change any existing code?


For a program to run as a RemoteApp program, the terminal server that hosts the program must be running Windows Server 2008. Any program that can run in a Terminal Services session or in a Remote Desktop session should be able to run as a RemoteApp program.

Some of the fundamental changes in the Windows Server 2008 operating system might impact earlier versions of programs that run correctly under earlier versions of the Windows operating system. If you experience difficulty running a program as a RemoteApp program, verify that it runs correctly on the local console of a server that is running Windows Server 2008.

Review other sections of this guide for additional information about compatibility issues.

Additional references


For more information about TS RemoteApp, see the TS RemoteApp Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=84895).

For information about other new features in Terminal Services, see the Terminal Services Role topic.


TS Web Access


Terminal Services Web Access (TS Web Access) is a role service in the Terminal Services role that lets you make Terminal Services RemoteApp™ (TS RemoteApp) programs, and a link to the terminal server desktop, available to users from a Web browser. Additionally, TS Web Access enables users to connect from a Web browser to the remote desktop of any server or client computer where they have the appropriate access.

What does TS Web Access do?


After you install TS Web Access on a Windows Server 2008-based server, users can connect to the TS Web Access server to access RemoteApp programs that are available on a Windows Server 2008-based terminal server. TS Web Access has many benefits. These include the following:

 Users can access RemoteApp programs or the full terminal server desktop from a Web site over the Internet or from an intranet. To start a RemoteApp program or desktop session, they just click the program icon.

 If a user starts more than one RemoteApp program through TS Web Access, and the programs are running on the same terminal server, the RemoteApp programs run within the same Terminal Services session.

 By using TS Web Access, there is much less administrative overhead. You can easily deploy programs from a central location. Additionally, programs are running on a terminal server and not on the client computer so they are easier to maintain.

 TS Web Access includes Remote Desktop Web Connection, which enables users to connect remotely to the desktop of any computer where they have Remote Desktop access.

 TS Web Access provides a solution that works with minimal configuration. The TS Web Access Web page includes a customizable Web Part, which can be incorporated into a customized Web page or a Microsoft® Windows® SharePoint® Services site.


Who will be interested in this feature?


The information in this topic applies to the following types of IT professionals:

 IT professionals who already run or who are interested in deploying programs to users by using Terminal Services.

 IT professionals who want better control over the users' experience.

 Web administrators and developers.

 Windows SharePoint Services administrators.

Are there any special considerations?


Before you install TS Web Access, review the following installation guidelines:

 You must install TS Web Access on a computer that is running Windows Server 2008.

 You must install TS Web Access together with Microsoft Internet Information Services (IIS) 7.0.

 The TS Web Access server does not have to be a terminal server.

To use TS Web Access, client computers must be running RDC 6.1. (RDC 6.1 [6.0.6001] supports Remote Desktop Protocol 6.1.) RDC 6.1 is included with the following operating systems:

 Windows Server 2008

 Windows Vista® with Service Pack 1 (SP1) Beta or Windows Vista with SP1 Release Candidate (RC)

 Windows XP with Service Pack 3 (SP3) Beta or Windows XP with SP3 RC




Download 1.83 Mb.

Share with your friends:
1   ...   16   17   18   19   20   21   22   23   ...   35




The database is protected by copyright ©ininet.org 2024
send message

    Main page