Microsoft Exchange Server 2007 is the industry's leading server for e-mail, calendaring and unified messaging. Exchange Server 2007 is the foundation for a dynamic and holistic unified communications...
Published May 11, 2009
Version 1.0
Blog Post
Matt has stated concisely and dispassionately what I apparently could not and get by the moderator...
There are too many comments from folks who think we need to learn arcane Powershell cmdlets for reasons OTHER than administrating our server. I don't need to understand the relationship between AD and Exchange, I don't need a more thorough understanding of how the system interoperates, what I need is a system that SENDS and RECEIVES email that I can administer in a way that is *not* more arcane than Exchange 5.0 was. I have supported at dozens of clients Exchange as far back as 5.0 and every iteration in between. Exchange 2007 has by far the most unwieldy mangled interface possible. While I don't miss the days of Exchange 5.0 x. addressing and tendency to hump the bunk on the priv.edb, everything I needed to do was available in an intuitive format. This is missing from Exchange 2007.
Nobody is arguing for either or. I think Powershell scripting is a great Exchange feature. It is not, however, a substitute for a full powered GUI for ease of administration.
I would have appreciated they spend more time creating an in-place upgrade path for Exchange (embarrassing that you cannot upgrade in place - simply embarrassing) or how about an exmerge that handles unicode PST files and isn't having to try and piecemeal a mailbox import/export/restore in 2GB chunks?
Read around the web - alot of folks are very displeased with the band-aid GUI Exchange 2007 has. I stopped updating clients to 2007 after the second one was as miserable as the first.
When people say they "hate" the powershell, what they hate is that they have no way to do tasks they used to be able to do without it. Why can I not see mailbox sizes in the GUI? That is RIDICULOUS.
Powershell - should be an add on. The full functioning GUI should not be.
There are too many comments from folks who think we need to learn arcane Powershell cmdlets for reasons OTHER than administrating our server. I don't need to understand the relationship between AD and Exchange, I don't need a more thorough understanding of how the system interoperates, what I need is a system that SENDS and RECEIVES email that I can administer in a way that is *not* more arcane than Exchange 5.0 was. I have supported at dozens of clients Exchange as far back as 5.0 and every iteration in between. Exchange 2007 has by far the most unwieldy mangled interface possible. While I don't miss the days of Exchange 5.0 x. addressing and tendency to hump the bunk on the priv.edb, everything I needed to do was available in an intuitive format. This is missing from Exchange 2007.
Nobody is arguing for either or. I think Powershell scripting is a great Exchange feature. It is not, however, a substitute for a full powered GUI for ease of administration.
I would have appreciated they spend more time creating an in-place upgrade path for Exchange (embarrassing that you cannot upgrade in place - simply embarrassing) or how about an exmerge that handles unicode PST files and isn't having to try and piecemeal a mailbox import/export/restore in 2GB chunks?
Read around the web - alot of folks are very displeased with the band-aid GUI Exchange 2007 has. I stopped updating clients to 2007 after the second one was as miserable as the first.
When people say they "hate" the powershell, what they hate is that they have no way to do tasks they used to be able to do without it. Why can I not see mailbox sizes in the GUI? That is RIDICULOUS.
Powershell - should be an add on. The full functioning GUI should not be.