Disable Windows Server 2003 services that are not required for a
dedicated Web server. To do this, follow these steps:
Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.
Under Computer Management (Local), expand
Services and Applications, and then click Services.
In the Status column, each service that is running is labeled "Started." The following services
are not required on a dedicated Web server:
Alerter
ClipBook
Computer Browser
DHCP Client
DHCP Server
Fax Service
File Replication
INfrared Monitor
Internet Connection Sharing
Messenger
NetMeeting Remote Desktop Sharing
Network DDE
Network DDE DSDM
NWLink NetBIOS
NWLink IPX/SPX
Print Spooler
TCP/IP NetBIOS Helper Service
Telephony
Telnet
Uninterruptible Power Supply
Note the services that depend on each service that
you want to disable. To do this, follow these steps:
Double-click the service that you want to disable.
Click the Dependencies tab.
In the This service depends on the following
system components list, note the services that this service depends on.
In the The following system components depend
on this service list, note the services that cannot start
without this service.
Click OK.
One at a time, disable each service that you have selected. To do this, follow
these steps:
Right-click the service that you want to disable, and
then click Properties.
In the Startup type list, click Disabled.
If you want to stop the service immediately, click Stop. If the Stop Other Services dialog box appears, note the other dependent services that
will also stop, and then click Yes.
Click OK.
Repeat step 4 to disable the other nonessential services.
Notes
Test the Web server for correct operation after you
disable each service to make sure that you did not disable a service you want to continue to use.
If the Internet Information Services (IIS) server is a member of a Windows Server 2003 domain,
you must have the TCP/IP helper service on your system to correctly apply Group Policy to the
computer.
When you disable the DHCP client, the DHCP client stops dynamic DNS registration. This disables DNS dynamic update protocol and requires manual DNS records to be added for this client in the DNS server.
Run the IIS 6.0 process pageable
code in working memory. To do this, follow these steps:
In Windows Explorer, right-click My Network Places, and then click Properties.
Right-click the Local Area Connection that you want to optimize, and then click Properties.
In the This connection uses the following
items list, click (but do not clear its check box) File and
Printer Sharing for Microsoft Networks, and then click Properties.
Click Maximum data throughput for network
applications, click OK, and then click Close.
Enable CPU monitoring to monitor and to automatically shut down
worker processes that consume large amounts of CPU time. To enable CPU
monitoring, follow these steps:
In Internet Information Services (IIS) Manager, expand the local computer, expand the
Application Pools folder, right-click the application pool that you want to enable CPU accounting on, and then click
Properties.
Click the Performance tab, and then click to select
the Enable CPU monitoring check box.
In the Maximum CPU use box, click the up
and down arrows to set the maximum percentage of the CPU that you want the application pool to use.
If the application pool uses more than the designated maximum, IIS
generates an error message in the Windows Events log.
In the Refresh CPU usage numbers (in
minutes) box, click the up and down arrows to set the refresh rate.
In the Action performed when CPU usage exceeds
maximum CPU use box, click the appropriate action for the
designated application pool:
Click No Action to have IIS generate
an error in the Windows Events Log when the designated application pool reaches
the maximum CPU usage.
Click Shutdown to shut down the
application pool. Click Shutdown to stop the
problematic application by terminating its host worker process.
Click Apply, and then click
OK.
For more information about CPU Monitoring, see the "Enabling CPU Monitoring"
topic in the Internet
Information Services 6.0 Administrators Guide.
Limit the number of connections available to individual Web
sites. To do this, follow these steps:
Start Internet Services Manager.
Expand server
name, where server name is
the name of the Web server.
Right-click the Web site that you want to limit, and then click Properties.
Click the Performance tab, and then click Connections limited to.
In the Connections limited to box, type
the number of connections that you want to allow.
Note Each connected client uses approximately four concurrent
connections. For example, a connection limit of 200 allows approximately
50 users to access the Web site.
Click OK, and then quit Internet Services Manager.