That seems insane. It is like asking someone to draw a map, without being able to actually visit the place that needs to be mapped.
Funny that you say that. As we all know Columbus discovered America (leaving earlier civilzations out of it for the moment).
Only he didn't. He thought he was in India. Later he thougt that he had discovered a new group of Islands. Who did first prove that an entire new continent was found (and gave his name to it)? Amerigo Vepucci. Did he physically visit the continent he 'discovered'? Yes! But only after he had deduced from information of others that there must be a new continent.
So you new role (and adapting to a new role is hard, so think about it) is not to go on a bold new expedition but to sift through the information you request from the different teams and build a global picture from that.
Also a concern for me is: you talk only about network, virtualization, databases etc. While an EA is also much involved in the design of the application landscape, data architecture of large projects, reporting infrastructure etc.
So, if you take the leap, let go of the low level control and widen you horizon.