?
Solved

SBS 2003 -> 2011 Migration partially failed, missing SBS components

Posted on 2012-09-10
21
Medium Priority
?
1,980 Views
Last Modified: 2012-11-08
Hello,
I was wondering if anyone can help us with an SBS 2003 -> 2011 migration issue. I will lay out our situation, progress and status and maybe some one  will be able to help us out.

Scope:
+ Migrate SBS 2003 -> 2011

Current config and situation:
+ the LAN subnet I am working with is 192.192.168.0/24.
+we are moving from a phisical server(SBS 2003) to a VM(vmware - SBS2011)
+we have a Sonicwall Tz190 Enhanced(with Sonic os 4.0.1.3-46e)

Changes an prepwork:
+since 192.192.x.x is not an acceptable subnet and I cannot change the subnet for the whole site at this moment i added a secondary ip to the 2003 DC: 10.192.168.x
+I then added a Published ARP entry for 10.192.168.1 (on LAN interface) on the sonicwall and configured a route for the 10.192.168.0/24
+I created my amswer file with 10.192,168.x ips for the source, destination server and gateway and manually set the ip of the new SBS2011 dc to reflect the 10.192.168.x(ip/gateway). The dns setting for the SBS2011 was set to the old ip of the SBS 2003 (192.192.168.x).
+ I also added hosts and lmhosts records for the old DC and for my current domain(on the SBS11 server)

Progress and errors after wizard finished:
+the setup started and finished fairly quick. When I logged on I noticed that AD/DNS/Sharepoint is ok but Exchange is missing, no Remote web access or companyweb available.
+I also noticed that I can't see the user roles. when I click on the "users and groups " it says "No user roles were defined". When I checked in AD the "User Roles" sec group was missing; the template users were missing
+In IIS there is no "companyweb" website nor a "remote" virtual directory
+The new SBS11 GPOs were not created
+the SBS Console is not very helpful. It only says: "The instalation of SBS 2011 Standard cannot finish"

Steps taken afterwards:
+I installed Exchange manually(worked ok) and applied the licensing fix

And now for the question:
+since AD is well, exchange is well, Is there anyway that I can continue the migration manually. I do not mind doing the manual labour; but to restore system state and do it all over again... come on Microsoft.
I'm hoping to exchange ideas and maybe I can carry this over to the end.

Respectfully,
Adrian
0
Comment
Question by:Yardstick
  • 9
  • 7
  • 4
  • +1
21 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 38384197
Please run the script in the following MS article to complete the installation:

http://support.microsoft.com/kb/2527626

Once completed - check all is happy and then deal with any issues afterwards.

Alan
0
 

Expert Comment

by:heliosit
ID: 38385969
That's the fix - I had to do this a few times last month.

Make sure to run BPA for Exchange and Windows once you think you're done, as I had some additional steps to configure Exchange and SBS.
0
 
LVL 1

Author Comment

by:Yardstick
ID: 38391677
I will try that and let you know how it goes. Thank you guys!
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
LVL 1

Author Comment

by:Yardstick
ID: 38392208
Perfect. that dealt with exchange. Thank you! I ran the hotfix before posting here but not the script; now there are other fretures that were not setup: for example,
+No User Roles ; when I try to add one it tells me that the feature was not properly installed
+ "companyweb" is missing ; no website in IIS
+the "remote" virtual directory under the "default web site" is missing , therefore, no RWW(or RWA as they call it now)

Any idea how I can install/configure this manually? or where does the migration wizard grab them?


Adrian
0
 
LVL 74

Assisted Solution

by:Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy earned 2000 total points
ID: 38399255
So it sounds like you do have a failed migration --- mostly a failed SBS 2011 installation.  The best thing you can do is to wipe the box and start over.  I realize this is not what you want to do, but there are plenty of checks along the way in the documented migration plan which should have clued you in before this point.

I am primarily concerned about your comment; "I cannot change the subnet for the whole site at this moment i added a secondary ip to the 2003 DC: 10.192.168.x" because it is a bit confusing.  Why couldn't you change it?  Not doing so will cause you significantly more problems (as you now know).

I do not mind doing the manual labour; but to restore system state and do it all over again... come on Microsoft.

The thing is that with SBS you don't ever want to "do the manual labour".  There are far too many interdependent systems which can end up misaligned if you don't use the server's built-in tools (THE WIZARDS -- which includes the migration wizards).

I've done more than 40 SBS 2003 Migrations (to both 2008 and 2011) and EVERY time I follow the Microsoft Migration guide to the letter.  By doing so, I've rarely had a problem other than a few unexpected things which will always come up in this kind of procedure.  The key though, is to avoid the problems which ARE expected.  This is why there is so much discussion (see http://sbsmigrationtips.com) and great documentation (see http://technet.microsoft.com/en-us/sbs/gg981878.aspx).

As I stated above, your best move is to cut your losses right now and start over.  Otherwise you will end up living with "strange" problems for the rest of the life of your new server.

Jeff
TechSoEasy
0
 

Expert Comment

by:heliosit
ID: 38399296
Jeff, I disagree! To start over will mean restoring the system state on the SBS 2003, as the forest has already been updated to allow the migration and second DC. Manually finishing the migration and SBS 2011 installation is relatively simple.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38399305
Actually... I just reread all of your question again...and I'm wondering... have you even started to run the Migration Wizard from the SBS 2011 Console?

Jeff
TechSoEasy
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38399326
@heliosit:  I don't understand what you see as the problem.  Of course it means restoring the  SBS 2003's system state from before the schema was updated... but then you just run the Migration Preparation tool again.  Why is that more difficult than having to make sure that you enter each part of the SBS 2011 configuration manually (I would estimate that to be at least 80 or 90 separate configuration steps).

Jeff
TechSoEasy
0
 

Expert Comment

by:heliosit
ID: 38399344
Jeff, I'm just talking from my experience. I found the manual steps (which are listed above) to be pretty straight forward. It's also quicker than taking a live server offline for a system state restore.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38399396
The fact is, that since neither of us has reviewed the sbssetup.log, we don't know what the exact state of the installation is.  If Yardstick cares to post that log, then it would be possible to make a better recommendation of how to move forward.

Jeff
TechSoEasy
0
 

Expert Comment

by:heliosit
ID: 38399417
We do know the current state of the migration. It completed and failed to install Exchange. This was installed manually and configured through the referenced Powershell script. The problem has moved on from simply a failed migration.
0
 
LVL 1

Author Comment

by:Yardstick
ID: 38399423
-The reason why I changing the LAN subnet was not an option is that we have  A CAD server, printers and another Router owned by a vendor (which has a permanent VPN tunnel to their network) that connects the users to an app service that is vital for business. These changes need to be made slowly, over time. So I created second rout-able subnet on the LAN. Slowly I will move all systems to the new subnet.

========================================================================

I Have not started running the migration tasks from the SBS console yet. The reason Why I haven't is the fact that if I open the SBS console(Advanced) go to Network->Computers, right-click on my New server and click "Manage Server Applications", all the Apps show as "Not installed"(including Remote Web access" and "internal Website"). I'm afraid that when I start the migration tasks All will error out I  would have no way to back out of that.
... and at this moment it is very hard for me to restore system state( as heliosit said): I have Exchange running on both server and yes the DC's are replicating ok.

Q1: Will the server apps be installed using the migration tasks or do I need to run something manually?
0
 
LVL 1

Author Comment

by:Yardstick
ID: 38399562
Sorry about the Logs:
I have attached the logs before the fix mentioned in the thread above and the SBS Log as it is now
SBSLogs-before-the-Fix-specified.zip
SBSSetup.log
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38399565
The reason Why I haven't is the fact that if I open the SBS console(Advanced) go to Network->Computers, right-click on my New server and click "Manage Server Applications", all the Apps show as "Not installed"(including Remote Web access" and "internal Website").

The reason they show as not installed is because you haven't set up the network yet so the SBS Console doesn't know where to look for those sites -- ie, there are no entries in DNS.  You need to start the Migration Wizard and go through the prescribed steps.  This will create the proper DNS entries for you and then things will start coming together.

However, I am concerned about this being a separate IP Subnet --- the wizards will not respond well to that.  You really should have done all the groundwork of changing these business critical connections BEFORE starting your migration.

Slowly I will move all systems to the new subnet.
Remember, you only have 21 days from the start of your migration to decommission your SBS 2003.  

Jeff
TechSoEasy
0
 
LVL 1

Author Comment

by:Yardstick
ID: 38406531
-It seems that at the moment I cannot start the Migration Wizard The application Fails when I started. I found an article that resolves this:
http://support.microsoft.com/kb/2533423

-however the : sbssetup-runtimedata.dat is missing as I never started the migration. I was able to click on the "Migrate SBS" link in the "SBS console" and start the wizard right after I installed Exchange (manually) but I did not go past the first screen at that moment so I assume the file never got created. In between that time and now, I installed exchange critical updates and a few windows updates which probably corrupted the XML.
Not sure if I can do something about it or If I need to do the following(which will be a pain):
-uninstall exchange
-demote SBS2011
-backup the SBS03 one more time
-systemstate restore
-rerun the SBS migration wizard
0
 
LVL 1

Author Comment

by:Yardstick
ID: 38406955
With one last swing at it, I managed to recover the original sbssetup-runtimedata.dat from a similar other server that I'm working on. I compared it with an SBS server that is already completed and noticed that they are the same. I copied it to the server that I'm having issues with and the wizards are now running. I am still very concerned about the fact that the "Server Applications" are showing that are "Not installed"(RWA, internal web site, Monitoring and reporting). I'm wondering if the Wizards will add them for me but i'm not sure. Does anyone know if I can manually install them? I have a feeling that the wizard only configures them.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38421154
-It seems that at the moment I cannot start the Migration Wizard The application Fails when I started.

My very first comment above was that you have a failed installation which should have been completely redone.  If you are still bent on keeping what you have, then you should at least go through the SBS 2011 Repair Guide to fix whatever is broken.

Jeff
TechsoEasy
0
 
LVL 1

Author Comment

by:Yardstick
ID: 38468212
Hi guys,
I placed a support ticket with Microsoft who, after looking around for a few hours, stated the obvious: System State Restore.
Since I'm using Vmware on the new server and I have lots of room, I decided to P2V the Current Server(SBS 2003), restore the C: volume to before the migration and then restore the Exchange and Data volumes to the most recent backup before the switch over to the VM. In a nutshell(C: = before the upgrade, Other volumes-including the Exchange DB+logs=most recent backup)
-I will then prep the server again, change the subnet  from 192.192.x.x to 10.192.x.x , take a snapshot and restart the migration.
That should do it
Push me luck, I will keep posting results
0
 
LVL 1

Accepted Solution

by:
Yardstick earned 0 total points
ID: 38477509
Wow, what a weekend!
Here is what I did to resolve the issue(for troubled techs that will have the same issue as me):

1) Source server: virtualized my sbs 2003 DC(vmware converter and Vsphere are a blessing, take it from me). placed the VM on a Vmware switch that is not connected to a physical NIC(so I don't have any conflicts)

2) Source server:We use Shaddowprotect so it was easy to restore the C: volume from before the migration.
Note:
-don't restore to a point after the migration tool was installed on your SBS 2003. The anoying 21 day clock starts ticking as soon as the tool is installed. I found this out the hard way.. must of missed that when I read the 90 page SBS migration doc :)
-if you are dealing with an issue like mine you can dual subnet on the LAN as long as the primary subnet (assigned to your LAB interface of your router is not publicly rout-able)

3) Source Server: I had to replay the exchange logs on the Exchange DB as it would not mount(http://daily-it.blogspot.ca/2012/05/restore-exchange-2003-database-from.html)

5) Source server: changed the Subnet from 192.192.x.x/24 to 10.192.x.x/24 using the "change server IP Tool" .... which failed for some reason; however I managed to change the IIS and exchange stuff manually.

4) Source Server: After checking that everything is running, I shut down the Physical Server and moved my Vm to a Vswitch connected to a physical NIC.

5)Source server: did all the prep work again and installed the migration tool; created the answer file

6)Destination Server: installed SBS 2011 and ran the migration wizard.
Ran like a charm

Jeff from TechsoEasy was right. There is no manual way of dealing with an SBS 11 migration... we spent $250 for Microsoft to  tell us that. Save your self the charge... :)
0
 
LVL 1

Author Closing Comment

by:Yardstick
ID: 38494329
-Jeff suggestion Was the partial answer to my question. My notes describe the solution in details
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 38579296
Jeff from TechsoEasy was right. There is no manual way of dealing with an SBS 11 migration... we spent $250 for Microsoft to  tell us that. Save your self the charge... :)

I think I'm going to print this out, frame it and then hang it above my desk!  :-)

Jeff
TechSoEasy
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question