Browsing the archives for the configuration tag.

Encountering a Persistent Chat Error? How to Resolve the “500 Internal Server Error” After December 2014 CU

Persistent Chat

This past week we encountered a Lync Server error internally. We found a solution online, thanks to a fellow Lync blogger. I’m blogging about it today to document how we handled the troubleshooting process, and to showcase the blogger, a Mr. Graham Cropley, for his helpful content!

The Situation: Adding a Cumulative Update

We run Lync Server 2013 Standard Edition, with Persistent Chat and a SIP Trunk. This past week our engineers had the time to implement the December 2014 CU (I know, I know…).

persistentchatdeniedHowever, once the update was in place, two employees noticed something right away. They couldn’t create a new Chat Room. Persistent Chat wouldn’t work.

The Error: Persistent Chat Fails

To quote the following blog post, Persistent Chat – December 2014 CU – 500 Internal Server Error at the Lync Exchange – UC Blog:

“After applying the latest December 2014 v2 Cumulative Update, the Persistent Chat webpage didn’t work externally, it just returned ‘500 – Internal Server Error’.”

One additional thing which isn’t mentioned in the post – not only does the Persistent Chat webpage fail, but so do existing chat rooms. Essentially all of Persistent Chat is unresponsive.

(Not to take away from Mr. Cropley’s good work here. Just adding our own observations for a more complete picture.)

According to his research/experimentation/glaring at the server, he determined this:

The culprit is in the web.config file from the later [December 2014] CU in %ProgramFiles%\Microsoft Lync Server 2013\Web Components\PersistentChat\Ext, which includes these extra lines inside the element:

<system.webServer> <modules> <remove name=”PreAuthModule” /> <add name=”PreAuthModule” type=”Microsoft.Rtc.Internal.PreAuthModule.PreAuthModule,Microsoft.Rtc.Server.WebInfrastructure, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/> </modules> </system.webServer>
1 <system.webServer>
2     <modules>
3         <remove name=”PreAuthModule” />
4         <add name=”PreAuthModule” type=”Microsoft.Rtc.Internal.PreAuthModule.PreAuthModule,Microsoft.Rtc.Server.WebInfrastructure, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″/>
5     </modules>
6 </system.webServer>
This would seem to ensure that anything called PreAuthModule that may be there already is removed, and the Microsoft.Rtc.Internal.PreAuthModule was registered instead. Also by removing it first, this won’t cause an error from that module already being added.

How to Fix the Error: 3 Potential Fixes, We Chose to Convert the Persistent Chat Directory to an Application

At first we went through some of our own troubleshooting steps. Server restart, internal/external tests, etc. No change at all. Persistent Chat remained down, even though all other Lync Server Roles worked perfectly.

Next up, looking at the last change made. The December 2014 Cumulative Update. Did that break Persistent Chat? A few searches, and voila – it did indeed. Mr. Cropley’s post came right up in results. Clear and directly addressing our issue.

We opted for “Fix 1″ of the 3 listed. For the same reasons he did – it has the least impact.

And it worked perfectly. The image above shows my Chat Rooms webpage (I added the red X), taken this morning. All Chat Rooms are working again, as is the Persistent Chat webpage on the server.

Thank You to Our Fellow Lync Blogger!

A big thank you to Mr. Cropley for his post! His work saved us a lot of troubleshooting time. The post is what I love to see in the blogosphere – solid, clear how-to documentation from people working with the technology.

Here’s the link again, if you too are faced with Persistent Chat failing after the December 2014 CU:
Persistent Chat – December 2014 CU – 500 Internal Server Error [Lync Exchange – UC Blog]

No Comments

Prepare to Support Skype for Business with a New Lync/Skype Troubleshooting Guide

Skype for Business

Okay! Back to talking about Skype for Business 2015.

I attended a Lync Users Group Meetup 2 weeks ago, where we discussed Skype for Business Server 2015. I’m not able to share specifics yet, but I can talk about the Meetup itself. It was very well-attended–Lync partners, third-party vendors like Sonus, and UC industry experts.

The preparatory process for Skype for Business has clearly begun.

It was in this same vein – preparing for Skype for Business’ arrival – that I wrote today’s post. Last month Thomas Poett, a Microsoft Lync MVP, released a troubleshooting guide (free download). Both for Lync Server 2013…and for Skype for Business 2015!

Troubleshooting Guide, Skype for Business and Lync – Thomas.Poett@UC

Who’s the Guide For?

ThSupporting Lync Servere guide is meant for systems administrators, Lync Server administrators and Exchange Server administrators. It isn’t spelled out exactly, but the subject matter clearly delineates admins for its target audience.

As you’d expect from the title, Thomas’ guide covers troubleshooting methods for resolving issues within Lync Server 2013 and Skype for Business 2015. It addresses topics like the following.

  • Support tools to use, such as Snooper and OCSLogger
  • Testing configurations for IM, Voice/VoIP, Conferencing
  • Analyzing calls for session problems
  • SIP troubleshooting
  • And much more

Things to Consider

–This guide is focused on troubleshooting, NOT on setup. Please read it with that in mind.
For instance: 21 pages are devoted to analyzing SIP data from one Lync call!

–This is a low-level technical guide. Expect to see Snooper logs, PowerShell cmdlets and session diagrams. If you are not already familiar with the Lync Server infrastructure, I suggest saving this for later. (May I suggest previous posts on this blog instead?)

–More attention is paid to Lync than Skype. No surprise here – Thomas does have access to the TAP, but there are strict privacy controls on Skype for Business information right now. And will be for a few more months.

Thomas was clever; he wrote a “universal” Troubleshooting Approach on pages 7-8 which can be applied to Lync, Skype for Business, Exchange Server, and even Office 365. I do not want to take away from his guide, so I will only quote a small part of the Troubleshooting Approach:

4 Major Quality Issue Areas:

  1. Network
  2. Core Performance
  3. Gateway
  4. Devices

Configuration/Environment Setup Regions to Check When Troubleshooting (in order):

  • Voice Setup (Dial Plans, Normalization, Routes)
  • Gateway Configuration
  • Exchange Unified Messaging Integration

Speaking from our Lync experience, this approach holds up. Network issues affect Lync more often than its own Server Roles hitting a snag. Which happens more often than a gateway failing to communicate. Which happens more than a device outright failing (only had that happen a couple times).

Why You Should Read the Troubleshooting Guide

I’m reading this for one reason: Identifying similarities between Lync Server 2013 and Skype for Business Server 2015’s support processes.

Thomas has done some good work here. He’s provided details for troubleshooting a software platform, before it’s commercially available, using its currently-running predecessor. It’s a document intended to help you transition from one to the other.

I’m sure in time we’ll have more documentation, both for setup and for support. But right now, we have a Skype for Business 2015 resource available. Avail yourselves of it – after all, it’s free!

Here’s the direct PDF download link at TechNet.

What steps are you taking to prepare for Skype for Business 2015? Please comment or email your thoughts. And join us back here next week for more!

No Comments

How to Access Lync Server Management Shell Remotely

Lync Server 2013, Reference

Welcome to 2015! Let’s start the year off with some helpful how-to’s.

The other day I was off-site, and a request came in to update the Web Conferencing branding. (I blogged about this at “Branding Your Lync Server”.)

Normally I’d just log into the server and make the change, either via PowerShell or in Control Panel. But I was off-site. My normal login wouldn’t work! I’d have to log in remotely.

IMG_1270a

Now, all you sysadmins who do work from 3 different locations (office, the couch, the coffee shop), you know what’s required for this: Remote Access to the Lync Front End Server. However, I had discovered that SOMEone on our Lync team had disabled remote access!

(Ordinarily that’s a sensible precaution. Unmonitored remote access to any server is a serious security risk. Keep that in mind when using the following instructions.)

After I returned to the office and re-enabled Remote User Access, I was able to access Management Shell remotely & enter the cmdlets I wanted. I’ve already given you the cmdlets themselves, and what they do (the link above).

Today, I’m talking about the process used to make this possible. Steps to access Lync Server Management Shell remotely.

Remote Management Shell Access, Step 1: Enable Remote User Access on Lync Server

WARNING: The following can leave your Lync Server vulnerable if your security does not address remote access. Check your network security configuration BEFORE attempting.

  1. If your Lync user account is a member of the RTCUniversalServerAdmins group (or is an Administrator), log on to your computer within your company network.
  2. Open a browser window, and then enter your Lync Server Control Panel’s administration URL. (This can be done via Remote Desktop Connection as well, if you prefer.)
  3. In the left navigation bar, click Federation and External Access. Then click Access Edge Configuration.
  4. On the Access Edge Configuration page, click Global / Edit / Show Details.
  5. You should be in Edit Access Edge Configuration.
    1. To enable Remote User Access, check the “Enable remote user access” box.
    2. To disable Remote User Access, clear the “Enable remote user access” box.
  6. Click Commit.

You can also do this via cmdlets (see this page for help: Enable or Disable Remote User Access in Lync Server 2013 – TechNet

I prefer doing so via Control Panel though, as it means you know where to go to enable/disable in the future. And you can switch it off whenever it’s not in use!

Step 2: Configure Policies

Enabling Remote User Access is not enough. You may also need to configure a policy allowing remote users to communicate back to Lync’s Front End.

  1. If you are still logged into Lync Server Control Panel, click External User Access in the left navigation bar.
  2. Click External Access Policy.
  3. Which policy you edit depends on which level you want to use.
    1. For the Global policy to support Remote User Access, click the Global policy. Click Edit, and then click Show details.
    2. To create a new Site policy, click New, and then “Site policy”. Select the appropriate Site from the “Select a Site” list and click OK.
    3. To create a new User policy, click New, and then “User policy”. Create an appropriate name under Name (“AllowRemotePowerShell” for example).
    4. If you want to change an existing policy, click it in the table, click Edit, and click Show details.
  4. To enable Remote User Access for the policy, check the “Enable communications with remote users” box.
  5. To disable Remote User Access for the policy, clear the “Enable communications with remote users” box.
  6. Click Commit.
  7. Exit out of Control Panel and log off.

More information is here: Configure Policies to Control Remote User Access in Lync Server 2013 – TechNet

**NOTE: As the comments below discuss, this step may in fact not be necessary. I will try removing our policy configuration & testing remote access afterward. If you want, you can skip this step and go right to Step 3. If you do experience an error, try configuring policies and see if that resolves it. If not, you’re good.

Step 3: Open PowerShell & Create New Session

Now you’re set on the server-side for remote access. Here’s how to log in via the client side.

  1. Copy down the FQDN of your Front End Server. Take this with you (but keep it secure!).
  2. When at a remote location, connect to the Internet. Open PowerShell.
  3. Enter the following cmdlet using your FQDN:

$session = New-PSSession -ConnectionUri https://lync.domain.com/PowerShell -Credential (Get-Credential)

Make sure you have the correct FQDN for your Front End Server! Otherwise you will see a Connection Failure error like this.

powershellFQDNfailure

You will be prompted to enter your credentials. Enter your login and password.

Once you’re authenticated, enter:

Import-PSSession -Session $session

This will create the new session.

Johan at Lync-Blog.nl has additional details on this page: Multiple Ways to Manage Your Lync Server Environment – Lync-Blog.nl

I also came across a script to speed up the process, here: #Lync and Remote PowerShell – Phyler’s Blog

After this, you should be there! Logged into PowerShell remotely and set to enter cmdlets.

When done, don’t forget to end your sessions with:

Remove-PsSession $session

P.S. – You May Need to Log Into Your Company VPN

Like many businesses, we use a VPN for external access. I was initially rebuffed from my remote PowerShell login. Logging into our VPN corrected this issue.

Depending on your network configuration, you may need to log into your VPN as well. Check with your network administrator for remote access rules.

========

Remote PowerShell access is a great help for admins who travel. Not every cmdlet will work from off-site (Johan mentioned that Enable-CsTopology will not, for instance). But you can create/disable users, get reports and restart some Lync services.

Thank you to everyone in our 2014 end-of-year polls! I’ll share the results next week. If you haven’t voted yet, I’ve extended the polls until Saturday the 10th. Please go here and vote: 2014 Reader Survey: What are Your 2015 Lync Plans?

How do you prefer administering your Lync Server? Please share your thoughts. We’ll see you again next week!

6 Comments

How to Brand Your Lync Server

Lync Server 2013

We’re starting in on some end-of-year upgrades for our datacenter. While we’re doing the work, we took another look at our Lync Server. Right now we run Lync Server 2013 Standard, with a SIP line and Persistent Chat.

Given our explorations earlier in the year into using Lync Server as a LogMeIn replacement, we’re implementing a few changes to make that easier. Which is where today’s Lync Insider topic comes from.

What I Mean By “Brand” – Identify Your Lync Services to Employees and Customers

Lync Server, like most server applications, is designed to look the same across every installation by default. But it includes methods by which you may brand it.

Chances are most of you know what “branding” is. In this case, I’m referring to tagging all elements of your Lync Server users see with your company name, logo, etc.

Why would you want to brand a Lync Server? Well, we’re doing it for two reasons:

  • Internally, this is a helpful measure to avoid confusion. People see their employer’s name on the Lync tools, they know this is what they should use.
  • Externally, branding fulfills a marketing function. Customers, prospects and partners whom you invite to use your Lync tools – they see Lync, yes. But they also see who’s providing Lync services to them.
Image courtesy of Simon Bleasdale on Flickr.

Image courtesy of Simon Bleasdale on Flickr.

Below you’ll find 5 branding changes to make. One you should already have. One you’ll find right here on the blog. The others are links to blog posts which give a good how-to. I’ve included short versions to familiarize you, but I do encourage you to visit the other blogs for more detail.

NOTE: The following applies to Lync Server 2013 installations.

Basic naming: Domain-based URLs

Creating Lync URLs using your domain is done during the Lync Server setup. Particularly when setting up your Edge Server for external user access. Meet.domain.com, dialin.domain.com, etc. This is a fundamental branding element – nobody else has your URL.

Set up/modify the Lync Meeting invitations

Customizing the Online Meeting Add-in in Lync Server 2013 – TechNet
Short Version: Including a logo, custom footer text, and links to your Help or Support pages in every Lync Meeting invitation. Accessible via Lync Server Control Panel, under Conferencing/Meeting Configuration.

Change the logo image on the Lync Web App page

Customizing the Lync Server 2013 Meeting Page – Ehlo World!
Short Version: Change the image on the Lync Web App page from “Lync Web App” to your company name (or whatever phrase you want to put in an image). Replace the “Lync Web App” image in the Lync Server’s Images subfolder. Then restart the Web Conferencing service using this PowerShell cmdlet:
Restart-Service RTCDATAMCU

Customize Lync Presence options

Want to add custom Presence status options to your users’ Lync 2013 clients? We’ve covered two ways to do this in the past. Here are the blog posts you’ll want to reference.
Lync Add-Ons: Lync Custom Status Tool
How to Create Custom Lync Presence States

Customize the Lync Dial-In Page

How to Customize Lync Dialin Page – ExchangePro.DK
Short Version: Editing the Dial-In Conferencing page’s HTML. Add in your logo, or adjust the page formatting. Not the biggest location for branding, but you can alleviate some external users’ confusion at the same time.

Small Changes, Big Visibility Improvement

None of these changes should take you long to make. They work within Lync’s standard setup, either via Control Panel, Management Shell or direct folder access. But the result is far-reaching – once you’ve made these branding edits, everyone will see your logo & information.

Every time you invite someone to a meeting.
Every time your users change their Presence.
Every time you run a conference or webinar.

Every time, they see your name.

How’s that for branding?

Have you branded your Lync Server? Did you use a different method from these? If so, please comment or email me. Always like to hear what work our readers have done.

No Comments

Reminder: Keep Your Lync Servers (and Other Application Servers) Patched

Lync Server 2013

Halloween is here! Hope you have some ghostly activities coming up.

For many businesses, the end-of year rush starts in November. Budgets to review, security to check, support tickets to address.

So I thought today was a good time for a reminder: Patch your servers before year’s end!

Microsoft released a bunch of patches for its application servers, these past couple months. Cumulative Updates for Lync, Exchange Server, SharePoint and others.

If your network automatically patches servers, you’re all set. If not, these are the latest server patches from Microsoft (with URLs for your easy download):

You Wouldn’t Want Zombie Servers, Would You?

Take a moment and put this in your calendar:1440371_30143697
“Current patch version on Lync Server/Exchange/SharePoint? Check. Update if necessary.”

Schedule it for November 3rd. Set it to remind you every quarter. Your Lync Server will thank you.

Not patching is what leaves servers vulnerable to slowdown and attack. You wouldn’t want any servers to suffer a malware infestation or a hacker break-in, would you?

There’s plenty of zombies coming to the streets on Friday night. We don’t need any more in the datacenter.

Have a safe and happy Halloween! We’ll see you back here next week.

2 Comments

MSPL: What It Is, and How to Use It with Lync Server

Lync Server 2013, Third-Party Lync Products, Voice over IP

I mentioned last week that I’d explore MSPL more. While researching the Automatic Logout post, I came across a few MSPL-related websites with lots of good information. This week I’ve found a few more–so it’s time to blog!

MSPL – Scripting for Lync Call Routing

MSPL stands for “Microsoft SIP Processing Language”. It’s a scripting language you can use to customize how Lync Server routes SIP messages.
MSPL Scripting Reference – MSDN
Frustratingly, the MSPL Script Syntax has been moved out of the Scripting Reference at MSDN. You’ll find it here instead:
MSPL Script Syntax – MSDN

How Does MSPL Work

The process of creating and adding MSPL scripts to your Lync Server is actually quite simple:

  1. Generate MSPL scripting, either by hand-coding or using an application (see “How to Create MSPL Scripting” below).
  2. Scripting is imported into the Lync Server front end via PowerShell cmdlets
  3. The Lync Server routes SIP messages (like phone calls) where you have directed them.

There’s an excellent how-to writeup at the Code4Lync blog: MSPL SCRIPT HOW-TO – Code4Lync
It documents script structure, when to use MSPL over UCMA, and describes the basic scripting syntax. Worth a read.

MSPL formats as XML when it’s ready for importing. Commenting is included too, so feel free to note your processes.

What You Can Do with MSPL

You are limited in scope to addressing SIP messages within your Lync Server environment. However within that scope, there’s quite a few things you can do with MSPL.

Here are two examples at Channel9:
Lync Server 2013: Use an MSPL Script to Forward IM Calls
Lync Server 2013: Use an MSPL Script to Enforce Custom Privacy Settings

MSPL lets you control routing of calls, Instant Messages and even video from one SIP address to another. Roughly, the more SIP-enabled endpoints you have, the more MSPL routes you can make.

How to Create MSPL Scripting

Like I said before, you can hand-code MSPL, or have an application generate it for you. Last week I visited Matt Landis’ blog and found he’d posted on an MSPL application called SimpleRoute.
The Masses Can Now Make Microsoft Lync MSPL Scripts Via Free Tool from Colima – Microsoft UC Report

I tried this tool out myself. And it works exactly as Matt describes–very easily! I selected Audio/Video call and routed one SIP address to another (using a fake number of course). This only took 3 steps.

Generating MSPL in SimpleRoute

What’s especially valuable about SimpleRoute is that, once you create an MSPL script with it, SimpleRoute actually helps you install it. Remember Steps 2 & 3 above, about importing scripting into Lync Server 2013?

Well, take a look at this. This is what SimpleRoute displays after you click Save:

MSPL Import Instructions in SimpleRoute

==============================
Detailed instructions on how to import the saved script (in an .am file) into the Lync front end via PowerShell. How’s that for helpful?

Download SimpleRoute here: Colima – Customize Lync Routing

MSPL: Good for Basic, User-Level Call Routing

MSPL is a very specific scripting language. It’s pretty much designed to do one thing and one thing only–change SIP routing within Lync Server 2013. I’ve said in the past that I like tools which focus on one job and do it well. MSPL is another example of this.

Administrators should look to MSPL if they want to customize call routing down toward the user-level. Say an employee leaves and you want to route their calls to someone else, right away. Use SimpleRoute to generate some MSPL. It’ll take care of that for you.

Have you used MSPL in your Lync Server environment? What did you do with it? Please comment or email! We’d love to hear about it.

No Comments

How Would Automatic Logout Work for Lync 2013? 2 Possible Ways

Lync 2013 Client

The other day, a Lync Insider reader asked a question in the comments:

“Is it possible to have Lync users auto-logout after a period of inactivity?”

He wanted to know if MSPL could be used to control an auto-logout process. If so, how would it be done?

Intrigued by this question, I did some research. And while I didn’t precisely find what our reader was looking for, I did find some helpful information.

I’ll start with MSPL itself.

What is MSPL?

MSPL stands for Microsoft SIP Processing Language. It’s a part of the Lync Server SDK. You can use MSPL for modifying Lync SIP routing behavior: intercepting calls, rerouting them, logging configuration and more.

lync account controlIt’s a pretty powerful tool. If you’d like to explore it – and don’t worry, I will in future posts – here’s some links for you.
MSPL Scripting Reference – Office DevCenter
SimpleRoute – MSPL Scripting Tool

All that said, I do not think MSPL is the way to enforcing automatic logout. Its focus is on SIP routing, not the Lync 2013 client controls.

You would use MSPL scripts to control where certain calls are sent, or through which voice routes each office goes. Local client modification is more the preserve of PowerShell and GPOs. Which is where my research went next.

I looked for a PowerShell cmdlet which may control user logins or session logouts – but there was nothing relevant. Which disappointed me a little – I thought PowerShell, with its extensive cmdlet library, would have at least one cmdlet for governing Lync 2013’s login/logout behavior.

Next I looked into GPOs. Here I did find some success. Not directly so, but close enough that I can say we have 2 possible solutions to the reader’s question.

2 Ways to Control Lync 2013 Logout

#1 – Use a Custom Group Policy Object (GPO). There isn’t a standard GPO which controls session logoff (at least not yet!). After much research, we did come across a custom GPO which comes close though. It was written by Murali Krishnan over at UnifiedMe.co.uk:
Lync 2013 Group Policy to Enforce Ringtones Centrally
Murali has graciously made the .ADM file available for download on this page. One of the functions it provides is setting users’ Idle Timeout and Session Timeout. Which accomplishes close to the same thing.

#2 – Configure Windows to auto-logout instead! When you log out of Windows, Lync automatically signs out too. And it’s very simple to log users out of Windows at the admin level. It’s a workaround, but hey, it does work!

Here’s one way to automatically log users off on Windows 7. You can also enforce logoff via Power Options in Control Panel, or through another GPO.

Or, if you’re using a Terminal Server, try this:
Open gpedit.msc (Local Group Policy) and configure the following:

User Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits

Jas, I hope this gives you something to work with. Honestly, I’d never thought about administration of Lync’s login/logout before. Since it’s normally dependent on the user’s actions – or in this case inaction – the system’s default functions were sufficient. But I can (now) easily see the need for control of such – if you’re in a large corporate environment and need to schedule updates, for instance.

Do you know of another way to automatically log users off of Lync 2013 clients? If so, please comment or email!

1 Comment

Third-Party Software for Lync Server: What are the Qualified Lync Applications?

Third-Party Lync Products

The other day we went through a list of hardware approved for Lync use. (Lync Add-On Hardware for Client Enhancement and Server Capability: 10 Examples)

But third parties don’t just make hardware for Lync. There’s a whole host of third-party software too!

Thanks to Shaun, a reader, for sending me his Lync experience and this URL:
Qualified Lync Applications – Office TechCenter

On this page is a list of third-party software applications Microsoft has approved for use with Lync Server. They are designated as “Qualified Lync Applications”.

What do these applications provide?

  • New Attendant Consoles
  • Billing and/or better reporting tools
  • Extensions for Lync 2013 clients (including mobile)
  • A Contact Center
  • Persistent Chat enhancements (these particularly interest me)
  • Recording tools
  • Software-defined networking

And a few more. Let’s go through the list and see what we find.

Samroxx Attendant

A new attendant console for Lync. Very easy to install – I had a free trial downloaded and running in less than 5 minutes. Setup takes a little bit longer, as it appears (at least in the trial version) that you must enter contacts yourself, instead of relying on Active Directory. Samroxx did grab my account information from Active Directory though.

samroxx

As you see from this screenshot, the Samroxx interface is very clean, and options are clearly listed. If you opt to use a third-party attendant console with Lync Server 2013, this is a pretty good choice.

Zylinc Attendant Console

Another attendant console. This one seems beefier though – it has more features, like calendar updating and statistics.

Zylinc-Attendant-Console_EN

Image courtesy of Zylinc.com.

Plus it works for both Lync Server 2010 and 2013. This in itself could provide a useful transition from 2010 to 2013–the interface for reception wouldn’t change.

No demo option I saw. But they do offer a product sheet: Zylinc Attendant Console Product Sheet (PDF)

Verba Recording

Call Recording add-on for Lync Server. While Archiving Server does some of this, it does have its limits Extending recording capabilities is a huge benefit – not only does it protect against lost productivity from confusion, but it helps with legal & regulatory compliance.

Two things I particularly like about Verba:

  1. It records all calls, IM conversations, and videos – media Archiving Server doesn’t record.
  2. It’s a server-side solution. Nobody has to install software on their PCs, which means everyone is recorded by default.

I’ll book a Verba demo and report back on my findings soon.

MindLink Mobile Chat

Persistent Chat is one of my favorite Lync tools. However it suffers from one notable limitation – mobile access. Or lack thereof.

MindLink extends Persistent Chat onto mobile devices (phones and tablets). It also works on Mac and Linux computers, extending Lync’s chat capabilities across pretty much all platforms. MindLink even integrates with email and SharePoint.

I’m signing up for a MindLink demo too. Watch for a future post on this too.

Many More Third-Party Applications – Have You Tried One?

These are only a few of the 95 total “Qualified Lync Applications”. I’ll revisit the page later, go through more software, test the ones I can, and report back. Feel free to do the same (and let me know what you find)!

The idea that Lync Server 2013 would need “extending” might make some think the software is incomplete, or immature. Not so. One software application isn’t perfect for all situations. That’s why so many release APIs and work with third-party developers to create extensions. Firefox has its Add-Ons. WordPress has its Plugins and Themes.

Lync Server has Qualified Applications. Use them to make Lync run like you need it to.

Does your business use a Qualified Lync Application? Please comment or email me with the details. I’d like to hear about the application, what you use it for, and how well it works.

No Comments

No Post This Week – Join Us for More Next Week

Lync Server 2013

Hello Lync Insider readers! Remember last week when I said I’d have a post on stress-testing Lync Servers today? Well, it’s not quite ready yet. I’d like to do a few more tests before I can call this topic well-researched. So I’m postponing this another week.

Join us next week though! It’ll be worth it, I promise.

No Comments

Read Up on Lync, SharePoint, Office 365 and More with Free Microsoft eBooks

Lync Server 2013

It’s happened again. Microsoft released a trove of ebooks about their various software products:
Largest collection of FREE Microsoft eBooks ever, including: Windows 8.1, Windows 8, Windows 7, Office 2013, Office 365, Office 2010, SharePoint 2013, Dynamics CRM, PowerShell, Exchange Server, Lync 2013, System Center, Azure, Cloud, SQL Server, and much more
(Yes, that’s the post’s real title!)readingbook

I think this is the third time such a giveaway has occurred in the past 2 years? Fourth? Either way, I’m grateful to Microsoft for releasing all these titles. And to Mr. Ligman for compiling them.

This latest collection is huge – and it contains more than enough Lync Insider-relevant books for me to mention it. Here’s a list of what I downloaded right away for brushing up.

  1. Office 365 Midsize Business Quick Deployment Guide (DOCX)
  2. Quick Start to Office 365 for Small to Medium Businesses (ZIP)
  3. The Wiki Ninjas Guide to SharePoint 2013 (PDF)
  4. The Wiki Ninjas Guide to SharePoint 2013 – Part II (PDF)
  5. Windows PowerShell 4.0 Language Quick Reference (PDF)
  6. The Big Book of PowerShell Gotchas
  7. Lync Server 2013 Stress Testing Guide
  8. Microsoft Lync Server 2013 Step By Step for Anyone (PDF)
  9. Microsoft Lync Server 2013: Basic Administration – Release 2.1 (PDF)

There’s a couple more Lync-related books in the post, so go check it out. But I’d like to talk about these last 3 today.

Microsoft Lync Server 2013 Step by Step for Anyone
Written by Matt Landis
Matt’s on the list! Looks like he has converted a series of posts on setting up Lync Server 2013 from his blog into an ebook. We’ve covered this material here in the past.

The book walks you through a Lync Server 2013 Standard Edition install. It also has several additional how-to’s, such as “Using Microsoft Lync Server with SonicWall Firewalls” and “How to Configure Lync Server 2013 Live Messenger PIC to Enable Skype Federation.”

At 258 total pages, it’s too big to print out. But it’s a great reference to have on hand if you’re running an installation offline (e.g. for a test project). Maybe put it on a tablet while you install Lync Server.

Microsoft Lync Server 2013 Basic Administration
Written by Fabrizio Volpe
This is a basic overview of Lync Server 2013 for administrators. It has a narrative approach, which would make it great for those newer to Lync and potentially unfamiliar with the scope of its capabilities. Good high-level detail on Lync’s structure and workings.

What I do like about it is that it includes information on:

  • Cost mindfulness when deploying server roles (p. 15)
  • Firewall rules & access requirements (p. 82)
  • Verification tools [which include TRIPP and Remote Connectivity Analyzer!] (p. 90)

It would make a good catching-up reference for new hires entering a Lync environment.

Lync Stress Testing Guide
Written by the Lync Server 2013 Virtualization Team
This one is just fun. It talks about conducting stress tests on your Lync installation with the Lync Server 2013 Stress and Performance Tool (LSS). Since this guide focuses on one toolset and one purpose, it’s very focused & heavily detailed. (I didn’t even know it could do some of these tests!)

It does recommend you run stress tests in a lab environment. NOT on a live deployed Lync Server system. If you do run it while live, don’t be surprised if you knock everyone offline!

I’ll do a full post on stress testing later. The contributors did a thorough job documenting the process; it deserves more attention. Pick this guide up and see for yourself.

Go Forth and Download – But Come Back for More Details!

Both the strength and the weakness of Microsoft free ebooks are that they are basic guides. Intended to introduce you to software, how to run it, how to work efficiently with it. Nothing at all wrong with that – in fact I think it’s a great way to foster knowledge – but it has its limits.

In books like these, gritty-details administration, troubleshooting, advanced modifications & developments are not usually covered. You need to rely on experience, more specialized manuals, and online resources. Like this blog!

Is there an upcoming Microsoft software release you’re waiting for? New version, an update or a fix? Please comment or email me. Let’s see what’s coming soon for all of us.

2 Comments
« Older Posts


  • Lync Insider Email Updates

    Skip the visit - get Lync Insider posts in your inbox! Emails delivered every Friday.

  • About the Lync Insider Blog

    The Lync Insider is a blog about the technology we use to communicate in business today. Here we talk about Microsoft Lync Server 2013, Skype for Business Server 2015, Unified Communications, Voice over IP and related technologies like Exchange Server. Written by Chris W., MCSE in Communication and PlanetMagpie IT Consulting's Tech Writer.
  • Categories

  • Archives