Minimum Services for IIS

---

Microsoft Corporation

April 2, 1997

Want a pared-down, lean Web server? Take a few moments to go into your Control Panel, then Services, and discover the Windows NT services that can be safely switched over to a manual status (or perhaps even disabled) and continue to allow Microsoft Internet Information Server (IIS) to run.

The list below outlines the minimum services you'll need to successfully run IIS version 3.0. Please note that the requirements below are for IIS. Your particular configuration, especially in an intranet, may change some of the parameters (e.g., you may require WINS and DHCP in some intranets).

Required:

• Event Log
• License Logging Service
• Windows NT LM Security Support Provider
• Remote Procedure Call (RPC) Service
• Windows NT Server or Windows NT Workstation
• World Wide Web Publishing Service

May Be Required:

• FTP Publishing Service (required if customer is using FTP Service)
• Gopher Publishing Service (required if it is a site with lots of Gopher information)
• Plug & Play (recommended, but not required)
• RPC Locator (required if doing remote administration from machine)
• Server Service (can be stopped, but you'll need to start it if you wish to run User Manager)
• Telephony Service (required if access is via dialup)
• Workstation (Optional; important if you have UNC virtual roots)

The three noted below shouldn't be required unless the customer wants to use the "Find All Servers" option in Internet Service Manager (ISM).

• NetBIOS Interface
• NWLink NetBIOS
• WINS Client (TCP/IP)

Not Required:

• Alerter
• ClipBook Server
• DHCP Client
• Messenger
• Net Logon
• Network DDE & Network DDE DSDM
• Network Monitor Agent
• Simple TCP/IP Services
• Spooler
• TCP/IP NetBIOS Helper
• UPS
• WINS Client (TCP/IP)
• Network Monitor Agent
• NWLink NetBIOS
• NWLink IPX/SPX Compatible Transport (not required unless you don't have TCP/IP or another transport)