asked on How to transition from SBS 2003 to Windows 2008 Standard?
Hi,
I'm preparing to migrate from a Windows 2003 SBS with Exchange 2003 and SQL Server 2000 to a Windows 2008 Standard machine with Exchange 2010 Standard.
I'd like to keep the 2003 SBS machine up running SQL 2000 for a few months after transitioning the DC to the Windows 2008 box and Exchange 2003 to 2010. Is this possible? Will SBS 2003 allow me to move over to the Windows 2008 as a Domain Controller? What's the procedure to do so?
I'm preparing to migrate from a Windows 2003 SBS with Exchange 2003 and SQL Server 2000 to a Windows 2008 Standard machine with Exchange 2010 Standard.
I'd like to keep the 2003 SBS machine up running SQL 2000 for a few months after transitioning the DC to the Windows 2008 box and Exchange 2003 to 2010. Is this possible? Will SBS 2003 allow me to move over to the Windows 2008 as a Domain Controller? What's the procedure to do so?
SBSWindows Server 2008Exchange
Last Comment
Rob Williams
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
You can add as many DC's or member servers as you like to an SBS domain for as long as you like with no issues whatsoever.. That is a common misconception. What you cannot do is add another SBS to an existing SBS domain. If you do that, one or the other will start shutting itself down after 7 days. In a migration scenario there is a hotfix that will extend that to 21 days, but that is all.
If you transfer the FSMO roles to another server the same restrictions apply. The SBS will start shutting down after 7 days.
If you transfer the FSMO roles to another server the same restrictions apply. The SBS will start shutting down after 7 days.
If you are looking to transition out of SBS2003 due to simply outgrowing it's user limit, I recommend a Swing Migration. I performed my first with the documentation from: http://www.sbsmigration.com/.
It isn't free, but the peace of mind is amazing for your first swing. Jeff Middleton is a great guy, who knows his stuff.
It isn't free, but the peace of mind is amazing for your first swing. Jeff Middleton is a great guy, who knows his stuff.
ASKER
I've begun the migration. Working on Exchange now.
ASKER
There seems to be an issue with e-mails being transmitted between exchange 2003 and exchange 2010 during the coexisting period. On EX 2010, my queue to the 2003 instance is filling up. I see that Exchange 2003's virtual SMTP connector shows a bunch of connections from the 2010 server, however none of the e-mails are making it through.
Looking at the Exchange 2003 SMTP logs, I see timeout waiting to connect entries:
2010-11-17 18:03:54 192.168.22.23 OutboundConnectionResponse
Looking at the Exchange 2003 SMTP logs, I see timeout waiting to connect entries:
2010-11-17 18:03:54 192.168.22.23 OutboundConnectionResponse
Sorry PaulELS, I am not familiar with that issue. You might be best to post that in a separate question.
--Rob
--Rob
Thanks for the insight. So to clarify, I would be able to maintain the SBS and Windows 2008 Standard server in the domain until the 5 FSMO roles are transferred? So long as the Windows 2003 SBS machine has the 5 FSMO roles, they will coexist peacefully?
I've read that Windows SBS will shut itself down once an hour in some circumstances where there are other DCs on the network. How do I avoid that?