Windows, Exchange 2003 to SBS 2011 migration Sourcetool not ran

Hello,

we're currently trying to migrate a normal Windows 2003 STD sp2 including Exchange STD SP2 to SBS 2011 by using the migration mode of the SBS 2011 installation.
Everything went fine including the answer file step.
But then it's failing saying that the source tool hasnt been ran on the source server.
But we did and it ran without any errors. Even rebooting the source server didnt had effect.
I've already checked the DCOM settings on the source server according to http://msmvps.com/blogs/bradley/archive/2010/12/30/source-tool-run-but-the-server-says-it-hasn-t.aspx .
Also i've changed the Remote Procedure Call service account to local system instead of network service regarding to http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/d91bd43a-597f-43ce-9bb9-c2cc21e202f6.

Any fix would be appreciated!
Thanks in advance experts.
pentheseAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
There are three common causes for this behavior.

Cause 1: the migration preparation tool has not been run. The tool that creates the answer file is NOT the same tool that prepares AD for the migration.

Solution:  You must run the migration preparation tool. It cannot be skipped.

Cause 2: too much time has passed singe the preparation tool was run.mthe tool writes information to AD, and the setup wizard of SBS knows how stale that info is. If you ran the prep tool, had to delay your migration and do other tasks, then returned to it, this can occur.

solution: re-run the prep tool. It'll restamp AD and the setup wizard will stop complaining.

Cause 3: the source tool did not/could not see your exchange server and make the necessary change to exchange to allow the migration. This happens in larger "standard product" migrations where the prep wizard may not have access to the exchange server due to permissions related configurations.

solution: manually make the necessary change as documented here. http://technet.microsoft.com/en-us/library/7577b5bb-7270-480f-993f-bbe93debd2b8.aspx

Hope that helps,

-Cliff

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pentheseAuthor Commented:
Hello Cliff, thanks for your suggestions.

1) i've ran the sourcetool from the tools folder of the sbs 2011 disk on the source server, i know.
2) I reran it multiple times including reboots, nothing.
3) Exchange is already running in native mode, i did that since its one of the steps in microsofts migration guide.

so nothing helps from your suggestions :(
0
Cliff GaliherCommented:
Well, as I said, those are the common ones. There are less common ones as well. Let's start with the simple ones. What version of exchange (you say SP2, but left off the yer...2003? 2007?) , is it a single server, and how did you check the service pack level?

-Cliff
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
0
pentheseAuthor Commented:
Windows 2003 SP2, checked thru system properties and msinfo tool.
Exchange 2003 version 6.5 (build 7638.2 sp2), checked it thru the system manager.
It's a single DC, with 1 2008 terminal server connected as member.
0
Cliff GaliherCommented:
Try this tool. Seethed may be orphaned objects in AD or your exchange server me be in a non-standard state that would cause a 2010 migration to fail, a d the source tool is not fully reporting the details.

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11636
0
pentheseAuthor Commented:
Hello Experts,

sorry for my late comments.
I've resolved this issue by re-running the prep migration tool on the source server.
Thanks for your help
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.