RabbieBurns (19th July 2009)
here, however if you have never used Exchange before I would then strongly recommend starting out on Exchange 2003 on Server 2003. Alot of organisations use Exchange 2003, infact some large organisations are still using Exchange 5.5 & 2000 (some NHS trusts for example).
Exchange 2007 brings in separate roles and 2010 brings in more enhancements, I believe that since you have had no exposure to Exchange, you may run into more complications hindering you rather than helping you.
Unfortunately I dont have a technet subscription or the like, and cant find an evaluation of 2003 Exchange.
All my Windows installs are virtual already, so Im not sure how well a virtual exchange would run within a virtual windows.
But, it seems I have found the problem. The verison of the trial I was using was just the 2007 not the 2007 SP1 version, so Ive found the SP1 trial and its actually letting me install.
Thanks for all the help and suggestions on this thread, and if anyone has any suggestions where I could get 2003 exchange to try, without being naughty, would be appreciated.
well whatever the install process did it has killed not only the VM but also the host
Can ping it, but thats about it. Ahah maybe its a sign
E2K7 needs a lot of RAM (tried it with a 1GB VM once and it was dreadful). For me:
E2K3 is OK in a 512MB W2K3 VM.
E2K7 is OK in a 1.5GB W2K3 R2 X64 VM.
I think I can see what Ken is getting at .. E2K3 does more in the GUI or ADUC, whereas with E2K7 (although it has an easier GUI) I inevitably end up typing 400+ character lines into powershell...
..but, I wouldn't spend too much time on E2K3 if you intend to get E2K7 coz you'll have to learn how to do quite a lot of things all over again.
There are currently 1 users browsing this thread. (0 members and 1 guests)