A "service account" only needs rights to logon as a service and rights
to whatever resources the service needs access to, for example; shared
directories or printers...
Dave D
>>> [EMAIL PROTECTED] 01/28/03 01:08PM >>>
>>> [EMAIL PROTECTED] 01/28/03 01:08PM >>>
We need to come up with a service account to use in running services in the enterprise, but I have a situation where I�m going to need to give that account and password to developers so they can use it too, so obviously I don�t want to just stick it in Domain Admins and forget about it. Are there any white papers on what rights an account needs to function as a typical service account (obviously some applications/services will have different requirements, but there�s got to be a place to start?)
Brad Martin
Go Daddy Software, Inc.
480.505.8800 ext. 250
<<attachment: IMAGE.gif>>
