In an earlier blog post I wrote about Using an F5 LTM Load Balancer for Reverse Proxy with Lync 2013. This works fine for the domains that you have entered when configuring the Lync 2013 iApp in the F5.
If you have multiple SIP domains and thus multiple Simple URLs like meet.contoso.com, meet.fabrikam.com and meet.alpineskihouse.com it doesn’t work out-of-the-box and your Lync client will fail using these URL’s.
To get this working you have to manually configure the Lync Revese Proxy iRule in the F5. To do this you first have to disable Strict Updates, otherwise updating the iRule will fail (for security reasons this makes sense).
When Strict Updates is disabled navigate to the proper iRule as shown in the following figure:
You’ll notice that the initial FQDN’s are configured here, in our example for lyncweb, meet, dialin and lyncdiscover. To get this working for other URL’s just add the other domains and you’re done (and don’t forget the lyncdiscoverinternal name).
When done, don’t forget to enable Strict Updates again, just in case…
For a project I had to create a CSV file with all Mailboxes, their UPN and their Email addresses. Not a big deal since you can use the following command:
Get-Mailbox | Select UserPrincipalName,EmailAddresses
Exporting to a CSV is a default feature in PowerShell using the Export-Csv command, like this:
Get-Mailbox | Select UserPrincipalName,EmailAddresses | Export-Csv C:\Temp\Addresses.csv
Continue reading Export Email Addresses in Exchange 2013
When deleting users in the Microsoft Online Portal these deleted users are moved to the Recycle Bin where they will be retained for another 30 days. You can see this when selecting Deleted Users in the Portal:
In the Portal it is not possible to permanently remove users, or purge deleted user accounts. This can only be done using Remote PowerShell. Please note that the Azure Active Directory Module for Windows PowerShell need to be installed. Click here to install this PowerShell module. Continue reading Purge deleted users in Office 365
On Tuesday December 9, 2014 Microsoft released Exchange Server 2013 Cumulative Update 7 and the UM Language Packs for Cumulative Update 7, 105 days after the release of the previous CU6 update. This release is a little overdue because of a last minute issue that was found moments before the original release date of CU7. As long as it improves the quality of the release this shouldn’t be a problem though.
CU7 contains fixes for issues reported by customers, including the Russian Time Zone issue and fixes for issues identified in MS14-075. Updates for MS14-075 are also available for Exchange Server 2013 Service Pack 1 and Exchange Server 2013 Cumulative Update 6. Because of the Microsoft (N-1) support policy this hotfix won’t be available for CU5.
Continue reading Exchange Server 2013 CU7
After installing an Exchange 2013 Edge Transport Server (CU6) I noticed the Microsoft Exchange Health Manager was not running. When trying to start this service the following error occurred:
Windows could not start the Microsoft Exchange Health Manager service on Local Computer.
Error 1075: The dependency service does not exist or has been marked for deletion.
Continue reading Health Manager does not start on Exchange 2013 Edge Transport Server