PingBack from http://www.datapoohbah.com/tech/?p=306
PingBack from http://blogs.msexchange.org/walther/2006/03/31/exchange-12-ctp-builds-in-your-production-environment/
This seems like a no-brainer to me... I wouldn't dream of putting an early beta or preview into major production!
As some of you maybe aware, the March edition of TechNet Plus included a CTP version of E12. I just want...
Today this list is longer, since I hadn't the time to post it last week. Sorry...
Exchange on NAS:...
"no-brainer", huh?
I'm about to deploy a new Exchange installation, and I can either choose 32-bit Windows 2003 and the old Exchange version (and upgrade both as "12" arrives), or I can install 64-bit Windows and 64-bit "12" beta and only upgrade Exchange when the release arrive.
So... Just how much does the Active Directory changes affect a small organisation with no prior Exchange installations?
--
Rune
Rune,
The right answer is definitely - choose 32 bit Windows with Exchange 2003 to run in production. Unless you are on TAP program for Exchange 12, we do not have really a way of supporting you.
I'm not necessarily looking for support, I'd just like to know that installing "12" won't destroy my Active Directory beyond all repair.
It would be very strange if even beta 1 won't run on a small&simple network involving one Win2k active directory server. (we have 15 users btw -- can't get any smaller than that)
At home I dual-boot between 32-bit and 64-bit Win2003 Server. I'm not at all convinced that upgrading a Exchange 2003 Server is going to be a milk-run. (and I do hairy stuff like sharing the same user profile between the two) A little active directory repair seems less daunting.
I'm almost tempted to berate you guys for not adding some 64-bit support into Exchange 2003. You've made this (how to be polite?) an "interesting" choice... ;)
Besides, the little 32-bit -> 64-bit Win2003 Server "upgrade" would set us back a few quids, now wouldn't it?
--
Rune
PingBack from http://blogs.msexchange.org/dalby/2006/04/05/dont-put-e12-into-a-production-environment/