I did network-admin work up to about 5 years ago in a small university deployment (a few dozen workstations), and we had the classical NFS+NIS setup that used t

I did network-admin work up to about 5 years ago in a small university deployment (a few dozen workstations), and we had the classical NFS+NIS setup that used to work more or less out of the box. Ubuntu itself was a nice distribution to administer, but even then a lot of the new X-kit and X-daemons that were developed to make single-user machines easier to run had flaws I had to work around. But more often that not it seems that solutions are integrated as core-components in Ubuntu which are obviously not sufficiently thought trough: When a service for administering user-accounts is brought in, I'd at least expect someone to ponder how it will integrate with the different sources of user-account data (local files, NIS/YP, LDAP, Microsoft-AD, nss-sql-something-?, ...), and "iterating over all users(groups" is definitely a no-go in any large deployment. Having to deploy this today would probably mean that I'd just disable that service, or replace it with a dummy, or re-code it in python, or ... but of course that would be one additional thing to "repair" in the default-install, and annoying to the sysadmin.