Link to home
Start Free TrialLog in
Avatar of russus
russusFlag for United Kingdom of Great Britain and Northern Ireland

asked on

can't update to Exchange 2010 SP2

Experts,

I am trying to update Exchange 2010 from SP1 to SP2.

current setup in simple words; master schema on domain.local and exchange 2010 is on child.domain.local.

when i run the setup, error: this computer is not in the same AD as the Schema master.

is there a way around this or do i have to run setup /prepareSchema on a PC under domain.local?

thank you
Avatar of Iradat Siddiqui
Iradat Siddiqui
Flag of India image

it looks like the domain trust issue between the parent domain and child domain. Fix the DNS, DS replication and Network.
Avatar of russus

ASKER

but the exchange box is member of the child domain. isn't it a normal behaviour to have this error message? because it's true the schema master is on the root domain and the exchange is on a child domain
But one has to make sure that DS/DNS replication is working just fine between the parent and child domain.
Avatar of russus

ASKER

i get "Active directory has replicated the connections".
checked dns on both DCs, look identical
Why only SP2? Why not SP3?
If you have multiple domains then you need to prep all of the domains. Therefore copy the SP3 media to the master domain with the schema master, run prep from the command line. Then do the same with any child domains that you have.

Only then run setup.exe

Simon.
Avatar of russus

ASKER

Hi Simon

i can't remember the exact reason why i chose SP2 and not SP3 but i think there was a concern and needed to do something i cannot do in my current environment.

i'll tell you exactly what i did.
i have domain.local and child.domain.local
the exchange 2010 is on a member server in child.domain
the schema master is the 2003 server and ONLY box in Domain.local.

steps i took below:

1- tried to install the sp2, i got "this computer is not on domain as the schema master."
2- i joined a win7 64bit laptop to the domain.local so i could prep schema and AD because i don't have a 2008 server
3- i did the setup /prepareschema on the win7 laptop, it completed smoothly.
4- i tried the setup /prepareAD i got errors.
5- i did setup /prepareDomain in both domains

please see error attached when i do the setup /prepareAD .

i did a small search and saw comments regarding the default email address policy, so i did what was suggested which is, edit the recipient policies in ADSI edit. there are 2 policies; "default policy" and "MyDomain.com" policy so i changed numbers on the msExchPolicyOrder so that MyDomain.com policy is the default.

tried to run the prepAD again no luck.

Please help
thank you
error.txt
ASKER CERTIFIED SOLUTION
Avatar of Iradat Siddiqui
Iradat Siddiqui
Flag of India 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
Both Sp2 and SP3 require schema changes, I cannot think of anything else that would cause you to want to install SP2.

How did you install Exchange originally, because the root domain must have been prepared for Exchange to be installed?

Default policy is usually the lowest.
Was this a migration from a previous version of Exchange do you know?

Simon.
Avatar of russus

ASKER

Simon, i got this from exchangeserverprodotcom
"If you are planning to upgrade your Exchange 2010 servers to SP3 you should be aware that there is an Active Directory schema update involved. If that is a concern for your environment, but you still want the bug fixes and security updates, you might consider sticking with Service Pack 2 and applying Update Rollup 6 instead."

last year i migrated from 2003 to 2010 and i used a 64 bit laptop to do the schema and AD preps. i don't know why it's not working when upgrading to SP2

 iradatsiddiqui, thank you v much for that.
i ran the first command, i got the policyname.com as true
i ran the 2nd command, it doesn't find "Default Policy".

maybe i should just rename MyPolicy.com to default policy ?
Avatar of russus

ASKER

prepareAD completed :)
iradatsiddiqui's solution put me in the right direction. i created a new policy and named it default policy. didn't work at first because child.domain.local was not in the accepted domain list. added that, tried again and we have a lift off.

thank you v much