Disabling Services
From: Bob Johnson (Bob_at_nomailforme.com)
Date: 04/22/04
- Next message: Marin Marinov: "Re: Disabling Services"
- Previous message: Kristofer Gafvert: "Re: MLS App wont run on TS"
- Next in thread: Marin Marinov: "Re: Disabling Services"
- Reply: Marin Marinov: "Re: Disabling Services"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 21 Apr 2004 16:00:15 -0600
Hello,
I'm new to the Microsoft Server world and am a little unsure of myself while
bumbling around in the management of the services.
I am trying to lock down our Windows 2000 Servers and would like to know
what services are a good idea to disable. We do not run a domain currently
as we are primarily a Novell shop and the user have Netware servers as their
file servers. This server is a stand-alone terminal server.
Application Management -- This looks as if it only interfaces with a domain
and could be disabled in our environment. Is that correct?
Boot Information Negotiation Layer -- This looks like a domain service also.
We use workstation imaging from a third party and do not use this service.
Computer Browser -- Is this necessary?
Distributed File System -- What would be the consequence of disabling this
service?
Distributed Transaction Coordinator
File Replication --- This sounds like an nice service but we do not run a
domain. Should it be disabled?
FTP Publishing?
IIS Admin?
Messenger?
Remote Access Connection Manager?
Remote Procedure Call?
Remote Registry Service?
Removable Storage?
RunAs Service?
SMTP?
SNMP?
Telephony?
WMI?
WMI Driver Extensions?
Wireless Configuration?
World Wide Web Publishing Service?
- Next message: Marin Marinov: "Re: Disabling Services"
- Previous message: Kristofer Gafvert: "Re: MLS App wont run on TS"
- Next in thread: Marin Marinov: "Re: Disabling Services"
- Reply: Marin Marinov: "Re: Disabling Services"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|