When I set up Exchange 2010 I wasn't sure about moving back to command line management from a fully functional GUI. But I gave it a chance. I learned it as best I could, but I still have to use my cheat sheet of commands. And now that users on office 2010 are requesting additions, changes, tweaks, and other modifications on a regular basis I really miss having the GUI from 2003. Why did Microsoft take away the power of the gui and force us to use powershell? Why not give both and let the admins choose? If you only admin an exchange server 1 hour a day or less, powershell is probably not a welcome change. If exchange is your whole job, then it may be nice. It feels like your being forced to drive a dump truck rather than a pickup truck. If you are moving a large load, it may seem nice, but if you are a small company IT admin and need it to fit into small spaces and take tight turns, you are now out of luck. I've seen tons of similar complaints starting years ago. But it seems we get dismissed easily, since very little has been done to add functionality to the GUI by Microsoft thus far. /end rant I feel better now.

FWIW, I completely agree. In the same vein I also miss Exmerge. -Peter

Do you use Powershell for anything other than Exchange administration?[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Which changes are you trying to do that can't be done in the Exchange Management Console? I know PS is a pain for routine admin stuff, but the EMC can do most things you'd want to do every day. OTOH, PS is great for reports (sadly lacking in the GUI versions), and for piping one command into another. But yes, with the power and versatility comes a steep learning curve.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m

I miss the functionality of being able to code the mailbox into creation. Powershell for Exchange sucks. It doesn't have the inclusive functionality of regular powershell and if you want to remote command and run script - well - nothing is a recognized cmdlet, function or script!