neiroatopelcc :
what organization is that?
ps. some parts of ms world is considerably harder to manage than linux - for instance default user profiles or 3rd party software written without multiuser systems in mind.
ps. some parts of ms world is considerably harder to manage than linux - for instance default user profiles or 3rd party software written without multiuser systems in mind.
This is faulty logic. A third party app that isn't multiuser friendly would act the same on both an NT system and on a Unix system. Those aren't used anymore, not even the archaic financial / banking systems are like that.
"Management" is patching / security contexts / user accounts / access control to resources and system policies. AD makes life in that regard much easier. You can even deploy ADFS and your productivity portals would be tied into your domain credentials, this enables single login. You then have your users login using either the older UN/PW combo or some PKI-based token / smart-card system. When your managing thousands of client systems and a few hundred servers this becomes very important, else you spend 100% of your time fixing things and become reactive vs proactive. Centralized management is a requirement, not an option for enterprise grade systems.
We once tried to get our Unix / Linux systems to authenticate to the domain as some hair brained scheme for universal access control. Didn't work too well and was very unpredictable. The default instructions that are posted all over the intarwebz doesn't work on a DISA STIG'd enclave. The Unix / Linux system simply doesn't know how to negotiate with the AD servers, and of course the developers doing Linux / Unix stuff have absolutely ~zero~ desire to add this functionality. We eventually got the Solaris 10 systems to work pretty well, Sun (Oracle now *barf*) has pretty good documentation on how to make it work in an enterprise including how to configure the Unix Services for Windows part and which group ID's to map. The linux stuff was not so good.