I've got the: Property IsHubTransportServer cannot be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. Current version of the object is 0.0 (6.5.6500.0). Error when I try to install an Exchange 2007 server in a domain that previously had Exchange 2003 in it. I've seen various stuff including a KB on removing attributes using ADSI edit, could someone just quickly point me to the actual answer and save me some time trying all of this? I already tried using setup /removeorg, that didn't seem to do anything, setup just said it had removed some stuff from the forest.

I already tried using setup /removeorg, that didn't seem to do anything, setup just said it had removed some stuff from the forest. Do you have Exchange 2003? Did you remove the ORG?Gulab | MCITP: Exchange 2010-2007 | Lync Server 2010 | Windows Server 2008 | Skype: Exchange.Ranger | Blog: www.ExchangeRanger.Blogspot.com

No, there is no Exchange 2003 server, not a physical box anyway but when I do get-organizationconfig it says the hub transport is version 0.0 as above, so there's obviously remnants of it floating around in AD.

Hi cybershooters, Did you old Exchange 2003 Server use the same computer account as this Server (used to install Exchange 2007)? I have seen a similar issue that customer has an old Exchange 2003 Server with the same computer account as the server (which used to installed Exchange 2007), When he try to install Exchange 2007, get the same error with you. This may when Exchange 2003 removed, still has the server object in AD. He has resolved the issue by follow steps: <1>Remove the Server from the domain. <2>Deleted the computer account for the Server. <3>Reinstalled windows, joined the domain with the same computer name as before and then install Exchange . Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

That was the first thing I thought of and it didn't work. What I did was to go into configuration in ADSIEdit and go to CN=Services, CN=Microsoft Exchange and delete the organization container. After I did this, Exchange 2007 setup succeeded without errors. However, when I do get-organizationconfig it still comes up with ExchangeVersion: 0.0 (6.5.6500) which obviously isn't correct. It doesn't appear to be causing a problem at present but I have no doubt it would if I tried to do a disaster recovery setup. Is there a way of manually changing that attribute, I can't seem to find it using ADSIEdit? Plus it also comes up with an error when applying a mailbox policy, says it can't be applied to the old 2003 system attendant mailbox so some details of that must still be floating around in AD as well. Is that something I could just delete?

Hi cybershooters, Did you check the Exchange Setup log? If you didn’t get any error when you install Exchange Server, ExchangeVersion: 0.0 (6.5.6500) may not the problem: I checked in my labs : Exchange Server 2007 SP3: installed on Windows 2003 (in a domain without installed any other Exchange Server ) The result I get is also ExchangeVersion: 0.0 (6.5.6500.0) I then checked on my Exchange Server 2007 SP2 (also in a domain without installed any other Exchange Server) The result still is ExchangeVersion: 0.0 (6.5.6500.0) Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

I can't see anything in the log that seems relevant. Have you tried doing a disaster recovery on either of your test environments?

Yeah I've also set up a test environment that never had 2003 and it comes up with ExchangeVersion: 0.0 (6.5.6500), which is bizarre... anyone know why?

Hi cybershooter, I think this is different from the version of Exchange Server. If you want to check the version of Exchange Server, you can use this command: Get –ExchangeServer –identity ServerName Build numbers and release dates for Exchange Server http://support.microsoft.com/kb/158530 Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com