Top 10 Indicators for a Rough Day as a Sysarch

I love top 10 lists, and I owe you something technical. Since the buck typically stops with the systems architects (i.e. " I can't figure it out. Ask the guy who designed it."), and people eventually feel entitled bypassing things like IT, the helpdesk, or the actual systems administrators, you get some of the best summaries of technological ignorance. It seems that when they can call the top sysarch on the phone, their brains turn off.

Anyways, here is my list:

10. A contractor delivers a .NET solution to deploy in your Linux infrastructure.
9. An engineer in QA calls and asks if Solaris is UNIX(tm).
8. A consultant for a vendor states that it's normal (and a requirement for their software to work) to allow root logins via ssh on all systems.
7. A contractor escalates the fact that typing ssh is too hard to the executive team.
6. A developer for the same contractor escalates not being able to access the Internet using IE from a production Windows server to the executive team.
5. Your COO calls you on your cell and says that the 'dir' command does not work on the Solaris machine he found the password to.
4. You log into a firewall system and discover the 'alias' command returns aliases to ssh logins to key systems with the password given on the command line.
3. You discover someone checked the root passwords for the systems they know about into CVS.
2. Telnetting to the main production router from home presents you with a "login: _" prompt.
1. An engineer from operations logs in as root and types the command 'hostname help' on your main database server.

I can't believe that just about everything on this list has happened to me in the past year. Titles, system types, and so on switched to protect the guilty.