Re: Server admin/service account - too many users
- From: "AllenM" <allen.miyake@xxxxxxxxx>
- Date: Mon, 13 Feb 2006 10:57:35 -0800
There is a best practice for you. You never use the "administrator" account
to run services. For programs such as SQL and Veritas or any other program
that requires an Administrative account to run a service, you need to
created "Admin" accounts and given these accounts the "Logon as a service"
rights.
"gstar" <gary.brett@xxxxxxxxx> wrote in message
news:1139855957.089262.255270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have a problem which needs resolving fairly quickly.. We have a
Win2003 AD server and 5 Win2000 member servers performing various
duties on the LAN. On the Win2000 servers I have an account which
allows the SQL developers to log on locally & remotely to perform tasks
but need to rescind this now due to some data delteions form SQL &
files overwrites in IIS! The developers have dev servers to work from
but I think there may have been a mix up & they copied the dev
directory to live casuing downtime to the website.
Is their a best practice for me, as I know if I simply change the
account password, services will not run such as SQL2000 , Veritas
backup exec server and their backup agents to name a few. I basically
want these servers locked down for anyone except the IT Director &
myself as we cannot afford to have data deleted from both drives & SQL!
Any advice would be much appreciated.
G
.
- Follow-Ups:
- References:
- Server admin/service account - too many users
- From: gstar
- Server admin/service account - too many users
- Prev by Date: Re: Print Server Domain Change NT4 to 2003
- Next by Date: SMS Package Dependancy on W2K3 Server Type
- Previous by thread: Server admin/service account - too many users
- Next by thread: Re: Server admin/service account - too many users
- Index(es):
Relevant Pages
|