Link to home
Start Free TrialLog in
Avatar of emconsulting
emconsulting

asked on

Migrating to SBS 2011 from 2003 hung on Preparing to configure windows

I am migrating from SBS 2003 to 2011 and have got caught up on the Stage 3 of 3Preparing to configure windows screen. I have already waited an hour and rebooted. It came right back to the same screen. It has been 3 hours and still at the same screen. It looks like the source server already has the destination server listed as a domain controller. The source server prepped with no issues and I did install in migration mode with an answer file. Any ideas?
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Did you hard reboot the first time?!?
Is Update Services OFF and disabled on the source server?

Philip
Try a diifferent Network Card.
If it is not a server class network adapter, you could have issues.

Mark
Avatar of emconsulting
emconsulting

ASKER

I did hard boot the first time.

After waiting 3+ hours it switched to the "Expanding and installing files", and has been there all night. The banner at the bottom of the screen continues to change.
I can connect to the destination servers event logs and I am seeing the following:

Event Type:      Warning
Event Source:      MSExchangeSA
Event Category:      (1)
Event ID:      9157
Date:            11/5/2012
Time:            9:17:48 AM
User:            N/A
Computer:      dc2.domain.local
Description:
Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. Wait for replication to complete and then check to make sure that the computer account is a member of the "Exchange Servers" and "Exchange Install Domain Servers" security groups.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      DCOM
Event Category:      None
Event ID:      10010
Date:            11/4/2012
Time:            10:26:53 PM
User:            N/A
Computer:      dc2.domain.local
Description:
The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      DCOM
Event Category:      None
Event ID:      10016
Date:            11/5/2012
Time:            4:32:41 AM
User:            domain\user
Computer:      dc2.domain.local
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
 to the user {61738644-F196-11D0-9953-00C04FD919C1}\domainSID (user).  This security permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This looks so much like the problem I had.
It my case it was because of the destination server network card was not up to the job.
I was using an on board one. Once I replaced it with a proper server one, compatible with Windows 2008R2, It all worked.
The only error that continues to log is the Exchange error:
I can connect to the destination servers event logs and I am seeing the following:

Event Type:      Warning
Event Source:      MSExchangeSA
Event Category:      (1)
Event ID:      9157
Date:            11/5/2012
Time:            9:17:48 AM
User:            N/A
Computer:      dc2.domain.local
Description:
Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. Wait for replication to complete and then check to make sure that the computer account is a member of the "Exchange Servers" and "Exchange Install Domain Servers" security groups.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

It seems this is what is keeping it from moving on.
Microsoft Exchange System Attendant status is "Starting" and doesn't change. When trying to stop/start/disable I get the following message:

Configuration Manager: The Plug and Play Service or another Required Services is not available.
I believe that the replication is unable to complete because of an incompatible network card.
I'm sorry I am not much help, it was such a long time ago.
Are you using an onboard NIC?
Why would it be the on board NIC? It seems to be communicating fine and the MSExchangeSA error continues to log indicating it is trying to use that service. Any other ideas?
All I can tell you is from my experiences.
I was using an on board NIC and there were certain things that were not being transferred. It took quite a while to work this out. But once I bought a cheap Used Server Network card from EBay, all was fine.
I believe that depsite the spec, the onboard NIC was not fully compatible with Windows 2008R2.
I was upgrading to a Virtual Machine on Hyper-V R2 at the same time. So it was in fact that the onboard NIC was not compatible with Hyper-V.
Once the upgrade was finished, I used the onboard card for Management and it worked fine for that. Just not for the actual upgrade.

Try this
http://www.ebay.co.uk/itm/HP-395861-001-NC373T-PCI-e-GBit-Multifunction-Server-Network-Adapter-/130793127987?pt=UK_Computing_Other_Computing_Networking&hash=item1e73e0c033

Mark
Your were getting the same Exchange errors with the System Attendant in the "starting" status with the onboard NIC?
I do not recall exactly. But my errors were due to problems with the initial replication.
Is the firewall service OFF in Services.msc on the source?
Is the domain admin account the default 500 account that was originally set up with the SBS 2003?
Is the default membership for the 500 account Domain Users?
Does the 500 account have ENTERPRISE ADMIN membership?

Please download and run the www.sbsbpa.com for SBS 2003. Once done, please report your results back here.

Philip
The firewall service isn't running
I am using an account created specifically for the migration "migadmin"
It is apart of the following groups:
Administrators
Domain Admins
Domain Users (Default)
Enterprise Admins
Group Policy Creator Owners
Mobile Users
Schema Admins

Attached are the issues the scan found. Before I started the migration there weren't any errors at all. The C drive has over 6GB of space left. It looks like the migration transferred the FISMO roles already.
Please use the default 500 account to get things going.

Another account will be created in the SBS 2011 Standard's SBS Console to begin the Migration Wizard steps.

We have a migration guide here:
http://blog.mpecsinc.ca/2011/05/sbs-2003-to-sbs-2011-migration-guide.html

Philip
Honestly, it sounds like you had your migration file configured to download andninstallmiodates during initial installation. And that takes a LONG time. Then you went and hard booted, breaking AD and other services. You may have to roll back and restart. Hard booting is NEVER a good idea.
What do you mean by the default 500 account?
The default account that was created when SBS 2003 was first set up, or inherited if SBS 2003 was dropped into an existing network.

The default 500 account is usually Administrator (but can be renamed via Group Policy or manually in Active Directory Users and Computers).

That account is special. :)

Philip
What do you mean by getting things going with that account? Do I need to start over?
Our preferences:
#1: Restore System State, do an AD/Server Health Check (our guide).
#2: Clean up AD/DNS/DSSite/ETC to remove destination do an AD/Server Health Check (our guide).

Yup.

One needs to get to the bottom of the failure. There can be any number of reasons, and believe me we've seen a lot of wonky ones, that things are not running smoothly. Many of the hiccups have been due to folks making changes to the source SBS that places the box/OS out of spec.

Philip
I am not very familiar with System State backups. Do you have a guide to do so in a situation like this? Also, I won't lose customer data correct? Just the system files and the AD Database?
Oh, I take it a System State was not taken before the process was started then?

Was there any sort of backup done prior to running the Source Prep Tool on the source server?

That is correct, restoring the System States starts you off where you were prior to running the Source Prep Tool saving some headaches.

No SS means you are already one step down the road without being able to go back unless you do a restore of the server with the backup solution that is in place.

So, run with option 2. Clean up AD, DNS, and DSSite to get things to the point where you can at least work through the current server setup before starting again.

You can verify your cleaning:
http://support.microsoft.com/kb/216498

Philip
I do have a system state backup from a day prior to prepping the source server. It should be sufficient for restoring files prior to running the prep tool.
I am still getting the Event ID 9157:
Event Type:      Warning
Event Source:      MSExchangeSA
Event Category:      (1)
Event ID:      9157
Date:            11/5/2012
Time:            9:17:48 AM
User:            N/A
Computer:      CCCSNT02.CCCSurgery.local
Description:
Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. Wait for replication to complete and then check to make sure that the computer account is a member of the "Exchange Servers" and "Exchange Install Domain Servers" security groups.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Does this have anything to do with the hang up?
Note the error:

Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory.

Are both Replication Links showing in DSSite.msc? Should say "Auto ... " under each server's link set. Probably not or just one and not the other.

If there are problems in AD they need to be sorted first. Also, not using the default domain admin account may have also counted against you.

Philip
Only the source server has the automatically generated, the destination server is empty.
Event Type:      Error
Event Source:      NTDS General
Event Category:      (5)
Event ID:      1863
Date:            11/5/2012
Time:            4:23:59 PM
User:            NT AUTHORITY\ANONYMOUS LOGON
Computer:      destinationserver.domain.local
Description:
This is the replication status for the following directory partition on the local domain controller.
 
Directory partition:
DC=ForestDnsZones,DC=domain,DC=local
 
The local domain controller has not received replication information from a number of domain controllers within the configured latency interval.
 
Latency Interval (Hours):
24
Number of domain controllers in all sites:
1
Number of domain controllers in this site:
1
 
The latency interval can be modified with the following registry key.
 
Registry Key:  
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency error interval (hours)
 
To identify the domain controllers by name, install the support tools included on the installation  CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest.   The command is "repadmin /showvector /latency <partition-dn>".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
ASKER CERTIFIED SOLUTION
Avatar of Philip Elder
Philip Elder
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Oddly enough, the server has somehow logged into the desktop. I now have access to the SBS 2011 server. The only thing is a help screen pops up indicating a failed installation. I have attached a screen shot. All the roles, Exchange and ADDS are installed and working. I can replicate fine and the computers log into the destination server to authenticate. I am at a loss. Any ideas?
Quite frankly, it's your call.

Check the logs on the destination as they will be a lot more informative.

Would I continue? I'd be wary at best. A tear through of the entire destination server setup would be in order. "Appear to be working" and actually working during production hours are two very different things.

Philip
Can I resort back without doing a system state restore?
Most backups are full restore. Most backups do not break out the System State into a separate backup. We script/schedule that separately.

So, restore depends on the backup in use.

Philip