Exchange 2007 Update

frevere
frevere used Ask the Experts™
on
We are running Exchange 2003 SP2.  4 of our DC's are Windows 2003 SP2, this includes the schema master.  The remain 3 DC's are Windows 2008 R2.  We installed Exchange 2007 SP1 with no problems, and have been migrating mailboxes over to the new Exchange environment.  Last night, an administrator apply SP 2 and SP 3 to the Exchange 2007 servers (CAS/Hub and Mailbox).  Now all of our DC's, with the exception of the schema master, report that the schema version is different than that which is on the Schema Master.

Questions before I begin to yell and scream:
1)  Did the setup /prepareAD need to be run before applying SP2 or SP3?
2) Since these service packs have been applied to the Exchange 2007 servers, can these be reversed?
3) Since the answer to 2 is probably no, is there anything we can do to get the schema between the 7 DC the same.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Rick FeeMessaging Engineer - Disaster Recovery Engineer

Commented:
There is no reversing the extenion of the schema beyond running a restore if you have the system state, but this would be worth it.    When you run the Service Pack install it will auto run the extension of the schema.
Sounds like there might be a replication issue between your DCs you might want to check.   Also you can run setup /prepareAD on your schema server to see if that fixes it..but first I would force a replication of all the DCs to see what occurs.   Check the event logs to see if you see any issues.

Author

Commented:
Thanks Kona,

But this is what is weird.  I do not have any errors in the system logs on any of the DC's.  I somewhat figured that this could not be reversed, so I am looking for any info to resolve this issue.  Another thing that I quite do not understand, is if the schema was extended using setup /prepareAD when we first installed the Exchange 2007 servers into our Exchange 2003 environment, why would it be required to be run again if a service pack extends the schema?  

Will check the logs of the 2008 DC's  for any errors and post information.  If I do not find anything, will discuss more about running the setup command later.

Author

Commented:
replication seems to be fine.  Cannot find any replication failures or issues.  The error I receive in our monitoring tools is that the schema version on DC3.domain.com different from the schema version on Schema Master FSMO role holder DC1.domain.com.

Since replication seems to be fully functional, is there a way to repair the schema versions (or force it).  Forcing replication to occur in Sites did not seem to fix the issue.

Any other suggestions, before we discuss using the setup command?
CompTIA Network+

Prepare for the CompTIA Network+ exam by learning how to troubleshoot, configure, and manage both wired and wireless networks.

Rick FeeMessaging Engineer - Disaster Recovery Engineer

Commented:
The service packs do extend the schema.   Service Pack 2 extends the schema which is required if you want to install Exchange 2010 servers.    I have run into the issue in the past where I have extended the schema and it somehow was lost.   Basically installed on Exchange 2007 server and then attempted to install another then it screamed at me because the schema was not extended.   That domain appeared to be healthly, what it turned out to be someone screwed around the permissions and they where not getting inhereted.
what I would do is run setup /prepareAD on all the DCs directly...then see if they are all synced up.    This will not hurt anything.
Also wonder if you will have to run Setup.com /prepareschema or Setup.com /preparedomain
I would start with preparead first and see which ones are off.    Or better yes run on your Schema Master then force replication to see if they are all the same.   The Schema Master is the only writeable one.

Author

Commented:
If 4 of our 7 DC's are windows 2003, including the schema master, how do we run the setup /prepareAD against it.  Would we have to install installer 4.5, powershell, etc. on all the 2003 DC's and then run "setup /perpareAD" from the E2K7SP232 download?

Author

Commented:
Installed the installer 4.5 but DC has to reboot.  This can only be done during  our early morning maintenance period, so we will have to halt this conversation until tomorrow morning.  Thanks for all the help Kona.  Talk with you tomorrow probably Thursday morning.  

Just as thought, after running the /prepareAD on the schema master and replicating to all DC's, should we reinstall the SP2 and then SP3?  Thoughts?
Rick FeeMessaging Engineer - Disaster Recovery Engineer

Commented:
Yes that is what I would do download SP3 32bit and attempt to run...you may need to installed 4.5 installer which I believe takes a reboot.
Rick FeeMessaging Engineer - Disaster Recovery Engineer

Commented:
Ah I would just make sure you use the SP3...and that the exchange boxes are all up to SP3.
Rick FeeMessaging Engineer - Disaster Recovery Engineer

Commented:
Question is your Schema Master in the same AD site?   As one exchange server?    If not can you move the schema master to that of one of your Exchange 2007 sites DCs then run the schema update?    

Author

Commented:
Kona,

Thanks for hanging on.  I installed installer 4.5 and rebooted late Tuesday night.  I was unable to run setup /prepareAD from the 32bit SP3 until this morning, forcing replication between the DC's.  Unfrotunately, this has not resolved the situation.

To answer your question: my schema master is in the same site as my mbx and cas servers.  Can you specify how to run the schema update?  Are you referring to setup /prepareSchema?
Rick FeeMessaging Engineer - Disaster Recovery Engineer

Commented:
Try this run setup.com /ps   which is also setup.com prepareschema  run this on your schema master.  
Messaging Engineer - Disaster Recovery Engineer
Commented:
ugh I left out the /   it needs to be setup.com /prepareschema  or /ps

Author

Commented:
Extending AD schema was successful.  Trying to replicate now to see if this resolves issue.
Rick FeeMessaging Engineer - Disaster Recovery Engineer

Commented:
Cool cool...let me know the result

Author

Commented:
Kona,

Thanks for all of your help with this.  Running the prepareSchema worked.  5 of 6 DC's have replicated and the schema mismatches are cleared.  Only 1 DC (slow link) has yet to update but am confident that it will.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial