Reliability and Performance

							Reliability and Performance
•   Application protection
•   IIS Reliable Restart
•   Socket pooling
•   Multisite hosting
•   Process throttling
•   Bandwidth throttling
Setup and Upgrade
Integration
•   The setup process of IIS is integrated with the Microsoft
    Windows 2000 Server setup process.
•   IIS creates the Default Web Site, the Administration Web Site,
    and the Default SMTP Virtual Server.
Internet Information
Services Snap-In
Internet Services Manager
(HTML)
Delegated Administration
•   Members of the Operators group have limited administration
    privileges on Web sites.
•   Operators can administer properties that affect only their
    respective sites.
•   Operators do not have access to properties that affect IIS, the
    Windows server hosting IIS, or the network.
Process Accounting
Command-Line
Administration Scripts
•   IIS ships with scripts that can be executed from the command
    line to automate the management of common Web server tasks.
•   You can create custom scripts that automate the management
    of IIS.
•   Windows Script Host (WSH) is used to run the .vbs scripts.
Backing Up and Restoring
IIS
Custom Error Messages
•   You can use the custom error messages that IIS provides, or
    you can create your own.
•   The custom error messages are stored in the
    %systemroot%\Help\iisHelp\common folder.
FrontPage Server
Extensions
•   You can use Microsoft FrontPage Web authoring and
    management features to deploy and manage Web sites.
•   FrontPage Web is enabled by default.
•   The FrontPage Server Extensions snap-in includes two setup
    features that are important for initially configuring and checking
    the extensions.
•   You can use the Internet Information Services snap-in to
    configure an existing Web server for server extensions.
Web Distributed Authoring
and Versioning
•   IIS supports Web Distributed Authoring and Versioning
    (WebDAV).
•   WebDAV allows users to share documents over the Internet or
    an intranet.
Distributed File System
(Dfs)
•   IIS can use Dfs.
•   You can make files that are distributed across multiple servers
    appear to users as if they reside in one place.
HTTP Compression
•   HTTP compression allows faster transmission of pages between
    a Web server and compression-enabled clients.
•   You can use the Internet Information Services snap-in to enable
    HTTP compression.
•   You can use the Internet Services Manager (HTML) tool to
    enable HTTP compression.
Internet Information
Services Snap-In
Internet Services Manager
(HTML)
FTP and FTP Restart
•   The FTP service is integrated into Windows 2000 Server.
•   Windows 2000 supports the FTP Restart protocol.
Security
•   Security features take advantage of the Internet-standard
    security features that are fully integrated in Windows 2000.
•   IIS supports a number of security protocols.
•   IIS uses five basic security mechanisms.
•   IIS includes three new security task wizards.
Web Server Certificate
Wizard
Permissions Wizard
Permissions Wizard
Certificate Trust List Wizard
Application Environment
•   Overview of Active Server Pages (ASP)
•   Component Services (COM+)
•   Active Directory services
Installing IIS 5.0
•   IIS is a component of Windows 2000.
•   Installation and removal of IIS is accomplished in one of three
    ways.
•   When a clean installation of Windows 2000 Server is performed,
    IIS is installed by default.
•   When an upgrade is performed, IIS is installed if another version
    of IIS, Peer Web Services, or Personal Web Server is detected.
Setting Up a Web
Environment
•   You should set up your Web sites by indicating which folders
    contain the documents that you want to publish.
•   You do not have to create a special folder structure to publish
    documents immediately.
•   Intranet users can access files in the default home folder.
Defining Home Directories
Creating Virtual Directories
Reroute Requests with
Redirects
•   If you move a page on a Web site, you can instruct the Web
    server to give the browser the new URL.
•   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.
•   You can use the Internet Information Services snap-in to
    redirect requests to a Web site, a virtual directory, or another
    directory.
Other IIS Tools
•   Server-side includes (SSI) allow you to perform a number of
    Web site management activities.
•   SSI commands are added to Web pages at design time.
•   ASP is a server-side scripting environment that you can use to
    dynamically alter Web content.
•   Unlike SSI, ASP requires you to use a scripting language such as
    VBScript or JScript.
Scripting
•   A script is a series of instructions and commands that you can
    use to programmatically alter the content of your Web pages.
•   There are two kinds of scripting: client-side and server-side.
ASP
•   You can create a server-side script to automatically perform
    difficult or repetitious Web management tasks.
•   ASP is a powerful, server-side scripting environment that you
    can use to write scripts with only a standard text editor.
•   ASP uses delimiters to differentiate script commands from
    regular text and HTML.
•   All ASP files must have an .asp extension and contain script
    commands written in a scripting language such as VBScript or
    JScript.
Web Sites and FTP Sites
Properties and Inheritance
of Properties
WWW Service Master
Properties
Operators Group
•   Operators are a special group of users who have limited
    administrative privileges on individual Web sites.
•   Operators can administer properties that affect only their
    respective sites.
•   Operators do not have access to properties that affect IIS, the
    Windows server hosting IIS, or the network.
•   Distributed server administration has several advantages.
Administering Sites
Remotely
•   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.
•   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.
•   Internet Services Manager (HTML) uses the Administration Web
    site to access IIS properties.
•   You can use Terminal Services over a network connection to
    administer IIS.
•   IIS documentation is available when you are performing remote
    administration tasks.
FTP Restart
•   FTP Restart addresses the problem of losing a network
    connection while downloading files.
•   Clients that support FTP Restart need only reestablish their FTP
    connection, and the file transfer automatically picks up where it
    left off.
Managing Sites
•   Starting and stopping sites
•   Adding sites
•   Naming Web sites
•   Stopping, starting, restarting, or rebooting in IIS
Restarting Internet Services
Backing Up and Restoring
IIS
•   You can use the Internet Information Services snap-in to back
    up your IIS configuration.
•   You can restore only your IIS settings, not the content files.
•   You can use the Internet Information Services snap-in to restore
    your IIS configuration.
Managing WebDAV
Publishing
•   WebDAV allows clients to perform a number of tasks.
•   Windows 2000 connects to a WebDAV server through the Add
    Network Place wizard.
•   Once connected to a WebDAV directory, you can quickly search
    the files on that directory for content as well as properties.
•   WebDAV security is integrated with Windows 2000 and IIS.
Creating a Publishing
Directory
•   To set up a publishing directory, create a physical directory
    below Inetpub.
•   You can put the directory anywhere except under Wwwroot.
•   You can create a new Web site or use an existing site and then
    create a virtual directory beneath it.
•   You are granting users the right to publish documents on this
    virtual directory and see a list of the files in it.
Managing WebDAV Security
Telnet Service
•   Windows 2000 Telnet service allows users of a Telnet client to
    connect to the computer running the Telnet service.
•   The Telnet service acts as a gateway for Telnet clients to
    communicate with each other.
•   Two Telnet service connection licenses are provided with each
    installation of Windows 2000 Server.
•   You can use your local Windows 2000 user name and password
    or domain account information to access the Telnet server.
Starting and Stopping
Telnet Server
Telnet Server Admin Utility
Troubleshooting
•   Invalid input
•   Failed to open the registry key
•   Failed to query the registry value
Telnet Client
•   You can use Microsoft Telnet Client to connect to a remote
    computer running the Telnet service.
•   Once you have made the connection, you can communicate with
    the server.
•   The Telnet client uses the Telnet protocol, which is part of the
    TCP/IP suite of protocols.
•   Microsoft Telnet Client is now a command-line application rather
    than a Windows application.
•   Microsoft Telnet Client provides NTLM authentication support.
Using Telnet
•   You can open Telnet in two ways.
•   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.
•   To display help for Telnet, type help at the Microsoft Telnet
    command prompt.
Introduction to Terminal
Services
•   Terminal Services enables all client application execution, data
    processing, and data storage to occur on the server.
•   The terminal emulation software sends keystrokes and mouse
    movements to the server.
•   Users can gain access to Terminal Services over any TCP/IP
    connection.
•   Terminal Services provides remote administration of network
    resources.
•   You can enable Terminal Services in one of two modes: Remote
    Administration or Application Server.
Remote Administration
•   Remote Administration allows administrators to remotely
    administer each Windows 2000 Server computer over any
    TCP/IP connection.
•   Remote Administration mode installs only the remote access
    components of Terminal Services.
Application Server
•   Application Server allows you to deploy and manage applications
    from a central location.
•   You can install applications directly at the Terminal server, or
    you can use remote installation.
•   Client licensing is required when deploying a Terminal server as
    an application server.
Terminal Services Client
Creator
•   Use this tool to create floppy disks for installing the Terminal
    Services Client software.
•   You can install the Terminal Services Client software on
    Microsoft Windows for Workgroups, Microsoft Windows 95,
    Microsoft Windows 98, or Microsoft Windows NT.
Terminal Services Manager
Terminal Services
Configuration
•   Use this tool to manage your Remote Desktop Protocol (RDP)
    configuration.
•   You can choose to inherit information from the same options
    located in the user configuration.
Terminal Services Licensing
•   Use this tool to store and track Windows 2000 Terminal Services
    client access licenses.
•   This tool can be installed either during installation of Terminal
    Services or later.
Microsoft Clearinghouse
•   The Microsoft Clearinghouse is the database that Microsoft
    maintains to activate license servers and to issue client license
    key packs.
•   The Clearinghouse stores information about all activated license
    servers and client license key packs.
License Server
•   A license server stores all Terminal Services client licenses that
    have been installed for a Terminal server.
•   A Terminal server must be able to connect to an activated
    license server before clients can be issued licenses.
•   One activated license server can serve multiple Terminal
    servers.
Terminal Server
•   A Terminal server is a computer on which Terminal Services is
    enabled and running.
•   A Terminal server provides clients access to Windows-based
    applications running on the server.
•   When clients log on to a Terminal server, the server validates
    the client license.
Client Licenses
•   Each client computer or terminal that connects to a Terminal
    server must have a valid client license.
•   The client license is stored locally and presented to the Terminal
    server each time the client connects to the server.
•   The server validates the license and then allows the client to
    connect.
Setting Up a License Server
•   A license server is required by Terminal Services when running
    in Application Server mode.
•   The Terminal Services Licensing service is a low-impact service
    that stores and tracks client licenses.
•   The license server must be activated through the Microsoft
    Clearinghouse and loaded with Client Access Licenses for
    distribution from the Clearinghouse.
Enabling a License Server
•   You can enable the Terminal Services Licensing service on your
    computer when you run Windows 2000 Server Setup.
•   Before installing the license server, you should consider which
    type of license server you require: domain or enterprise.
•   When Terminal Services is enabled, the Terminal server begins
    polling the domain and Active Directory services looking for a
    license server.
•   Install the license server on a computer that has Internet
    access.
•   You must enable a Windows 2000 license server within 90 days
    of enabling Terminal Services.
Activating a License Server
•   A license server must be activated in order to identify the server
    and allow it to issue client licenses to your Terminal servers.
•   You can activate a license server by using the Licensing wizard.
•   There are four methods of activating your license server.
•   You are required to activate a license server only once.
•   The digital certificate that uniquely identifies your license server
    is stored in the form of a License Server ID.
Installing Licenses
•   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.
•   After you have installed your licenses, your license server can
    begin deploying the licenses.
Deploying to Client
Computers
•   Client computers or terminals connect to a Terminal server by
    using a small client program installed on disk or in firmware.
•   Windows-based client computers should meet minimum
    hardware requirements.
•   The Terminal Services client takes up only about 500 KB of disk
    space and typically uses about 4 MB of RAM.
•   There are two ways to deploy the client.
Client Configurations
•   Disable the Active Desktop.
•   Disable smooth scrolling.
•   Minimize the use of graphics and animation.
•   Enable file sharing on client computers and share drives with
    easily identifiable names.
•   Avoid the use of MS-DOS or Win16 (16-bit) applications where
    possible.
•   Configure the Terminal server to return the user’s logon name.
•   Train users to use Terminal Services hot key sequences.
Upgrading to Terminal
Services
•   WinFrame with or without MetaFrame
•   Terminal Server 4.0 without MetaFrame
•   Terminal Server 4.0 with MetaFrame
•   Windows NT without Terminal Services
Installing and Configuring
Applications
•   Terminal Services in Application Server mode provides multiple
    concurrent user connections to any number of applications.
•   You should use the Add/Remove Programs utility in Control
    Panel to add or remove applications.
•   You can install applications by putting the Terminal server in
    Install mode.
•   Only administrators are allowed to install applications on a
    Terminal Services application server.
Deploying Applications
through Group Policy
•   You can deploy applications through Active Directory services
    and Group Policy by using Windows Installer.
•   There are three main ways you can deploy applications when
    using Windows Installer.
Deploying Applications from
a Domain Controller
•   To deploy an application from a domain controller, a system
    administrator needs to assign an .msi-based application to a
    computer.
•   Transform files are required if the original application installation
    package did not install all the necessary components.
•   A system administrator can install an application from a remote
    session or the console of an application server.
•   The installation of an application in a multi-user environment is
    very different from an installation to an individual user.