Of course if there is anything else that you need help with, you can always post in the forums here, there is pretty much always someone to help out - plus you get access to some of the best Exchange people outside Microsoft.
Back again today. :) We were installing a new firewall yesterday so I had to assist with that. I have been reading over the links you posted...great information...the glossary is excellent. I am working on memorizing that entire thing.
I will be outlining a structure and plan this weekend and next week a little bit. I hope to have some progress by the end of next week. I will definitely keep you posted and return here as questions arise...
Posts: 1917
Joined: 12.Apr.2005
From: London
Status: offline
Hey Chris, glad you like it. I have posted the events that we went through on my blog (I cut out some of the stuff we went through, but I hope that you enjoy the read).
as I said post back anytime, there are lots of people here that are more than happy to help.
I know it's an year old subject, but i had the same problem yesterday and i managed to find what was wrong. Now i want to share with others so they can easily fix what it is to be fixed.
So, the problem is that the domain was created as child of another forest. But there was not another forest because i installed a virtual machine. I deleted the old virtual machine and i installed a new one, this time i chose "domain in new forest". After the installation, i tried to run setup of exchange 2003, i got to the point where you must run forestprep and.. it worked.
I read on earlier posts that cwallace received the domain as it is from the previous network administrator. Maybe he made that domain as part of a forest... but there wasn't a forest. Exchange 2003 seems to make difference between domain in a new forest and child domain in a forest.