PowerShell v3 and below does not have any built in commandlets to assist with DNS resolution. Additionally even if you have a higher version of PowerShell, these commandlets will still not be available unless you are running Windows 8.1 or Windows Server 2012 R2.
This script uses NSLOOKUP to query DNS records and converts the output to a PowerShell object that can be used more easily in scripts that need to perform DNS lookups. Currently it only support A, CNAME and SRV records.
Due to the complexities of parsing text returned by NSLOOKUP, you may find that some DNS servers results may be incorrectly handled. If you experience this please let me know the circumstances and I will attempt to resolve the issue in a future release.
Download
TopNav
Friday, 21 November 2014
Friday, 14 November 2014
Lync Room System (LRS) Configuration
Only screenshots for now, will update my experiences soon as time permits.
Useful Information:
- New-CsLyncRoomSystem.ps1 – Easily Deploy Lync Room Systems
- Microsoft Lync Room System Deployment Guide
- Lync Room System won't show the Exchange Calendar
The End product:
Lync/Exchange Setup:
- Run .\New-CsLyncRoomSystem.ps1 to configure Lync and Exchange
- If you dont already have suitable user policies for LRS these will need to be created
- Ensure that you assign a UserServicePolicy with Unified Contact Store (UCS) disabled
- Assign Policies:
- Grant Conferencing Policy
Grant-CsConferencingPolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant UserServicePolicy
Grant-CsUserServicesPolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant Dial Plan Policy
Grant-CsDialPlan -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant Voice Policy
Grant-CsVoicePolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account" - Grant External Access Policy
Grant-CsExternalAccessPolicy -PolicyName "LyncRoomSystem Policy" -Identity "LRS User Account"
LRS Configuration Screenshots:
New Zealand's first Crestron Lync Room System (LRS)
First Crestron Lync Room System deployed by Lexel in Auckland, NZ - Very powerful collaboration system!!
Application Sharing fails in Server 2012 R2 due to changes in how TLS sessions are cached
If you are running Server 2012 R2, due to changes in how TLS sessions are cached, you may see the following error message in the event log. I my experience this effected a users ability to use application sharing e.g. whiteboard, polls share application etc.
Log Name: Lync Server
Source: LS MCU Infrastructure
Date: 10/15/2013 4:02:20 AM
Event ID: 61045
Task Category: (1022)
Level: Error
Keywords: Classic
User: N/A
Computer: LyncFE01.contoso.local
Description: The DATAMCU was not able to stay connected to the Front End over the C3P channel (HTTPS Connection).
The Web Conferencing Server failed to send C3P notifications to the focus at https:// LyncFE01.contoso.local:444/LiveServer/Focus.
Cause: The Front End may not be running correctly or may be unreachable over the network (broken HTTPS connection) from the MCU. Unavailability of The C3P channel affects conference controls, and can also prevent users from joining, starting conferences.
Resolution: Verify that the Front End server is running correctly and that network connectivity and an HTTPS Connection can be established between the MCU and the Front End server.
--------------------------------------------
To resolve this add the following registry key and restart your Lync services:
Note
http://support.microsoft.com/kb/2901554
--------------------------------------------
Event 61045Log Name: Lync Server
Source: LS MCU Infrastructure
Date: 10/15/2013 4:02:20 AM
Event ID: 61045
Task Category: (1022)
Level: Error
Keywords: Classic
User: N/A
Computer: LyncFE01.contoso.local
Description: The DATAMCU was not able to stay connected to the Front End over the C3P channel (HTTPS Connection).
The Web Conferencing Server failed to send C3P notifications to the focus at https:// LyncFE01.contoso.local:444/LiveServer/Focus.
Cause: The Front End may not be running correctly or may be unreachable over the network (broken HTTPS connection) from the MCU. Unavailability of The C3P channel affects conference controls, and can also prevent users from joining, starting conferences.
Resolution: Verify that the Front End server is running correctly and that network connectivity and an HTTPS Connection can be established between the MCU and the Front End server.
--------------------------------------------
To resolve this add the following registry key and restart your Lync services:
Note
- You can disable this value without compromising the security of the system. The system will revert to handling TLS sessions exactly like the sessions were negotiated in earlier Windows Server operating systems.
- Lync Server 2013 is supported by Windows Server 2012 R2 when this registry workaround is performed.
- Click Start, type regedit in the Start search box, and then click regedit.exe in the results list.
- Locate the following registry subkey:
- HKLM\System\CurrentControlSet\Control\SecurityProviders\Schannel
- Right-click Schannel, and then click New DWORD (32-bit) value.
- Type EnableSessionTicket, then press Enter.
- Right-click EnableSessionTicket, and then click Modify.
- Change the existing value to 2, and then press Enter.
- Exit Registry editor.
- Open the Lync Server Management Shell.
- Run the following Lync Server PowerShell commands in the given order:
- Stop-CsWindowService
- Start-CsWindowsService
http://support.microsoft.com/kb/2901554
Thursday, 13 November 2014
Lync Server 2015 to be renamed as Skype for Business Server
Microsoft has just announced that Lync will be renamed to Skype for Business. The underlying technology is not changing, and the 2 products will remain distinctly separate products, but features and client experience will become similar across the business and free versions.
For more information see the Office Blog. Also Matt Landis has a great summary here.
For more information see the Office Blog. Also Matt Landis has a great summary here.
Microsoft Frequently Asked Questions
What did Microsoft announce on November 11, 2014?
In Gurdeep Pall’s blog on November 11, 2014, Microsoft
introduced Skype for Business which brings together the familiar experience and
user love of Skype with the enterprise security, compliance and control of
Lync. In the first half of 2015, the next version of Lync will become Skype for
Business with a new client experience, new server release, and updates to the
service in Office 365. We believe that Skype for Business will again transform
the way people communicate by giving organizations reach to hundreds of
millions of Skype users outside the walls of their business.
Why are you renaming Lync to Skype for Business?
Skype for Business brings together the familiar experience
and user love of Skype with the enterprise security, compliance, and control
from Lync. End users get a familiar Skype experience that is as easy to use at
work as it is at home. Organizations gain reach into a network of hundreds of
millions of Skype users across the globe. And, IT remains confident they are
providing secure, reliable, high-quality communications to their organizations.
Why announce rebrand in advance of the general
availability release?
We are making this announcement now in order to give our
customers time to learn about the product and prepare their organizations so
they can deploy when the product is released. We are also using this time to
help partners build the offerings and capabilities to support those
deployments.
When is Lync actually changing to Skype for Business?
Lync will become Skype for Business in the first half of
2015 with a new client experience, new server release, and updates to the
service in Office 365.
Is there any change to the existing Skype brand used by
consumers?
No. The consumer experience that people around the world
know and love will continue to be referred to as Skype. Consumers will still be
able to use Skype the way they always have – with the same user account,
contacts, user interface and functionalities that they have always used.
When will there be future announcements about Skype for
Business?
We will be launching the new brand and product in the first
half of 2015. We will keep our customers informed. Lync is becoming Skype for
Business – First Half of 2015
What should I do now that I know that Lync is becoming
Skype for Business in the first half of 2015?
- Now that you know Lync will becoming Skype for Business in 2015, we recommend that you:
- Download the Skype for Business – Partner Kit from the Skype for Business Partner Kit in the Partner Marketing Center on the Microsoft Partner Network.
- Review all of the materials in the kit to understand why the brand is changing, when it takes effect in your area, and what it means for customers.
- Contact customers using the email template provided in the kit to let them know that Lync will become Skype for Business in the first half of 2015 and then set up calls or meetings to present the Skype for Business customer presentation.
- Register and join us at our Office 365 Summits starting in January 2015 to learn what you need to know to help your customers deploy and adopt Skype for Business.
What should I say to customers about the new brand?
Share your enthusiasm for announcement. Tell customers about
the value Skype for Business will bring to their organization. Microsoft is
bringing together the best of Skype and Lync without losing any of the
features, security and manageability that they care about. They will see
further adoption of unified communications in their businesses and the cost and
efficiency benefits that go along with that because of the familiar user
experience that hundreds of millions of Skype users engage with every month. Furthermore,
this change truly connects them to the vast Skype network which includes many
of their customers and partners.
It’s important to reassure customers that the features they
care about and use the most in Lync are not going away. Remind them that as a
Microsoft partner, your close connection to Microsoft best positions you to
continue meeting all their development, deployment, and service needs as this
product evolves.
When do I use the Skype for Business name and logo in my
marketing materials, website, and customer communications?
Lync is the current product in market and the materials do
not change at this time. Partners should not use Skype for Business logo/brand
prior to the next release, which will be available in first half of 2015. Our partners
will be provided the Skype for Business brand guidelines in the coming months
in time for the new release. It will outline when and how to apply the Skype
for Business name and logo to your materials and communications. Do not use
the brand or logo prior to receiving the brand guidelines. Lync is becoming
Skype for Business – First Half of 2015
Are you still committed to delivering Enterprise Voice in
the Cloud?
Absolutely. We remain committed to our roadmap including the
future delivery of enterprise voice in the cloud.
How will the product experience for Lync change when it’s
Skype for Business?
The best features of Lync and Skype have been combined in a
Skype-inspired user interface. The user experience is more tightly aligned
between Skype for Business and Skype so the features are similar and intuitive
whether you are in a work environment or communicating with friends and family.
- Skype for Business will include other new features such as:
- Familiar Skype icons for calling and video
- A call monitor to keep active calls visible while switching between apps
- Enterprise connection with the Skype network with IM, audio, and video
- A simpler upgrade and patch process for Skype for Business server
- and more…
Will Lync users lose any functions or features when the
product becomes Skype for Business?
No. Skype for Business will deliver the same features and
functionality as well as control, security, and reliability that enterprise
customers expect. For instance, Skype for Business Admins will be able to
control when and how the users interface is displayed for their users. This
additional control means they can deliver Skype for Business on their terms.
Can I try out Skype for Business before it becomes
available?
We have nothing to announce at this time, and will keep
customers informed as more information becomes available.
Monday, 3 November 2014
Access Denied to Address Book Folder
After installing a new Lync 2013 Standard Edition server, the event log continually presented the following error:
---------------------------
Address Book Server has encountered an unexpected exception.
Exception: Access to the path '\\LyncServerFQDN\LyncFileShare\1-WebServices-2\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000' is denied.
Exception Type: System.UnauthorizedAccessException
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.ABServer.ABServer.ReadContactsFromSqlAndWriteToOutput(NormalizeRuleSet normalizationRules, SqlConnection sqlConnection, List`1 sinks)
at Microsoft.Rtc.ABServer.ABServer.Synchronize()
Cause: Internal Error
Resolution:
---------------------------
Address Book Server has encountered an unexpected exception.
Exception: Access to the path '\\LyncServerFQDN\LyncFileShare\1-WebServices-2\ABFiles\00000000-0000-0000-0000-000000000000\00000000-0000-0000-0000-000000000000' is denied.
Exception Type: System.UnauthorizedAccessException
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.ABServer.ABServer.ReadContactsFromSqlAndWriteToOutput(NormalizeRuleSet normalizationRules, SqlConnection sqlConnection, List`1 sinks)
at Microsoft.Rtc.ABServer.ABServer.Synchronize()
Cause: Internal Error
Resolution:
Contact Product Support Services.
---------------------------
To resolve the issue I had to manually add the following local system groups to the folders sharing permissions:
LOCAL\RTC Local Administrators CHANGE,READ
LOCAL\RTC Local Config Replicator CHANGE,READ
LOCAL\RTC Server Local Group CHANGE,READ
LOCAL\RTC Component Local Group CHANGE,READ
After adding these and running Update-CsUserDatabase I immediately could see the creation of the expected Address Book files.
Checking other deployments these permissions were not listed, so I am unsure why in this case they were required.
Subscribe to:
Posts (Atom)





























