I recently (hopefully recently, my last post took two years to get published so I'm not sure when this one will go out, LOL) posted one of my typical light-hearted looks into life at Microsoft (it wa...
Updated Jul 01, 2019
Version 2.0
Blog Post
Honestly, I am going to stick with my Exchange 2003 servers (I have 48 of them) until all of this nonsense gets sorted out. All benefits of 64-bit computing aside, I have to throw out the baby with the bathwater to get Exchange 2007 rolled out in my enterprise. Not worth the expense, hardware-wise or labour-wise if you ask me.
my criticisms:
- crappy upgrade path (see above), I have complained ad nauseum about it so I will leave it at that.
- de-integration of ADUC. You had a wonderful thing going and then you change it. *meh*
- de-guification of major features. (see above)
It is almost like you intentionally obfuscated the administration of Exchange to foster and protect the jobs of the "Exchange administrator". Not that I am against a competent product managed by competent people, but our jobs are being crammed into ever-so-tighter schedules and I for one would like to see EASIER and QUICKER to use products rather than ones with some sort of "paradigm shift" to command-line interactivity.
With my bevy of Unix (and Linux) servers, I have an intrinsic LOVE of the command-line. That is the beauty and simplicity of Unix and Unix-like operating systems. Windows, however, is NOT Unix and is NOT a command-line operating system. It is a graphical user interface with a very large and complex engine running underneath. Windows users expect (and indeed sometimes REQUIRE) a GUI interface to interact with it. By shoehorning in all of this command-line interactivity, regardless of merit, you are needlessly complicating things for the people I am, in the end, going to have train to support it.
So, like I said...I'll be sticking with Exchange 2003 for now. Thank you very much.
my criticisms:
- crappy upgrade path (see above), I have complained ad nauseum about it so I will leave it at that.
- de-integration of ADUC. You had a wonderful thing going and then you change it. *meh*
- de-guification of major features. (see above)
It is almost like you intentionally obfuscated the administration of Exchange to foster and protect the jobs of the "Exchange administrator". Not that I am against a competent product managed by competent people, but our jobs are being crammed into ever-so-tighter schedules and I for one would like to see EASIER and QUICKER to use products rather than ones with some sort of "paradigm shift" to command-line interactivity.
With my bevy of Unix (and Linux) servers, I have an intrinsic LOVE of the command-line. That is the beauty and simplicity of Unix and Unix-like operating systems. Windows, however, is NOT Unix and is NOT a command-line operating system. It is a graphical user interface with a very large and complex engine running underneath. Windows users expect (and indeed sometimes REQUIRE) a GUI interface to interact with it. By shoehorning in all of this command-line interactivity, regardless of merit, you are needlessly complicating things for the people I am, in the end, going to have train to support it.
So, like I said...I'll be sticking with Exchange 2003 for now. Thank you very much.