- Mon, Aug 26 2019 at 1:27 am #1376070ReikoParticipant
Post count: 1Member Points: 60Rank: Level 1
- Topics: 1
- Replies: 0
I am trying to upgrade Exchange 2007 to Exchange 2013.
- AD: Windows Server 2008 R2 SP1.
- Echange 2007: Windows Server 2003 R2 SP2.
- Exchange 2013: Windows Server 2012 R2.
The procedure is performed in a test environment on a backup server.
PrepareSchema runs without any problems and the configuration objects have ex13cu23 level attributes. But when I run /prepareAD, the fun begins. It simply cannot modify objects. In the logs you see ALL objects that are affected during the installation.
/PrepareAD aborts with with this error
Microsoft.Exchange.Data.InvalidObjectOperationException: The RoleFlags property cannot be set for this object, because the version of the object must be at least 0.10 (18.104.22.168). The current version of the object is 0.1 (8.0.535.0)
I think it’s strange because it seems that /prepareAD must raise the version. And if you change the version of the attribute manually (on hundreds of objects, huh), then it claims that they are all Read-Only.
And here it seems to me that the problems is about permissions.
The user from which we perform the installation has the following rights: Domain Admin, Schema Admin, Enterprise Admin, organization management, Exchange Organization Administrators1, Exchange Install Domain Servers (well, what if).
I am grateful for any ideas, I’ve been fighting for a week. Since I am working on a backup, I tried to delete the problematic objects in ADSI and /prepareAD then creates new ones. Everything is cool, but they need to be deleted (renamed) manually, and there are a lot of them. It seems to me, Exchange 2007 will not work anymore after such manipulations. This was done for fun in order to see what happens. I’m not going to do this in my main environment.
Any advice is appreciated!0
- Mon, Nov 4 2019 at 9:08 pm #1516498IT EngineerParticipant
Post count: 9Member Points: 416Rank: Level 2
- Topics: 5
- Replies: 5
There are some ways to do it differently:
- Logon to the Domain Controllers with the Schema Master role.
- Make sure the login account is part of the Enterprise Admins, Organization Management & Schema Admins AD group.
- Right Click, then Run as Administrator on the cmd. prompt.
Then let us know how it goes.0
- You must be logged in to reply to this topic.