In an IT position without administrative rights, you don't have authority. Responsibility without authority = run away screaming.
I'm not sure you completely understand the point behind an architecture role. The responsibilities are *different*. They're not tactical operations in nature. The role is strategic; thinking months if not years in advance, asking questions about something that no one else has thought about, seeing big-picture things (50,000-ft view) versus close-in things (1000-ft view).
Folks who can successfully make that transition get to enjoy the benefits of being an architect. One of the key benefits, at least in my mind: no more on-call. :-) I've done my decade and a half of network on-call and it wore me the eff out. I'm glad I don't have to do it any more. I'm still and individual contributor (vs being a manager) and still highly technical in nature. I just don't "conf t" in production any longer. I do in the lab, but not where it counts.
Folks who *can't* make that transition in thought will stay in an operations role for the rest of their careers. And that may be perfectly acceptable to them; there's nothing wrong with it at all. It's just a different set of skills.
Don't be so quick to shun your architects. They might actually know more than you do. ;-)