Learn Exchange the Guru way !!!


How to do the schema update of Exchange 2007/2010 or its service packs in Production

This article outlines the need to update schema in an environment before installing Exchange.

Ensure to have a system state backup done prior to the schema update. Here we have described how to do the schema update in a secure mode where you can ensure the schema master domain controller is working in a proper state then you can open the replication. This is also recommended to prepare you in the Pre-Production environment before implementing this.

  • Give the “Schema Admins” group membership to the user from Active Directory Users and computers which will be used to do this task.
  • Log on to the where you want to do the schema update
  • Determine and transfer Schema Master role.

    *Ensure you launch CMD as administrator before continuing

    • Check the schema master server
      • From a DOS prompt execute the following command:

C:>netdom query fsmo

 Record the Schema master Server. The role will need to be transferred back when the schema has been successfully extended.

  • Transfer the schema FSMO role to the domain controller you have logged in.
    • Use ntdsutil. From a DOS prompt execute the following commands:
      • C:>ntdsutil roles connections
      • Type connect to server “fqdn of the server”
      • Then type ‘q’
      • Transfer schema master
      • Quit from the ntdsutil


    • Open schema mmc and transfer operations master role to the local server
  • Copy the SP3 or the software dump for schema update.
    • Create c:tempexchange on the server.
    • Copy the dump or extract to this folder.
  • Install the prerequisite on the domain controller to run schema update for exchange 2007
    • Install windows powershell by running ServerManagercmd –i powershell
    • Install windows installer 4.5
    • Restart the server
    • Install Ldifde.exe by running ‘ServerManagerCmd –i RSAT-Adds’
    • Restart the server
  • Check the replication of the and stop replication.
    • Go to cmd and run the command “repadmin /replsum” and check for error. If no error then move ahead for next step. If there is any error related to the schema master then wait for the replication to complete or manually replicate from Active directory site and services.
    • Open the cmd with run as administrator and run the following cmd to stop outbound and inbound replication to the
      • repadmin /options serverhostname +DISABLE_OUTBOUND_REPL
      • repadmin /options serverhostname +DISABLE_INBOUND_REPL
  • Verify replication is turned off, EVENT log should have 1115 and 1113 events .
  • Do the schema update with the following steps
    • Open cmd with Run as admin and go to CD to c:tempexchange
    • Run Setup /PrepareSchema
  • Post schema update checks
    • Run diag and check for errors. Replication error will come as replication is disabled.
    • Open Active Directory Schema mmc and check it is working properly.
    • Open Active Directory users and computers then check working.
  • Open the replication traffic
    • Open the cmd prompt and run the following cmds
      • repadmin /options serverhostname -DISABLE_INBOUND_REPL
      • repadmin /options serverhostname -DISABLE_OUTBOUND_REPL
  • Go to cmd and run the command “repadmin /replsum” and check for error. Try doing manual replication from Active Directory Site and services.
  • We are done if the replication is working fine.

Prabhat Nigam

Team @MSExchangeGuru

Keywords: Update Schema in Exchange, update schema before installing exchange

6 Responses to “How to do the schema update of Exchange 2007/2010 or its service packs in Production”

  1. Anand Sunka Says:

    Hi ExchangeGuru’s,

    I am getting confused by looking at this article, why do we need to transfer schema master to other DC prior to update schema master.

    Any clarification really appreciated

    Anand S

  2. Sunder Says:

    No need to move the schema. Even I want to know why we have to move the schema master?

  3. Ilya Says:

    Some additiol details
    Before run schema master update needs isolating schema on DC that
    holds FSMO role.
    run from cmd
    repadmin /options serverhostname +DISABLE_OUTBOUND_REPL
    repadmin /options serverhostname +DISABLE_INBOUND_REPL
    or just disconect cable/disable NIC
    run /PrepareSchema
    To see if something goes

    1. successful run
    repadmin /options serverhostname -DISABLE_INBOUND_REPL
    repadmin /options serverhostname -DISABLE_OUTBOUND_REPL
    verify by running replmon to see see changes have been replicated

    2. Is not
    DC which holds Schema Master FSMO role must be decomissioned from AD and rebuild

    The Schema Master role should be seized nad homed on another controller in domain

  4. Wizkid Says:

    Hi Guys,

    Sorry, I missed to reply you guys. Let me answer here. Thank you Ilya for covering.

    Anand and Sunder: Move the schema to a DC which is in the DR datacenter and then stopping the replication this will stop the schema update to spread to all other DCs in the AD. This is to avoid replicating the corrupted or bad schema. So if your schema goes bad after the update then you just need to seize the schema master role to other DCs and run forceremoval of AD on this corrupted schema master DC. Let me know if you have more questions.

  5. Exchange 2013: Cumulative Update 6 Released « Says:

    […] Isolate schema master and update the schema as discussed here. […]

  6. Exchange 2013: Cumulative Update 6 Released | Says:

    […] Isolate schema master and update the schema as discussed here. […]

Leave a Reply




Do NOT follow this link or you will be banned from the site!