Installing Exchange 2007 into an existing Small Business Server 2003 domain
My recent article on mexchange.org has started getting quite a bit of interest.
http://www.msexchange.org/tutorials/Installing-Exc...1.html
Especially regarding the issue of having a second DC in the SBS domain and the need for the Schema Master to reside on SBS.
A second domain controller can reside in an SBS domain. However, all the FSMO roles must remain on the SBS and SBS must be the root DC within the whole forest. In part one, I did move the Schema master to the E2007 server. However, this will be moved back in part 2.
I checked this article with the SBS tech support team and the Schema master role and the need to DCPromo are known issues.
In reality, this article is pretty theoretical as it is unlikely to ever be implemented in a production environment due to licensing. Just trying to get 2007 out there!
Technorati : exchange
Matt Fletcher Says:
March 21st, 2007 at 11:40 am
A FSMO role being moved off SBS! “..Let there be light…” in the guise of Part 2.
Seriously though, is registering the schmmgmt.dll part of the procedure to enable the FSMO role to be moved back?
Does removing the role fill up event viwer logs?
Cheers
Matt
Jeremy Says:
November 21st, 2007 at 3:01 pm
Has anyone actually implented Exh07 into a production SBS 2003 network? I’d be curious to know what issues you ran into.
Thanks,
Jeremy
Business Financing Guru Says:
March 1st, 2008 at 6:14 pm
Is implementing the Exchange2007 tool into Small Business Server domain really that necessary? We’re doing some equipment leasing and I’m not sure it’ll help for the temporary situation we’re in but what have you guys found? How long will it take?
chris dalby Says:
March 3rd, 2008 at 7:30 pm
Insalling Exchange 2007 into SBS 2003 is not needed unless you want to use the new features of Exchange 2007. Personally I wouldn’t bother. There will be a new release of SBS this year with Exchange 2007 included. Personally I’d hold out for that, otherwise SBS 2003 will work just fine.