Information, Configuration and Advice for Microsoft Intelligence Communication.
Sycor Strategy Sales Enablement, specialized in Intelligence Communication (Teams & Modern Workplace). Microsoft Elite Team Member Redmond (PG). User Group Owner Teams & #
TrustinTech. Microsoft awarded me multiple times with MVP Office Apps & Service for my professional work and community support.
Subscribe to this blog
Follow by Email
Polycom VVX UC Software 5.1.1 Revision B is released
We are pleased to announce the most awaited Polycom®
UC Software 5.1.1 Revision B associated utilities and documents are now
available on the Polycom Product Support web pages (http://support.polycom.com) for download.
UC Software 5.1.1 Revision B is a UC Software feature for
all VVX Business media phones and SoundStructure.
Version 5.1.1 Rev. B is now certified from Microsoft for Lync 2013
Polycom UC Software 5.1.1 Revision B
offers support for the following endpoint platforms:
300/310 business media phone
·VVX® 400/410 business media phone
·VVX® 500 business media phone
·VVX® 600 business media phone
·VVX® 1500 business media phone
This release also provides support for the following VVX
·Polycom VVX® camera
·Polycom VVX® Expansion Module
What is available now on web?
·UC Software 5.1.1
Revision B ( Split & Combined)
·Polycom CAB files for
UC Software 5.1.1 Revision B
·Release Notes for 5.1.1
download UCS 5.1.1 Revision B software, release
notes & documents:
Hi all, (This is an updated version 2.2: 09.07.2015)
This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here.
there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains.
Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed
Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar. The feature depending on EWS ar…
Security zone setting error Please make sure these two domains are added to the trusted sites in IE or Microsoft Edge: https://admin.teams.microsoft.com and https://login.microsoftonline.com. If you are using other browsers, please close all browser windows and try again.
Error Code: SECURITY_ZONE_ERROR
This Error you will receive if a actual Security Setting in Edge Browser is missing and can be solved as:
You need to add the https://admin.teams.microsoft.com and the https://login.microsoftonline.com page to the trust site. As of now, the feature in adding trusted websites on Microsoft Edge is not yet available on both
Windows 10 PC and Phone. This very troublesome, but this work a round solves the problem for now.
Work a round:
Click on Start.Type inetcpl.cpl, and then press Enter.Internet Properties window will open. Select Security tab.Under Trusted Sites, click on Sites button.In the Add this website to the zone box, type in the website that you wanted to add.Click on Close button.Open…
In a special scenario, where I faced certain issue publishing the Lync Topology, where the Lync Frontend Servers are located in Sub Domain, you need to open certain TCP Ports to at least one Root Domain Controller:
If you enabled the Lync Topology, you might face this issues:
Error: The given key was not present in dictionary. Type: KeyNotFoundException
Error: An error occurred when attempting to add "computer" to "RTCGroupxxx" Type: DeploymentException
CategoryInfo: InvalideOperation: ( Microsoft.R....Core.Service) WebServer:pool.<fqdn> execution failed on an unrecoverable error.
Error: Cannot obtain the domain information for computer "Root DC fqdn". Please make sure the computer FQDN is correct.
Error: DsRoleGetPrimaryDomainInfromation failed with error "6BA".
Just missing are the requirements for Topology publishing.
If you are going to enable the Topology, you can use: Enable-CsTopology [-Confirm [<SwitchParameter>]] [-Force