A Sysadmin for Sysadmins?

crazyharry asks: "I have recently been hired to be a system administrator to a bunch of system administrators. Aside from my personal experience, which is probably biased, I would like to know from the disproportionately large number of IT people here: if you, as a system administrator, were forced to have a system administrator, what would you expect of that role? How would you want your business machines (not the ones you admin, but your daily use machines) managed, if they were not up to this point? This is a mixed environment (Windows, Mac, and Linux/Unix), so feel free to assume I've already heard the 'leave me the FSCK alone' comments. What other issues are probably going to crop up, if you have been in a similar situation?"

Comments

I'm a sysadmin who has a sysadmin

[Theatetus]

This seems to be the opposite of what other people say, but as a sysadmin who has a sysadmin I can say I like mine because I never have to apply my sysadmin-ing to our internal computers. I don't expect to be given Special Powers just because I've got root somewhere else, but I expect the same quality of service I deliver to our external clients (well, OK, I expect better than that).

I'm not root on our local Linux boxes; I'm not a domain admin on our local Windows domain (though I think I'm a schema admin for some reason) -- I don't want to be. I want the local resources I need to connect out and do my work, and I don't want to have to think about them.

YMMV.