Lync 2010 mobile can’t connect to the server. it may be busy or temporarily unavailable

Dears, I would like to share the following article with you,

In the last week we have renewed the Lync 2010 internal and external certificates, internal and external desktop client working normally without any issue, but the mobile client can’t connect.

General Info.

Mobile application requests for Mobility Service.

mobile application requests for Mobility Service

PS Both the internal Mobility Service URL and the external Mobility Service URL are associated with the external Web Services FQDN. Therefore, regardless of whether a mobile device is internal or external to the network, the device always connects to the Microsoft Lync Server 2010 Mobility Service externally through the reverse proxy.

Issue symptoms

Lync Mobile users get the following Error message “can’t connect to the server. It may be busy or temporarily unavailable” while trying to connect.


Investigation result

· After reviewed the mobile client logs and simulate the test by the test Lync connectivity analyzer, I have found that An error occurred while mobile client sending the request to the Lync proxy server even through port 443 or 80.

. In my scenario we don’t have a reverse proxy, instead of that we using the Lync Frontend servers as a proxy server at the same time, it has a two IPS on the same NIC,22 for internal services and,51 for the proxy server.

PS. This is not supported scenario, you must use a separate server for the Revproxy if you are going to use software like TMG or any other else, and that if you don’t have a reverse proxy device.

. We use the HW load balance for High availability for the internal and proxy services.


In my case the IIS web service component of the internal and external sites was missing the binding configuration, so that if you have the same case with the same scenario all you want to do is assign the proxy IP to the external site with port 443 and public cert, and assign the internal server IP to the internal site with port 443 and internal cert.


Your Account has been disabled after reconnect a Disconnected Mailbox in Exchange Server 2010

Dears when an Exchange 2010 mailbox has been disabled it becomes a disconnected mailbox, may be you need to restore this mailbox and suddenly after restored you get the above message when you try to login through OWA “your account has been disabled”  but the mailbox already enable and to be sure you can list the disconnected mailboxes run the following PowerShell command

Get-MailboxStatistics -Database DBName | Where { $_.DisconnectReason -eq “Disabled” } | Format-List LegacyDN, DisplayName, MailboxGUID, DisconnectReason

Surprise!! Now the mailbox is simply disabledSad smile You have been guided to enable this mailbox by the following PowerShell command,

Enable-Mailbox -Identity UserName

Another Surprise !! you got the following Error message “This task does not support recipients of this type.” Sad smile And after Check the user type by the following PowerShell command

Get-mailbox UserName|Fl Recipient* you got the following results that mean no problem with the user type.

RecipientLimits            : unlimited
RecipientType              : UserMailbox
RecipientTypeDetails : UserMailbox

In this case if you try to export the user mailbox you will get the following error message: “Couldn’t connect to the source mailbox”

5-6-2014 9-53-48 AM

And this message let you make check on the MAPI if enable or not for this user by the following PowerShell command:

Get-CASMailbox -Identity UserName

5-6-2014 9-51-22 AM



And you found the MAPI enabled True that mean no problem by MAPI as the above figure.


At the End you need to say Haaaaaaa7Smile And solution is the following PowerShell Command after run it everything will be working normally SmileSmileSmile

Get-mailboxdatabase | Clean-mailboxdatabase