Showing posts from 2013

"[File Name].pptx can't be converted for presentation because PowerPoint is not installed. Please install PowerPoint and try again."

With Lync 2010 and Lync 2013, some user run into an issue while they try to share a powerpoint presentation: This is regardless if a Office Web App server is installed or not (as Lync 2010 do not support OWA) The problem is mainly a client issue and should be seach for any server issues. That why in troubleshooting, it is necessary that you identifiy if you have general or partelly issues. You will receive the following error on a client: Solution: To fix the problem you will need to edit the [HKEY_CLASSES_ROOT\TypeLib\{91493440-5A91-11CF-8700-00AA0060263B}\2.b\0\Win32] @="C:\\Program Files\\Microsoft Office 15\\Root\\Office15\\MSPPT.OLB" and point it to the Office 14/15 directory in regedit.  The easiest way to do it would be to copy the registry entry for the TypeLib 2.a entry and paste it over the 2.b entry. Author: Thomas Pött Managing Consultant Microsoft UC

Dialplan normalization with extension number if user do not have a DDI

If we only have internal extensions and the URI will look like this: +4989123400;ext123 we have several point we need taking care about: - incoming calls shall be addressed via Exchange Auto Attendant - internal call now need to be normalized including the users extension - in some circumstances, we have assigned multiple DID number including the head number. if so we need the incoming normalization, analog to the internal calling normalization Confused finally? Don't worry, it really looks simple: Say our Head Number is: +4989123400 and we have extension from ;ext=01 until ext=99, the normalization rule will look like: If the Exchange Auto Attendant has also an extension, we need to have an incoming normalization rule on the trunk or gateway: Exchange AA: +4989123400;ext=99 Pattern to match: ^(\+4989123400)$ Translation rule: $1;ext=99 the internal assigned phone number has the said range (01-98), so a users phone number looks like: a) tel:54;phone-context=Si

Lync 2013 Web Scheduler (How to setup guide)

The Lync 2013 Web Scheduler was made for User who need to setup a Web Meeting without having Outlook available. It is a very convenient method and easy to understand. In our Demo Lab, I have documented all necessary steps: So let’s add a new Simple URL.  We have three simple commands: $urlEntry = New-CsSimpleUrlEntry -Url “ ” $simpleUrl = New-CsSimpleUrl -Component “WebScheduler” -Domain “*” -SimpleUrlEntry $urlEntry -ActiveUrl “ ” Set-CsSimpleUrlConfiguration -Identity Global -SimpleUrl @{Add=$simpleUrl} -Verbose  First, we check the Simple URL Configuration and ensure all Topology settings were correctly made. Than you have to use the script exactly as provided:   You do not need to run Enable-CsComputer, since this will not update the IIS URL Redirect , this will be one of our last steps, where we are running the Bootstrapper and let this changes be happen   DNS Configuration has to be m

Polycom CX700 cannot sign in with Lync 2013

this is a fast published article Warning: DO NOT UPGRADE TANJAY/ CX700 TO THE LATEST FIRMWARE 4397/4411. Your lync phone will be partially not able signing in with Lync 2013 more info an fix will be provided soon Reference: SOLUTION: As I promised, here it come... The bug is related to some undocumented processes for the so called old OCS Phone, which are the Tanjay/ cx700. this login process and firmware update process is totally different from other Lync phones. What do I have to do: TANJAY: Update the phone to the newest firmware, but be aware, the phone holds the version before 4397. LYNC environment: Phone Login: -  the OCS Phone Edt, will NOT login via sip.<domain fqdn>, it will only us the sipinternal.<domain fqdn>. Therefore ensure, the SIPINTERNAL FQDN is on the local certificate. Our findings have shown, Tanjay will still query the sip.<domain fqdn>, will also

Lync Edge Server Replication failed FALSE with red cross

LYNC REPLICATION NOT WORKING In a Lync Deployment, where we have installed Lync Edge Server, we see the Replication is not healthy. You will notice a red cross or in the Management Shell the Replication is not UpToDate: False. If actually have telnet to the Edge Servers Port 4443, you realize that the port is open and working. As well you can test access the service itself: https://<edgeserver.fqdn>/replicationwebservice Via this access, you also be able to validate the assigned internal Certificate and the Certificate Chain. If you encounter an error with trusted root certificate, you will end up adding it other Trusted Root Authorities. Afterwards, you will still encounter the red cross, or false up-to-date status. This is normal! The Replication itself is working fine, but your Connectivity to the Edge is limited. This mean we cannot query the service due to the SECURE CHANNEL limitation. Solution: Open REGEDIT navigate to: HKey_Local_Machine\SYSTEM\Curren

Lync 2013 Audio Gateway Debug Logging (Ferrari, AudioCodes, Dialogic, NET Quintum)

I need writing about Debug Logging on several ISDN Audio Gateways. Please visit this article more frequently, since I will update all common vendors over the time. --------------------------------------------------- First we need to identity tools we need for Debug Logging: WireShark for PCAP file analysis: download properly WireShark can be your Syslog Server too. it is not the best option, but under Capture Options , define a filter: upd port 514 and start your capture on the eth. Syslog Server: download Snooper if its Lync Mediation Server related: download (Lync 2013 Debug Tools) --------------------------------------------------- Ferrari Electronics (Office Master): updated soon.... --------------------------------------------------- AudioCodes (Mediant): First we need to configure the Syslog Server: Navigate to Management-> Management Setting-> Syslog Setting.   Setting   Value   Description  Syslog Server

Hide User Last Active Time Stamp (Lync Server 2013 Modification)

As very often requested or even legally forbidden in certain countries, Administrators seeking for a possible solution removing the user activity time stamp. Mostly it is misinterpreted and secretly used for user activity monitoring. There Microsoft introduced an update with Lync Server 2010 CU6 and enabled without additional costs a simple and easy way removing this LastActive Attribute from the Users Lync Object.   Note: After you apply this solution, only newly written/ detected activity time stamps are effected. In other words, if the user object was Lync enabled before has not yet logged into Lync again, the last time stamp is still visible, as you can see in the illustration below. As well remember, this setting affect all user hosted on the Front-End Server (Pool) and cannot be set to individual users.   Procedure:   1. Create a text file, named Rtcaggregate.exe.config in the Lync Server 2013 Folder, e.g. C:\Program Files\Microsoft Lync Server 2013\Server\Core   2

Lync 2013 Server Prerequisites (per roles and with powershell script)

Lync 2013 Server Software Prerequisites: Lync 2013 requires several additional software to be installed and has the need of certain roles and features, as well as hotfixes. Since I'm missing a scripted PowerShell installation, segregated into Lync 2013 roles, I decided writing this detailed Blog, based on Microsoft Technet article and experiences. It shows you all requirements  and prerequisites for each Lync Server Roles and all supported Operating Systems. Especially with the additional software you need to install, the installation sequence is important , therefor .NET Framework is a prerequisites for PowerShell 3.0 and Identity Foundation As a common question; Which prerequisites do we have if I need the Administrative tools only. You simply can consider the Administrative Tools as a server role, therefor you need the same prerequisites as listed in the common section for "All Server Roles required". The other components, e.g. Visual C ++ or SQL Tools.... R

Deploy Office Web Apps Server 2013 and external publishing

Office Web Apps Server 2013 is the central component presenting and editing Microsoft Office document with Web services. The Web Apps Server is shared with Lync, Exchange and SharePoint. Version 1.5: 17.12.2014 Web Apps can be installed as standalone system or in a web cluster (Load Balanced). Prerequisites: Microsoft Office Web Apps Server was downloadable from the Download Portal. But since 24.Nov.2014 it is from now on only downloadable via the Volume Licensing  Portal and MSDN Subscription. For easy deployment, make sure you download it including Service Pack 1. (Reference: ) While it downloads, we can configure the other prerequisites. Windows Server 2008 R2 If you’re using Windows Server 2008R2, please download  Microsoft’s .Net Framework 4.5, download  Windows Management Framework 3.0, and download  KB2592525 , which will allow you to ru