|
|
|
|
|
by kriro
2763 days ago
|
|
"""I use Linux now, but I think to be used in Enterprises or public service it lacks features as good central maintainability (where Microsoft really shines)""" I think in a Linux only environment maintainability is pretty good. Especially for centralized software rollouts and updates (and security fixes) I prefer Linux over Windows. There's virtualization and software packaging solutions in Windows land but from my experience the things that work best are usually from third parties, cost quite a bit and don't work all that great in many edge cases. For user management in Linuxland, Kerberos for authentication and LDAP for authorization works pretty well. But AD in Windowsland is very good. As you said, the problems start once you enter a mixed environment (which is pretty much always the case). I'm not sure if the blame should be put on Windowsland or Linuxland in mixed environments but it's usually put on Linux. |
|
Previously I had an AD domain running (to integrate Win7 machines) via Samba4. When I switched the Win7 machines to Linux, I found usage awkward (performance, strange user names such as name@domain.local, slow shares). I switched to local users and sshfs instead of shares. This would make for a more convoluted onboarding of new users (which is not a use case for me). However I'd be interested how this would be solved in an Enterprise environment.