richardsit
asked on
Migration Prep Tool Issue going from SBS 2008 to SBS 2011
I have done a number of 2003 to 2011 migrations with varying issues and resolutions.
This is the first SBS 2008 to SBS 2011 I have done. This SBS 2008 source server was originally migrated from a source SBS 2003.
I'm using the migraqtion guide specific to 2008>2011 and I've done all the updates, BPA fixes, etc. I'm at the Prep Tool stage. ( http://technet.microsoft.com/en-us/library/gg615494.aspx#BKMK_RunTheMigrationPreparationTool )
When the prep tool gets to "Expand Schema" it puts a red X next to it, then skips the next steps (licensing estension, Exchange) on that same page and lights up the continue button. If you continue, it runs the checks for issues on the next page and says there are no problems. The tool makes it all thw ay to the last page where you check the box for making a migration file without popping up an error. No errors are logged in the event logs.
Is it skipping all this because these steps were already done by the original migration from 2003>2008? Or is there a problem in the server that needs fixing?
Is it safe to proceed to create the file and install the other server? Will we still have the 21 day limit, will it migrate at all?
This is the first SBS 2008 to SBS 2011 I have done. This SBS 2008 source server was originally migrated from a source SBS 2003.
I'm using the migraqtion guide specific to 2008>2011 and I've done all the updates, BPA fixes, etc. I'm at the Prep Tool stage. ( http://technet.microsoft.com/en-us/library/gg615494.aspx#BKMK_RunTheMigrationPreparationTool )
When the prep tool gets to "Expand Schema" it puts a red X next to it, then skips the next steps (licensing estension, Exchange) on that same page and lights up the continue button. If you continue, it runs the checks for issues on the next page and says there are no problems. The tool makes it all thw ay to the last page where you check the box for making a migration file without popping up an error. No errors are logged in the event logs.
Is it skipping all this because these steps were already done by the original migration from 2003>2008? Or is there a problem in the server that needs fixing?
Is it safe to proceed to create the file and install the other server? Will we still have the 21 day limit, will it migrate at all?
Cris Hanna
Don't proceed until you check the Functional level of the 2008 server
ASKER
OK, thanks for that. Not sure why I didn't think to check that. It's at 2003, and it won't raise to 2008.
"An operations error occurred."
I don't see anything in the event logs that corresponds, I do see the below item on a recurring basis, I wonder if this is the issue? Since they are retiring the server and it's been working just fine I hate to do an offline defragment of that have it damage the server.
HOWEVER, I do see that they have been getting NTDS ISAM 467 Errors:
Log Name: Directory Service
Source: NTDS ISAM
Date: 11/8/2013 8:34:13 AM
Event ID: 467
Task Category: Database Corruption
Level: Error
Keywords: Classic
User: N/A
Computer: <redacted>.local
Description:
NTDS (808) NTDSA: Database C:\Windows\ntds\ntds.dit: Index DRA_USN_index of table datatable is corrupted (0).
"An operations error occurred."
I don't see anything in the event logs that corresponds, I do see the below item on a recurring basis, I wonder if this is the issue? Since they are retiring the server and it's been working just fine I hate to do an offline defragment of that have it damage the server.
HOWEVER, I do see that they have been getting NTDS ISAM 467 Errors:
Log Name: Directory Service
Source: NTDS ISAM
Date: 11/8/2013 8:34:13 AM
Event ID: 467
Task Category: Database Corruption
Level: Error
Keywords: Classic
User: N/A
Computer: <redacted>.local
Description:
NTDS (808) NTDSA: Database C:\Windows\ntds\ntds.dit: Index DRA_USN_index of table datatable is corrupted (0).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, I'll check into that. Major bummer. They only have a few users, so doing it "the hard way" as I call it may be the most economical for them. It's just a lot more disruptive.
ASKER
I had to end up doing it the "hard way" creating a new domain and migrating the clients. Thanks for warning me off.