Try our training for free.

Gain instant access to our entire IT training library for 1 week. Train anytime on your desktop, tablet, or mobile devices.

Exam 70-664 was retired July 31, 2013. However, this course retains value as a training resource....
Exam 70-664 was retired July 31, 2013. However, this course retains value as a training resource.

This Lync Server video training with Tim Warner covers Microsoft’s versatile enterprise communications technology, including deploying Lync Server 2010, implementing enterprise voice, and more.

Related Area of Expertise:
  • Messaging/Communications

Recommended skills:
  • Experience with Lync Sever 2010
  • Experience with complex deployments
  • Familiarity with Windows Server Active Directory 2010

Recommended equipment:
  • Microsoft Lync Server 2010

Related certifications:
  • MCTS: Microsoft Lync Server 2010, Configuration
  • MCITP: Microsoft Lync Server 2010 Administrator

Related job functions:
  • IT professionals
  • Telecommunication professionals

  • Microsoft Lync Server 2010 is hot! This all-in-one enterprise communications solution is a 64-bit enterprise-class Unified Communications (UC) server that runs on Windows Server 2008. This course will cover core features of this platform, including instant messaging; conferencing; integrating with or replacing enterprise voice systems; Microsoft Office integration; and using Lync from mobile apps. You'll also learn how Lync works seamlessly with other Microsoft enterprise server products, including SharePoint Server 2010 and Exchange Server 2010.

    Trainer Timothy Warner guides you through this platform and the powerful communication tools it offers. Internet telephony is a “black art” with which many systems administrators have no knowledge. But by the time you finish this Lync Server 2010 CBT Nuggets training course, you will understand both the rudiments of Voice over IP (VoiP) and Unified Communications (UC) as well as how to install, configure, and troubleshoot Microsoft Lync Server 2010.

    If your goal is to obtain Microsoft Certified Technology Specialist (MCTS) or Microsoft IT Professional (MCITP) certifications, start here. Not looking for a cert? Non-certification-oriented IT professionals can also derive great benefit from this course, saving them hours upon hours of otherwise trial-and-error work, as well as potentially saving their companies tens of thousands of dollars in ensuring a quality Lync rollout.
1. Course Introduction (29 min)
2. Understanding Lync Server 2010 Architecture (52 min)
3. Deploying Lync Server 2010 (59 min)
4. Enabling Users and Managing the Lync Client (49 min)
5. Managing External User Access (62 min)
6. Implementing Enterprise Voice Part 1 of 2 (62 min)
7. Implementing Enterprise Voice Part 2 of 2 (42 min)
8. Implementing Response Groups (37 min)
9. Administering Call Admission Control (44 min)
10. Using Location Information Services and Enhanced 9-1-1 (43 min)
11. Conferencing in Lync Server 2010 Part 1 of 2 (55 min)
12. Conferencing in Lync Server 2010 Part 2 of 2 (34 min)
13. Implementing a Unified Mailbox with Exchange Server 2010 SP1 UM (40 min)
14. Ensuring Voice Resiliency (47 min)
15. Monitoring and Archiving in Lync Server 2010 (58 min)
16. High Availability and Disaster Recovery in Lync Server 2010 (42 min)
17. Deploying and Managing Clients and Devices (34 min)
18. Patching and Troubleshooting Lync Server 2010 (60 min)
19. Administering Lync Server with PowerShell (53 min)
20. Lync Server 2010 Additional Learning Resources (26 min)

Course Introduction

Understanding Lync Server 2010 Architecture

Deploying Lync Server 2010

Enabling Users and Managing the Lync Client

Managing External User Access

Implementing Enterprise Voice Part 1 of 2

Implementing Enterprise Voice Part 2 of 2

Implementing Response Groups

Administering Call Admission Control

Using Location Information Services and Enhanced 9-1-1

Conferencing in Lync Server 2010 Part 1 of 2

Conferencing in Lync Server 2010 Part 2 of 2

Implementing a Unified Mailbox with Exchange Server 2010 SP1 UM

Ensuring Voice Resiliency

Monitoring and Archiving in Lync Server 2010


Monitoring and archiving in Lync Server 2010. This Nugget is all about troubleshooting and compliance. Monitoring and archiving are optional roles. They're not necessary to deploy in your infrastructure. However, you may want to enable one or both to give you, as a Lync administrator, greater insight into how your users experience with Lync is going.


And also as I said, you may be subject to various industry and/or governmental regulations that require you to retain the content, for instance, of instant messages across your organization. First, we're going to differentiate what monitoring and archiving means, and make the business case for it.


After we take care of that front end stuff, I'll discuss what infrastructure changes are necessary to integrate monitoring and/or archiving into your Lync environment. And by the end of this Nugget, you'll understand how to deploy and use both the monitoring and archiving server roles.


Let's get started. Let's take a look at the business case for monitoring and archiving. What do we mean actually? If we install the monitoring server role in Lync 2010, what actually is happening? Well, the two main metrics, numerical data sets that are being aggregated by the Lync monitoring server are QoE and CDR.


Now, what the heck does that mean? QoE refers to Quality of Experience and CDR refers to the Call Detail Record. Taken together, that set of metrics is going to give you a graphical and quantitative method of showing things like call metadata, how many minutes have been consumed and between which users.


What is the quality of that line? How much jitter? How much noise was present on those calls? Conferences. Who joined conferences? Who left conferences? When? All of that associated metadata. I'm actually going to give you what is and what is not captured with monitoring in an upcoming whiteboard.


But just know that this monitoring, this aggregation of data is useful for us as administrators, both for ensuring a good user experience as well as for troubleshooting when things go poorly. Lync is an expensive product. As we know, it's not just paying for the Lync Server and client access licenses, we're also paying for additional hardware to scale out the topology-- scale up and scale out the topology we should say.


If you're using Microsoft Exchange Server, Active Directory infrastructure, possible SharePoint integration, we could be talking about a very sizable investment, indeed. And if you're the one who convinced the powers that be within your organization that you need a Lync solution, it seems to me then you're going to be especially interested in keeping your finger on the pulse of Lync performance.


Now, Warner's first rule of IT is you're never going to satisfy your entire user base. There are going to be folks who grumble and complain no matter what, saying they wish that the environment was what it was prior to Lync, and that their Lync experience is-- I don't know, I'm thinking of things I've heard.


Too cumbersome, too complex, I just want a phone, darn it, kind of thing. So by keeping your eye on those metrics, you can then generate reports with hard numbers to show to the stakeholders in your organization and say, this is the buy-in we have over this time frame.


These are the problems we've identified. These are the good things that we've identified. And then as I said, the key to good troubleshooting-- and this is standard across the board with IT-- is as rich and robust intelligence on the front end of things as possible.


We want to have as much data to work with as possible. Speaking of which, it's one thing for the monitoring server to gather the data for you. It's another thing to present it in a way that's easy to analyze and interpret. What we have with the Lync monitoring server is tight integration with SQL Server's reporting services component.


In the demo, we're going to do a front to back installation, and we're going to install SQL Server 2008 R2 as part of that. Now note that we're not talking Express edition here. You actually have to have an instance of SQL Server running in your environment.


It does not have to be running on your monitoring box, but it has to be reachable by your monitoring Lync server. And of course, we have to make sure to install and configure the reporting services role of SQL Server. You're also going to see, as we go along, that the Lync Deployment Wizard has a one-click install.


Actually, it's a few questions. It's a traditional wizard that installs a bunch of canned Lync monitoring reports into a target SSRS instance that saves us what would be a tremendous amount of work building those reports on your own. Forget about it, I would not want to do that for anything.


So that in a nutshell is what's going on with monitoring. Now, archiving is again, a data aggregation process. The deal with archiving though is what may drive your adopting an archiving server is regulatory compliance, with things like information life cycle management, document retention.


One of the great benefits of the Office Communications Server when it first was published by Microsoft LCS 2005, is that a company could own a private IM infrastructure. Confidential communications that were transmitted by instant message could be archived, parsed, and brought out in maybe a legal issue if that comes up.


Or as I said, just simple compliance with some governmental or industry regulation. So you do, in fact, own your own private instant messaging infrastructure. The archiving can do more than archive just instant messages. As I said, shortly I'll give you the laundry list of what is and what is not captured.


One thing you want to consider though, and this will come out in the demo is when you enable archiving, Lync gives you a choice to archive internal and/or external communications. Now, why is that important? Well, internal we presume that they're all company staffers.


So we write it into their employment agreement that their email, their instant messages are all subject to archiving and auditing. But external partners, who could be Federated business partners, vendors, whomever, they may not cotton or appreciate having their communications captured and archived.


So there's some things we can do with that. We can just turn off external archiving. And we can also send a disclaimer to those external folks when they're involved in an instant message or conferencing exchange. One thing that I find really weird about Lync Server 2010 archiving is that there's no reporting feature.


As I said with the monitoring server, we have all these canned reports that you can generate great, great informative reports, and then export those to a number of different formats-- XML, CSV, PDF, Microsoft Word, you name it. But on archiving, it's just the opposite.


There's almost nothing there. You literally have to either NoSQL and write SQL queries to go into the LCS log database and hit specific tables in there, or we could run a PowerShell cmdlet to take a timeframe and then dump of all of the archived content into a separate folder where you can use, say, an email client or a notepad, or whatever, to view that data.


Now, I've heard rumors. At this point, Lync Server 2013 is well in development, but there's not an awful lot out there on it yet. But I've read and heard rumors that in the next version of Lync server, Microsoft has done quite a bit of tweaking and optimizing of monitoring and archiving.


And when I say optimizing, I'm not saying optimizing for speed. I'm saying optimizing for user experience. Hopefully, they'll fix this lack of a reporting feature for archiving and give Lync administrators a much better interface for querying the archived content.


I do know, if what I'm reading is correct, that the monitoring and archiving roles in Lync Server 2013 will be, by default, co-located on your front-end servers. That's very convenient. It makes deploying monitoring and archiving a heck of a lot easier, number one.


And number two, businesses don't necessarily have the resources-- hardware, software, or human resources-- to take care of an additional server, or two or three. Monitoring and archiving are relatively low bandwidth services. They're meant, at least in Lync Server 2010, to be deployed together.


So we can co-locate monitoring and archiving on the same box with no muss, no fuss, or greasy aftertaste. An important question here practically speaking is, what exactly is monitored versus is not monitored in terms of data aggregated by the Lync monitoring server? Well, as you see, there's a lot more that it is captured than is not.


Let's actually go over to the "is not" column first. Phone call, instant message session, conference content is not monitored. The reason for that is that all of this data is captured by the archiving server. We don't need content. We don't need instant message message content.


We don't need uploaded files and shared files in a conference session. We don't need metrics concerning phone call metadata-- who called whom, when, blah, blah, blah. Instead, we're interested in more technical metadata on the monitoring side. Other aspects that are not monitored are non-Lync processes and services.


That should make sense to you intuitively. Windows Server process info is not going to be captured by Lync monitoring tools. You're going to need to use the Windows Server in-box monitoring tools for that. The Performance Monitor tools, for instance. Similarly, application logging that's not Lync related is not captured by the monitoring server.


We know that Lync does, in fact, write event log entries to its own log in Windows Server 2008 R2 and Windows Server 2012. But it's not going to do anything not Lync related. Now, on the other side, what data is captured by the monitoring server? Voice over IP phone call, IM session, and conferencing metadata.


Metadata is a fancy term that means data about data. It's descriptive information. Endpoint metadata, the IP addresses, connection speed, which servers are being used by your endpoints. And your endpoints refer to the Lync Client, Lync Phones, et cetera. Call admission control session data, when policies are being enforced, PSTN rerouting, all of those details are captured for your analysis, or analytic pleasure I should say.


Diagnostics for session failures. This goes to the troubleshooting equation. These first items are nice to know just to make sure everything's going well. We also have troubleshooting specific stuff-- session failure metadata, what's going on server-wise as it relates to Lync, packet loss, signal degradation, line noise, and quality measurements for SIP signaling, video streams, and so forth.


So there's a lot of grist for the mill as Lync administrators for performance tuning, optimization, and troubleshooting. Now, let's do the same analysis, this time for the archive server. What is archived? Peer to peer and multi-party IM. So basically, all of your chat messages are picked up.


However, file transfers are not, period. So if two Lync users transfer files, that traffic is not going to be picked up. Even in an honest to goodness MCU-based conference, file transfers are not picked up. However, in a conference, uploaded and shared content is in fact captured.


And you'll see that in a demo. So if a presenter uploads a file and shares a file with other conference attendees, that file itself is going to be captured and archived. Similarly, if a presenter shares a PowerPoint deck, that will be included. Unfortunately, other methods of conference collaboration are not archived in this release.


The poll feature, that would be really useful if the archive server grabbed polls. But it doesn't. Whiteboards, annotations. Again, those whiteboard are, in my experience, very useful for future analysis. It's crazy that they're not part of the archive corpus.


I did hear-- again, this is a semi-rumor-- that Lync Server 2013 does, in fact, archive that conference poll and whiteboard and annotation data. Conference metadata in terms of who joins and who leaves. That can be especially important. I found in my experience, working as part of a virtual team, especially the sales departments.


When a sales manager has a web conference to do a knowledge transfer, product launch, whatever, they want to audit to make sure they know who was there for that conference. And I imagine it would be a black mark on a sales representative's jacket or their human resources personnel file if they're shown by looking at archive logs either not to have attended a conference or to have left it prematurely.


Well, all of that is documented and captured in the Lync Server archive server. Your heavier weight data, your audio and video streams from peer to peer IM and conferences are not captured. Application sharing from peer to peer or conferencing, that's a lot of really good stuff.


I imagine Microsoft did not archive this. Well, number one, how do you share if somebody shares their desktop? It seems to me kind of cumbersome and difficult to archive that. And in terms of video feed, it would probably just be a network bandwidth and disk storage space issue why that would not be archived by default.


Finally, session failure diagnostics are not captured. And the reason for that is simple. That goes across the fence so to speak, and that data is picked up by the monitoring server. So what is the deployment process for monitoring and archiving? First, we have our prerequisites.


And these are really important. If you don't do this, you're not going to get any results in your monitoring or archiving. It's just as simple as that. You have to make sure that on all of your Lync servers, particularly your front-end servers and your monitoring and archiving servers, that you've installed the .NET


framework 3.5.1. That can be done through Server Manager or Server Manager CMD or PowerShell on your servers in Windows Server 2008 R2. And then this is crucial, you have to install Microsoft Message Queuing with Directory Services Integration. These are components, feature components.


Again, you can get to them right from the Server Manager features list. MSMQ is a way for processes on the same box, or more likely separate machines, to exchange data with each other in the form of messages. And what's neat about MSMQ is that it's almost a guaranteed delivery system.


It's meant to be asynchronous, such that if two hosts on the other end of a WAN connection need to exchange messages using MSMQ and the WAN goes down or is too heavily congested, MSMQ can actually-- well, queue the data until it's safe to go across that WAN.


It's a reliable communication scheme, and that's actually how the monitoring and archiving transmits its data. Actually, on your front-end server where the action is happening, when you roll out the monitoring and archiving bits, you actually wind up with the agent bits on the front end.


And then on your monitoring and archiving server, you receive the data as it's generated on the front end. And of course, messaging and archiving is going to tie-in to a SQL Server back-end database. That's where the data is actually stored. We then interact with that using either SQL Server Reporting Services, SQL Scripts, or Ad-hoc queries.


And finally, we have a PowerShell cmdlet as I told you earlier, with which we can export archived data. So you want to make sure those prerequisites are absolutely in place. You then need to deploy SQL Server with the SSRS component. And that's going to involve some configuration on its own, frankly.


The next few steps should be very familiar to you. It's how we adjust the topology in Lync. First, we use topology builder to add the servers to the topology. No big deal. We're going to do that in the demo. You'll see how that works. And then, you know what's next.


We go to the machine, or machines, that are going to host these roles and run the Deployment Wizard. The Deployment Wizard knows because it's going to install a local copy of the central management store database, and therefore has intelligence of the topology.


The machine and Lync Deployment Wizard will understand which components need to come down to that box. Once you've done that, it's time to log in to the Lync Control Panel or use PowerShell cmdlets to define your monitoring and archiving policies. Again, we'll cover all that in detail in the demo.


And then from there, you just simply sit back and let some data aggregate. And then at your leisure, analyze either your canned monitoring reports or use some of these tricky tools to look at your archived data. Now, there is a sub-step here. I'm going to add it right here.


And that is to install the report pack. I told you once already that the Deployment Wizard on the main screen, there's a link there, a hyperlink that will kick off the installation of the Lync 2010 built-in reports that are so useful for us in this context.


Before we go into the demo, let's just tie up any loose ends regarding archiving and monitoring. Actually, let me start with monitoring because that's historically what we've been doing. Let's make sure we haven't missed anything. The components of Lync Server 2010 monitoring are your data collection agents that exist on every front-end server.


I just told you about that. The monitoring server itself with back-end database, using message queuing for passing the messages back and forth. That does need MSMQ. does need to be integrated in Active Directory. And then as a separate installation, our server reports.


The metrics or the numerical data is divided as I said earlier into quality of experience and CDR. Specifically, the QoE data deals with the number and quality of calls, participant metadata, endpoint metadata. The call detail records is usage information regarding your VoIP calls and IMs.


It's a subtle difference, and really they're blended together in the reporting interface. A/V conversations, meetings, file transfers, the content is not included. And again, by way of review this time on the archiving side, same basic components-- MSMQ, back-end database, archiving server, and the front-end pools have archiving agent bits installed.


The archiving policy can be scoped. We know now how a policy-based configuration works in Lync Server. And the fact that we have built-in global policies that by default hit your entire infrastructure, all of your central sites, all of your branch sites. But we can scope that policy down to the site level, or even the user level.


And what's neat about that is if we did do that, let's say we were very parsimonious if you want a $5 word with our archiving policy, and we set it only to scope to certain users. If one of those archived enabled users were a member of a web conference, let's say, then the entire web conference, the IMs and the conference data, will be archived.


Pretty powerful stuff. There's also what's called a critical mode configuration. You'll see this in the demo. I'll show you where it exists. And critical is used for those shops who have compliance requirements that are so stiff that you would deny service to your users.


You would actually block instant messages and conferencing from taking place if archiving is somehow going to fail. So that is an option. And it should give some stakeholders security who are, as I said, under heavy regulation, that anything within that schema-- instant messaging, conferencing-- will, in fact, be archived.


And if it can't for any reason, we're actually going to shut down the ability of our users to do that. All right then, I think enough talking and whiteboarding. Let's now head into the demo and I'll show you how this stuff works step by step. Hello, and welcome to this demo in which we work with monitoring server and archiving server in Lync Server 2010. We're actually going to co-locate both of these roles on branch nugget, which is a Windows Server 2008 R2 member server box that served several roles in various Nuggets throughout this training.


It served as a survivable branch server as well as a front-end server. Here as I said I'm going to deploy the monitoring and archiving roles on it. I figure we'll start with monitoring because the set up is slightly more complex. As far as prerequisites go, I'm going to start by opening Server Manager.


And we need to install the message queuing feature. This needs to be done not only on your monitoring and archiving server or servers, but also on your front-end servers as well. This is a feature, so I'm going to right click the Features node. Make sure that .NET framework 3.5.1 features are installed, which they are on my box.


And it looks like I have at least some of the bits for message queuing installed as well. As a matter of fact, I have half of it there. The only thing I need to add is directory service integration. We'll click Next and Install. And I'll click Close. Another thing I'm going to need to do actually, I do have the IIS web server installed.


That's going to be important when we bring up SQL Server Reporting Services for sure. And you can verify which role services are installed by right clicking the role and selecting either Add or Remove Role Services specifically. I've got the full boat, pretty much, installed on this IIS web server.


Then next thing we're going to do is buzz through an installation of SQL Server 2008 R2. I'm going to right click that. I've mounted the DVD and choose Install or Run program from your media. That's going to launch the Deployment Wizard for SQL Server. Now, I'm going to blow through this pretty quickly.


The only pause in configuration I'm going to go into any degree of depth on is that of SSRS to support what we're doing with Lync Server monitoring server. If you're interested in more in-depth training, front to back training for SQL Server, I've done training on SQL Server.


Garth Schulte, Don Jones, several of my CBT Nuggets colleagues have done it. So you're in good hands really, if you're interested in that training. All right, so here's the SQL Server Installation Center. Let's go to Installation and New Installation. Prerequisite check has passed, so we'll OK past that.


We specify the product key as usual and click Next. We have to accept the terms of the license agreement. I won't send future usage data. We'll install our setup support files next. And we're prompted for a restart. Great, we've passed all of our tests. The warnings I see here aren't that big of a deal, firewall and .NET security.


This is a testing environment. We'll leave the default feature installation enabled and click Next. This is really the money of it. I'm going to install the database engine. We can't have SQL Server proper without database engine services. And of course, reporting services, very interesting.


As soon as I selected that, notice we had a couple of additional options or things to do in our list here. I'm also going to install the management tools, client tools connectivity just for grins. Leave the default directories, click Next. I'm going to create a named instance called Lync 2010. Notice that we have RTC local and RTC.


Remember, that the Central Management Store Database, the read/write copy exists on your first front-end server. And then you have a replicated copy that goes to also that server, but all of your other servers. That's what makes the topology builder publishing so powerful.


Let's click Next to continue. We're just taking care of prereqs here. I'm going to use the same service account for all SQL Server Services. Domain Administrator is not recommended in a live production environment, but it'll work just fine here in my lab. I'm going to leave everything here at the default except I'm going to add in Domain Admins.


Not all shops are that broad with their SQL Server permissions, for administrators that is. This is an important page for our purposes. When we install reporting services, we can do the default or native mode where it's just a simple web application and that's it.


Or, if we're integrating reporting with SharePoint Business Intelligence, we can use SharePoint integrated mode. Or, we could say install the bits but don't do any configuration. I'm going to just simply leave the default here. Click Next. And it looks like we're ready to go ahead, ready to install.


We can verify and click install and start chunking. Sit back and wait, I guess. While this installation proceeds, why don't we pop over to Lync Nugget, our front-end server. I've popped open topology builder as you see here. And we're going to go ahead and open our central site node, come down to monitoring servers, which there's nothing there.


And we're going to modify the topology to bring in branch nugget as our monitoring server. We'll right click, select New Monitoring Server from the Shortcut menu, and we're asked to define an FQDN for that server. So it's We're asked to define a SQL store.


Well, it looks like we may have to wait for that server installation to finish. I was hoping we could save ourselves some time, but let's come back to branch nugget. It looks like we're almost finished here. In my experience installing SQL Server, it tends to take the longest right at the end of the installation progress.


It seems to hang up to the point where you wonder if the installation has, in fact, frozen. All right, so we're complete, but it tells us we have to reboot, which I'm expecting. I'm going to close out here and let's just bounce this server really quickly.


And when it comes back, we should be able to see that instance in topology builder. All right, so we're coming back into this server. Let me close out of Lync because we don't actually need the client running here. And let's switch over to Lync Nugget. Right click Monitoring Server, New Monitoring Server.


And we're going to define a new SQL store for this. The FQDN is My FQDN, as you know, is The instance is Lync 2010. So we'll click Next. We're asked to associate with one or more front-end pools. Note that the monitoring server can provide call detail recording for multiple front-end pools.


We have just one, so I'll select it and click Finish. If we edit the properties of the new monitoring server, there's really nothing there. There's the FQDN, which resolves in DNS, and the SQL database instance name. To actually make this go into effect, we can publish.


But actually, since we're here, why don't we go ahead and add our archiving server? It's right underneath monitoring server. We'll choose New Archiving Server, branchnugget-- same box-- In this case, we can use a previously defined SQL store.


And we'll click Next. It's asking for a file share. This is important because as we're going to see a little bit later in the demo, we interact with archived file data, conversations, et cetera, in the share. Now, we can create a new share or we can reuse the share that's on our front-end server.


I'm going to do that. lyncnugget/-- and the name of my shared folder is unimaginatively enough share. Same as monitoring, we associate with a front-end pool and Finish. And the properties are just allowing us to change those very same options-- the FQDN, SQL database, and the file share.


At this point now, we can publish the topology. We've been here so many times you can go through topology manager blindfolded by now, can't you? Everything was successful. You know what this is going to say, too. We need to run Lync server setup on branch nugget to install those bits.


So let's do that now. We'll close out of topology builder and come back to branch nugget. I have SQL Server Management Studio fired up and I'm connected to that named instance. Let's refresh our view. We haven't done anything yet. We will see some new databases in there once we install the bits.


Let me mount the Lync 2010 media. And I still have remnants from my previous work in Lync. Lync doesn't do a particularly good job of cleaning up. When you decommission a Lync server, you might remember earlier when I showed you the fact that we have the RTC instances installed on this box.


This box is no longer a front end, but it still has those databases left over. Similarly, we still have Lync Server 2010 with a link to the Deployment Wizard, the logging tool. And I wonder if the management shell is actually here, or if that's just a dead shortcut? I have a feeling it's actually still here.


While we're waiting for the Deployment Wizard and the management shell to load into memory, we might as well get reporting services configuration finished. In our Start menu, we have links to all of our relevant tool-- SQL Server Management Studio being the DBA's best friend.


Under Configuration Tools, we have Reporting Services Configuration Manager. So let's fire this guy up. A lot happening at once here. We have the Deployment Wizard, which I will tuck down here. You can minimize the window, but I can try to tuck it out of the way.


It looks like we do have a PowerShell command. Let me, just for grins, run a get command where the noun portion includes CS. Remember, CS are all of our communication server cmdlets. And they're all here, so that must have been left behind when we decommissioned this server.


I actually did that behind the scenes as I was getting ready to teach you this Nugget. So this is the Reporting Services Configuration Manager. It's asking us first to connect. Let's make sure our server name and instance are correct. It is, so we'll connect.


Verify the server is running, the service is running. Yep. The service account, verify that. That was done at installation time. Web service URL. This is fairly important. How are we going to connect to that box? We're asked to specify a virtual directory name, IP address, TCP port, SSL port.


Advanced button takes you into sockets and SSL identities. In a production environment, it's really up to you on whether you want to use SSL/TLS. Or in other words, HTTPS. If you do, you're going to need digital certificates and all that kind of stuff. It's telling us here that our URL is going to be kind of honking here.


Let me just change this virtual directory to reports. And it's also going to hit on the standard port 80. I'm worried that I already have that in use. So I'm going to switch that up to 8081 and I'm going to make the SSL port 4443 just to be safe. Apply these changes.


Make sure nothing blows up. You can see down here in the results, as it's making changes to your configuration, it echoes that on the screen, which is pretty cool. This is actually a very nice tool. OK, so we're back in business here. That's really the major point.


Database, it's verifying that. Again, that's all blah, blah, but. This is another URL, not for the web service but for actually the site. I'm going to call this Report Site, and I'm going to hit Advanced. And again, change the TCP port just to be sure. Don't need SMTP in this case.


We're not going to worry about encryption keys or execution accounts or scale out. We're good here. So let's click Exit and now come into the Deployment Wizard. We're actually going to use two sections here, friends. We're going to do our regular bits install, then we're going to come over here to Deploy Monitoring Server Reports.


It's nice that Lync gives us a link-- a nice pun there, of course. I've reused it so many times you're probably ready to gag, though. But anyway, it's nice that Lync links to it right there. That we don't have to go to the Microsoft Download Site. We can just install it directly from within the Deployment Wizard.


We're asked to install a copy of the local configuration store, and then set up those components. I'm going to buzz through both of these quickly behind the scenes. Because again, we've been there so many times I don't want to bore you. I want to show you as much different stuff as possible.


At first, let's just make sure that we can in fact get back a replica of the central management database. We could. So now we can actually install the bits. Here I am going back on my word and showing you this. Note that it's checking for MSMQ. I'm sure it's checking for .NET as well.


You see some raw developer-ish calls here to modules and files, DLLs, whatever. They don't have particularly useful names for us, as administrators, but they keep somebody in business over at Microsoft and give them some kind of job security. There we go.


Installing the monitoring server.msi. Installing the archive service msi. That's what we want to see. Good deal, that finished. Much faster than I thought, quite honestly. But we're not installing a full-fledged front-end server here. We're just installing some very lightweight server roles.


Let's go ahead and start those services. Point to mention-- I don't know if I've told you this thus far. But when the Lync Deployment Wizard runs start CS Windows service, note that it passes in the no wait parameter. What that means is the Deployment Wizard sends a start signal for those services but does not wait to ensure that they've started successfully.


It's almost a UDP operation, where it attempts it best effort. And if it fails, it fails. And sometimes, it does fail, which I think is why we have this final link in the wizard to check the service status. Which I'm actually going to hit now, so I can show you some of those new services that are in here.


Here's this call detail recording, QoE monitoring service, and Lync server archiving. Those are your three main new services running on this box. Now let's reopen SQL Server Management Studio, refresh the display, and open the databases node. We now see three new databases in our Lync 2010 instance-- QoE metrics, LCS log, and LCS CDR.


Of course, CDR is our call detail records. QoE metrics is for quality of experience data. We're almost there. We've taken care of most of the back-end plumbing. We need to get back to Lync Nugget. We could, of course, just hit the admin URL from any box, but I've been having some Silverlight issues.


So I'm going to open the Control Panel on Lync Nugget. I've downgraded Silverlight to version 4 on this box. I will authenticate as a CS administrator on this box. Maximize my view. And let's take a look at what we've got. We're going to visit a new area of the control panel, monitoring and archiving.


And we're used to how this works by now. The fact that we have a default global policy that affects your entire deployment, but you can in fact scope certain policies, not call detail recording evidently. But for archiving policy, we can do site or user-level policies.


And we go from there. Secondary Navigation shows two tabs for monitoring and two tabs for archiving. There's not a lot here to choose from, quite honestly. For call detail recording, if we select a policy, the global is the default. You can enable or disable CDR with just one click of the mouse from the Action menu.


Otherwise, we can Edit, Delete, or just double left click to go in. I'm just going to modify the global policy in this example. Again, there's not too much here. Enable monitoring for CDR, enable purging. If you're going to do monitoring, obviously you need that enabled.


Purging means that after a certain number of days, SQL and Lync will work together to purge old data. 60 is about 2 months, isn't it? This is going to be dependent upon your security policy and your compliance requirements. I'm going to set this to 1 year, or 365 days, and Commit. Note that that's an instant commit.


If we go to QoE data-- again, if we select a policy, we can globally enable or disable QoE for the policy with just a click. If we go into the policy, besides its name-- again, enable monitoring of QoE data, enable purging, and then you have the purge interval, the maximum duration which I will set to 365. Pretty straightforward.


Archiving as I said, there's two tabs. One that covers policy, one that covers configuration. You can quickly, using the Action menu, enable or disable archiving for internal or external communications. By contrast, you can double left click and do it that way.


Either way, it doesn't matter. One thing that does require a little bit more talking is this external communications. Now, archiving of internal communications almost a no-brainer. But what about when you're dealing with federated partners? Legally, are you required to notify them that you're archiving those communications because their communications are affected by your policy? Well, here's what happens.


With a federated partner, it's assumed that we're using Lync Edge Server for secure federation connections. If we go over to external user access, this is a bit of review from earlier in the course. Excess edge configuration and double left click our Active Policy.


If we have federation enabled, note that we have Send Archiving Disclaimer to Federated Partners. That might be important, again, from a compliance standpoint. And frankly, just a good neighbor standpoint. I know myself, even when I'm hosting web conferences, most of the time I don't record.


But sometimes for archival and training purposes, I'll record. And I just simply know out of habit to ask everybody on the line, I plan to record this. Is everybody cool with that? Now then, if we come back to-- where were we here? Monitoring and archiving.


I don't want to leave this page yet, because I want to make sure I'm not enabling federation. Let me Commit that, and we'll come back to Monitoring and Archiving, Archiving Policy. Let's make sure that both of those are selected on my box. And then we'll go to Archiving Configuration last.


The action menus here are o globally disable archiving, archive IM, archive IM and web conferencing. Very basic. Very basic. We choose the archive setting right here. I'm going to bring it to maximum archiving, both IM and web conferencing. This sub-policy is important, block IM or web conferencing sessions if archiving fails.


You may have such an important need compliance-wise to store all of your IM traffic and conferencing metadata that you don't want anything lost. That you would rather deny service to your IM and conferencing users than not be able to archive that data. So think carefully before selecting that option.


Alternatively, or in addition, we have again, the purge option. Purge exported archiving data and stored archiving data after a certain number of days. Now, if you export and move that data to a different location, I don't see how Lync can get to it. But certainly, the stored archiving data will purge after a certain number of days.


Let's Commit that change. And that's really it. At this point, our configuration of both archiving server and monitoring server is complete. So it's just time to generate some traffic, some IM stuff, and bring up some web conferences with uploaded files. I'm going to do most of that activity behind the curtain so you don't have to watch it.


Because I think you know by now, we've been through conferencing. We've been through IM. I'll spend some time generating the data, and then we'll complete this demonstration by my showing you how we can follow-up on those reports. And also, follow-up on viewing the archived data.


Before we leave the Deployment Wizard, let's as promised, come over to Deploy Monitoring Server Reports. What we're doing here is installing canned reports into SQL Server reporting services. This is going to give us insight. We don't have to create cubes or worry about OLAP or any of that stuff.


We can just use these canned reports to take a look at our quality of experience and CDR data. The first thing it asks us is, where is our monitoring server? We know that's correct. It asks us for the instance and it auto-detected the correct server and instance name.


So we'll click Next. I'm going to give the domain administrator credentials. For the read-only analysis group, I will do nuggetlab/RTCUni versalReadOnlyAdmins. That group is going to be up to you, in terms of who your business analysts are, who needs to actually look at that Lync data.


Actually, I wouldn't think this stuff would be viewable or should be viewable to anybody outside your infrastructure team. And in particular, your Lync admin team. It tells us that the following URL will be used for deployment, HTTPS-- 4443/reports. We specified all of your URL metadata back in the SSRS Configuration Manager as we saw before.


The reports are now starting their deployment. Great, we want to see all these success messages with no warnings. That's definitely awesome. And these are the individual reports that are being echoed. And while we're waiting for this to complete, friends, I've popped out to the Microsoft Download Center.


Before we take a look at the reports, I'll tell you in advance SQL Server Reporting Services is one of those tools that you really need to understand what's being displayed in a report. The report builder and all that is a separate kettle of fish entirely.


Again, CBT Nuggets-- my colleagues, Julie Johnson, Don Jones, Garth Schulte, they've all given some excellent training on SQL Server Reporting Services if you need a deep dive. But for now, I would think that it would be very well advisable to you to download these Work Smart Guide documents for Lync Monitoring Server Reports.


Check it out. These are Word files that show you how to understand those reports, how to get started with monitoring, using the reports, understanding alerting, or you could just download them all as a ZIP file. This is an important resource for you, not so much for the exam success but for your real-world monitoring best practices.


Because unfortunately, due to time we're not going to be able to understand every report in this brief demo. Everything's completed successfully, so let's Exit out. And that completes that configuration. Next thing we want to do is fire up a web browser and navigate to your SQL Server Reporting Services Home URL.


Remember, if you forget that, you can just open the Reporting Services Configuration Manager from your monitoring server SQL Server box, and verify. These are actually clickable URLs here for the Report Manager URL. Now, all I have installed are the Lync Server Reports.


This interface should look familiar to you if you have any experience with working with SharePoint. It's a very stripped down version of Windows SharePoint Services 3.0. There are elements of it that reminds me of WSS 2 quite honestly. But anyway, if we hover over Lync Server Reports, there's a pop-up menu that gives us some management options to actually dive in.


We can get to the Reports Home Page, and then there's a Reports Content sub-folder. All right, so we see our monitoring server reports that were given to us courtesy of the Lync Deployment Wizard are based on system usage. This is call detail recording, or CDR data, call diagnostic reports.


These are failure diagnostics per user. We have called diagnostics that are in a summary for all your users, and we have media quality diagnostic reports. Can you add your own reports? Can you build archiving reports? The answer is absolutely, yes. But you have to know how to use Report Builder and that's a separate subject for a separate time.


If I go to Conference Summary Report, it takes us into the report proper where we can customize the date range, the starting and ending dates, the interval. The options are hourly, daily, weekly, monthly. We can page through, change the zoom, do keyword searches, refresh the view, print.


This guy is pretty cool. Look at all the different output options. General options, basic options, like XML and CSV. We can do PDF, which makes me chuckle when you think about it that we don't have an XPS option, but we have a PDF. Web archive, Excel, TIFF image, and Word.


In other words, we can take this data out, perform further manipulations on it, or just snapshot it as is. Export to Data Feed is pretty cool. What this does is kick out an XML format. It's actually an atom-based XML feed file that you can feed into your feed reader, if you're into really simple syndication or RSS.


That's especially helpful when we're viewing the dashboard page. So this is giving us, in Conference Summary Report, total number of conferences, total number of participants, average participants per conference. Pretty global information. If we come back to Reports, we can do a Peer-to-Peer Activity Report to look strictly at peer-to-peer conversations.


Notice that we get graphics as well as the tabular data, which is good for showing trends. Let's come back to Reports one more time. User Registration Reports, Logons, unique logons, et cetera. And it just goes on from there, failures, et cetera. If you're going to look at these on a daily basis, I'd suggest you bookmark the Dashboard page.


See the link up here in the upper right? We click it, and this is a traditional business intelligence dashboard. It's taking a moment to load. And what it shows us are summary items for all of those reports-- system usage, conference info, call diagnostics.


Not only for this week, but also as a trend, a line chart for the past six weeks. So you can see upward versus downward trends, versus steady states. This is a really nice roll-up of all of those metrics pertaining to monitoring. Now, notice that we also have the ability to export this as an atom feed, pop it into your RSS, and whenever a new entry is added to one of these reports, you'll see it in your feed reader.


So those are the basic elements of monitoring, actually following monitoring using this web application. It's an ASP.NET web application that comes to us courtesy of SQL Server Reporting Services. All right then, now that we have our configuration down, it's time to test monitoring and archiving.


I've been playing around behind the scenes generating traffic in my Lync network. We're talking IM message strings, telephone calls, right up into conferences. And I'm going to quickly generate a conference now so I can show you. But first, just a quick point-- troubleshooting.


This is important. If you find that your Lync Server is not picking up archiving or monitoring, the reports generate no data, you go into SQL Server Management Studio, you're not getting any archiving back, there's a few things that you should check. The first thing you should do is verify your service account identities and your logins and security to SQL Server.


Another thing you want to check-- and this is not very well documented at all. You want to make sure that your computer accounts, your Lync front-ends as well as your monitoring and archiving servers allow the network service MSMQ privileges. Let me quickly show you how that works.


We'll go into Active Directory Users and Computers. We'll make sure that we're showing Advanced features from the View menu. Navigate to the container or OU that contains our servers. Right click and select Properties from the Shortcut menu. Navigate to Security.


Navigate to Advanced. And you want to add-in the network service identity, which I've already done. And I've given it full control in my lab environment. But in your production environments, you obviously want to be very careful about those permissions. Create MSMQ, delete MSNQ.


Make sure that network service is allowed to do that. Even still, you might find that monitoring and archiving doesn't pick up any records. In this case, your front ends, not necessarily your monitoring and archiving servers. You may need to uninstall MSMQ, reboot the server, come back, install MSNQ, and then that worked like a charm for me.


Suddenly, everything started working. So all that having been said, let me switch over to Lync Nugget where Susan Warner is here and she'll start an IM message with her contact and friend, Pat Fabello, I should say. Let's switch over, get that toast, respond, "I'm going to call you." And from the call menu, we'll escalate


this to a VoIP call. We'll come back to Susan's machine. We'll accept the call. Let me immediately mute my microphone and speakers, actually on both ends of the equation. And now to turn this into a three-person conference, why don't we again, come back to Lync Nugget? And why doesn't Susan bring Administrator? By just dragging that guy into the list.


Of course, we're going to have to grab the toast over here on Administrators box. And at this point, we have a full-fledged conference. I believe Susan is the originator of this conference. Things have happened so quickly. Let me open the People Options menu.


Make everyone an attendee. Sure enough, the originator always is a presenter. By default, these other attendees, based on my conferencing policy, originally were presented as well. If Pat for instance, did that same command to make everyone an attendee-- I'm also going to mute the audience while I'm at it-- then that would leave the presenter and Pat as presenters, and just kick Administrator down to the attendee level.


Got it? So let's make sure everybody has their stuff muted. I think we all do. Almost all. And now what I'm going to do is on Lync Nugget Susan's box, let's do a Share, Show Stage. Another bit of troubleshooting that I'm sure we'll see in the troubleshooting.


Nugget is, if you find that you're in a conference and the share option doesn't show PowerPoint presentation, whiteboard, or poll, instead just shows desktop and program, the most likely reason for that is that the Lync Web Conferencing Service has somehow become stopped, or is otherwise not responding on your front-end server.


So be aware of that. I'm going to upload a file here as Susan. I'm going to Add Attachment. I have a simple text file on my desktop that I'm going to use as an example here. The reason I'm adding this attachment is to demonstrate what is archived and what is not.


And there it is, you see the one. What will happen is when participants click that link, they can download the file to their computer. They can also make it available if they've uploaded it to themselves. I'm going to, by default, leave it at everyone. Open, rename, remove.


Other folks in the conference can download it, but they're not going to be able to delete it. Let me now open up and share a PowerPoint presentation that I've put on my desktop. The gotcha here, friends, is that you have to have PowerPoint installed on the system on which you're sharing the deck.


The other attendees don't have to have it, but you, as the presenter, do need to have it installed. So now I've uploaded a file. I've shared PowerPoint. We've done text messaging. We're already on a call, so I think I've generated enough data, both from a monitoring as well as archiving standpoint.


So let's remove everyone and end the meeting, close out the instructor session, and go over to Branch Nugget. Again, close the stage there. We'll minimize the Lync client. And let's have a look at what's going on. You're going to need a little bit of SQL or SQL skills for that.


You'll need to fire up and login to your instance. In my case, it was branchnugget/lync2010. And in there, we want to draw our attention to the LCS log database. The CDR and the metrics, those are for the monitoring. And unless you're really a hard SQL fan, probably don't want to monkey around in those because you have the reports already built for you in Report Manager, or SSRS I should say.


On the other hand, as we already discussed with archiving, there's no really nice front end that Microsoft gives us yet. So you're either looking at a third-party solution. I'm sure there are folks on CodePlex and elsewhere, who have developed a front end for you to look into your archiving data.


Or, we're going to be working here in the SQL directly. Now, there are several tables here. The cool thing is that the LCS log tables are named pretty intelligently. You should be able to understand what they mean. Joins and leaves, MCU join and leaves, messages, roles, et cetera.


Easiest possible way to look at your IM messages is to simply run select star from the messages table. I'm going to use the use command here, use LCS log, go, and then select star for messages and hit Execute. And this gives you-- let me shrink up the navigation pane, the Object Explorer-- all of the recorded messages.


So what do we have here? The columns are a little bit cryptic. You can definitely check out the documentation to understand the schema of the table. But you see here, we have with some markup. You know you have rich text support in the Lync 2010 client. With inline CSS it takes up a lot of space.


Finally, you can see the message there. And these are plain text. They're not stored in any encryption way. Was there a toast associated with that particular message? Of course, there's questions that I'm sure you have. How do you figure out who the sending and receiving users are? Well, that's beyond our scope, unfortunately.


But there's plenty of documentation online that you can leverage to that end. You may have to involve in some table joins. Again, the schema for these archiving databases is available online. If we do a select star from data MCU folder, that just returns one row.


This is the path to where your conferencing files are stored. And remember, we specified the file store when we set up the archive. So it's telling us in the archiving server folder. Notice that there's DataConf and MeetingConf.


There's nothing in MeetingConf yet, but I have just had a session here and it has a really cryptic name. Again, it's not very user friendly, I have to just be honest with you. And finally, when you get into that particular GUID that corresponds to that conference-- it looks like it ends with b37-- there we have the text file that I uploaded.


And we also have the pptx file that I shared. So those files are, in fact, captured. Let's do a select star from conferences and see if we can find b37. I think that's the number that I had just referenced, right? It tells us that the conference URI is originating from sharter.


Conference start time, end time. Again, if you want to change this into user-friendly format and just get more meaningful human readable data, you're going to have to delve into SQL, unfortunately, or go the third-party route. Final thing I'm going to show you-- we're going to fire up the Lync Server Management Shell-- is how to export that conference data.


I'm going to shift, right click, and run this session as administrator, just to make sure I don't run into any rogue permissions issues. All right, the cmdlet in question is export-csarchivingdata. And we can get syntax help for this by prepending get help.


If we just want to see the examples, which is what I like to do a lot, I know generally what the cmdlet means. I want to see examples, just throw in -examples. And it'll give you plenty. It looks like we have three in this case. And we're going to model our work on that.


So let's do an export-csar. And watch this, I'll press Tab. And it guessed correctly. That Tab auto complete is a feature of PowerShell that you really ought to take a look At. It's gotten really smart, especially in Windows Server 2012. We pass in dbinstance, which is a string, "branchnugget/lync2010." We specify a start date. This is a string, "8/25/2012-- I'll say 12 o'clock. End date is "8/25/2012" 22 o'clock. 24 hour time as you see. Finally, outputfolder.


c. It created a folder. Let me quickly pop up explorer conf. Press Enter and let this thing chug. The cmdlet takes a moment to run. If you don't have much that's been archived, like in my case, it was almost instantaneous. Looks like total number of sessions, seven.


Successfully exported sessions, seven. Failed, zero. Well, that's what I want to see. A very final step is to open that target folder, see conf. We have a sub-folder named after the SQL Server and the instance name. And again, we have cryptic folders. And resultant email transcripts, depending upon whether they're peer-to-peer or conference-based in EML format.


To view these message files, you need an application that can handle .EML files. And that's going to be Outlook client, or I've actually downloaded the free kernel EML viewer application that you're seeing here. And as you see, we can browse each one of those files and get metadata about them.


It looks like that largest file, that 800 something kilobyte file, contains the uploaded and shared files from my session. And then working our way back, we can check out the contents of those messages, in plain or even rich text, depending upon what tool you're using to view those EML files.


So there you have it, conferencing and archiving in Lync Server 2010. Monitoring and archiving in Lync Server 2010 review. We began this Nugget by-- you guessed it, as usual, describing the technology. You now understand the business case for monitoring and archiving in Lync Server 2010. You know what's involved infrastructure-wise.


You know about the agent component, the server component, the back-end database component. Going further, you will absolutely answer correctly any questions you receive on your certification exam concerning the deployment, configuration, and use of the monitoring server and archiving server.


We covered some really good rubber meets the road practical content in this Nugget. And it should pay off rich dividends because now more than ever, businesses do have to worry about compliance issues. And now more than ever with people being so accustomed to technology, they want the best possible experience they can get with their telephony, instant messaging, and conferencing.

High Availability and Disaster Recovery in Lync Server 2010

Deploying and Managing Clients and Devices

Patching and Troubleshooting Lync Server 2010

Administering Lync Server with PowerShell

Lync Server 2010 Additional Learning Resources

Please help us improve by sharing your feedback on training courses and videos. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

comments powered by Disqus
Intermediate 16 hrs 20 videos


Basic Plan Features

Speed Control
Included in this course
Play videos at a faster or slower pace.

Included in this course
Pick up where you left off watching a video.

Included in this course
Jot down information to refer back to at a later time.

Closed Captions
Included in this course
Follow what the trainers are saying with ease.

Included in this course
Files/materials that supplement the video training

Premium Plan Features

Practice Exams
These practice tests help you review your knowledge and prepare you for exams.

Virtual Lab
Use a virtual environment to reinforce what you are learning and get hands-on experience.

Offline Training
Included in this course
Our mobile apps offer the ability to download videos and train anytime, anywhere offline.

Accountability Coaching
Included in this course
Develop and maintain a study plan with assistance from coaches.