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

SBS 2008 migration

migration of SBS 2003 to 2008.  I did all the prep work outlined by Msoft to setup the source server.  I created the answer file, started the migration.  The SBS2008 server installed in the current dmain.
After installation, i have a few "Installation Issues" in the console.

It says "Exchange 2007 cannot be installed" .  This is one that concerns me.
I have read the solution in the Question SBS2008 Migration Issue, and I have tried the soultion recomended there, as I understand it. No chnge for me though. I've been working on this for days!!! Any help really would be appreciated.
Error.bmp
0
mattpaulin
Asked:
mattpaulin
  • 5
  • 4
  • 3
1 Solution
 
rfportillaCommented:
You can not perform an upgrade as per Microsoft.
http://technet.microsoft.com/en-us/library/bb124008.aspx

The recommendation is that you install Exchange 2007 on another server, migrate the data and then take down the older Exchange service.  But, you are doing SBS and doing an upgrade.  

First, make sure you have good and complete backups.  Then export the mail boxes.  Remove Exchange.  Install the new version.  Import the data.  You will probably lose all of the exchange rules.  
0
 
mattpaulinAuthor Commented:
This is SBS 2003 - 2008 - on a new server.
I have followed the instructions given in http://www.microsoft.com/downloads/details.aspx?FamilyID=52b7ea63-78af-4a96-811e-284f5c1de13b&DisplayLang=en,

I used Microsoft's wizards to preform the migration. This includes the source server prep, the creation of the answer file, and then the install of the 2008 SBS server in migration mode.

The source server had the best practices app run first and no isses were detected. The install of the 2008 SBS goes fine, reading the answer file as it should, and installing the server as expected, except for exchange.

Are you saying that all of this, and this blog http://blogs.technet.com/sbs/archive/2009/02/19/sbs-2008-migrations-from-sbs-2003-keys-to-success.aspx are a waste of time and they don't work?
0
 
rfportillaCommented:
No, I am not saying that they are a waste of time.  I thought you were trying to upgrade on the same machine.  If you have created a separate server with win 2008 then you should be able to install Exchange 2007 on it.  
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

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.

 
mattpaulinAuthor Commented:
Yep, thats what I thought! But exchange is actually there, just not fully installed. It is listed as an installed product, but won't let me remove it. Can't install it if I cant remove it. I think I'll have to log a support call with Microsoft....
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Is the source server up to date?
 Exchange SP2
 Win2K3 SP2
Did you MU the source server prior to running the Source Server Prep Tool? Did you run the prep tool?

Did you run the SBS 2003 Best Practices Analyzer to verify the health of the source server.

DCDiag and NetDiag on the source server to verify the health of the box.

http://blogs.technet.com/sbs/archive/2008/12/19/sbs-2008-migrations-fail-when-the-migration-preparation-tool-has-not-been-run.aspx

If you can, restore the source server to the point before it was touched and run through again. We use ShadowProtect to image our source servers prior to each phase of the migration and from there we use the built-in SBS 2008 backup to backup before each phase too.

Philip
0
 
rfportillaCommented:
I have to agree with MPECSInc.  Yeah, I would consider doing it over.  I create a separate partition when I do an install and then do regular bkp images throughout the install.  I do once after the initial install.  I do another after updates.  Then another after major software installs such as Exchange.  This keeps me from having to start at the beginning each time.  I do have a few questions, though.

1. What does your log say?  What errors are you getting?
2. Did you do all of the server updates before installing Exchange?  
3. Am I understanding that you can not complete the install of Exchange 2008, but you can not remove the partial install?
0
 
mattpaulinAuthor Commented:
Hi Philip,

Yes SBS 2003 SP2, Exchange SP2. SBS 2003 BPA was run prior, no issues. MU?? what's that? The source prep wizard was run prior to the migration, and reported no issues.
The source and destination server are both virtual machines running on Citrix Xenserver 5. I have backups and have tried this upgrade about 5 times now - each time following a full restore of the initial system, including AD etc. It's a simple process, but takes about 6 hours to recover.
This entrie system is on a test setup, but is a copy of a clients system  - I'm just testing the upgrade process before I tackle the real one. Fortunately!

rfportilla, I guess I'm slow! I only just noticed the abilty to export the log file this morning! Reading thru, it had 2 issues - the primary was that it failed to upgrade the domain controller. I also note that it was looking for 192.168.1.253 or 254 as the default gateway - this is incorrect - should be 192.168.1.1. SO, I have deteled both the source and destination servers, and am currenlty recovering the source server image prior to update.

I intend to make a couple of checks - which group is set to primary for Administrator (the A/C i'm using for the upgrade), and the default gateway the source server had before I start the wizard. I'll also untick the "unattended" box in the answer file options so I should get prompted if there are any issues. Hopefully it will work this time!!
I appreciate your help guys..
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
I suggest putting the source server onto physical hardware. We keep a few server boxes around that are a couple years old and similar in configuration to the servers we are migrating. We test every migration (billable too).

We use ShadowProtect. The recovery times are fairly quick.

Virtualizing introduces an unknown element in the way the virtual machine additions interact with the underlying OS. MAC addresses along with NIC setups can be mucked up by virtualizing a production machine. Make sure you remove any hidden devices in the Device Manager. See http://blog.mpecsinc.ca/2008/02/sbs-shadowprotect-some-hardware.html blog post that explains how to do that.

Make sure the NIC on source server is the only one. That is, you must remove NIC2 if 2NIC and rerun CEICW to set the router into place in both the NIC properties and DNS for the forwarders.

When you set up the answer file, make sure the IPs are correct and that your domain admin account is the original 500 account with Domain Users as the Primary Group when looking at the properties.

MU = Microsoft Update.

Make sure you have one physical NIC of your virtual server connected to a physical router that gives both SBSs access to the Internet.

Philip
0
 
rfportillaCommented:
Please let us know if it works.  Thanks
0
 
mattpaulinAuthor Commented:
OK, I've solved it - none of the above though! The problem was the existence of an AD exchange connector. I used the Windows Essential Business Server Preparation and Planning Wizards, and it detected this problem. Removed the AD connector, and the install worked fine.
Thanks for your help guys.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Good to hear!

Philip
0
 
rfportillaCommented:
That's funny because I did read that somewhere in the documentation.  Take care.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 5
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now