Windows Terminal Services

Article
02/20/2014

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Microsoft® Project 2002 has been designed to work effectively with Microsoft Windows® NT® Server version 4.0, Terminal Services Edition and the Windows 2000 Terminal Services feature (Terminal Services). Terminal Services allows users to run Windows-based programs on computers that cannot run the latest versions of Windows. With Terminal Services, you can deploy Microsoft Project 2002 on the server and have users run Microsoft Project over the network.

Using Microsoft Project 2002 with Terminal Services

Windows NT Server version 4.0, Terminal Services Edition and the Windows 2000 Terminal Services feature (Terminal Services) provide a thin-client solution in which Windows-based programs are executed on the server and remotely displayed on the client. If your users have computers with limited disk space, memory, or processing speed, you can install Microsoft Project 2002 to run in this environment.

With Terminal Services, you install a single copy of Microsoft Project on the Terminal Services computer. Instead of running Microsoft Project locally on their hard disks, multiple users can connect to the server and run Microsoft Project from there.

The following is an overview of how you use Microsoft Project with Terminal Services:

The administrator installs a single copy of Microsoft Project on the Terminal Services computer.

Users install Windows Terminal Client on their computers.

Users log on to the Terminal Services computer, and run Microsoft Project 2002 from within the Windows session.

In the Terminal Services environment, Microsoft Project 2002 separates application and user data, and uses environmental information supplied by Terminal Services. This arrangement allows multiple Terminal Client users to run Microsoft Project from the same installation.

To improve performance in the Terminal Services environment, certain features of Microsoft Project will not function in order to reduce the amount of network traffic necessary to update the user's display. For example, in the Terminal Services environment, Microsoft Project displays a text-based splash screen, rather than the standard graphics-based screen — the text-based screen is displayed faster.

How to Install Microsoft Project 2002 on a Windows Server with Terminal Services

You install Microsoft Project 2002 from the Microsoft Project CD on a server running Microsoft Windows NT Server 4.0, Terminal Services Edition, or Windows 2000 Terminal Services in much the same way you install Microsoft Project on a client computer. With some careful planning and a few modifications, Microsoft Project performs well in the Terminal Services environment.

To run Microsoft Project 2002 in this environment

Install Microsoft Project on the Terminal Services computer.

Set the Microsoft Project settings for Terminal Client users.

Running Microsoft Project on individual users' computers is different from running it in a Terminal Services environment. When you install Microsoft Project on a Terminal Services computer, the users who connect to the server are limited to the Microsoft Project configuration on that computer and cannot install or remove features. If your users need different sets of Microsoft Project functionality, you might need several Terminal Services computers — one for each unique Microsoft Project configuration.

Install Microsoft Project on the Terminal Services Computer

To install Microsoft Project, run Microsoft Project Setup on the Terminal Services computer. You can run Setup from a network administrative installation point or from the Microsoft Project 2002 CD.

To install Microsoft Project 2002 with Terminal Services enabled

In Control Panel, double-click Add/Remove Programs.

Click Add New Programs in the left pane, and then click CD or Floppy in the right pane.

Put the Microsoft Project 2002 CD into the CD-ROM drive and then click Next.

Click Finish to run Microsoft Project Setup.

To install Microsoft Project on Windows NT 4.0 Terminal Server

In Control Panel, double-click Add/Remove Programs, click Install, and then click Next.

Click Browse.

In the root folder of the Microsoft Project CD, select Setup.exe, then click OK.

On the command line, add the following command after Setup.exe, separated by a space:

/l* "%WINDIR%\Microsoft Project 2002 Setup(0001).txt"

FakePre-623d9ed1afb14a1381e696a2b5f52c4e-752372da324142da9405777057077d09

Click Next.

Select All users begin with common application settings, and then click Next to run Microsoft Project Setup.

Running Microsoft Project in a Terminal Services environment is different from running it on individual users' computers. When you install Microsoft Project on a Terminal Services computer, the users who connect to the server are limited to your Microsoft Project configuration and cannot install or remove features.

In other words, all users running Microsoft Project from the Terminal Services computer inherit the features you select during the installation. If your users need different sets of Microsoft Project functionality, you might need several Terminal Services computers—one for each unique configuration.

Because of the multi-user nature of the Terminal Services computer, and users' restricted access to the server, Microsoft Project Setup, by default, installs all features to one of the following installation states:

Run from My Computer

Not Available

If you want to accept the default Microsoft Project configuration, you do not need to modify the Setup feature tree. However, if there are Microsoft Project features that are not needed by your users, you can improve overall performance and conserve disk space by customizing installation so that Microsoft Project Setup does not install these features on the Terminal Services computer.

Distributing Customized Microsoft Project Settings to Users

You can use the following methods to deliver your customized settings to Terminal Services users:

Using the Office XP Custom Installation Wizard

If you install Microsoft Project on the Terminal Services computer from an administrative installation point, you can use the Office XP Custom Installation Wizard to create a transform on the administrative installation point with your customized settings. You can then install Microsoft Project on the Terminal Services computer using that transform, and Microsoft Project users who log on to the Terminal Services computer will use your customized settings.

Note, however, that any files added to the transform will not be propagated to the Terminal Services users. This includes files that you add using the Add/Remove Files page of the Custom Installation Wizard, as well as any files included in an Office Profile Wizard OPS file that you may have added to the transform. Also, programs that you add to the transform using the Add Installations and Run Programs page of the Custom Installation Wizard will not be executed for each user.

To add per-user files, use the Office XP Custom Maintenance Wizard after Microsoft Project 2002 is installed on the Terminal Services computer. Files added with the wizard are installed as each user logs on to the Terminal Services computer and runs Microsoft Project.

Using the Office XP Profile Wizard

You can install Microsoft Project 2002 on a test computer, configure user options, and then save those options to an OPS file by using the Office Profile Wizard. You can then use the Office XP Custom Maintenance Wizard to incorporate the OPS file in a configuration maintenance file (CMW file). The customizations will be applied when users first log on to the Terminal Services computer and run Microsoft Project 2002.

Using the Office XP Custom Maintenance Wizard

You can configure Microsoft Project after you have installed it on the Terminal Services computer by using the Custom Maintenance Wizard. When users log on to the Terminal Services computer and run Microsoft Project 2002 for the first time, they will receive your customized settings. You can also include an OPS file or other additional files in the CMW file, which will be propagated to users.

Using Windows System Policies

An additional method for configuring Microsoft Project 2002 for users is to use Windows System Policies. You can use the System Policy Editor with the Microsoft Project templates to configure user options and then distribute those policies to users or groups within your network. Each time a user runs Microsoft Project 2002 on the Terminal Services computer, the user's options are configured according to the policies. These templates can be downloaded from the Microsoft Project 2002 Resource Kit Toolbox.