clarification on "service accounts"

My organization is calling active directory accounts they use to connect to some network functions as a service account.

I am trying to tell them that service accounts are inherently not active directory accounts but only reside on the local machine in a classical windows setup.
am I correct?
jamesmetcalf74Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steve WhitcherSystems AdministratorCommented:
No, an AD account could be used as a service account.  In recent windows versions, there are even managed service accounts, which MUST be ad accounts.
0
McKnifeCommented:
"in a classical windows setup" - funny term - what do you think that means? :)
Imagine: on a domain joined machine (a "classical" win7/server 2008 r2), if you configure a service to use the system account - is that an active directory account you are using, or not? It is! The machine is domain joined and the system account (aka computer account aka computername$) is an active directory object and can even act across the network.

With the aforementioned managed service accounts, microsoft tried to promote the concept even further so that some admins might finally leave their own strong domain admin accounts out of this dangereous service business...
0
jamesmetcalf74Author Commented:
So What Kind Of ACCOUNT Is NORMALLY Used As A Service ACCount if ad users can be used as a service account.   What's the other method
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Will SzymkowskiSenior Solution ArchitectCommented:
When you are using Services Accounts it is always a best practice to do the following...
- Create an OU specifically for Service Accounts (central location)
- Create a Service Account Name Prefix like SVC_ServiceName
- Make sure that Passwords for Service accounts cannot be changed
- Ensure that Service Accounts have a stronger password than Default domain policy (using FGPP/PSO 2008 and up)
- On the Service Accounts make sure that you set the logon computers only to the ones where the service account needs to be running

Also regarding Managed Service Accounts can also be used but from personal experience they are not a good solution to implement. They take a lot of time setting them up and you do not see much benefit. Also Service Accounts are a glorified computer object. As computer objects also have passwords but they are managed within Active Directory itself.

If you have followed the steps above then you will be in a good situation when managing/locating/securing Service Accounts

Will.
0
McKnifeCommented:
"What Kind Of ACCOUNT Is NORMALLY Used As A Service ACCount" - There's no "normally", we cannot use that term.

But most applications that install services use "local system" which is an active directory account on domain joined computers.
0
Steve WhitcherSystems AdministratorCommented:
The main advantages to Managed Service accounts are security related --
1) The account password is managed by AD and the computer the account is used on.  That means the password gets changed regularly, and no users, not even the admins, know the password or have it saved in a list somewhere.   (Setting an account to have a password never expire, like some admins did for old style service accts, is less than ideal.)
2) The MSA can't be used to log on to a computer interactively, even if you DID somehow know what the password for the account was.

The older type of MSA's, introduced in server 2008r2, were limited to being used on a single computer or server.  That did provide some additional security, in that the account can not be used anywhere but on that one machine.  Unfortunately, this also made them a little more of a hassle to use in some cases. Group Managed Service Accounts, introduced in Server 2012, can be used across multiple servers.

Here's a technet article on the new gMSA's, and an older blog post about the server 2008 style of MSA's.  There's a lot of good information in these:

https://technet.microsoft.com/en-us/library/hh831782.aspx

http://blogs.technet.com/b/askds/archive/2009/09/10/managed-service-accounts-understanding-implementing-best-practices-and-troubleshooting.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.