SBS2003 | Windows Server 2008 - Exchange 2007
|
From: Cary Shultz on 15 Oct 2009 08:57 Ace, Client does indeed want SBS2003 to be gone....so, I have already moved all of the Exchange stuff to be homed on the EXCH2007 box....and have stopped all of the Exchange Services to ensure that the mail flow is happening and that everything else is working...it is (checked the Firewall to check the forwarding...it was in order so I did not have too many fears of doing this). Tomorrow we remove MS Exchange 2003 from SBS (done this several times...no issues...) and will then remove SBS from that SBS box (have done this twice...). Tip on doing all of this...you *MUST* log on as Administrator. Any other account that is a member of DA, EA, SA, built-in Administrators...doesn't matter...you *MUST* log on using the Administrator account... I will let you know what happens.... Oh, and SharePoint 3.0 is on the SBS Box...going to move that before getting rid of everything.... Thanks, Cary "Ace Fekay [MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message news:mn.5ac47d9acc675908.105663(a)mvps.RemoveThisPart.org... >> Good morning, Ace! >> >> No idea....was not part of any discussion with this client. All of that >> is handled by our Sales team. Will find out, though. >> >> Cary > > Hi Cary, > > And a beautiful morning it is! > > From your description with one of them at a different location, it will > make a difference. Although kind of odd that they would want to keep the > Ex2003 instance on SBS2003 with Ex2007 on another server in the same org, > nor am I sure that will work in an SBS environment in such a fashion > unless migrating away from it. > > Ace > > >> >> "Ace Fekay [MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message >> news:%23IFkBScSKHA.1908(a)TK2MSFTNGP04.phx.gbl... >>> "Cary Shultz" <cshultz.nospam(a)nospam.outsourceitcorp.com> wrote in >>> message news:uQZhE4YSKHA.3540(a)TK2MSFTNGP04.phx.gbl... >>>> Good morning! >>>> >>>> We have a new client that ultimately has an SBS2003 environment with an >>>> additional Domain Controller (WIN2008) and an additional Exchange >>>> Server >>>> (2007). I have not been apart of this at all (except for looking at it >>>> now) >>>> and have just gained remote access so I have very few details. >>>> >>>> I remotely accessed the WIN2008 | Exchange 2007 box (*hate* putting >>>> Exchange >>>> on a DC) and noticed that the SBS2003 box is not on the network. All >>>> sorts >>>> of failures with all of the utilities that I run. Come to find out >>>> that we >>>> took that SBS2003 box to our corporate office. >>>> >>>> Now, it is still the SBS2003 box. It still holds all five FSMO Roles. >>>> It >>>> is still running MS Exchange (although it appears that all of the >>>> mailboxes >>>> have been moved over to the EXCH2007 box). One of my colleagues 'has >>>> some >>>> ideas'.....not saying that in a negative way (really not). >>>> >>>> Is it possible to: >>>> >>>> 1) remove Exchange 2003 from the SBS2003 box (I know all about having >>>> to use >>>> the Administrator account...have done this several times) over a VPN >>>> connection (just thinking what we must have been thinking when we >>>> removed >>>> the SBS2003 server from the client's office)? As long as we have CD2, >>>> right? >>>> 2) remove SBS2003 from that SBS2003 box over a VPN connection? As long >>>> as we >>>> have CD1, right? >>>> 3) backup the SharePoint installation (assuming WSS 2.0....not WSS 3.) >>>> and >>>> then ultimately use that backup to restore to WSS 3.0 that will be >>>> installed >>>> on the WIN2008 | EXCH2007 box (I can only assume that this is going to >>>> be >>>> the thought process that my colleagues have)? >>>> >>>> Any and all comments welcome. >>>> >>>> Thanks, >>>> >>>> Cary >>>> >>> >>> >>> I'm not the best at SBS, and the gurus in this group will better help >>> with the removing Exchange off the SBS part and expecting Ex2007 to work >>> as well as the Sharepoint installation, but my question is, does the >>> customer expect to continue to use SBS2003 along with the non-SBS 2008 >>> DC that has Exchange 2007 on it in the same infrastructure, or do they >>> want to just move the SBS 2003 to a different location and sever ties? >>> >>> -- Ace >>> >>> This posting is provided "AS-IS" with no warranties or guarantees and >>> confers no rights. >>> >>> Please reply back to the newsgroup or forum for collaboration benefit >>> among responding engineers, and to help others benefit from your >>> resolution. >>> >>> Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA >>> Messaging >>> Microsoft Certified Trainer >>> >>> For urgent issues, please contact Microsoft PSS directly. Please check >>> http://support.microsoft.com for regional support phone numbers. >>> > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Please reply back to the newsgroup or forum for collaboration benefit > among responding engineers, and to help others benefit from your > resolution. > > Ace Fekay, MCT, MCTS Windows 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, > MCSA Messaging > Microsoft Certified Trainer > > For urgent issues, please contact Microsoft PSS directly. Please check > http://support.microsoft.com for regional support phone numbers. > >
From: D. Gabriel on 15 Oct 2009 12:16 Your root issue - is that you don't understand SBS... Is this a SBS 2003 to SBS 2008 migration or SBS 2003 to standard windows domain migration? You can have only ONE DC - the SBS Box - in any SBS domain (2003/2008). You can also NOT have any domain trusts. You also can NOT move the core components off the server. In 2003 you could mildly separate the server components by getting the transition pack licensing, but that was designed to let an organization grow out of SBS and Migrate to standard server licensing. I don't even know if this is around anymore, but may be what you should look into. You CAN install member servers into the SBS domain, typically through the SBS Advanced version which gives you a second server for SQL. Regardless of the number of member servers, SharePoint or Exchange will need to remain on the SBS server. (SBS is engineered specifically for this, so you can let go of your exchange on a DC concerns.) As far as migration is concerned, you can transition rather smoothly from SBS 2003 to SBS 2008, and have both servers online together. (Look for the docs in TechNet). However, this is a time limited special for migration only. You can't easily go from SBS 2003 to Standard Windows 2008 and Exch 2007. In this scenario, you would have to just do plain data transfer from the old SBS domain into the new standard Windows domain, because you'll never get domain trust between the SBS and non-sbs DCs. "Ace Fekay [MCT]" wrote: > > Good morning, Ace! > > > > No idea....was not part of any discussion with this client. All of that is > > handled by our Sales team. Will find out, though. > > > > Cary > > Hi Cary, > > And a beautiful morning it is! > > From your description with one of them at a different location, it will > make a difference. Although kind of odd that they would want to keep > the Ex2003 instance on SBS2003 with Ex2007 on another server in the > same org, nor am I sure that will work in an SBS environment in such a > fashion unless migrating away from it. > > Ace > > > > > > "Ace Fekay [MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message > > news:%23IFkBScSKHA.1908(a)TK2MSFTNGP04.phx.gbl... > >> "Cary Shultz" <cshultz.nospam(a)nospam.outsourceitcorp.com> wrote in message > >> news:uQZhE4YSKHA.3540(a)TK2MSFTNGP04.phx.gbl... > >>> Good morning! > >>> > >>> We have a new client that ultimately has an SBS2003 environment with an > >>> additional Domain Controller (WIN2008) and an additional Exchange Server > >>> (2007). I have not been apart of this at all (except for looking at it > >>> now) > >>> and have just gained remote access so I have very few details. > >>> > >>> I remotely accessed the WIN2008 | Exchange 2007 box (*hate* putting > >>> Exchange > >>> on a DC) and noticed that the SBS2003 box is not on the network. All > >>> sorts > >>> of failures with all of the utilities that I run. Come to find out that > >>> we > >>> took that SBS2003 box to our corporate office. > >>> > >>> Now, it is still the SBS2003 box. It still holds all five FSMO Roles. It > >>> is still running MS Exchange (although it appears that all of the > >>> mailboxes > >>> have been moved over to the EXCH2007 box). One of my colleagues 'has some > >>> ideas'.....not saying that in a negative way (really not). > >>> > >>> Is it possible to: > >>> > >>> 1) remove Exchange 2003 from the SBS2003 box (I know all about having to > >>> use > >>> the Administrator account...have done this several times) over a VPN > >>> connection (just thinking what we must have been thinking when we removed > >>> the SBS2003 server from the client's office)? As long as we have CD2, > >>> right? > >>> 2) remove SBS2003 from that SBS2003 box over a VPN connection? As long as > >>> we > >>> have CD1, right? > >>> 3) backup the SharePoint installation (assuming WSS 2.0....not WSS 3.) and > >>> then ultimately use that backup to restore to WSS 3.0 that will be > >>> installed > >>> on the WIN2008 | EXCH2007 box (I can only assume that this is going to be > >>> the thought process that my colleagues have)? > >>> > >>> Any and all comments welcome. > >>> > >>> Thanks, > >>> > >>> Cary > >>> > >> > >> > >> I'm not the best at SBS, and the gurus in this group will better help with > >> the removing Exchange off the SBS part and expecting Ex2007 to work as well > >> as the Sharepoint installation, but my question is, does the customer > >> expect to continue to use SBS2003 along with the non-SBS 2008 DC that has > >> Exchange 2007 on it in the same infrastructure, or do they want to just > >> move the SBS 2003 to a different location and sever ties? > >> > >> -- Ace > >> > >> This posting is provided "AS-IS" with no warranties or guarantees and > >> confers no rights. > >> > >> Please reply back to the newsgroup or forum for collaboration benefit among > >> responding engineers, and to help others benefit from your resolution. > >> > >> Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA > >> Messaging > >> Microsoft Certified Trainer > >> > >> For urgent issues, please contact Microsoft PSS directly. Please check > >> http://support.microsoft.com for regional support phone numbers. > >> > > -- > Ace > > This posting is provided "AS-IS" with no warranties or guarantees and > confers no rights. > > Please reply back to the newsgroup or forum for collaboration benefit > among responding engineers, and to help others benefit from your > resolution. > > Ace Fekay, MCT, MCTS Windows 2008, MCTS Exchange, MCSE, MCSA 2003 & > 2000, MCSA Messaging > Microsoft Certified Trainer > > For urgent issues, please contact Microsoft PSS directly. Please check > http://support.microsoft.com for regional support phone numbers. > > >
From: Ace Fekay [MCT] on 15 Oct 2009 18:45 "Cary Shultz" <cshultz(a)outsourceit.com> wrote in message news:OwxzYcZTKHA.1792(a)TK2MSFTNGP04.phx.gbl... > Ace, > > Client does indeed want SBS2003 to be gone....so, I have already moved all > of the Exchange stuff to be homed on the EXCH2007 box....and have stopped > all of the Exchange Services to ensure that the mail flow is happening and > that everything else is working...it is (checked the Firewall to check the > forwarding...it was in order so I did not have too many fears of doing > this). Tomorrow we remove MS Exchange 2003 from SBS (done this several > times...no issues...) and will then remove SBS from that SBS box (have > done this twice...). > > Tip on doing all of this...you *MUST* log on as Administrator. Any other > account that is a member of DA, EA, SA, built-in Administrators...doesn't > matter...you *MUST* log on using the Administrator account... > > I will let you know what happens.... > > Oh, and SharePoint 3.0 is on the SBS Box...going to move that before > getting rid of everything.... > > Thanks, > > Cary So it sounds like you're getting closer to your end result. Just in case there may be something you've missed, here aer some links I've compiled from the SBS group. I hope they help. Standard Server 2003 Migration to SBS 2008 Part 1 - Part 4 http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-1 http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-2 http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-3 http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-4 SBS 2008 Migrations from SBS 2003 - Keys to Success http://blogs.technet.com/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-success.aspx Migrating from Windows 2003 and Exchange 2003 to SBS 2008: http://www.powerbiz.net.au/Migrating%20from%20Windows%202003%20and%20Exchange%202003%20to%20Small%20Business%20Server%202008.pdf SBS 2008 Migration Checklist http://blogs.technet.com/11/ SBS 2003 to Server 2008/Exchange 2007 http://social.technet.microsoft.com/Forums/en-US/winserverMigration/thread/d874300d-04fe-4c5a-aed1-65720c1019f5 Windows Small Business Server 2008 Migration Help http://www.microsoft.com/downloads/details.aspx?FamilyId=95E4863E-BB59-4A66-9FEE-9874E8903888&displaylang=en Catalog of Windows Small Business Server 2008 Installation Error Messages http://technet.microsoft.com/en-us/library/cc546065(WS.10).aspx Ace
From: Cary Shultz on 15 Oct 2009 19:00 D, I think that I understand SBS2003 and SBS2008 plenty well....but that is okay. I do not take offense to what you are saying... A couple of things that I noted: 1) you can indeed have multiple Domain Controllers in an SBS environment. Shoot, you can have an additional 25 if you wanted. You just need to make sure that you maintain the following: A) that the SBS box holds all five FSMO Roles B) that the SBS box is a Global Catalog Server C) that - if we are talking SBS2008 - the SBS box is a DHCP Server 2) You most certainly can have additional Exchange Servers | MS SQL Servers in an SBS environment. You just have to purchase the additional software and appropriate number of CALs as the second MS Exchange or MS SQL would clearly not be covered by the SBS CALs. Have it in many environments. Generally, the question is why would you do such a thing....and, generally, the answer is that you are going to be migrating to 'normal' Windows (or, that there are sever performance issues). We have, for example, in two environments SBS2003 Standard but have a second Exchange Server (Exchange 2003 in both cases). In another environment, we have SBS2003 Premium but have MS SQL 2005 on another box. In all cases everything works very very well. You do not *move* anything....you simply do not use the services on the SBS2003 box. Naturally, you would need to move the mailboxes (if we are talking about Exchange) or migrate the data (if we are talking about SQL or SharePoint). 3) Trusts - agreed. The SBS box has to be the "main" domain controller in the forest root. You *MUST* have a single domain/tree/forest environment as there is no possibility of a trust. Well, there are a couple of exceptions, like when you are moving SBS2003 to new hardware or when you are moving SBS2003 to SBS2008 (you install SBS2008 in Migration Mode and have 21 days to complete everything....actually going to be doing this in a couple of weeks). But, there can not be a child domain or another tree in your SBS forest..... 4) Transition Pack - went away one year ago (okay, actually 10 months ago) so that is not an option anymore. 5) Pretty sure that you mean SBS Premium.....not SBS Advanced (if we are getting technical here....which apparently we are). 6) Exchange on a DC - always a concern. Why? You are very limited in what you can do. You can not run dcpromo on that box (okay...agreed,,,if you are doing that on an SBS box then running Exchange on a Domain Controller is the least of your concerns at that particular moment). If you do have an environment where you do have multiple Domain Controllers | Global Catalog Servers then MS Exchange - because it is installed on a DC - will only make use of *THAT* DC | GC (DSProxy and DSAccess). So, if that DC | GC is down.......again, if the SBS box is down then you do not really care about whether or not Exchange is on a DC or not and which DCs \ GCs it *could* possibly use...but it is still a concern. Also, store.exe consumes a TON of RAM. And, if we are talking about SBS2003 Premium, then having MS Exchange 2003 and MS SQL 2000 | MS SQL 2005 running on the same box is a *HUGE* concern [think RAM....32-bit is limited to 4GB....we have a couple of SBS 2003 Premium environments where they have 150MB of available RAM at any given point because MS SQL is taking up a ton of RAM (use MS SQL based applications that are RAM Resource HOGS) and MS Exchange is taking up a ton of RAM....]. 7) Totally disagree with the last paragraph....have done it (well, Windows Server 2003....no Windows Server 2008 as you indicate....) a couple of times....in fact, we still manage an environment where we went from SBS2003 to "normal" Windows 2003 | Exchange 2003. In that environment we did not use the Transition Pack. Same in at least one other. And, we have gone through that same process, only we did indeed make use of the Transition Pack. In fact, in the environment where we did not use the transition pack....several of the SBS features are still available. And, are being used this very day. So, while it is fair that you state that my root issue is that I do not understand SBS it is also fair that I disagree with your statement. But, again, no offense taken. "D. Gabriel" <DGabriel(a)discussions.microsoft.com> wrote in message news:1F7E561D-AECF-4C7B-BC7E-E728009C9CCE(a)microsoft.com... > Your root issue - is that you don't understand SBS... Is this a SBS 2003 > to > SBS 2008 migration or SBS 2003 to standard windows domain migration? > > You can have only ONE DC - the SBS Box - in any SBS domain (2003/2008). > You > can also NOT have any domain trusts. > > You also can NOT move the core components off the server. In 2003 you > could > mildly separate the server components by getting the transition pack > licensing, but that was designed to let an organization grow out of SBS > and > Migrate to standard server licensing. I don't even know if this is around > anymore, but may be what you should look into. > > You CAN install member servers into the SBS domain, typically through the > SBS Advanced version which gives you a second server for SQL. Regardless > of > the number of member servers, SharePoint or Exchange will need to remain > on > the SBS server. (SBS is engineered specifically for this, so you can let > go > of your exchange on a DC concerns.) > > As far as migration is concerned, you can transition rather smoothly from > SBS 2003 to SBS 2008, and have both servers online together. (Look for the > docs in TechNet). However, this is a time limited special for migration > only. > > You can't easily go from SBS 2003 to Standard Windows 2008 and Exch 2007. > In > this scenario, you would have to just do plain data transfer from the old > SBS > domain into the new standard Windows domain, because you'll never get > domain > trust between the SBS and non-sbs DCs. > > > > "Ace Fekay [MCT]" wrote: > >> > Good morning, Ace! >> > >> > No idea....was not part of any discussion with this client. All of >> > that is >> > handled by our Sales team. Will find out, though. >> > >> > Cary >> >> Hi Cary, >> >> And a beautiful morning it is! >> >> From your description with one of them at a different location, it will >> make a difference. Although kind of odd that they would want to keep >> the Ex2003 instance on SBS2003 with Ex2007 on another server in the >> same org, nor am I sure that will work in an SBS environment in such a >> fashion unless migrating away from it. >> >> Ace >> >> >> > >> > "Ace Fekay [MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message >> > news:%23IFkBScSKHA.1908(a)TK2MSFTNGP04.phx.gbl... >> >> "Cary Shultz" <cshultz.nospam(a)nospam.outsourceitcorp.com> wrote in >> >> message >> >> news:uQZhE4YSKHA.3540(a)TK2MSFTNGP04.phx.gbl... >> >>> Good morning! >> >>> >> >>> We have a new client that ultimately has an SBS2003 environment with >> >>> an >> >>> additional Domain Controller (WIN2008) and an additional Exchange >> >>> Server >> >>> (2007). I have not been apart of this at all (except for looking at >> >>> it >> >>> now) >> >>> and have just gained remote access so I have very few details. >> >>> >> >>> I remotely accessed the WIN2008 | Exchange 2007 box (*hate* putting >> >>> Exchange >> >>> on a DC) and noticed that the SBS2003 box is not on the network. All >> >>> sorts >> >>> of failures with all of the utilities that I run. Come to find out >> >>> that >> >>> we >> >>> took that SBS2003 box to our corporate office. >> >>> >> >>> Now, it is still the SBS2003 box. It still holds all five FSMO >> >>> Roles. It >> >>> is still running MS Exchange (although it appears that all of the >> >>> mailboxes >> >>> have been moved over to the EXCH2007 box). One of my colleagues 'has >> >>> some >> >>> ideas'.....not saying that in a negative way (really not). >> >>> >> >>> Is it possible to: >> >>> >> >>> 1) remove Exchange 2003 from the SBS2003 box (I know all about having >> >>> to >> >>> use >> >>> the Administrator account...have done this several times) over a VPN >> >>> connection (just thinking what we must have been thinking when we >> >>> removed >> >>> the SBS2003 server from the client's office)? As long as we have >> >>> CD2, >> >>> right? >> >>> 2) remove SBS2003 from that SBS2003 box over a VPN connection? As >> >>> long as >> >>> we >> >>> have CD1, right? >> >>> 3) backup the SharePoint installation (assuming WSS 2.0....not WSS >> >>> 3.) and >> >>> then ultimately use that backup to restore to WSS 3.0 that will be >> >>> installed >> >>> on the WIN2008 | EXCH2007 box (I can only assume that this is going >> >>> to be >> >>> the thought process that my colleagues have)? >> >>> >> >>> Any and all comments welcome. >> >>> >> >>> Thanks, >> >>> >> >>> Cary >> >>> >> >> >> >> >> >> I'm not the best at SBS, and the gurus in this group will better help >> >> with >> >> the removing Exchange off the SBS part and expecting Ex2007 to work as >> >> well >> >> as the Sharepoint installation, but my question is, does the customer >> >> expect to continue to use SBS2003 along with the non-SBS 2008 DC that >> >> has >> >> Exchange 2007 on it in the same infrastructure, or do they want to >> >> just >> >> move the SBS 2003 to a different location and sever ties? >> >> >> >> -- Ace >> >> >> >> This posting is provided "AS-IS" with no warranties or guarantees and >> >> confers no rights. >> >> >> >> Please reply back to the newsgroup or forum for collaboration benefit >> >> among >> >> responding engineers, and to help others benefit from your resolution. >> >> >> >> Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA >> >> Messaging >> >> Microsoft Certified Trainer >> >> >> >> For urgent issues, please contact Microsoft PSS directly. Please check >> >> http://support.microsoft.com for regional support phone numbers. >> >> >> >> -- >> Ace >> >> This posting is provided "AS-IS" with no warranties or guarantees and >> confers no rights. >> >> Please reply back to the newsgroup or forum for collaboration benefit >> among responding engineers, and to help others benefit from your >> resolution. >> >> Ace Fekay, MCT, MCTS Windows 2008, MCTS Exchange, MCSE, MCSA 2003 & >> 2000, MCSA Messaging >> Microsoft Certified Trainer >> >> For urgent issues, please contact Microsoft PSS directly. Please check >> http://support.microsoft.com for regional support phone numbers. >> >> >>
From: Cary Shultz on 15 Oct 2009 19:06
Thanks, Ace! "Ace Fekay [MCT]" <aceman(a)mvps.RemoveThisPart.org> wrote in message news:ulA8lkeTKHA.4364(a)TK2MSFTNGP04.phx.gbl... > "Cary Shultz" <cshultz(a)outsourceit.com> wrote in message > news:OwxzYcZTKHA.1792(a)TK2MSFTNGP04.phx.gbl... >> Ace, >> >> Client does indeed want SBS2003 to be gone....so, I have already moved >> all of the Exchange stuff to be homed on the EXCH2007 box....and have >> stopped all of the Exchange Services to ensure that the mail flow is >> happening and that everything else is working...it is (checked the >> Firewall to check the forwarding...it was in order so I did not have too >> many fears of doing this). Tomorrow we remove MS Exchange 2003 from SBS >> (done this several times...no issues...) and will then remove SBS from >> that SBS box (have done this twice...). >> >> Tip on doing all of this...you *MUST* log on as Administrator. Any other >> account that is a member of DA, EA, SA, built-in Administrators...doesn't >> matter...you *MUST* log on using the Administrator account... >> >> I will let you know what happens.... >> >> Oh, and SharePoint 3.0 is on the SBS Box...going to move that before >> getting rid of everything.... >> >> Thanks, >> >> Cary > > So it sounds like you're getting closer to your end result. Just in case > there may be something you've missed, here aer some links I've compiled > from the SBS group. I hope they help. > > Standard Server 2003 Migration to SBS 2008 Part 1 - Part 4 > http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-1 > http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-2 > http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-3 > http://itknowledgeexchange.techtarget.com/sbs/standard-server-2003-migration-to-sbs-2008-part-4 > > SBS 2008 Migrations from SBS 2003 - Keys to Success > http://blogs.technet.com/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-success.aspx > > Migrating from Windows 2003 and Exchange 2003 to SBS 2008: > http://www.powerbiz.net.au/Migrating%20from%20Windows%202003%20and%20Exchange%202003%20to%20Small%20Business%20Server%202008.pdf > > SBS 2008 Migration Checklist > http://blogs.technet.com/11/ > > SBS 2003 to Server 2008/Exchange 2007 > http://social.technet.microsoft.com/Forums/en-US/winserverMigration/thread/d874300d-04fe-4c5a-aed1-65720c1019f5 > > Windows Small Business Server 2008 Migration Help > http://www.microsoft.com/downloads/details.aspx?FamilyId=95E4863E-BB59-4A66-9FEE-9874E8903888&displaylang=en > > Catalog of Windows Small Business Server 2008 Installation Error Messages > http://technet.microsoft.com/en-us/library/cc546065(WS.10).aspx > > Ace > > > |