Knowledgebase
OAB Migration failed
Posted by Eric Hanig on 14 January 2015 07:35 PM

If you have migrated from Exchange 2010 to 2013, and have found that the OABs are not working, you will need to do the following.

 

Delete the Old OAB in Exchange, and then create the new one in Exchange 2013. Once that is created, use our tool to execute scripts making sure to change the parts in yellow to match the OAB your working on.

To execute the script, go to the engine and to the provisioning client and run it there. This should resolve your issue.  Be sure you change the parts in yellow.

 

<?xmlversion="1.0"encoding="utf-8" ?>

<requestdebugMode="Detailed">

  <data></data>

  <procedure>

    <procedureSteps>

      <procedureStep>

        <stepMethod>

          <providerTaskproviderName="Active Directory Provider"taskName="SetOtherWellKnownObjects"instance="local">

            <providerData/>

            <taskData>

              <data>

                <server>DC01.hosteduc.biz</server>

                <distinguishedName>OU=OA2,OU=OA,OU=Hosting,DC=HostedUC,DC=org</distinguishedName>

                <otherWellKnownObjects>

                  <otherWellKnownObject>

                    <guid>D22DFCC5B73645E99E16C9AD3D61F34F</guid>

                    <distinguishedName>CN=OA2 OAL,CN=Offline Address Lists,CN=Address Lists Container,CN=HostedExchange,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=HostedUC,DC=org</distinguishedName>

                  </otherWellKnownObject>

                </otherWellKnownObjects>

              </data>

            </taskData>

            <resultDestinationdestinationRoot="thisResult"/>

          </providerTask>

        </stepMethod>

      </procedureStep>

 

    </procedureSteps>

  </procedure>

</request>

(0 vote(s))
Helpful
Not helpful

Comments (0)