Chapter 14, Microsoft Windows 2000 Application Servers

Chapter 14, Lesson 1

Exploring Microsoft Internet Information Services 5.0 Features

1. Introduction to Microsoft IIS 5.0

|1| A. Reliability and performance

1. Application protection

a. The operating system guards each application process from other processes in memory.

b. IIS 4.0 allowed applications to run either in the same server process or out-of-process.

c. IIS 5.0 allows applications to run in a pooled process separate from the IIS server process.

d. Greater isolation comes at the cost of slower performance.

2. IIS Reliable Restart

a. In the event of a system failure, you must be able to get IIS running as quickly as possible.

b. Windows 2000 includes Reliable Restart, which is a faster, easier, and more flexible one-step restart process.

3. Socket pooling

a. A socket is a protocol identifier for a particular network node.

b. In IIS 4.0, each site has its own socket that is not shared with sites bound to other IP addresses.

c. In IIS 5.0, sites bound to different IP addresses but sharing the same port number can share the same set of sockets.

d. More sites can be bound to an IP address on the same machine.

4. Multi-site hosting

a. Windows 2000 Server supports the ability to host multiple sites on a single server.

b. Each Web site has a unique, three-part identity it uses to receive and respond to requests.

(1) Port number

(2) IP address

(3) Host header name

c. Each Web site can share two out of three unique characteristics and still be identified as a unique site.

5. Process throttling

a. You can limit how much processor time a Web site’s applications are permitted to use.

b. Process throttling helps ensure that processor time is available to other Web sites or applications.

6. Bandwidth throttling

a. Bandwidth throttling frees up bandwidth for other services.

b. Bandwidth throttling allows administrators to regulate the amount of server bandwidth each site uses.

B. Management

|2| 1. Setup and upgrade integration

a. The setup process of IIS is integrated with the Windows 2000 Server setup process.

b. IIS creates the Default Web Site, the Administration Web Site, and the Default SMTP Virtual Server.

2. Centralized administration

|3| a. You can use the Internet Information Services snap-in to administer IIS.

|4| b. You can use the Internet Services Manager (HTML) tool to administer IIS remotely over an HTTP or HTTPS connection.

|5| 3. Delegated administration

a. Members of the Operators group have limited administration privileges on Web sites.

b. Operators can administer properties that affect only their respective sites.

c. Operators do not have access to properties that affect IIS, the Windows server hosting IIS, or the network.

|6| 4. Process Accounting

a. Process Accounting allows you to monitor and log how Web sites use CPU resources.

b. Process Accounting adds fields to the W3C Extended log file to record information about how Web sites use CPU resources.

c. You can enable Process Accounting through a site’s properties in the Internet Information Services snap-in.

|7| 5. Improved command-line administration scripts

a. IIS ships with scripts that can be executed from the command line to automate the management of common Web server tasks.

b. You can create custom scripts that automate the management of IIS.

c. Windows Script Host (WSH) is used to run the .vbs scripts.

|8| 6. Backing up and restoring IIS

a. You can use the Internet Information Services snap-in to back up and restore your IIS configuration.

b. You can back up and restore the Web server configuration, but not the content files or registry settings.

|9| 7. Custom error messages

a. You can use the custom error messages that IIS provides, or you can create your own.

b. The custom error messages are stored in the %systemroot%\Help\iisHelp\common folder.

|10| 8. Support for FrontPage Server Extensions

a. You can use Microsoft FrontPage Web authoring and management features to deploy and manage Web sites.

b. FrontPage Web is enabled by default.

c. The FrontPage Server Extensions snap-in includes two setup features that are important for initially configuring and checking the extensions.

(1) Configuring an existing Web server to use the server extensions

(2) Checking server extension security

d. You can use the Internet Information Services snap-in to configure an existing Web server for server extensions.

|11| 9. Web Distributed Authoring and Versioning

a. IIS supports Web Distributed Authoring and Versioning (WebDAV).

b. WebDAV allows users to share documents over the Internet or an intranet.

|12| 10. Distributed file system (Dfs)

a. IIS can use Dfs.

b. You can make files that are distributed across multiple servers appear to users as if they reside in one place.

|13| 11. HTTP compression

a. HTTP compression allows faster transmission of pages between a Web server and compression-enabled clients.

|14| b. You can use the Internet Information Services snap-in to enable HTTP compression.

|15| c. You can use the Internet Services Manager (HTML) tool to enable HTTP compression.

|16| 12. FTP and FTP restart

a. The FTP service is integrated into Windows 2000 Server.

b. Windows 2000 supports the FTP Restart protocol.

|17| C. Security

1. Security features take advantage of the Internet-standard security features that are fully integrated in Windows 2000.

2. IIS supports a number of security protocols.

a. Fortezza

b. Secure Sockets Layer (SSL) 3.0

c. Transport Layer Security (TLS)

d. PKCS #7

e. PKCS #10

f. Basic Authentication

g. Digest Authentication

h. Integrated Windows Authentication

3. IIS uses five basic security mechanisms.

a. Authentication

(1) Anonymous FTP and HTTP authentication

(2) Basic FTP and HTTP authentication

(3) Digest authentication for Windows 2000 Domains and browsers supporting this HTTP 1.1 authentication method

(4) Integrated Windows authentication (HTTP only)

b. Certificates

c. Access control

d. Encryption

e. Auditing

4. IIS includes three new security task wizards.

|18| a. The Web Server Certificate wizard simplifies certificate administration tasks.

|19| b. The Permissions Wizard walks administrators through the tasks of setting up permission and authenticated access on an IIS Web site.

(1) The Permissions Wizard provides two top-level options: inherited security settings and security settings based on a template.

(2) Two templates are available for configuring security: the Public Web site template and the Secure Web site template.

|20| (3) The Permissions Wizard can be started from the Internet Services Manager (HTML) tool.

|21| c. The Certificate Trust List Wizard allows administrators to configure certificate trust lists (CTLs).

|22| D. Application environment

1. Overview of Active Server Pages (ASP)

a. The ASP technology within IIS, along with the data access and component services within Windows 2000 Server, provide a well-rounded application environment.

b. ASP is easier to use because of enhanced flow control and error handling, Windows Script Host Components, and other improvements.

c. ASP is a server-side scripting environment that you can use to create and run dynamic, interactive Web server applications.

2. Component Services (COM+)

a. IIS and COM+ work together to form a basic architecture for building Web applications.

b. COM+ provides all transaction support for MTS.

c. IIS uses the functionality provided by Component Services to perform several tasks.

(1) Isolate applications into distinct processes

(2) Manage communication between COM components (including the ASP built-in objects)

(3) Coordinate transaction processing for transactional ASP applications

3. Active Directory services

a. Active Directory services stores and manages information about networked resources.

b. Active Directory Service Interfaces (ADSI) is a COM-based directory service model that allows ADSI-compliant client applications to access a wide variety of directory protocols.

c. IIS stores most Internet site configuration information in the IIS metabase.

|23| 2. Installing IIS 5.0

A. IIS is a component of Windows 2000.

B. Installation and removal of IIS is accomplished in one of three ways.

1. When installing or upgrading to Windows 2000

2. By using the Add/Remove Programs utility

3. By using an unattended.txt file during an unattended installation

C. When a clean installation of Windows 2000 Server is performed, IIS is installed by default.

D. When an upgrade is performed, IIS is installed if another version of IIS, Peer Web Services, or Personal Web Server is detected.

E. During the IIS installation, Setup verifies that TCP/IP is installed.

F. During the IIS installation, the Default Web Site, Administration Web Site, and SMTP Virtual Server are created.

3. Setting Up a Web Environment

A. Getting started

|24| 1. Overview

a. You should set up your Web sites by indicating which folders contain the documents that you want to publish.

b. You do not have to create a special folder structure to publish documents immediately.

c. Intranet users can access files in the default home folder.

(a) http://<computer_name/file_name>

(b) http://<FQDN/file_name>

(c) http://<IP_address/file_name>

|25| 2. Defining home directories

a. Each Web site and FTP site must have one home directory.

b. The home directory is the central location for your published pages.

c. A default home directory is created when you install IIS and when you create a new Web site.

d. You can use the Internet Information Services snap-in to change the home directory.

e. The home directory can reside on the computer running IIS, on a share, or can be redirected to a URL hosted by another Web site.

|26| 3. Creating virtual directories

a. You can create a virtual directory to publish from a directory not contained within your home directory.

b. A virtual directory has an alias.

c. For a simple Web site, you can place all your files in the home folder, and you will not need to create a virtual directory.

d. You can use the Internet Information Services snap-in or the Internet Services Manager (HTML) tool to create a virtual directory.

|27| 4. Reroute requests with redirects

a. If you move a page on a Web site, you can instruct the Web server to give the browser the new URL.

b. Redirecting a URL is useful when you want to make a portion of your site unavailable or when you have changed the name of a virtual directory.

c. You can use the Internet Information Services snap-in to redirect requests to a Web site, a virtual directory, or another directory.

|28| 5. Other IIS tools

a. Server-side includes (SSI) allow you to perform a number of Web site management activities.

b. SSI commands are added to Web pages at design time.

c. ASP is a server-side scripting environment that you can use to dynamically alter Web content.

d. Unlike SSI, ASP requires you to use a scripting language such as VBScript or JScript.

B. Using ASP to manage Web site content

|29| 1. Scripting

a. A script is a series of instructions and commands that you can use to programmatically alter the content of your Web pages.

b. There are two kinds of scripting: client-side and server-side.

(1) Client-side scripts run on the Web browser and are embedded in the Web pages.

(2) Server-side scripts run exclusively on the Web server and are most often used to modify Web pages before they are delivered to the browser.

|30| 2. ASP overview

a. You can create a server-side script to automatically perform difficult or repetitious Web management tasks.

b. ASP is a powerful, server-side scripting environment that you can use to write scripts with only a standard text editor.

c. ASP uses delimiters to differentiate script commands from regular text and HTML.

d. All ASP files must have an .asp extension and contain script commands written in a scripting language such as VBScript or JScript.

Chapter 14, Lesson 2

Administering a Web Environment

1. Administering Web and FTP Sites

A. Overview

|31| 1. Web sites and FTP sites

a. You can create multiple Web sites and FTP sites on a single computer.

(1) Append port numbers to the IP address

(2) Use multiple IP addresses, each having its own network adapter card

(3) Assign multiple domain names and IP addresses to one network adapter card

b. Each site has the same security options as they would if they existed on separate computers.

c. Each site has its own access and administration permission settings.

|32| 2. Properties and inheritance of properties on sites

a. Properties are values that can be set on your Web site.

b. During the installation of IIS, default values are assigned to the various properties.

c. Properties can be set on the site level, directory level, or file level.

d. Some properties have a value that takes the form of a list.

|33| e. Master properties, server extensions, bandwidth throttling, and MIME mapping are viewed from the properties of a computer node in the Internet Information Services snap-in or the Internet Services Manager (HTML) tool.

f. Internet Server API (ISAPI) filters are displayed in a list format, but are not treated as a list.

|34| 3. Operators group

a. Operators are a special group of users who have limited administrative privileges on individual Web sites.

b. Operators can administer properties that affect only their respective sites.

c. Operators do not have access to properties that affect IIS, the Windows server hosting IIS, or the network.

d. Distributed server administration has several advantages.

(1) Each member of the Operators group can act as the site administrator and can change or reconfigure the Web site as necessary.

(2) The Web site operator is not permitted to change the identification of Web sites, configure the anonymous user name or password, throttle bandwidth, create virtual directories or change their paths, or change application isolation.

(3) Because members of the Operators group have more limited privileges than Web site administrators, they are unable to remotely browse the file system and therefore cannot set properties on directories and files, unless a UNC path is used.

|35| 4. Administering sites remotely

a. If you are connecting to your server over the Internet or through a proxy server, you can use the Internet Services Manager (HTML) tool to change properties.

b. If you are on an intranet, you can use the Internet Information Services snap-in or the Internet Services Manager (HTML) tool to change properties.

c. Internet Services Manager (HTML) uses the Administration Web site to access IIS properties.

d. You can use Terminal Services over a network connection to administer IIS.

e. IIS documentation is available when you are performing remote administration tasks.

|36| 5. FTP Restart

a. FTP Restart addresses the problem of losing a network connection while downloading files.

b. Clients that support FTP Restart need only reestablish their FTP connection, and the file transfer automatically picks up where it left off.

|37| B. Managing sites

1. Starting and stopping sites

a. By default, sites start automatically when your computer restarts.

b. Stopping a site stops Internet services and unloads Internet services from your computer’s memory.

c. Use the Internet Information Services snap-in to start, stop, or pause a site.

2. Adding sites

a. You can add new sites to a computer by launching the Web Site Creation wizard, the FTP Site Creation wizard, or the SMTP Virtual Server wizard.

b. Follow the on-screen directions to assign identification information to your new site.

3. Naming Web sites

a. Each Web site has a descriptive name and can support one or more host header names.

b. Not all browsers support host header names.

c. A visitor with a browser that does not support host header names is directed to the default Web site assigned to the IP address.

d. You can use the Internet Information Services snap-in to name a site.

|38| 4. Stopping, starting, restarting, or rebooting in IIS

a. In IIS, you can stop, start, or reset (restart) all your Internet services, or you can reboot the server from within the Internet Information Services snap-in.

b. The restart function stops and starts internet services.

c. You should use the Internet Information Services snap-in to restart Internet services, not the Services snap-in in Computer Management.

|39| C. Backing up and restoring IIS

1. You can use the Internet Information Services snap-in to back up your IIS configuration.

2. You can restore only your IIS settings, not the content files.

3. You can use the Internet Information Services snap-in to restore your IIS configuration.

2. Managing WebDAV Publishing

|40| A. Overview of WebDAV

1. WebDAV allows clients to perform a number of tasks.

a. Manipulate resources in a WebDAV publishing directory on your server.

b. Modify properties associated with certain resources.

c. Lock and unlock resources so that multiple users can read a file concurrently, but only one person at a time can modify the file.

d. Search the content and properties of files in a WebDAV directory.

2. Windows 2000 connects to a WebDAV server through the Add Network Place wizard.

a. Windows 2000 displays the contents of a WebDAV directory as if it were part of the same file system on your local computer. Once connected, you can drag and drop files, retrieve and modify file properties, and do many other file-system tasks.

b. Internet Explorer 5 connects to a WebDAV directory and lets you do the same file-system tasks as you can through Windows 2000.

c. Make sure to enable the Directory Browsing permission in the properties of the virtual directory in order to access the virtual directory using Internet Explorer 5.

d. Office 2000 creates, publishes, edits, and saves documents directly into a WebDAV directory through any application in Office 2000.

3. Once connected to a WebDAV directory, you can quickly search the files on that directory for content as well as properties.

4. WebDAV security is integrated with Windows 2000 and IIS.

a. WebDAV borrows the security features offered by both Windows 2000 and IIS.

b. Clients with proper permissions can write to a WebDAV directory.

c. IIS supports Digest authentication, which offers tighter security for passwords and for transmitting information across the Internet.

|41| B. Creating a publishing directory

1. To set up a publishing directory, create a physical directory below Inetpub.

2. You can put the directory anywhere except under Wwwroot.

3. You can create a new Web site or use an existing site and then create a virtual directory beneath it.

4. You are granting users the right to publish documents on this virtual directory and see a list of the files in it.

|42| C. Managing WebDAV security

1. Authenticating clients

a. IIS 5.0 supports several levels of authentication.

(1) Anonymous

(2) Basic

(3) Integrated Windows

(4) Digest

b. The best way to configure a WebDAV directory depends on the kind of publishing you want to do.

2. Controlling access

a. Setting up Web permissions

(1) Read, Write, and Directory Browsing enabled

(2) Write enabled, Read and Directory Browsing disabled

(3) Read and Write enabled, Directory Browsing disabled

(4) Index This Resource enabled

b. Controlling access with DACLs

(1) When setting up a WebDAV publishing directory, Windows 2000 Server gives everyone Full Control by default.

(2) Change the default permission so that everyone has Read permission.

(3) Grant Write permission to certain individuals or groups.

c. Protecting script code

(1) You can deny access to script files that you do not want to expose to clients.

(2) Scripts include files with extensions that appear in the Applications Mapping list.

(3) You can prevent .exe files from being downloaded and treated as if they were HTML files.

(4) You can set permissions so that clients can write to executable files.

3. Denying service

a. Dragging and dropping extremely large files into a WebDAV directory could take up a large amount of disk space.

b. To limit the amount, consider setting quotas on disk usage.

4. Publishing and managing files

a. You can connect to a WebDAV publishing directory, publish documents, and manipulate files.

b. You can connect to a WebDAV publishing directory on another server through My Network Places.

c. You can connect to a WebDAV publishing directory through Internet Explorer 5.0.

Chapter 14, Lesson 3

Configuring and Running Telnet Services

1. Telnet Service

|43| A. Overview

1. Windows 2000 Telnet service allows users of a Telnet client to connect to the computer running the Telnet service.

2. The Telnet service acts as a gateway for Telnet clients to communicate with each other.

3. Two Telnet service connection licenses are provided with each installation of Windows 2000 Server.

4. You can use your local Windows 2000 user name and password or domain account information to access the Telnet server.

a. The security scheme is integrated into Windows 2000 security.

b. If you are using NTLM authentication, the client uses the Windows 2000 security context for authentication and the user is not prompted for a user name and password.

|44| B. Starting and stopping Telnet Server

1. By default, the Telnet service is set to manual startup.

2. You can use the Services snap-in to start, stop, or configure the Telnet service for automatic startup.

3. You can start or stop the Telnet service from a command prompt.

|45| C. Telnet Server Admin utility

1. You can use the Telnet Server Admin utility to start, stop, or get information about Telnet Server.

2. You can open the Tenet Server Admin utility in two ways.

a. Open the Telnet Administration Tool in the Administrative Tools program group.

b. Click Start, click Run, type tlntadmn, and then click OK.

3. The Telnet Server Admin utility includes a number of options.

a. 0, Quit this application

b. 1, List the current users

c. 2, Terminate a user session

d. 3, Display/change registry settings

e. 4, Start the service

f. 5, Stop the service

4. You can modify the Telnet Server registry settings.

a. 0, Exit this menu

b. 1, AllowTrustedDomain

c. 2, AltKeyMapping

d. 3, DefaultDomain

e. 4, DefaultShell

f. 5, LogonScript

g. 6, MaxFailedLogins

h. 7, NTLM

i. 8, TelnetPort

5. When you change the default domain account, the setting takes effect only after the Telnet service is restarted.

|46| D. Troubleshooting

1. Invalid input

2. Failed to open the registry key

3. Failed to query the registry value

2. Telnet Client

|47| A. Overview

1. You can use Microsoft Telnet Client to connect to a remote computer running the Telnet service.

2. Once you have made the connection, you can communicate with the server.

3. The Telnet client uses the Telnet protocol, which is part of the TCP/IP suite of protocols.

4. Microsoft Telnet Client is now a command-line application rather than a Windows application.

5. Microsoft Telnet Client provides NTLM authentication support.

|48| B. Using Telnet

1. You can open Telnet in two ways.

a. Click Start, click Run, type telnet, and then click OK.

b. Type telnet at a command prompt, and then press Enter.

2. To use Telnet, you must have TCP/IP installed and configured on your computer and you must have a user account established on the remote host.

3. To display help for Telnet, type help at the Microsoft Telnet command prompt.

Chapter 14, Lesson 4

Installing and Configuring Terminal Services

1. Overview of Terminal Services

|49| A. Introduction

1. Terminal Services enables all client application execution, data processing, and data storage to occur on the server.

2. The terminal emulation software sends keystrokes and mouse movements to the server.

3. Users can gain access to Terminal Services over any TCP/IP connection.

4. Terminal Services provides remote administration of network resources.

5. You can enable Terminal Services in one of two modes: Remote Administration or Application Server.

|50| B. Remote Administration

1. Remote Administration allows administrators to remotely administer each Windows 2000 Server computer over any TCP/IP connection.

2. Remote Administration mode installs only the remote access components of Terminal Services.

|51| C. Application Server

1. Application Server allows you to deploy and manage applications from a central location.

2. You can install applications directly at the Terminal server, or you can use remote installation.

3. Client licensing is required when deploying a Terminal server as an application server.

2. Tools for Administration

|52| A. Terminal Services client creator

1. Use this tool to create floppy disks for installing the Terminal Services Client software.

2. You can install the Terminal Services Client software on Windows for Workgroups, Windows 95, Windows 98, or Windows NT.

|53| B. Terminal Services Manager

1. Use this tool to manage all Windows 2000 Server computers running Terminal Services.

2. You can view current users, servers, and processes.

|54| C. Terminal Services configuration

1. Use this tool to manage your Remote Desktop Protocol (RDP) configuration.

2. You can choose to inherit information from the same options located in the user configuration.

|55| D. Terminal Services licensing

1. Use this tool to store and track Windows 2000 Terminal Services client access licenses.

2. This tool can be installed either during installation of Terminal Services or later.

3. Terminal Services Licensing Components

|56| A. Microsoft Clearinghouse

1. The Microsoft Clearinghouse is the database that Microsoft maintains to activate license servers and to issue client license key packs.

2. The Clearinghouse stores information about all activated license servers and client license key packs.

|57| B. License server

1. A license server stores all Terminal Services client licenses that have been installed for a Terminal server.

2. A Terminal server must be able to connect to an activated license server before clients can be issued licenses.

3. One activated license server can serve multiple Terminal servers.

|58| C. Terminal server

1. A Terminal server is a computer on which Terminal Services is enabled and running.

2. A Terminal server provides clients access to Windows-based applications running on the server.

3. When clients log on to a Terminal server, the server validates the client license.

|59| D. Client licenses

1. Each client computer or terminal that connects to a Terminal server must have a valid client license.

2. The client license is stored locally and presented to the Terminal server each time the client connects to the server.

3. The server validates the license and then allows the client to connect.

4. Administering a License Server

|60| A. Setting up a license server

1. A license server is required by Terminal Services when running in Application Server mode.

2. The Terminal Services Licensing service is a low-impact service that stores and tracks client licenses.

3. The license server must be activated through the Microsoft Clearinghouse and loaded with Client Access Licenses for distribution from the Clearinghouse.

|61| B. Enabling a license server

1. You can enable the Terminal Services Licensing service on your computer when you run Windows 2000 Server Setup.

2. Before installing the license server, you should consider which type of license server you require.

a. Domain license server

b. Enterprise license server

3. When Terminal Services is enabled, the Terminal server begins polling the domain and Active Directory services looking for a license server.

4. Install the license server on a computer that has Internet access.

5. You must enable a Windows 2000 license server within 90 days of enabling Terminal Services.

|62| C. Activating a license server

1. A license server must be activated in order to identify the server and allow it to issue client licenses to your Terminal servers.

2. You can activate a license server by using the Licensing wizard.

3. There are four methods of activating your license server.

a. Internet

b. Web-based

c. Fax

d. Telephone

4. The Internet activation method is the quickest and easiest.

5. You are required to activate a license server only once.

6. The digital certificate that uniquely identifies your license server is stored in the form of a License Server ID.

|63| D. Installing licenses

1. Terminal Services licenses must be installed on your license server in order for the Internet Connector setting to be enabled or for non–Windows 2000 clients to permanently access a Terminal server.

2. After you have installed your licenses, your license server can begin deploying the licenses.

5. Deploying to Client Computers

|64| A. Overview

1. Client computers or terminals connect to a Terminal server by using a small client program installed on disk or in firmware.

2. Windows-based client computers should meet minimum hardware requirements.

a. 80386 microprocessor running at 33 MHz

b. 16-bit VGA card

c. Microsoft TCP/IP stack

3. The Terminal Services client takes up only about 500 KB of disk space and typically uses about 4 MB of RAM.

4. There are two ways to deploy the client.

a. Create a file share to do the installation over the network.

b. Select Terminal Services Client Creator from the Administration Tools program group, and make a client image that can be installed with a floppy disk.

|65| B. Client configurations

1. Disable the Active Desktop.

2. Disable smooth scrolling.

3. Minimize the use of graphics and animation, including animated graphics, screen savers, blinking cursors, and the animated Microsoft Office Assistant. Place shortcuts on the desktop and keep the Programs submenu as flat as possible. Avoid using bitmaps in wallpaper; in Display Properties set Wallpaper to None on the Background tab, and select a single color from the Appearance tab.

4. Enable file sharing on client computers and share drives with easily identifiable names like “drivec.”

5. Avoid the use of MS‑DOS or Win16 (16-bit) applications where possible.

6. Configure the Terminal server to return the user’s logon name rather than the computer name to applications that make use of a NetBIOS function that calls for the computer name.

7. Train users to use Terminal Services hot key sequences. There are a few important differences between the hot key sequences used in a Terminal Services client session and those used in a Windows 2000 session.

|66| 6. Upgrading to Terminal Services

A. WinFrame with or without MetaFrame

B. Terminal Server 4.0 without MetaFrame

C. Terminal Server 4.0 with MetaFrame

D. Windows NT without Terminal Services

7. Installing and Configuring Applications

|67| A. Overview

1. A Windows 2000 Server computer running Terminal Services in Application Server mode provides multiple concurrent user connections to any number of applications.

2. You should use the Add/Remove Programs utility in Control Panel to add or remove applications.

3. You can install applications by putting the Terminal server in Install mode.

4. Only administrators are allowed to install applications on a Terminal Services application server.

|68| B. Deploying applications through Group Policy

1. You can deploy applications through Active Directory services and Group Policy by using Windows Installer.

2. There are three main ways you can deploy applications when using Windows Installer.

a. Install on a local computer by the user

b. Assign by the system administrator from the domain controller to a user or a computer

c. Publish by the system administrator from the domain controller for a user

|69| C. Deploying applications from a domain controller

1. To deploy an application from a domain controller, a system administrator needs to assign an .msi-based application to a computer.

2. Transform files are required if the original application installation package did not install all the necessary components.

3. A system administrator can install an application from a remote session or the console of an application server.

4. The installation of an application in a multi-user environment is very different from an installation to an individual user.