This post is about how office space is allocated at Microsoft, and it has nothing to do with the movie of the same name. You will also be hard pressed to find something really useful Exchange-rela...
Updated Jul 01, 2019
Version 2.0
Blog Post
This isn't the right forum for some of these comments but as there isn't a more appropriate one here are some more in the same light.
Unfortunately I have to agree with Brian G and others. I was all fired up about upgrading from Exchange 2003 to Exchange 2007, being an MS supporter ... then I went on the Exchange 2007 training course. I came out of it thinking "There is no way my company is going Exchange Server 2007".
Public Folder support seems to have hit a nerve with many people, and even though SP1 improved things greatly, it still isn't back on par with Exchange 2003. I didn't want to focus on PF with this post as it is a minor concern when compared to others, but even the new SP1 GUI (seperate from the Exchange GUI mind you!) doesn't allow permission changes. What the .. ?
Speaking of permision changes, this is one of the top 5 functions an Exchange Admin does in my org on Mailboxes. Need to give someone full access to a shared/generic mailbox, or assign send-as permissions?Such a simple process under ADUC with Exchange 2003. So simple it is delegated out to AD admins across the org who look after users in each department. How do you do it in Exchange 2007? command line! (yeah, right. I'm going to give that to a hundred admins to play with).
The powershell has been given to us with a great deal of cheering from your team. I agree, it does empower some admins. People like me, who write scripts for everything and have a chance of understanding it. Using it for the whole admin of Exchange? Make everyone who NEEDS to do simple Exchange admin task use it? Are you crazy? Nearly everything in the shell should be possible via the GUI.
When you compare that to the things that were in ADUC interface and the Exchange 2003 Admin GUI everything seems to be a step backwards.
I read on the Exchange 2007 that the install process is much simplified. If that is true then everything every other aspect of managing Exchange seems to have gotten magnitues of order more complex. In Exchange 2003, navigate in the gui or ADUC and see an answer. In Exchange 2007, not possible via the gui and attributes not visible in ADUC, so run a shell command requiring 10 parameters and not be able to see the results be the simeple view cuts column data after 10 characters. [of course that isn't a problem, just use -format list and be overwelmed by the pages of irrelevant data you weren't interested in].
Guys, I'm sure Exchange 2007 is a great product. The engine is probably tuned to perfection. But listen to the people here; The management of Exchange is a HUGE step backwards for most people. It sure made us halt upgrading.
John
Unfortunately I have to agree with Brian G and others. I was all fired up about upgrading from Exchange 2003 to Exchange 2007, being an MS supporter ... then I went on the Exchange 2007 training course. I came out of it thinking "There is no way my company is going Exchange Server 2007".
Public Folder support seems to have hit a nerve with many people, and even though SP1 improved things greatly, it still isn't back on par with Exchange 2003. I didn't want to focus on PF with this post as it is a minor concern when compared to others, but even the new SP1 GUI (seperate from the Exchange GUI mind you!) doesn't allow permission changes. What the .. ?
Speaking of permision changes, this is one of the top 5 functions an Exchange Admin does in my org on Mailboxes. Need to give someone full access to a shared/generic mailbox, or assign send-as permissions?Such a simple process under ADUC with Exchange 2003. So simple it is delegated out to AD admins across the org who look after users in each department. How do you do it in Exchange 2007? command line! (yeah, right. I'm going to give that to a hundred admins to play with).
The powershell has been given to us with a great deal of cheering from your team. I agree, it does empower some admins. People like me, who write scripts for everything and have a chance of understanding it. Using it for the whole admin of Exchange? Make everyone who NEEDS to do simple Exchange admin task use it? Are you crazy? Nearly everything in the shell should be possible via the GUI.
When you compare that to the things that were in ADUC interface and the Exchange 2003 Admin GUI everything seems to be a step backwards.
I read on the Exchange 2007 that the install process is much simplified. If that is true then everything every other aspect of managing Exchange seems to have gotten magnitues of order more complex. In Exchange 2003, navigate in the gui or ADUC and see an answer. In Exchange 2007, not possible via the gui and attributes not visible in ADUC, so run a shell command requiring 10 parameters and not be able to see the results be the simeple view cuts column data after 10 characters. [of course that isn't a problem, just use -format list and be overwelmed by the pages of irrelevant data you weren't interested in].
Guys, I'm sure Exchange 2007 is a great product. The engine is probably tuned to perfection. But listen to the people here; The management of Exchange is a HUGE step backwards for most people. It sure made us halt upgrading.
John