The Subscriber and AutoAttendant are offline in Lync and when you call either of them the call is dissconnected.

In my senario the Voip Security on Exchange UM Dial Plan was set to “SIP Secured” and not “Secured”

A new install of Lync and Exchange. Enabled enterprise voice and Unified Messaging. Useres never get missed call notifications in their mailbox. On the exchange server there where several entries in the eventviewer complaining about smtp and voice mail files.

Solution to this is to verify that the receive connector that exchange itself uses is enabled With “Exchange Server authentication”. Most common issue is that som admin has created a relay connector and defined a IP subnet in the “network” tab, and this IP network contains the IP address of the exchange server. You can verify witch connector that is used by Exchange by examining the smtp log file.

Update: 

Also verify that the CA trust list is not to large as i pointed out in my Lync post : https://www.vatland.no/post.aspx?id=24303d6b-a29e-432c-b448-3dac2779bd14

When you install Exchange 2013 into a Exchange 2010 organization and try to access https://exchange2013cas/ecp  – Exchange server will show Exchange 2010 ecp. To access the Exchange 2013 ecp you will have to specify your Exchange version in the URL.

https://exchange2013cas/ecp?ExchClientVer=15

Reference: http://technet.microsoft.com/en-us/library/jj150562(v=exchg.150).aspx#access

This is my tool to display Exchange Autodiscover information. I wanted to verify that Exchange published the information that I had entered into the management console and shell. It is written i C# on Windows 8. It requires .NET framework 4.5 and 64bit. 

ExchDiagSetup.zip (1.39 mb)

Finally the long awaited Exchange 2010 sp3 is released.

http://support.microsoft.com/kb/2808208/en-us

We can now start to migrate our Exchange 2010 to Exchange 2013.

This could be usefull when moving users and you would like to free up some space.

# Permanently delete disconnected mailboxes.

List disconnected:
Get-MailboxStatistics -Server MAILSERVER | ?{$_.DisconnectDate -ne $null} |ft Displayname,Identity,Disconnectreason

Remove by using mailbox database and mailbox identity.
remove-storemailbox -Database MAILBOXDATABASE -Identity “8be4d91d-6380-4dcd-b5a4-d003f4ec3f14” -MailboxState Disabled

After installing Exchange 2013 I got this “Server Error in ‘/ecp’ Application” when entering “Exchange Admin Center” web page.

“Could not load type ‘Microsoft.Exchange.Managment.Security.AdfsFederationAuthModule'”

Solution: Exchange 2013 did not install the “Windows Identity Foundation 3.5” automatically. So all there is to it, add this feature.

Make sure the required files are present in exchange bin folder:

(These can be copied from another Exchange or from install media – Version at the same servicepack level.)

• – CommonConnectFunctions.ps1
• – CommonConnectFunctions.strings.psd1
• – Connect-ExchangeServer-help.xml
• – ConnectFunctions.ps1
• – ConnectFunctions.strings.psd1
• – RemoteExchange.ps1
• – RemoteExchange.strings.psd1

Create a New shortcut on desktop or somewhere else:

Command:  

   C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -noexit -command “. ‘C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1’; Connect-ExchangeServer -auto”

Start in : <blank>

Name : Exchange Management Shell

Change the icon : Paste it into the Browse text Box and press enter. Select Icon.

%SystemRoot%\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\PowerShell.exe

Atle

When doing some exchange powershell you would probably get this error or somthing like it sooner or later:

Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. This user is allowed a max
imum number of 18 concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user. For more information, see the about_Remote_Trouble
shooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
    + FullyQualifiedErrorId : PSSessionOpenFailed

Workaround for this is to recycle the MSExchangePowerShellAppPool Application Pool

The eventlog entry 1221 is gone. Now you run powershell.

Get-MailboxDatabase -Status | fl identity,availablenewmailboxspace

[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\new-TestCasConnectivityUser.ps1
Please enter a temporary secure password for creating test users. For security purposes, the password will be changed r
egularly and automatically by the system.
Enter password: **********************************
Create test user on: Server1.test.local
Click CTRL+Break to quit or click Enter to continue.:
CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requi
rements.
At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\new-TestCasConnectivityUser.ps1:267 char:31
+       $result = CreateTestUser <<<<  $exchangeServer $mailboxServer $securePassword $OrganizationalUnit $UMDialPlan $
UMExtension $Prompt
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,CreateTestUser

This error is because you have several OU’s named “Users”. Edit the scrip to use a spesific OU, i.e “CN=Users,DC=test,DC=local”