• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 182
  • Last Modified:

how to migrate a sbs 2003 server to a new Windows Server 2003 R2 Enterprise Edition Server

Anyone have experience doing this?  Lead me to the correct docs and 500 points are yours!
0
sbcw
Asked:
sbcw
  • 7
  • 7
2 Solutions
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You need the Transition Pack in order to break the limits of the current server parts (Exchange, AD, and SQL if you have it).

Documentation is here:  http://www.microsoft.com/downloads/details.aspx?FamilyID=BBCF7319-4947-4FD2-A2EA-145588765E68&displaylang=en

Licensing information is here:  http://www.microsoft.com/WindowsServer2003/sbs/techinfo/planning/transition.mspx

Jeff
TechSoEasy
0
 
Martin_DalpeCommented:
this is the way I done it, without any problem.

if you have another machine to install Windows 2003, you integrate that new server into the domain, make it a DC, install Exchange onto that server , then you transfer your mailbox from SBS2003 to the new exchange2003 server, you transfer all DNS and DHCP to the new server

then you run on the SBS2003 the install program to remove exchange2003.
you then do a dcpromo on the SBS2003 to make it a member server
then you remove your SBS2003 to a Workgroup.

those are the basic guideline to do it without the tansition pack
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Martin,

That's essentially what the Transition Pack procedure does.  However it provides the expanded user Exchange license and Windows Server license at a MUCH LOWER cost.  The reason for the Transition Pack is two-fold.  One is cost and the second is allowing you to legally make the SBS a Windows 2003 member server.

Jeff
TechSoEasy
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Martin_DalpeCommented:
I know,

but I found myself, twice, that the transition pak was not the best solution.  
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
How so?  What issues were there?
0
 
Martin_DalpeCommented:
first, the client had already a Windows 2003 server install onto is domain and he already bought exchange 2003.

second, if you have a SBS2000, the transition pak does not exist anymore.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Thank you for clarifying... since the first example you site may or may not have anything to do with this question because we don't know that information and the second example has absolutely nothing to do with this question.  i think it's important to be clear about WHY things aren't a good solution if you are going to state that in an answer.

Thanks!

Jeff
TechSoEasy
0
 
Martin_DalpeCommented:
but the procedure that I mentione does works.

but , yes the transition pak should be the way, but other way exist. information is missing from the question to point out the correct and most efficients way.

;)
Martin
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I may work, but it violates the EULA (LICENSING) of SBS and is therefore illegal.  I would like to point out that recomending such a procedure is also in violation of the Experts-Exchange Member Agreement.  So, while you may think this is more efficient, it's most definitely not correct.

Jeff
TechSoEasy
0
 
Martin_DalpeCommented:
if it's illegal, why does Microsoft provide me with this procedure ?

it's not illegal, because you pay for all the software ( Windows 2003 + exchange 2003 + sbs 2000 or 2003 )

the only thing is the customer overpay is solution.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I think I misinterpreted the part where you say you "Remove SBS2003 into a Workgroup" because this didn't make any sense.  Is your suggestion that you trash that server?

In growing a network, you will need that server to run SOMETHING.  You cannot use the Windows Server 2003 component of SBS for anything other than the Root of the AD Forest with no more than 75 Clients unless you buy the Transition Pack which allows you to remove those restrictions legally.

Also, you cannot use the Exchange Server or SQL Server components on other machines unless you buy the transition pack.

In your situation, what was done with the old SBS?

Jeff
TechSoEasy
0
 
Martin_DalpeCommented:
yes the point was to remove permenently the SBS Server. and replace it with Windows 2003 SErver and Exchange 2003 Server

the customer, bought all the product indivudualy ( Windows 2003 Server + Exchange 2003 Server + MS Sql)

so in the end he paid a lot more than goin with the transition pak.

Martin
0
 
Martin_DalpeCommented:
I think we are getting a little carry away ( sorry for my poor english )

dear SBCW , what excacly do you whant to do,  I think the best way ( like TechSoEasy said) is to go with the Transition pak.

does it anwser your question ?
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I think this kind of debate is good to have... while it may not be in direct response to the question, I always learn from these type discussions, and hope others do as well.  I will only point out that if the customer bought Windows 2003 Server, Exchange 2003 Server and MS SQL, that means that you would be putting Exchange 2003 and SQL on the same box.  Not always a good practice if it's not SBS. You would still need another Server 2003 license to put Exchange or SQL on.

Yes, your client paid A LOT more than going with the Transition Pack (thousands of dollars!) which is why I so strongly questioned your suggestion to begin with.    

Jeff
TechSoEasy
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 7
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now