<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/MU" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Upgrading SBS 2000 to SBS 2003 and Exchange 2000 to 2003</title>
	<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/</link>
	<description>Chris Dalby's blog focuses on Microsoft Exchange Server and the interaction and integration of Exchange Server within Windows, mixed networks, and mobile networks. The blog also includes tips and tweaks for Exchange Server within Small Business Server, both SBS 2000 and SBS 2003. It also reviews various Exchange tools and utilities plus Exchange scripts and codes for managing an Exchange enterprise</description>
	<pubDate>Thu, 18 Mar 2010 01:06:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>

	<item>
		<title>by: Mike Nielsen</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-13682</link>
		<pubDate>Thu, 20 Dec 2007 21:22:46 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-13682</guid>
					<description>I am about to upgrade a domain from SBS2000 to server standard 2003 with exchange 2007.

I have decided that won't try to upgrade from exchange2k to exchange07, I'll just export the mailboxes to PSTs and import.  Only twenty or so mailboxes all less than 100meg.  No biggie.

What I do want to avoid is having to rejoin the workstations to the domain as some are scattered around the city using VPNs,  nor do I want to lose the user accounts.

In the above article you use a temporary 2003 standard server as a way-point on the way to sbs2003, so I assume if I don't want to move to sbs2003 I can leave the way-point server as the new DC and retire the old SBS2000 server?</description>
		<content:encoded><![CDATA[<p>I am about to upgrade a domain from SBS2000 to server standard 2003 with exchange 2007.</p>
<p>I have decided that won&#8217;t try to upgrade from exchange2k to exchange07, I&#8217;ll just export the mailboxes to PSTs and import.  Only twenty or so mailboxes all less than 100meg.  No biggie.</p>
<p>What I do want to avoid is having to rejoin the workstations to the domain as some are scattered around the city using VPNs,  nor do I want to lose the user accounts.</p>
<p>In the above article you use a temporary 2003 standard server as a way-point on the way to sbs2003, so I assume if I don&#8217;t want to move to sbs2003 I can leave the way-point server as the new DC and retire the old SBS2000 server?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lachlan Martin</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-8414</link>
		<pubDate>Wed, 20 Jun 2007 04:39:59 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-8414</guid>
					<description>Chris

We are in the process of decommissioning an SBS2003 Prem box and replacing with Server 2003 Standard with Exchange on a new box.

I believe that the above process you have described will work ok.
In point 4 you say;

&quot;4. Make the 2003 Standard Server a Global Catalog server. Reboot and wait for event 1119 or 1869 showing the new DC is now a GC - This very important. Remember no Global Catalog means no one can log on!&quot;

Might sound silly, but how do I make the new server the GC?

Regards

Lachlan</description>
		<content:encoded><![CDATA[<p>Chris</p>
<p>We are in the process of decommissioning an SBS2003 Prem box and replacing with Server 2003 Standard with Exchange on a new box.</p>
<p>I believe that the above process you have described will work ok.<br />
In point 4 you say;</p>
<p>&#8220;4. Make the 2003 Standard Server a Global Catalog server. Reboot and wait for event 1119 or 1869 showing the new DC is now a GC - This very important. Remember no Global Catalog means no one can log on!&#8221;</p>
<p>Might sound silly, but how do I make the new server the GC?</p>
<p>Regards</p>
<p>Lachlan
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Adam</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5972</link>
		<pubDate>Fri, 04 May 2007 03:09:30 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5972</guid>
					<description>Thanks Chris, wasnt sure what the changing of ip address was in relation to, thanks for clearing that up :) will be trying this out shortly.</description>
		<content:encoded><![CDATA[<p>Thanks Chris, wasnt sure what the changing of ip address was in relation to, thanks for clearing that up <img src='http://blogs.msexchange.org/dalby/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  will be trying this out shortly.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chris Dalby</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5965</link>
		<pubDate>Thu, 03 May 2007 20:27:30 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5965</guid>
					<description>When you join the new DC to the domain and following the DCPROMO and changing the GC. You must set the new DC's DNS server setting on the etwork card to poin to the ipaddress oif the new DC.  This is because the SBS is being removed from the domain and will no longer be running DNS forthe network.  Hope that helps.</description>
		<content:encoded><![CDATA[<p>When you join the new DC to the domain and following the DCPROMO and changing the GC. You must set the new DC&#8217;s DNS server setting on the etwork card to poin to the ipaddress oif the new DC.  This is because the SBS is being removed from the domain and will no longer be running DNS forthe network.  Hope that helps.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Adam</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5957</link>
		<pubDate>Wed, 02 May 2007 11:35:17 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5957</guid>
					<description>Hi Chris,

Can you please elaborate on;

5. Change the IP address of the new DC to point to itself. Change the IP address of the SBS to point to the new DC.

Thanks.</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>Can you please elaborate on;</p>
<p>5. Change the IP address of the new DC to point to itself. Change the IP address of the SBS to point to the new DC.</p>
<p>Thanks.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dqueue</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5576</link>
		<pubDate>Fri, 27 Apr 2007 17:43:55 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5576</guid>
					<description>I've read over your two-part article about introducing W2k3 Server with Exchange 2007.  If I'm starting with SBS2k, do I need to first upgrade to SBS2k3?  Microsoft documentation indicates Exchange 2000 -&amp;#62; Exchange 2007 is a supported upgrade.  I know I require having a W2k3 Server heading my domain before Exchange 2007 may be installed, but I prefer to handle the transition without upgrading to SBS2k3.

Many thanks for the reply.  It's much appreciated.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve read over your two-part article about introducing W2k3 Server with Exchange 2007.  If I&#8217;m starting with SBS2k, do I need to first upgrade to SBS2k3?  Microsoft documentation indicates Exchange 2000 -&gt; Exchange 2007 is a supported upgrade.  I know I require having a W2k3 Server heading my domain before Exchange 2007 may be installed, but I prefer to handle the transition without upgrading to SBS2k3.</p>
<p>Many thanks for the reply.  It&#8217;s much appreciated.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: chris</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5566</link>
		<pubDate>Fri, 27 Apr 2007 15:39:08 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5566</guid>
					<description>introducing W2k3 Server with Exchange 2007 into a domain, while ripping SBS2k out of the domain is possible. I have recently written an article on msexchange.org covering this.</description>
		<content:encoded><![CDATA[<p>introducing W2k3 Server with Exchange 2007 into a domain, while ripping SBS2k out of the domain is possible. I have recently written an article on msexchange.org covering this.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dqueue</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5457</link>
		<pubDate>Thu, 26 Apr 2007 17:11:55 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-5457</guid>
					<description>Thanks for describing your experience.  I'm hopeful of following the steps, in part, in order to: introduce W2k3 Server with Exchange 2007 into my domain, while ripping SBS2k out of my domain.  Is this a possible transition?  Any gotchas to expect?

Thanks again.</description>
		<content:encoded><![CDATA[<p>Thanks for describing your experience.  I&#8217;m hopeful of following the steps, in part, in order to: introduce W2k3 Server with Exchange 2007 into my domain, while ripping SBS2k out of my domain.  Is this a possible transition?  Any gotchas to expect?</p>
<p>Thanks again.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: chris</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-4269</link>
		<pubDate>Thu, 15 Mar 2007 23:14:06 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-4269</guid>
					<description>There is no prblem adding another server and exchange server to an SBS domain.  Just mak sure all the FSMO roles stay on the SBS box.  You can then simply put the mailboxes for the required domain name on the new server.</description>
		<content:encoded><![CDATA[<p>There is no prblem adding another server and exchange server to an SBS domain.  Just mak sure all the FSMO roles stay on the SBS box.  You can then simply put the mailboxes for the required domain name on the new server.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Michael</title>
		<link>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-4267</link>
		<pubDate>Thu, 15 Mar 2007 17:39:40 +0000</pubDate>
		<guid>http://blogs.msexchange.org/dalby/2006/04/20/upgrading-sbs-2000-to-sbs-2003-and-exchange-2000-to-2003/#comment-4267</guid>
					<description>Hi,

We want to add an additional windows 2003 server with exchange to our netwok (SBS 2003).  Can you use two exchange servers? we want to use the second one for a differnet email domain to take the load of the SBS.  Can this be done or do we need two win 2003 servers with two domains?

Thanks</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>We want to add an additional windows 2003 server with exchange to our netwok (SBS 2003).  Can you use two exchange servers? we want to use the second one for a differnet email domain to take the load of the SBS.  Can this be done or do we need two win 2003 servers with two domains?</p>
<p>Thanks
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
