Link to home
Start Free TrialLog in
Avatar of trivin
trivin

asked on

SBS 2011 migration failed on exchange

Hi Experts,

I am busy with a sbs2011 migration.
We have a running sbs2008 (migrated from sbs2003 a year ago).

I made a fresh copy of the sbs2008 in vmware esxi.  In the same vmware server, I installed the sbs2011 in migration mode.
Everything went fine.  After the installation I get an error about Exchange.

I fully updated the sbs2011 server, with the service packs and updates for exchange.
Then I tried to repair the exchange installation, it hangs on a error on the hub transport role.
I removed the role, and tried to install it again.  Same problem.
In the setup logs, I get this error:

The following error was generated when "$error.Clear();
      set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController
" was run: "Property IsHubTransportServer can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0)

I see alot of problems/solutions on the internet about the hub transport failing.  But theire all about the ipv6.  And it's still enabled here.

Does someone has an idea what to do?
ASKER CERTIFIED SOLUTION
Avatar of Glen Knight
Glen Knight
Flag of United Kingdom of Great Britain and Northern Ireland 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
Avatar of trivin
trivin

ASKER

The sbs2008 is in good health.
The migration preparation tool, didn't find any errors also.
I read somewhere, that the setup fails on Hyper-V systems with some virtual disks.
Could this also be the reason in vmware?
I have done 14+ migrations in VMWare and not had any problems.
If you have multiple NIC's associated with the SBS2011 or SBS2008 virtual machines then the setup will fail
Avatar of trivin

ASKER

hmmm!
I have one nic on the sbs2011.
But 2 nic's enabled on the sbs2008 vm.
That could be the problem then?

So is it enough to remove the nic from the vm, and try to do the migration again?
SBS2008 and SBS2011 are only supported with a single NIC, remove the second one from the SBS2008 server.  if you can roll back to remove all the configuration then great if not then you will need to cleanup the SBS2008 server otherwise the migration will fail again.
Avatar of trivin

ASKER

I made a snapshot before the migration.  So I can roll back from before the migration.
I keep this thread open, till it's installed succefull.
SOLUTION
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
Avatar of trivin

ASKER

@ demazter, you did several migrations?
So is it whise to do the following?

I want to make a virtual machine of the running sbs server. When it's converted, I want to format the original server.And do a migration from the sbs virtual machine to the original server.

Is that ok?
I want to do this method, because I want to re-use that server, because it has good hardware.
That can be done if you have appropriate hardware for the virtual image which as it's 32bit shouldn't be a problem.

Just make sure the Virtual machine is working properly before you format the original server.
Avatar of trivin

ASKER

It's now also running in a vm (for a test migration).

Ok, I check if it's running fine.
Thanks guys!
Avatar of trivin

ASKER

so the problem was, I used the old server name, from an older migration..
Changed the name, and now it's installing fine.
So like demazter told me, check the base config of the source server.