Hi all, My environment is like this: 2008 R2 Standard which hosts 2008 R2 Enterprise using Hyper-V. On the Enterprise (the Virtual one) I`m trying to install Exchange 2010. The problem is that I have several problems with the Hub Transport Role - first I had to use KB980050 to fix the first one. However - the next message I see is this one: [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).". [03/16/2010 16:17:12.0197] [1] [ERROR] 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). Everywhere I see discussions on forums about disabling IPv6 but it didnt work for me. Also I cant understand why is IPv6 related as it apparently is a Component Version issue. Any comments would be greatly appreciated!

Is this the first Exchange server you setup in your environment? What is your forest and domain functional level? regards, Peter

It`s Clean Installation with nothing added (maybe only the Microsoft Office 2007 Filter Pack which was required by the Exchange setup). I tried with 2008 R2 domain/forest level and got this problem, also I`ve tried with 2003 functional level for domain and forest on a completely different Hyper-V virtual machine - but it`s the same. I still cant understand what it is about: [ERROR] 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). Which is that $RoleFqdnOrName object ? Have I missed to add some Role Service or something in the Server Configuration ? Thank you http://blackandwhitebg.com

Have you installed all prereqs? http://technet.microsoft.com/en-us/library/bb691354.aspx Try to run the schema update before you run the installation to see if that goes thru.. Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

I Agree with Jonas. You should run setup /PrepareAD [/OrganizationName: <organization name> ] This will prepare your Active Directory so that you can install Exchange!

Thank you. I had missed some of the prereqs as I had installed them manually using the Server Manager. This automated script with the Add-WindowsFeature cmdlet helped in this case. One final question - To reinstall I had to setup a completely new Virtual Machine, because Uninstallation didnt work after the setup failure. How do we avoid reinstallation of everything in real non-virtual environments ? Thank you.http://blackandwhitebg.com

You can install a new virtual server with same name and ip address and then run setup.com /Mode:RecoverServer Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

For any who come across this, I highly suspect the answer is that the Hyper-V VM must have time synchronization unchecked.