No UPN is listed in Exchange 2010 after promote Child Domain

Here I am covering this topic while doing all everything such Exchange and Active Directory.

In my scenario, there is a parent domain called and the exchange server is installed under this domain. Then the organization is adding the child domain controller such as Management and its domain is A Management’s domain controller is located in the site office and they just wanted to use the exchange server that was already had in parent domain

When the administrator tried to create mailbox for new users that was sitting in child domain of, they encountered the problem. the UPN is not appeared as figure below:




what is the solution?


Here is the thing, we need to update the domain using the Exchange Server Installation Media and run “the setup /preparealldomains” in the exchange.

For example figure below. Make sure the preparations are fully completed.


After it is completed. Then try open the console and create mailbox for using that sitting under the


Integrate OWA 2010 and Lync IM

Last few days, I have configured Echange 2010 Outlook Web App (OWA) to integrate the Instant Messaging (IM) of Lync Server 2010.

The objective is to enable communication such as chat with Lync Client and OWA Instant Messaging.

You can also refer this link below:

I also want to demonstrate on how I configure.

On Your Exchange Client Access Server, do the following things below:

  1. Install the Unified Communication Managed API 2.0 Core Runtime (64 bit) in your Exchange Client Access Server (CAS). Click this URL link:
  2. On your Exchange Client Access Server, download the Microsoft Office Communication Server 2010 R2 Web Service Provider. click the link . Then, it run the file CWAOWASSPMain.msi and it will extract the files.
  3. Go to the folder that you’ve extracted the files and run CWAOWASSP.msi
  4. Download again the hotfix of OCS 2007 R2 Web Service Provider Hotfix KB961256 ( and install it in the CAS Server.
  5. Download and install the hotfix Unified Communication Managed API 2.0 Redist Hotfix KB 2647091 (
  6. Once you have done that, Open the Exchange Management Shell
  7. Run the command Get-ExchangeCertificate  |fl Services, Thumbprint . Copy the thumbprint
  8. Run Get-OWAVirtualDirectory. Please make sure the OWA is currently configured with certificate.
  9. Then run again Get-OWAVirtualDirectory and Set-OWAVirtualDirectory using pipeline. Make sure the thumbprint that you’ve copied is pasted on the command like below: 
  10. While no error is prompted, you type iisreset to restart the IIS service. 

On Your Lync Server, please do the following below:

  1. Open Up Lync Server Topology Builder on the lync server and choose to Download Topology from existing deployment. Then save the tbxml file.
  2. Expand the site, and go to Trusted Application Pool.
  3. Right-click and create New Trusted Application Pool. in the FQDN column, type your exchange FQDN and choose Single Computer Pool. click Next.
  4. Select the Next Hop Pool and site name of the Lync Server 
  5. Then, right click the Site and Publish the Topology.
  6. Open Lync Management Shell and run the command below. “New-CsTrustedApplication -ApplicationId OWAID -TrustedApplicationPoolFQDN -Port 5059”.
  7. Run this comman Enable-CsTopology

Verify the successful Configuration

To verify the successful Configuration that you have done above, simply open your Outlook Web App (OWA) and you will see IM integration as the screen shot below:

Troubleshoot the Problem

From my first configuration, I admit that the IM integration is not working well and the contact of IM in unavailable. So I run the Lync Server Logging Tool and monitor the log.

Here is what I found on SIP Stack.

I went through the Social TechNet Forum and search for the solution. I search through the similar problem and the solution is the SSL Certificate. Then I reissue the SSL certificate of OWA and assigned back to the OWA IIS and reconfigured the OWA using Powershell.

Finally the IM Integration works well.

See The Differences between Public OWA and Internal OWA?

please see at the bottom at the Public OWA. I used Forefront Threat Management Gateway 2010 to publish OWA. You need to have a cetificates installed at the personal certificate (using MMC) and enter the private key. the certificates can be obtained from your OWA exchange server at Client Access under Server Configuration.



The public webpage looks like below.