SBS 2003 - SBS 2011 migration

Which guide are you following?

I have used Demazter's for ALL the migrations I have performed and have never had a problem, never run into this problem and all have gone perfectly smoothly.

If you haven't read it and are not following it, I would heartily recommend it (even over the Microsoft guide).

https://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_4234-Migrate-Small-Business-Server-2003-to-Small-Business-Server-2011.html

I'm using Microsoft's migration document, have read it thoroughly beginning to end.

There doesn't seem to be a reference to the Exchange Pre-deployment Analyzer in the guide you reference. It is in the MS guide. Have you run this analyzer as part of your migrations?

Never run it - never had a problem.

Have you or anyone else ever had an Exchange 2007 server on your network (even for testing)?

The "The Active Directory schema will need to be upgraded (via the /PrepareSchema switch of Exchange Server 2010 setup) before Exchange 2010 servers can be installed into the organization" part will be automatically updated anyway, so that isn't anything to worry about.

There has never been an Exchange 2007 server on this network. I think you're right that I can ignore it but am going to do a little more research.

I'll check the MS guide and fire up the tool on a customer's SBS 03 server to see if it has the same issue, which I know hasn't seen an Exchange 2007 server.

BRB

I get the following:

Exchange 2007 Compatibility:
There are no Exchange 2007 servers in the organization. If you prepare the Active Directory with Exchange Server 2010, you will not be able to subsequently install Exchange Server 2007. (Who cares?)

Windows Server 2003 Forest Functional Mode or higher is required:
The forest functional level of the Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2010, the forest functional level must be at least Windows Server 2003 native. (The Migration process does this automatically)

Active Directory Schema Upgrade is Required:
The Active Directory schema will need to be upgraded (via the /PrepareSchema switch of Exchange Server 2010 setup) before Exchange 2010 servers can be installed into the organization. (The Migration process does this automatically)

Link State Suppression is not enabled:
Before introducing Exchange Server 2010 into this topology, the 'SuppressStateChanges' configuration parameter should be set to '1' on server dmssvr01.DMSLGW.local. This parameter is essential if you plan to create multiple connectors to the dedicated Exchange 2010 routing group. (Not something I have ever had to change for a migration, so may get done automatically).

Your question states you get a warning about Exchange 2007, yet the warning is about Exchange 2010 - are you reading everything properly?  Did you get your versions mixed up?

No, I didn't get versions mixed up. Initially I did get that error about link stat suppression and made the registry change. That error then went away, replaced by the one warning from my initial post. I suspect making that registry change made the system think I had 2007. I'm moving forward with the migration, currently installing on the new server.

I'm giving this a grade of good as opposed to excellent because I think the answer was more of a guess. I was able to go on with the migration so the error was not an issue.