We're wrapping up our Beta of Exchange 2007 SP1 (to be released through TechNet plus this April), and as always we wanted to discuss it publicly here first. We are targeting final release with Long...
Updated Jul 01, 2019
Version 2.0
Blog Post
I agree with the others: Power shell is great for large organizations with highly specialized IT positions, but leaving simple, common things out of the GUI is just lazy, cheap programming. Are we regresssing to DOS again here?
I attended the launch event in Seattle and watched the poor dude trying to demo the 'amazing' features of Exchange Powershell fail over and over due to syntax error and typos. "See how great this is? Oops. Uh. Let me try that again."
Small environment admins don't want to type 200 character commands into a CLI to accomplish what can be done with three mouse clicks. A flashy name like "Powershell" doesn't make it any better.
Get off your butts and finish the freaking GUI. It's called "WINDOWS" after all. If we wanted a cryptic, arcane, tedious CLI we'd all be using *nix.
I attended the launch event in Seattle and watched the poor dude trying to demo the 'amazing' features of Exchange Powershell fail over and over due to syntax error and typos. "See how great this is? Oops. Uh. Let me try that again."
Small environment admins don't want to type 200 character commands into a CLI to accomplish what can be done with three mouse clicks. A flashy name like "Powershell" doesn't make it any better.
Get off your butts and finish the freaking GUI. It's called "WINDOWS" after all. If we wanted a cryptic, arcane, tedious CLI we'd all be using *nix.