Powershell module for DNS of Windows 2008R2

Here is a module that you can use on legacy servers http://dnsshell.codeplex.com/, once instaled you can run as example get-dnsrecord

But if you have Windows 2012 R2 you do not need external module anymore, use build-in Get-DnsServerResourceRecord and enjoy.

How to enable Modern Authentication in Exchange Online

https://social.technet.microsoft.com/wiki/contents/articles/32711.exchange-online-how-to-enable-your-tenant-for-modern-authentication.aspx

MultiFactor authentication onCloud or OnPremises switch by powershell

https://blogs.technet.microsoft.com/bulentozkir/2016/05/01/office-365-customers-who-have-adfs-installed-can-do-simple-filtered-mfa-using-adfs-claim-rules/

PSTN gateway not recognised by Lync 2013 mediation

Getting an error with SIP trunk TLS after deployment of new SBC:

Log Name:      Lync Server
Source:        LS Mediation Server
Date:          8/16/2017 12:36:43 PM
Event ID:      25075
Task Category: (1030)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xx
Description:
Mediation Server encountered an invalid setting that has been ignored.

Setting: PSTNGatewayService Fqdn: xx;trunk=yy
Reason: [Config] A Gateway Peer's (xx) internal settings are not configured correctly: NextHopPort = 5067, TransportType = TLS, NextHopIpAddress = N/A

Cause: Settings configured incorrectly.
Resolution:
Reconfigure the specified setting.


Double checking certificates, DNS, topology did not reveal any discrepancy, all looks correct. Do I need restart server?

The solution was to re-publish same topology second time, this time Mediation refreshed it's internal tables correctly and let SIP trunk to get up.

Exchange 2016 UM telephone extension dial plan

If you integrate Avaya or Cisco to Exchange 2016 UM, you may be surpised that a Dial plan with Tel. extension can't be associated with a Exchange 2016 server. Error message "The dial plan can’t be associated with the Client Access server. Only SIP URI dial plans can be associated with Exchange 2013 Client Access servers".  Do not worry, server will still respond and use this dial plan:


https://social.technet.microsoft.com/wiki/contents/articles/23416.exchange-2013-unified-messaging-with-cisco-unified-communication-manager.aspx

https://technet.microsoft.com/en-us/library/bb125151(v=exchg.150).aspx

ADFS 3.0 from Windows 2012 R2 does not support TLS 1.2 out of box

Surprise!  Look for details here: https://support.microsoft.com/en-us/help/3194197/considerations-for-disabling-and-replacing-tls-1-0-in-adfs

The article will explain how to enable TLS 1.2 especially that we know that TLS 1.0 is obsolete and wil be dropped by Microsoft in 2018.