Sunteți pe pagina 1din 33

Gibraltar

Microsoft Internet Server ‘95


Installation/Setup

Note: Generally, this project is not being discussed under NDA with any
accounts or third parties. Should you require permission to discuss this with a
particular organization outside the company, please contact the author.

Revision: 0.3
Date: May 30, 1995
Author(s): Kerry Schwartz (KerryS)
Document: issetup.doc

Microsoft Confidential 1
1. INTERNET SERVER......................................................................................................................
2. SETUP OVERVIEW......................................................................................................................
2.1 User Interface...........................................................................................................................
2.2 Setup Initialization....................................................................................................................
3. SETUP INITIAL MODE.................................................................................................................
3.1 Preparation for Installation......................................................................................................
3.1.1 Administrator Privileges.................................................................................................................
3.1.2 Create Directories...........................................................................................................................
3.1.3 Administrator Password Check.......................................................................................................
3.1.4 TCP/IP Installation Check...............................................................................................................
3.1.5 License Logging Service (Honesty)................................................................................................
3.2 Service Installation...................................................................................................................
3.2.1 Copy Files.......................................................................................................................................
3.2.2 Update the Registry........................................................................................................................
3.2.3 Performance Monitor Counters & SNMP MIBs.............................................................................
3.2.4 Service Registration........................................................................................................................
3.3 Service Administration Installation..........................................................................................
3.4 SmallProx Client-Side Gateway Interface................................................................................
3.5 MS Mosaic Browser Installation...............................................................................................
3.6 Client Share-Point Installation.................................................................................................
3.7 Service Administration Share-Point Installation......................................................................
3.8 Online Help and Sample HTML Files......................................................................................
3.9 ODBC Drivers and Administration..........................................................................................
3.10 SMS Files................................................................................................................................
3.11 Installation Progress Dialog...................................................................................................
3.12 Internet Server Program Group..............................................................................................
3.13 Installation Completed............................................................................................................
3.13.1 Services Installed and Started.......................................................................................................
3.13.2 No Services Installed....................................................................................................................
3.14 Interruption of Installation.....................................................................................................
4. MAINTENANCE MODE................................................................................................................
APPENDIX A REGISTRY KEYS FOR INTERNET SERVICES...................................................................

2
1. Internet Server
Internet Server is a Back Office product for Windows NT versions 3.51 and later. The product
includes a set of services that help make Windows NT Server an excellent Internet publishing
platform, as well as a secure access gateway1. Integration with Windows NT system components,
such as security, and other Back Office products (SQL Server, etc.) is included. Internet Server
also includes the client-side components necessary to allow standard CERN-proxy browsers to
access the Internet via the secure access gateway2.
The Windows NT/WFW versions of the Microsoft Mosaic Web/Gopher/FTP browser are included
with Internet Server. The Windows 95-specific version of the browser will ship as part of the
Windows 95 O’Hare product, and will not be included in version 1 of Internet Server, although it
will work in conjunction with Internet Server components. The O’Hare browser will run on the
Windows NT Shell Update Release, and will be the preferred browser on this release.
All versions of the Microsoft Mosaic browser can be used to access the Internet directly, to access
the Internet via the Catapult secure access gateway, or to access internal publishing servers.
Following is a list of components included in Internet Server Version 1, and which operating
system platforms each component requires:

Services (Windows NT 3.51 Server only):


- World-Wide-Web Publishing and Proxy Services
- Gopher Publishing Service
- File Transfer Protocol (FTP) Publishing Service
- Domain Name Service (DNS)
- Internet Applications Gateway (Catapult)

Service Administration Components (Windows NT 3.51 and Windows 95)


- Internet Service Manager
- DNS Configuration Manager
- Gopher Namespace Configuration Manager

Client Components (Windows NT 3.51, Windows 95, WFW)


- MS Mosaic browser
- SmallProx interface for secure Internet access via Catapult
issue: are we going to call this SmallProx?

1
The internal codeword for the secure access gateway is Catapult. Catapult includes CERN-
proxy server compatibility for non-Windows clients (UNIX, etc.), and additional functionality for
Windows clients, such as user-level access control, and transport independence.
2
The internal codeword for the client-side CERN-proxy interface for Catapult is SmallProx.

Microsoft Confidential 3
issue: what client-side configuration UI do we need ( mime mapping, catatpult server
config, etc.)?

Other Components (Windows NT 3.51, Windows 95, WFW)


- Help files
- Internet Assistant
issue: will we ship Word with IA installed, or just IA? What version(s)?

2. Setup Overview
The Internet Server setup program allows the user to select which components to install, and
contains as few choices as possible to obtain all information necessary to install the components,
and in the case of the servers, to start execution. Upon completion of the setup process, the user is
offered the option of running the Internet Service Manager tool for advanced configuration.
A script file (.inf file) will be included for running the Setup program in unattended mode. In
unattended mode, the Setup program will not display any screens requiring user input. This can
be used when installing/upgrading the components via SMS, and for OEM pre-installs.
The Internet Assistant for Microsoft Word HTML authoring and Web browsing tool is included
on the Internet Server CD. This component includes its own setup program, and is not installed
via the Internet Server setup tool.
The setup program will offer only the installation options allowed for the operating system
running on the target machine. The options offered will be determined when the setup program is
initially run (for the local machine), and when a machine name is specified for remote
installation.
Setup can build a share-point (directory) on the hard disk for later installation of client, or
administration components across the network. Setup will not offer the option of creating a
sharepoint for services, however a complete installation share-point can be created by xcopy-ing
the CD image to a directory, or by sharing the CD drive.
When Setup initializes, it will determine which Internet Server components are available in the
installation (source) directory, and only offer those components for installation. The same Setup
program can be run from a sharepoint, and only the components shared will be listed in the
installation-options dialog3.
Installation of service components require that the person running setup be an administrator of
the target machine. Upon completion of installation, the services will be started, and marked for
autostart after a reboot. If the administrator would like to do advanced configuration of the
services immediately, the Internet Service Manager admin tool will be initiated.
If any services are installed, Setup will create a local group in the target machine’s user database,
called ‘Internet Administrators’. Permissions assigned to this group will include administering
the Internet Server services, locally, or remotely.

3
This feature of Setup will also allow us to make changes in the packaging of Internet Server
components, without needing to modify the Setup program.

4
issue: will the ‘Administrators’ group also be able to administer Internet Services? Should the
user running Setup be added automatically to the ‘Internet Administrators’ group?
Internet Server Setup will not include any form of copy protection or serialization. Files installed
will not be stamped with user name or company information. There will not be a product ID
number dialog.
Setup will create an Internet Server program group at the end of installation. This program group
will include icons for items installed, including: the Microsoft Mosaic browser, client admin
tools, server admin tools, help files, and Performance Monitor configurations. If none of these
components are installed (for example, only a client share-point is created), the program group
will not be created. Icons will not be created for services.
issue: we should develop log viewers, log conversion app. (CERN/NCSA format), and install
icons.

2.1 User Interface


The setup tool’s user interface will closely match that of the Exchange Server, the Exchange
client, and the ACME setup application.
The backdrop will be the standard blue backdrop in Microsoft setups. the text at the top will be
“Microsoft Internet Server Setup” in Times New Roman bold italic 22 point.
issue: Final product name waiting on packaging and naming decisions
All dialog boxes requiring configuration information for the installation will be displayed before
the installation is performed. Once all data has been entered, the components will be installed
and configured. Progress will be displayed during installation and configuration. During
installation, billboards will be displayed recommending that the Internet Server software be
registered, and explaining where to look for help information. The billboard will indicate how to
register the software online on the Internet, and that doing so will also offer updated online
information about the product.
issue: need to figure out how many billboards and have product UI group design.
issue: offering online registration would be a great win. we need to setup a web server for this
with appropriate forms, and content. Offering some add-ons to download would generate much
more interest in connecting.

2.2 Setup Initialization


When Setup starts, it displays a dialog indicating “Setup is searching for installed components”.
It determines what O/S platform it is running on, and whether Internet Server setup has ever
been run on this machine before (by checking the registry, and the existence of admin/client
components). If setup has not been run on this machine before (to the point of modifying the
registry and/or installing client/admin components), setup will enter Setup Initial Mode. If Setup
has been run before, setup will enter Setup Maintenance Mode.
During Setup initialization, the operating system platform of the local machine will be
determined so that the options dialog can display only the components that will run on the target

Microsoft Confidential 5
machine. This step will need to be done again later if the user selects another machine for remote
installation.

3. Setup Initial Mode


When running setup.exe for the first time on a machine, the following initial screen is displayed:

issue: Do we need this dialog. If so, should we remove the text about closing down applications?
Upon selecting ‘OK’, the Options dialog is displayed:

6
This ‘options’ dialog is used to specify which computer the install is to be performed on, and
which options to install. The installation options are:
Internet Services
Web Browser Components
Client Share-Point
Service Admin Share-Point

Only the options permitted to be installed on the target machine’s operating system appear in the
options dialog. See section 1 above for the list of permitted components for each O/S platform.
The default settings of the checkboxes installs Internet Services (publishing services, but not
DNS or Application Gateway), and the Web Browser Components.
The directory selection controls allow specifying the install directory for each option. The
‘Change Directory’ button brings up a directory browse window. The directory browser only
displays local drives, except for the installation share-points, which can be installed to any drive
letter.
issue: for installation share-points, can we allow entry of a UNC name?
issue: How do we browse directories when installing on a remote machine?
Some of the options consist of a set of components, and there is a default setting of which
components to install for each option. After selecting (highlighting) an option in the options
listbox, the user presses the ‘Customize Option’ button to replace the option listbox with a listbox
of components. An option can also be double-clicked to bring up it’s component list. When an
option is selected that does not have individual components, the ‘Customize Option’ button is
disabled.

Microsoft Confidential 7
Install directories are specified when viewing the options listbox. Install directories cannot be
modified when viewing the component listbox for an option. All components installed as part of
one option must be installed to the same directory. For example, all Internet services and the
Internet Service Manager are installed to the same directory. This is efficient because these
components share files.
The default installation directories are as follows:
For Internet Services: C:\inetsrvr\services\
For browser components:: C:\inetsrvr\client\
For client share-point: C:\inetsrvr\installc\
For service admin share-point: C:\inetsrvr\installa\

When the listbox displays a set of components for an option, the Change Machine and Customize
Option buttons are disabled.
When the components for the Internet Services option are displayed, the text ‘Install Directory
for Selected Option’ becomes ‘Publishing Directory for Selected Option’. This group box now
specifies the ‘home’ publishing directory for the services, and is enabled only when the selected
service is the FTP, Gopher, or WWW service.
Default ‘home’ directories for publishing content are as follows:
FTP: directory=C:\ftproot
Gopher: directory=C:\gophroot
WWW: directory=C:\webroot

8
When the ‘Customize Option’ button is pressed for any option other than the Internet Services,
the Directories group box text does not change, but the group box becomes disabled.
The components for each option, are as follows. An ‘X’ in front of a component indicates that it
will be checked for installation by default:

Internet Services
X World Wide Web Publishing Service
X Gopher Publishing Service
X FTP Publishing Service
X ODBC Drivers & Administration
X Internet Service Manager
X Help & Sample Files
DNS Name Service
Application Gateway
issue: do we want to offer selection of Windows Gateway and non-Windows CERN Proxy
Gateway?

Web Browser Components


X Microsoft Mosaic
X SmallProx Access Gateway Interface
issue: what will we call this?
X Client Administration Tools
issue: maybe just install these tools along with Mosaic/SmallProx.

Client Share-Point
No components for this option

Internet Service Manager Share-Point


No components for this option

When the user changes the drive, the Space Required/Space Available indicators change to
indicate the new drive letter. These values are the sizes of all files to be added to the drive. The
Space Available is the space currently available on the drive. The size of each option is displayed
in the list box.
The default target installation machine is the local machine. This is indicated in the Target
Computer group box. The button labeled “Change Computer” brings up a dialog that allows

Microsoft Confidential 9
entering the name of any computer on the network. This dialog has a computer ‘browser’ list box,
and ‘OK’, ‘Cancel’, and ‘Help’ buttons:

When ‘OK’ is pressed, the existence of the machine specified is verified. If the machine is not
found, the following msgbox is displayed:

After machine, components, and directories, are specified the user selects ‘Continue’.

3.1 Preparation for Installation


The steps listed in this section are performed, as indicated, before any modifications to the target
machine’s disk/registry are done.

3.1.1 Administrator Privileges


If at least one service is being installed, the setup program verifies that the loggged on user has
administrator privileges on the target machine (the machine being installed to - not necessarily
the machine on which the setup tool is running). If the user does not have such privileges, the
following msg box is displayed:

10
Selecting ‘OK’ returns the user to the options dialog.

3.1.2 Create Directories


Each directory specified (both install directories and publishing directories) is checked. If at least
one directory doesn’t exist, the following window is displayed with all non-existent directories
displayed, requiring only one dialog asking to create directories:

Selecting ‘Cancel’ returns the user to the options dialog.

3.1.3 Administrator Password Check


If Setup is installing any of the services, a secure machine is recommended. Setup will attempt to
authenticate with the username ‘Administrator’, and a blank password. If the authentication is
successful, the following dialog is displayed:

Microsoft Confidential 11
If the use selects ‘Create Password’, a standard ‘Change Password’ dialog is displayed, and the
‘Administrator’ password will be changed.

3.1.4 TCP/IP Installation Check


Next, if any of the Internet Services is being installed, or if MS Mosaic is being installed without
SmallProx, the registry of the target machine is checked to see if TCP/IP is installed. If not, the
following msg box is displayed:

issue:RAS setup runs TCP/IP installation in a mode with very little UI. Can we do the same?
What about when we are installing on a remote machine?

3.1.5 License Logging Service (Honesty)


After the Gibraltar-specific setup dialogs are displayed, if the Catapult server is being installed,
the license server CplSetup API is called to bring up the two license dialogs. The needed registry
entries will be made, and the user will be asked information such as type of licensing (per seat vs.
concurrent), number of client licenses, etc. The setup program needs to do nothing more than call
the API. Verification of available license will be done by the Catapult server at connect time.

3.2 Service Installation


The following four steps are done for each service being installed:
· Copy files
· Update the Registry

12
· Install Performance Monitor Counters & SNMP MIBs
· Register the service(s) with the service controller, RNR registration, and starting the
service(s)

3.2.1 Copy Files


All Services are installed to the same directory. The options dialog forces the same directory to be
selected for all services. This simplifies installation since some files are shared by the services.
The following files are shared by multiple Internet services, and are copied if at least one server
is being installed. All shared files are hardware platform dependent:

Shared Files
inetsvcs.exe program for Internet Service process
tcpsvcs.dll common code, shared by services
_wininet.dll Win32 Internet APIs
(copied for Catapult/Proxy & client only)
inetasrv.dll common RPC interface
inetctrs.dll common performance monitor counters

The following files are copied for each service being installed, into the directory specified in the
options dialog. All files are hardware platform dependent, unless otherwise specified:

FTP Service
ftpsvc.dll ftp service
ftpsvapi.dll stats. & admin RPC client stub APIs
ftpctrs.dll performance monitor counters
ftpmib.dll SNMP support

Gopher Service
gopherd.dll gopher service
gdapi.dll stats. & admin RPC client stub APIs
gdctrs.dll performance monitor counters
gdmib.dll SNMP support
gdspace.dll gopher-space admin APIs (tag-file manager)

WWW Service
w3svc.dll WWW service
w3svapi.dll stats. & admin RPC client stub APIs
w3ctrs.dll performance monitor counter
httpodbc.dll ODBC gateway handling
httpmib.dll SNMP support

Microsoft Confidential 13
DNS Service
DNS database files (not hardware platform dependent)
arpa-127.rev reverse look-ups in 127 (localhost) network
arpa-257.rev reverse look-ups in 257 (sample) network
boot lists filenames of database files to read
cache lists computers that can supply names of
root name servers
place.dom look-ups for place.dom (sample) domain

DNS application files (hardware platform dependent)


dnssvc.dll DNS service
Catapult Service
gateway.dll catapult service
gateapi.dll stats. & admin RPC client stub APIs

3.2.2 Update the Registry


When a service is installed, the registry keys needed for that service are created. If it is the first
Internet Service being installed, the shared registry items will be created as well. The values of
these registry keys will be the default values, except for items obtained by user input at install
time, and items the inital values of which can be determined by reading existing registry entries.
issue: what default values can be obtained from the registry?

See Appendix A for a list of the registry keys created, and default values.

3.2.3 Performance Monitor Counters & SNMP MIBs


Setup will install Performance Monitor counters and SNMP MIBs for each service. Performance
Monitor icons will be installed in the Internet Server Program Group which configure PerfMon
to display some of these statistics.
issue: which statistics should we include in the PerfMon icons?
The counters maintained are as follows:

FTP Service
Total Bytes Sent
Total Bytes Received
Total Files Sent
Total Files Received
Current Anonymous Users
Current Non-anonymous Users
Total Anonymous Users

14
Total Non-anonymous
Max Anonymous Users
Max Non-Anonymous Users
Current Connections
Maximum Connections
Connection Attempts
Logon Attempts

Gopher Service
Total Bytes Sent
Total Bytes Received
Total Files Sent
Total Directories Sent
Total Searches Done
Current Anonymous Users
Current Non-anonymous Users
Total Anonymous Users
Total Non-anonymous Users
Max Anonymous Users
Max Non-anonymous Users
Current Connections
Max Connections
Connection Attempts
Logon Attempts
Aborted Connections

WWW Service
Total Bytes Sent
Total Bytes Received
Total Files Sent
Current Anonymous Users
Current Non-anonymous Users
Total Anonymous Users
Total Non-anonymous Users

Microsoft Confidential 15
Max Anonymous Users
Max Non-anonymous Users
Current Connections
Max Connections
Connection Attempts
Logon Attempts
Total Gets
Total Posts
Total Heads
Total Others
Total CGI Requests
Total BGI Requests
Total Not-Found Errors

issue: need to add for DNS, Access Gateway

3.2.4 Service Registration


For each service being installed, the Service Controller and RNR APIs will be used to register the
service, and bind to appropriate adaptors/protocols. The services will be registered to autostart at
reboot, and they will be started immediately; no reboot will be required.

3.3 Service Administration Installation


The integrated service administration tool is installed if the box for it on the options dialog is
checked. The administration tool files are installed into the directory specified in the options
dialog box, and an icon is created for the tool in the Internet Server program group. The files are
hardware platform dependent.
Internet Service Manager Files
inetmgr.exe ISM program
fscfg.dll configuration UI for FTP service
gscfg.dll configuration UI for Gopher service
w3scfg.dll configuration UI for WWW service
inetmgr.hlp WinHelp file (not hardware platform dependent)
Files shared by Internet services and Internet Service Manager
ftpsvapi.dll RPC support for FTP service
gdapi.dll RPC support for gopher service
w3svapi.dll RPC support for WWW service

issue: files being added for DNS & access gateway administration

16
3.4 SmallProx Client-Side Gateway Interface
The SmallProx files are installed if the user checked the box for it in the options dialog. The files
are installed in the directory specified in the options dialog. Files installed include:

miniprox.dll SmallProx ‘Shim’


_wininet.dll Win32 Internet APIs
wsock32.dll ‘dummy’ WinSock dll(passes SmallProx requests to _wsock32.dll)
_wsock32.dll WinSock code needed for SmallProx functionality
(_wsock32.dll is installed into %systemroot%\system32\ directory)

The SmallProx components requires Win32S and RPC be installed on the machine. If the target
machine is running WFW, these components will be installed if not already present.
issue: need details on what to install for running Win32S applications with RPC.

In order for the MS Mosaic browser, or any other browser to access an Internet Applications
Gateway Service, the client machine must have the following entry in its registry, which will be
added at install time (where ‘jericho2’ is the computer name of the machine running the Gateway
service):
issue: will we automatically configure Netscape/NCSA Mosaic, etc. to use SmallProx if they are
installed?

\registry\machine\system\currentcontrolset\services\internetclient
Parameters
GatewayServers = REG_MULTI_SZ "\\jericho2"
AccessType = REG_DWORD 0x00000002

issue: need UI at setup time to specify the name of the Internet gateway machine

3.5 MS Mosaic Browser Installation


If the browser was selected for installation, the browser files will be copied into the directory
specified in the options dialog, and an icon will be created for it in the Internet Server program
group. If the target machine is running Windows for Workgroups, Win32S will be installed if not
already installed on the machine.

emosaic.exe
<about 60 .gif & .htm files for online help>

issue: are we rewriting the online help in .hlp format or other?

Microsoft Confidential 17
issue: what needs to be configured for browser?

3.6 Client Share-Point Installation


If the user requested a client share-point be created in the options dialog, the directory is created
if necessary, and shared if necessary, granting ‘everyone’ read-only access. The share-name will
be ‘installc’. If the directory exists, and is already shared, the share permissions will not be
changed. The files are copied to the directory needed for installation of the browser, SmallProx,
the client admin tool, and 16 and 32 bit versions of the setup tool. Upon later execution of the
setup tool, it will discover that only client files are available, and only display client options in
the options dialog box.
If client share-point and service administration share-point, are installed into the same directory,
only one copy of the setup tool will be placed in the directory, and when run, it will discover that
both client and administration install options should be displayed.
After the share-point is created, the administrator can edit the inetsvr.inf file to create a
customized automated install for any execution of setup.exe from this share.

3.7 Service Administration Share-Point Installation


If the user requested an administration share-point be created in the options dialog, the directory
is created if necessary, and shared if necessary, granting ‘everyone’ read-only access. The share-
name will be ‘installa’. If the directory exists, and is already shared, the share permissions will
not be changed. The files are copied to the directory needed for installation of the service admin
tools, and 16 and 32 bit versions of the setup tool. Upon later execution of the setup tool, it will
discover that only service administration files are available, and only display administration
options in the options dialog box.
If client share-point and service administration share-point, are installed into the same directory,
only one copy of the setup tool will be placed in the directory, and when run, it will discover that
both client and administration install options should be displayed.
After the share-point is created, the administrator can edit the inetsvr.inf file to create a
customized automated install for any execution of setup.exe from this share.
issue: need to document format and customization of inf file

3.8 Online Help and Sample HTML Files


If services are being installed, and the Help/Sample files component was checked, the files
associated with the services being installed will be copied to ‘help’ and ‘samples’ subdirectories
of the services directory, as specified in the options dialog.
issue: investigating whether we’ll ship help files in WinHelp, HTML, or both formats
Anytime the Mosaic browser is installed, the browser’s help files will be installed. The user
cannot disable installation of the browser’s help files. These files will be installed in the ‘Help’
subdirectory of the browser directory, as specified in the options dialog.

18
3.9 ODBC Drivers and Administration
ODBC Drivers and Administration tool are used by all services when configured to log
transactions via an ODBC DSN. In addition, the Web server includes an ODBC gateway
mechanism for Web access to databases. Internet Server ships with ODBC drivers for SQL and
Access, and the ODBC Administration tool for creating DSNs. The drivers will be installed into
the drivers directory, and the Administration tool will be installed into the directory specified in
the options dialog.

3.10 SMS Files


Each component of the Internet Server product is treated as a separate SMS package. SMS can
install, upgrade, and inventory, installed software, via a PDF (package definition file) for the
package. The Internet Server Setup program will copy a PDF file for each installed component
into the proper directory on the machine (as determined in the registry).
SMS MIF files describe properties of a package, and are accessible to the SMS administration
tool, as well as other applications via a standard interface. A MIF file for each component
installed will also be copied to the correct directory on the target machine.
issue: investigating how to build and where to install these files

3.11 Installation Progress Dialog


While the above installation steps are being done, the setup program brings up a progress
indication dialog. This dialog shows the percent complete, and indicates the current step being
performed.

While this dialog is displayed, billboards will be displayed recommending that the Internet
Server software be registered, and explaining where to look to learn how to register the software
online on the Internet, and that doing so will also offer updated online information about the
product.
issue: need to define exact number and text on billboards

Microsoft Confidential 19
issue: offering online registration would be a great win. we need to setup a web server for this,
and ask at setup time if the installation computer has an Internet connection?

3.12 Internet Server Program Group


The final step of installation will be creation of the Internet Server program group. This program
group will not be created if only installation share-points are created. The program group will
contain icons for the following items (if installed):
MS Mosaic
Client Admin Tool (mime-mapping, etc)
issue: will we need/have a client admin tool?
Internet Service Manager Admin Tool
ODBC Admin Tool
DNS Configuration Tool
Online Help
Performance Monitor (setup for monitoring Internet Service counters)
issue: should the program group be ‘common’, or a ‘current user’ group?
issue: need icons

3.13 Installation Completed

3.13.1 Services Installed and Started


If at least one service was installed, the following window is displayed:

Selecting “Start Internet Service Manager” will terminate the setup program and start the
Internet Service Manager, without doing a network discover, but rather, only show services on the
currently installed machine. Selecting exit brings up the ‘Installation Completed’ window below.
issue: need a parameter to Internet Service Manager to tell it to only show target computer.

3.13.2 No Services Installed

20
If the components installed do not include any Internet services, or if ‘Exit’ is selected on the
Services Installed dialog (section 3.13.1), a standard setup completion dialog is displayed, with
an ‘OK’ button.

3.14 Interruption of Installation


If the user cancels the setup operation anytime before it completes, a standard setup interruption
dialog is displayed informing s/he that they can rerun setup anytime. The setup program will
bring the machine back to the state it was in before setup was run - ie: delete files & directories,
clean up the registry, etc.

Microsoft Confidential 21
4. Maintenance Mode
When setup.exe is run, it checks the system’s registry to determine if it has been run on this
machine before. If it determines that it has been run before (to the point of updating the registry),
setup enters maintenance mode.
In maintenance mode, setup uses the same Options dialog as in inital install mode. The dialog
will be displayed with the installed components/options checked, and the uninstalled
components/options unchecked. The bottom of the dialog will contain a ‘Reinstall’ button to
allow reinstallation of already installed components. As soon as any check boxes are changed, the
‘Reinstall’ button becomes a ‘Continue’ button (see below).

The user can perform the following functions in maintenance mode:


Install Check a box to install an option/component (the word ‘Install’ will display)
When Continue (‘Reinstall’ button changes to ‘Continue’ when a checkbox is checked)
is selected, the option/component will be installed
Remove: Uncheck a box to remove an option/component (the word ‘Remove’ will
display)
When Continue (‘Reinstall’ button changes to ‘Continue’ when a checkbox is
unchecked) is selected, the option/component will be removed. All files, icons, registry
keys will be removed.
Reinstall: Simply Click ‘Reinstall’ to Reinstall same components. Registry values will
be used, and user will not be asked for any information.
Remove All: Uncheck all boxes to remove all Internet Server options/components.

22
When Continue (‘Reinstall’ button changes to ‘Continue’ when a checkbox is
unchecked) is selected, all options/components will be removed and all files, directories,
and registry keys will be cleaned up.

When an installed option is selected in maintenance mode, the ‘Change Directory’ button is
disabled. The setup program does not allow changing the directory after installation.
When an installed publishing service is selected on the Publishing Services component window,
the ‘Change Directory’ button is disabled. To change the ‘home’ directory of an already installed
publishing service, the Internet Service Manager must be used.
When the target machine is changed, setup enters initial install mode, or maintenance mode, as
appropriate, for the specified machine.

When Continue is pressed on the Options dialog, the installation process continues as with initial
install mode. The required dialogs are displayed, and install progress is indicated with the
standard progress dialog.

When maintenance installation is completed, the standard Setup Completion dialogs are used
(see sections 3.13 and 3.14).

Appendix A Registry Keys for Internet


Services
Following is the list of registry items created for the services.
issue: need to finalize what default values will be, and which keys we need

A.1 Common

Microsoft Confidential 23
\registry\machine
SYSTEM
CurrentControlSet
Services
TcpSvcs
Parameters

//
// This is maximum size of the shared memory cache
//

MemoryCacheSize = REG_DWORD 512000

//
// This is the maximum number of outstanding listens
// to backlog. Each entry costs 1k of physical RAM
// and 16k of quota.
//

ListenBacklog = REG_DWORD 15

MimeMap

//
// MIME mappings are in the form of:
//
// <mime type>,<file extension>,<image file>,<gopher type>
//
// There must not white space between the commas
//
// Note: We really want a Multi-SZ here, but
// Chicago doesn't support it
//
// This list is used for both directory browsing
// *and* processing client HTTP Accept: headers
//

//
// Default mapping type uses "*" for the
// file extension
//
text/plain,*,/images/default.gif,1 =

application/wav,wav,/images/sound.gif,1 =
application/zip,zip,/images/binary.gif,1 =
application/rtf,rtf,/images/doc.gif,1 =
application/postscript,ps,/images/image.gif,1 =

24
application/msword,doc,/images/doc.gif,1 =

text/html,html,/images/doc.gif,1 =
text/html,htm,/images/doc.gif,1 =
text/plain,txt,/images/doc.gif,1 =

image/gif,gif,/images/image.gif,1 =
image/jpeg,jpeg,/images/image.gif,1 =
image/jpeg,jpg,/images/image.gif,1 =
image/tiff,tiff,/images/image.gif,1 =
image/tiff,tif,/images/image.gif,1 =

video/mpeg,mpeg,/images/video.gif,1 =
video/mpeg,mpg,/images/video.gif,1 =
video/avi,avi,/images/video.gif,1 =

audio/basic,au,/images/sound.gif,1 =

A.2 WWW Service

\registry\machine
SYSTEM
CurrentControlSet
Services
W3Svc

//
// These shouldn't need to be changed
//

DependOnGroup = REG_MULTI_SZ
DependOnService = REG_MULTI_SZ TCPIP
DisplayName = REG_SZ Microsoft World Wide Web Service
ErrorControl = REG_DWORD 0x1
ImagePath = REG_EXPAND_SZ
SystemRoot%\System32\tcpsvcs.exe
ObjectName = REG_SZ LocalSystem
Start = REG_DWORD 0x3
Type = REG_DWORD 0x20

//
// W3 parameters are kept under the parameters key
//

Parameters

AdminName =

Microsoft Confidential 25
AdminEmail =
ServerComment =

//
// Maximum number of simultaneous connections allowed
//

MaxConnections = REG_DWORD 0x00000014

//
// Location of the log file
//

LogFileDirectory = %SystemRoot%

//
// Operation of the log file
//
// No log file =0
// Log to File =1
// Log to SQL =2
//

LogType = REG_DWORD 1

//
// If type is Log to periodic file, the period can be:
//
// No period =0
// Daily =1
// Weekly =2
// Monthly =3
//

LogFilePeriod = REG_DWORD 3

//
// The maximum size of the log file (in bytes)
//

LogFileTruncateSize = REG_DWORD 5000000

//
// Values if logging to SQL are selected
//

LogSqlDataSource =
LogSqlTableName =

26
LogSqlUserName =
LogSqlPassword =

//
// Authentication control
//
// if only anonymous, then
// Ignore all authentication information and force
// users to the anonymous token
//
// if anonymous and Basic or NT then
// Authorize using Basic or NT (denies if bad
// username/password), force all others to the
// anonymous token
//
// if only Basic or NT then
// Basic or NT authentication is required,
// anonymous/unknown authentication is denied access
//
//
// Allow anonymous = 0x00000001
// Allow Basic = 0x00000002
// Allow NT = 0x00000004
//

Authorization = REG_DWORD 0x00000007

//
// The account anonymous connections are impersonated
// as and UNC connections are connected with. The password
// is stored as an LSA secret
//

AnonymousUserName = Guest

//
// IP Based security keys
//
// The first value is the network mask, the second value
// is the network number.
//
// The incoming IP address is "anded" with the mask, then
// compared to the network number. If the network number
// matches then the connection is accepted or rejected.
//

Deny IP List
//255.255.255.255 101.12.15.63 =

Microsoft Confidential 27
Grant IP List
//255.255.0.0 101.12.0.0 =

//
// Virtual Volumes
//
// The first value is the symbolic link for the physical
// directory specified by the second value.
//
// If an IP address is specified, then the root applies
// to the locally connected IP address (machine must
// be multi-homed). No space can be on either side of
// the comma.
//

Virtual Roots
/ = e:\webroot
// /Root1/ = d:\OtherRoot\
// /,127.0.0.1 = e:\root2
// /unc = \\server\share\dir,UserName

//
// Everything below here is HTTP Server Specific
//

//
// If a get request is made on a directory and
// the default file exists in the directory,
// then auto load this file if "Load Default File"
// is set in the Dir Browse Control flags
//

Default Load File = REG_SZ Default.htm

//
// Browsing display control
//
// Show Date = 0x00000002
// Show Time = 0x00000004
// Show Size = 0x00000008
// Show Ext. = 0x00000010
// Display long date = 0x00000020
//
// Allow client to browse directories?
//
// Enabled = 0x80000000

28
//
// If this bit is set, then load the file specified
// by "Default Load File" if it is in a directory to
// be browsed
//
// Load Default File = 0x40000000
//

Dir Browse Control = REG_DWORD 0xC000001e

//
// If the request is a "GET", the object being retrieved
// has the same name (minus extension) as the WAIS data-
// base and there are search strings, spawn Waislook with
// the database (name of object minus extension). This
// provides compatibility with EMWAC's HTTP server.
//

CheckForWAISDB = REG_DWORD 1

//
// For tracing debug output
//
// Output to debugger= 0x40000000
// Output to logfile = 0x80000000
//

// The URL of the image to display next to directory


// entries when doing a directory listing. This is
// similar to the image specified in the MIME Mapping
// list
//

Directory Image = /images/dir.gif

//
// Installable filter dlls that can be used to implement
// custom authentication, encryption or signing services.
//
// The list is a comma seperated list of fully qualified
// paths to filter dlls. The server calls the dlls
// in the order they are specified in the list.
//

//Filter DLLs = c:\http\filter1.dll,c:\http\filter2.dll

ServerAsProxy = REG_DWORD 0

Microsoft Confidential 29
A.3 Gopher Service

\registry\machine
SYSTEM
CurrentControlSet
Services
GopherSvc

DependOnService = REG_MULTI_SZ TCPIP


DisplayName = REG_SZ Microsoft Gopher Service
ErrorControl = REG_DWORD 0x1
ImagePath = REG_EXPAND_SZ
%SystemRoot%\System32\tcpsvcs.exe
ObjectName = REG_SZ LocalSystem
Start = REG_DWORD 0x3
Type = REG_DWORD 0x20

//
// Gopher parameters are kept under the parameters key
//

Parameters

Virtual Roots
/ = REG_SZ c:\internet\gophroot
//samples = REG_SZ c:\internet\gophroot\samples

//
// Security related parameters
//
SecurityOn = REG_DWORD 1
AllowAnonymous = REG_DWORD 1
LogAnonymous = REG_DWORD 1
LogNonAnonymous = REG_DWORD 1
AnonymousUserName = REG_SZ Guest

//
// Administrative Information
//
AdminName = REG_SZ
AdminEmail = REG_SZ
Site = REG_SZ
Organization = REG_SZ
Location = REG_SZ
Language = REG_SZ En_US

30
Geography = REG_SZ

//
// Specifies when to timeout connection (in seconds)
//

ConnectionTimeout = REG_DWORD 900

//
// Allow client to browse directories?
//
// Enabled = 0x80000000
//
// If this bit is set, then load the file specified
// by "Default Load File" if it is in a directory to
// be browsed
//
// Load Default File = 0x40000000
//

//
// Maximum number of simultaneous connections allowed
//

MaxConnections = REG_DWORD 0x00000014

//
// Log Configuration for Gopher Service
// Size is set to 4 MegaBytes
//

LogType = REG_DWORD 2
LogFileDirectory = REG_EXPAND_SZ
%SystemRoot%\System32
LogFileTruncateSize = REG_DWORD 4000000000
LogFilePeriod = REG_DWORD 1
LogSqlDataSource = REG_SZ
LogSqlTableName = REG_SZ
LogSqlUserName = REG_SZ
LogSqlPassword = REG_SZ

//
// Path name specifies location of the SNMP MIB DLL
//
Pathname = REG_EXPAND_SZ %systemroot%\system32

//
// Specifies the Extension Agent registry entry under SNMP service

Microsoft Confidential 31
//

\registry\machine
SYSTEM
CurrentControlSet
Services
SNMP
Parameters
ExtensionAgents
GOPHERMIB = REG_SZ
SYSTEM\CurrentControlSet\Services\GopherSvc\Parameters

A.4 FTP Service


issue: missing old FTP parameters such as welcome msg. etc....

\registry\machine
SYSTEM
CurrentControlSet
Services
FtpSvc

DependOnService = REG_MULTI_SZ TCPIP


DisplayName = REG_SZ Microsoft FTP Service
ErrorControl = REG_DWORD 0x1
ImagePath = REG_EXPAND_SZ
%SystemRoot%\System32\tcpsvcs.exe
ObjectName = REG_SZ LocalSystem
Start = REG_DWORD 0x3
Type = REG_DWORD 0x20

//
// Gopher parameters are kept under the parameters key
//

Parameters

Virtual Roots
/ = REG_SZ c:\ftproot

//
// Security related parameters
//
SecurityOn = REG_DWORD 1
AllowAnonymous = REG_DWORD 1
LogAnonymous = REG_DWORD 0

32
LogNonAnonymous = REG_DWORD 0
AnonymousUserName = REG_SZ Guest

//
// Specifies when to timeout connection (in seconds)
//

ConnectionTimeout = REG_DWORD 900

//
// Maximum number of simultaneous connections allowed
//

MaxConnections = REG_DWORD 0x00000014

//
// Access Masks
//
ReadAccessMask = REG_DWORD 0x4
WriteAccessMask = REG_DWORD 0x0

//
// Log Configuration for ftp
// Size is set to 4 MegaBytes
//

LogType = REG_DWORD 1
LogFileDirectory = REG_EXPAND_SZ %SystemRoot
%\System32
LogFileTruncateSize = REG_DWORD 4000000000
LogFilePeriod = REG_DWORD 1
LogSqlDataSource = REG_SZ
LogSqlTableName = REG_SZ
LogSqlUserName = REG_SZ
LogSqlPassword = REG_SZ

//
// Path name specifies location of the SNMP MIB DLL
//
Pathname = REG_EXPAND_SZ %systemroot%\system32

Microsoft Confidential 33