Microsoft Lync Server 2013 Step by Step For Anyone - REV013
Microsoft Lync Server 2013 Step by Step For Anyone - REV013
Microsoft Lync Server 2013 Step by Step For Anyone - REV013
Author
There are a couple benefits of this type of book: Quick to market, mistakes can be easily
addressed and new revision released. One last and big benefit is the interactivity of this
book: You can click on that date/time URL underneath each chapter title and jump to the
live blog article and comment/interact!
Several challenges are: No editorial process (arrgg!) and we are working with products that
are not even released yet! So expect new editions of this book and your welcome to submit
mistakes you see via blog comments or twitter to @matthewlandis
Enjoy!
Matt has been very involved with Windows Server based communication and PBX solutions
including Microsoft Lync, 3CX and snom ONE. He is currently a Microsoft Lync MVP, a prolific
blogger at http://windowspbx.blogspot.com and has written many articles on Microsoft Lync
including "Planning, Implementing, and Using Microsoft Lync Server in Small Business
Scenarios" on Microsoft Technet. He was the first 3CX Valued Professional (2008-2010) and
has co-authored a book on Windows communication software "3CX IP PBX Tutorial". Matt likes
giving back via community forums: he has contributed thousands of posts to Microsoft Lync,
snom/snomONE and 3CX community forums over the years.
Matt is also a pastor at Cavlary Mennonite Fellowship and when the chance affords he likes to
travel internationally with his wife Rosalyn.
Company: http://www.landiscomputer.com
Blog: http://www.windowspbx.blogspot.com
NOTE: Remember Lync Server 2013 Preview is not meant for live/production environments.
Below are the step by step instructions to install Lync Server 2013 Standard Edition Front End
on Windows Server 2012. Here is an outline of what we will do:
1. Prepare Servers
2. Install Lync Server 2013
3. Prepare Active Directory
4. Prepare First Server
5. Configure DNS
6. Build Topology
7. Install Lync Server System
8. Add & Enable AD Users
9. Login to Lync 2013
Prepare Environment
Some prerequisites for you Lync system:
Server Requirements
o Front End server must be joined to domain
o FE must have UI installed
Install Silverlight (will save time later)
Front End Must have these Features
o Roles
Web Server (IIS)
o Features
Message Queuing | Message Queuing Services
Remote Server Administration Tools | Role Administration Tools |
AD DS and AD LDS Tools
User Interfaces and Infrastructure | Desktop Experience
Windows Identity Foundation 3.5
.NET Framework 3.5 Features
.NET Framework 3.5
HTTP Activation (Important!)
Non-HTTP Activation
.NET Framework 4.5 (all options)
o Roles
Web Server (IIS)
Role Services
Common Http Features Installed
Static
Default doc
Https errors
Health and Diagnostics
Http logging
Logging Tools
Tracing
Performance
Static Content Compression
Dynamics Content Compression
Security
Request Filtering
Client Cert Mapping Authentication
Windows Authentication
Install using Windows Server 2012 “Add Roles and Features Wizard”
Insert CD and Run Setup.exe. You will be prompted to install Visual C++, click “Yes” (below)
Note: Microsoft Lync Server 2013 has a new centralized logging mechanism.
This is the reason for the logging tool not being installed with Lync Server
2013 Preview. Jens Trier Rassmussen has a complete article on this subject
at http://bit.ly/S3DL4Q. Also, Randy Wintle has written a Powershell UI for
this new central logging at http://bit.ly/Pbbp8v.
Click “Prepare Active Directory”. (As noted in prerequisites, you will need AD DS and AD LDS
Tools Feature installed on your Front End to complete this step.)
CSAdministrator
NOTE: the user running setup needs to be Administrator of the Lync FE local machine.
Now lets go back to the Deployment Wizard and click “Prepare first Standard Edition server”.
(Note: as noted in prereqs, Windows Identity Foundation 3.5 must be installed for this
process to complete successfully)
Lets open DNS Manager on AD server. Right click on your domain (in our case lab.local) under
Forward Lookup Zones, click “Other New Records…” and scroll down to “Service Location
(SRV)” and click Create Record.
Service = _sipinternaltls
Protocol = _tcp
Port number = 5061
Host Offering the service = fqdn of Lync Std. FE server or Pool. (In our case
FE01.lab.local)
We will also create 3 DNS A Records. Right click, “New Host (A or AAAA)…” Add a DNS A
record for
meet
dialin
admin
as shown below
Now lets go back to the Deployment Wizard and click “Install Administrative Tools”.
Next we will go to Start and run “Lync Server Topology Builder” (below).
Select New Topology (as shown below) and then give the topology some name (just any old
name like “mylab.tbxml”)
Microsoft Lync Server 2013 Step by Step for Anyone
19
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
Now we will be define this topology.
Click “Finish”
FQDN: FE01.lab.local
o Note: if this is a Standard Edition, this FQDN will be exactly the same
FQDN as your FE server (FE01.lab.local in our case)
Standard Edition Server
Conferencing
Enterprise Voice
CAC
Tip: What works best for me is to NOT define ARCHIIVE and MONITOR
servers till you are ready to actually install them. I suggest to NOT select
Archiving and Monitoring now. We will do that after we have actually
installed the SQL server and are ready to define those roles in topology
builder.
Right click on “Lync Server 2013 (Preview) and then “Edit Properties”
Now we will install some Lync Server System components, put Certs in place and Start
Services:
Delayed or Immediate Request? Send the request immediately to an online cert authority
SIP Domain Setting on SAN: Select SIP Domain (example: lab.local) | Next
After services are started you can open the Services to verify all the Lync Services are
running.
Next, we will move to our AD server and add several users to Active Directory (I suggest for
your first test users to NOT use the Administrator, but 3 other users). In our case I added:
u1@lab.local
u2@lab.local
u3@lab.local
Click “Enable” and if you get no errors, you should have 3 Lync users ready to login. Let’s
open Lync 2013 and login!
Please note some pieces in Lync that you have not configured yet:
Continue your lab with more articles in this Lync Server 2013 Step by Step Series:
Part 1 – Step by Step Installing Lync Server 2013 Standard Edition Front End
Part 2- Step by Step Installing Lync Server 2013 SE Monitoring Server
Part 3 – Step by Step Installing Lync Server 2013 Persistent Chat Server
Part 4 - Step by Step Installing Your 2nd Lync Server 2013 SE Server Associated
Backup Pool for Resiliency
Part 5 – Step by Step Enabling Lync Server 2013 Enterprise Voice Features, Response
Groups and Managers
Using Lync 2013 and OneNote 2013 Integration
Tommy Clarke: for point out “HTTP Activation” required for successful LWA
operation
Syed Nasir Abbas: Notes some Lync prerequisites that will be helpful
o http://ourgalaxyorg.blogspot.com/2012/12/installingdeploying-microsoft-
lync.html#!/2012/12/installingdeploying-microsoft-lync.html
FortressITX: For pointing out that this article did not list steps to create Lync Share:
o http://fortressitx.com/blog/microsoft-lync-topology-file-share-error-fix/
In Part 1 of Installing Lync Server 2013 Standard Edition we go our lab Lync 2013 server up
and running. In this next step by step we will install the Monitoring role using SQL 2008. In
Lync Server 2010 a Monitoring required an additional server. In Lync Server 2013 this has
changed and Monitoring will be on your Front End.
So, to get started, lets prepare our Lync Server Front End (Windows Server 2012) by
installing Queuing (you will/may not need this in RTM Lync Server). Do this by opening the
“Add Roles and Features Wizard”
Native Mode
Now click Install (15minute install/wait time)
When done test SQL Reporting Services by running “Reporting Services Configuration
Manager” (from Start menu)
Install-CsDatabase –LocalDatabases
Specify credentials to access monitor SQL database. (for this lab I used domain
Administrator)
Note: After rebooting this server, SQL Server Reporting Services (MONITOR) did not seem
to auto start and need to go into the SRS Config and start it.
We are on a journey installing the various Lync Server 2013 roles. Today we will install the
Persistent Chat role collocated on our Lync Server 2013 Standard Edition Front End! I would
like to give Elan Shudnow credit as I read over his excellent Persistent Chat with Enterprise
Pool articles before launching on installing this collocated edition.
Prerequisites:
Next will define a Persistent Chat pool in our topology. Let’s Open Topology Builder
Click Next.
Next we will add a new chat room. Let’s drop into Lync Powershell and run
Next we will add a user to this new Chat room by running the below Powershell:
Continue your lab with more articles in this Lync Server 2013 Step by Step Series:
We are on a journey installing various Lync Server 2013 roles. In today’s step by step, we will
setup our 2nd Lync Server Standard Edition pool and then set it up as a Backup Registrar so
automatic failover can happen. We will also look at Lync Server 2013’s new failover
capabilities that allow full client capability to be restored in the event of a disaster. To use this
blog the only other lab you need to have done is Part 1.
Part 1 – Step by Step Installing Lync Server 2013 Standard Edition Front End
Part 2- Step by Step Installing Lync Server 2013 SE Monitoring Server
Part 3 – Step by Step Installing Lync Server 2013 Persistent Chat Server
Part 4 - Step by Step Installing Your 2nd Lync Server 2013 SE Server Associated
Backup Pool for Resiliency
See Lync Server 2013 prerequisites here. Installing your 2nd Lync Pool is much like installing
the first. We will go over the steps below briefly, with special notes. But for detailed notes on
installing an FE server, just refer to the Part1 blog in this series.
Insert Lync Server 2013 CD, and when you see popup below, click Yes
Right Click on “Standard Edition Front End Servers” | New Front End Pool
NOTE: While the topology builder and this blog refer to a Standard Edition Front End Pool,
just be aware that a Standard Edition Front End Pool really is just one Front End Server,
because there only can be one server in a Standard Edition Pool.
Microsoft Lync Server 2013 Step by Step for Anyone
85
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
Next | Enter our Backup Front End FQDN (FE02.lab.local) | Next
Check Conferencing, Enterprise Voice. (Note: you will not be able to check CAC because
only 1 per Site)
Goto the Primary (FE01.lab.local) Standard Server and Open Lync Server
2013 Deployment Wizard
Now Goto the Backup (FE02.lab.local) Standard Server and Open Lync Server
2013 Deployment Wizard
To test, log into Lync Server control panel. Notice you will now be asked which Lync pool
you want to log in to. Let’s select FE01.lab.local.
Once the LSCP is open well click Users | Find | Select u1@lab.local | Action | Move Selected
Users to Pool… |
Now lets open Lync 2013 client and login using user u1@lab.local that we just enabled on our
2nd Standard Edition Front End Pool/Server (FE02.lab.local). Good, our new pool works!
Since we could easily move user(s) to our new Pool/Server with no sweat, now lets get
dangerous. Call someone using u1@lab.local and CHANGE POOLS DURING THE CALL.
Let’s repeat the steps we just took above, but do it during a live call and see what happens.
Below is a screenshot of what happens if you change pools/servers during a peer to peer call:
The Lync 2013 client will momentarily logout and back in again
During this time (as you see below) the call continues
Sharing continues
Video continues
As noted in the conversation window, functionality is momentarily limited:
o Video cannot be started during momentary logout/in
o Sharing limited and below items will be interrupted
Polls
whiteboard
Powerpoint
o
Now let’s setup our 2nd Front End Pool/Server as an Associated backup pool so that if our 1st
Front End Pool goes down the clients can automatically failover to the 2nd Front End Pool.
Next, we’ll edit the primary “Standard Edition Front End Servers” by right clicking and click
“Edit Properties”
Associated backup pool = FE02.lab.local; (Note the warning about having both FE’s
in the same site. For our lab, and in some production we can ignore this)
Automatic = Checked
Failover = 30secs (for lab purposes, this would be short for production…)
Failback = 30secs (for lab purposes)
Then click OK to finish.
Open text file to see what you should do next. In our case we are instructed to run Install or
Update Setup/Update on FE01 and FE02. Now click Finish.
Lets open Lync Server Deployment Wizard on FE02.lab.local and click on “Install or Update
Lync Server System”
Now lets go into DNS and add a record for our Backup Pool /Server. This SRV record is
necessary so that if the first server (FE01.lab.local in our lab) goes down, the client can find
the backup Pool/Server.
So let open the DNS server management and add the SRV record. The things that are
important:
Service = _sipinternaltls
Protocol = _tcp
Priority = 10 (take note: this value is different than your initial SRV record)
Weight = 10 (take note: this value is different than your initial SRV record)
Port number = 5061
Host offering this server = FE02.lab.local
NSLookup
set type=srv
_sipinternaltls._tcp.lab.local
NOTE: Please, take a minute and thank Dustin Hannifin and Jason Lee for providing this
crucial step in this blog post.
With both Primary and Backup Front End Server running do the following:
Navigate to: Personal | Certificates and delete the cert named same as your Lync username.
Make sure all your users (that you want to test resiliency for) are homed on FE01.lab.local.
Next, we’ll simulate our FE01.lab.local machine being down by disabling the NIC.
Now they will try to login to the backup pool (in this case FE02.lab.local)…
NOTE: We setup our failover to happen in 30seconds. I’ve noticed in my lab the failing Lync
clients will logout very near 30 seconds, but it could take several minutes till the clients are
able to log back into the Associated Backup Pool/Server (FE02.lab.local). (ie: be fully failed
over) I haven’t taken the time to investigate if this is my lowly lab’s performance , or
something built into Lync. (if someone knows, please post a comment)
Microsoft Lync Server 2013 Step by Step for Anyone
99
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
But sure enough, it logged into backup pool! You will notice the Lync 2013 client let’s you
know you have some limitations:
Now if we enable the NIC on FE01.lab.local the clients should Failback to FE01.lab.local in
30 seconds. (NOTE: on my lab some clients would failback as soon as 10 seconds.)
Much of what we have discussed in this blog so far is largely the functionality you will find in
Lync Server 2010. (I suspect you could use most of the above steps in Lync 2010.) But with
Lync Server 2013, the Lync Server administrator can now failover the CMS and the failed
pool so that the “Limited Functionality due to outage” is removed. Let’s get started with our
failover.
Our first step is to find out where the Active Central Management Database is hosted. To do
this we run the PowerShell:
Get-CsService –CentralManagement
As shown below, FE01.lab.local is the PoolFqdn (we will refer to this as $CMS_Pool) of the
currently Active CMS.
The next step is to check if the the $CMS_Pool is running Lync Server 2013. You can do this
in Topology Builder (in our lab we know it is, but in a live environment we might not) If the
$CMS_Pool is running Lync 2013 we can use this PowerShell to see who it’s backup pool is:
Get-CsManagementStoreReplicationStatus –CentralManagementStoreStatus
Below we have an example how this command will look with the $CMS_Pool available.
Now lets disable the NIC on $CMS_Pool (ie FE01.lab.local) to simulate server down. Our
primary Lync FE is now down! (shown below)
(NOTE: If this is a Ent. Edition server you will need to check which Back End holds the
primary CMS using: Get-CsDatabaseMirrorState -DatabaseType CMS -PoolFqdn
<Backup_Pool Fqdn> . Read more about this command by Clicking Here. Running this
command on Std. Edition will fail. On a Std. Edition server there is only one server so we
know which it is. )
Next we will run the command to failover the Central Management Server to our Backup
Server:
Get-CsManagementStoreReplicationStatus –CentralManagementStoreStatus
Sure enough! the new ActiveMasterFQDN is now FE02.lab.local (as shown below). Great!
On my 3 user lab this script took about 50 seconds to complete. After it completed I
waited a little over a minute until full capability was restored to the Lync client!
The Chat service was not restored because resiliency was not setup in our lab for this
service.
Conclusion
Well--yahoo! We have successfully setup a Lync Standard Edition Associated Backup Pool
and we have demonstrated Lync Server 2013’s very improved complete Failover resiliency.
Continue your lab with more articles in this Lync Server 2013 Step by Step Series:
Part 1 – Step by Step Installing Lync Server 2013 Standard Edition Front End
Part 2- Step by Step Installing Lync Server 2013 SE Monitoring Server
Part 3 – Step by Step Installing Lync Server 2013 Persistent Chat Server
Part 4 - Step by Step Installing Your 2nd Lync Server 2013 SE Server Associated
Backup Pool for Resiliency
Part 5 – Step by Step Enabling Lync Server 2013 Enterprise Voice Features,
Response Groups and Managers
Using Lync 2013 and OneNote 2013 Integration
Special Thanks to Elan Shudnow and his great article on Lync 2010 Resiliency:
http://www.shudnow.net/2012/05/04/lync-2010-central-site-resilience-w-backup-registrars-
failovers-and-failbacks-part-3/
http://social.technet.microsoft.com/wiki/contents/articles/9289.second-lync-standard-edition-
server-to-provide-a-limited-high-availability-en-us.aspx
http://jasonmlee.net/archives/459
In this step by step we will look at enabling Enterprise Voice features in Lync Server 2013. If
you are interested in the new Response Group Manager feature in Lync 2013 click here .
To get by in Part 5 you need to have done at least Part 1 of Our Lync 2013 Lab.
To enable our users for Ent. Voice lets open the Lync Server Control Panel. Now click on
Users. To save on CPU no users are shown by default so just click on Find to show all your
currently enabled Lync users.
Now We will see a list of Lync enabled users. Note in the Telephony column that our users
are enabled for “PC-to-PC only”. Let’s changed that by double clicking on a user to edit.
Microsoft Lync Server 2013 Step by Step for Anyone
108
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
Now we can change a few setting
Telephony:Enterprise Voice
Line User: tel:+18005551003;ext=1003
If we click on the Phone Tab/Button we will see our phone dial pad. From here we can make
our first “Voice” call. If we click the “Check” button Lync will call the Lync Audio Test
Service. Go ahead.
To enable the call Park feature go to Voice Features | Call Park | New
Once the call is Parked, you will be notified which of the “slot” the call is in. In the below
case it is in #500. Anyone on Lync with Ent. Voice enabled can pick up this call Parked by
dialing #500. You can click “COPY” to IM this to someone or verbally.
By default, if no one picks up the park xx minutes, the call will ring back to the
person who parked the call.
You can only have 1 call park orbit per user/deskphone. So, for example, you can
not have a Park for Sales and a Park for Service.
Unlike some PBX systems, you will not be able to see if someone is currently in
Park via a light/button on a phone
Setting Up Normalization
Name: Extensions
Length: Exactly 4
Pattern to match: ^(1\d(3))$
Translation rule: +1800555$1;ext=$1
Internal extension = checked
Note: The normalization rule we just setup will only take care of extensions in the 1000-1999
range. In our lab exercises we’ll make sure we stay in that range, but if you to a little
“exploring” just be aware.
Because of the way Lync Server is designed the changes we made above will take some time
to propagate out to all the clients if we just let the process happen normally. We can “push”
this process by taking the below steps on each client we want to test “right now”.
Run Update-CSAddressBook from the Lync PowerShell and wait about 5 minutes
o you can check Lync Server event log to see when this happens
Signed out of the Lync 2013 Client and delete everything under:
o C:\Users\%username%\AppData\Local\Microsoft\Office\15.0\Lync
o Lync 2010 =
C:\Users\%username%\AppData\Local\Microsoft\Communicator
Now you should be able to dial Lync user’s by their Ent. Voice 4 digit extension number.
Unassigned Number
ERRATA NOTE: the 2nd number in the number range below should be exactly the same as
the first. If you are using the ext=xxxx suffix you can have only 1 extension per range. If
using plain jane DID number you can have a range.
http://technet.microsoft.com/en-us/library/gg398522
If you have an “ext” LineURI you can only have 1 number in Unassigned Number
range. If a normal DID you can have a range.
If you have a legit number that falls inside an unassigned range you will still be able
to call it
Response Groups…
Commit
Next we’ll setup a Queue. Queue | New | Select a Service (Front end Pool. In our case
FE01.lab.local) |
Lync will now pop out a browser window will pop up. From here you can create a new
workflow/response group. Let click on “Create” beside “Hunt Group”.
next
Now that we have tested our response group, let’s circle back and look at a new feature in
Lync Server 2013: Response Group Managers. RGS managers allows us to configure
otherwise normal Lync users as RGS managers that can login to Lync Server Control Panel,
Response Group Config web page or PowerShell and only have access to appropriate
response group(s) and configuration.
Response Groups in 2013 can be Managed by a manager or UnManaged, which means they
are administrated by the Lync Admin.
To setup a Response Group Manager is to add our Response Group manager user to the
CSResponseGroupManager AD Group. We’ll ad u1@lab.local.
The Queues and Groups cannot be used in another Response Group if we are going
to make this a managed RGS
After we add our user, scroll to the bottom and click Save.
https://FE01.lab.local/cscp
https://FE01.lab.local/rgsconfig/default.aspx
and Lync Powershell
In Users tab, Manager can see users, but not edit them
In Response Group tab Manager can see only their own Response Groups, Queues
and Groups.
They can not add new RGS, but can add new Queues and Groups.
Continue your lab with more articles in this Lync Server 2013 Step by Step Series:
Part 1 – Step by Step Installing Lync Server 2013 Standard Edition Front End
Part 2- Step by Step Installing Lync Server 2013 SE Monitoring Server
Part 3 – Step by Step Installing Lync Server 2013 Persistent Chat Server
Part 4 - Step by Step Installing Your 2nd Lync Server 2013 SE Server Associated
Backup Pool for Resiliency
Part 5 – Step by Step Enabling Lync Server 2013 Enterprise Voice Features,
Response Groups and Managers
Using Lync 2013 and OneNote 2013 Integration
The Lync Web App (aka LWA) gives external users (even without
credentials) ability to connect to Lync 2013 meetings without having Lync
client installed on their pc. Users with organization credentials might use
LWA when they are at a PC that doesn’t have the Lync 2013 client
installed.
If we followed the steps in Part 1 of this series then the Lync Web App
should be installed and ready to use. By installing the pre-requisites on
your FE and enabling Conferencing when defining the Lync Topology you
did everything needed to install and configure LWA.
In this blog we will test to make sure the LWA is working correctly.
Before starting, if you are using a server or virtual machine to test LWA,
make sure your audio devices are properly configured
right click on speaker beside clock, click on “Playback Devices” and you
be asked if you want to enable Windows Audio Service, the answer is
Yes.
To start a meeting, go to a computer that has the Lync 2013 client installed
and logged in and start a meeting by pressing ALT+M or clicking Options
| MeetNow
Open Internet Explorer and enter the above URL. (Note: actually LWA
will work on select versions of Internet Explorer, Firefox and Safari,
depending on O/S and Version. See this page for details.
NOTE: If this PC has Lync client installed on it, suffix the URL with
?SL=1. This will force the PC to use the browser instead of the Lync
client.
Example: https://meet.lab.local/u2/NVCKCK1G?SL=1
Microsoft Lync Server 2013 Step by Step for Anyone
134
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
NOTE: When you browse to the meeting url in your lab, you may get a
Windows Security logon request, you can click Cancel.
Next you will see the Lync Web App sign in screen. Since our first test
will simulate a guest external user, let’s click on “Sign in here instead”.
Now we see the guest login screen below. Now we can type any guest
name and click Join the meeting
If this is the first time you ran LWA on this pc you will be prompted to
download and install a small 7MB LWA plugin. Click Run
NOTE: if you do not install the plugin you will still be able to connect to
the meeting, just the media based part of the meeting (audio, video,
application viewing)
Below is the Options and settings screen, which we will note is similar to
the Lync client Options.
[screen shots]
due to the functionality of the LWA there is not a Lync 2013 branded
Attendee client for Lync
LWA does not require Silverlight
Continue your lab with more articles in this Lync Server 2013 Step by
Step Series:
Part 1 – Step by Step Installing Lync Server 2013 Standard Edition Front
End
Part 2- Step by Step Installing Lync Server 2013 SE Monitoring Server
Part 3 – Step by Step Installing Lync Server 2013 Persistent Chat Server
Part 4 - Step by Step Installing Your 2nd Lync Server 2013 SE Server
Associated Backup Pool for Resiliency
Part 5 – Step by Step Enabling Lync Server 2013 Enterprise Voice
Features, Response Groups and Managers
Part 6 - Step by Step Testing Lync Server 2013 Lync Web App and
Looking at Functionality and Features – Part 6
Using Lync 2013 and OneNote 2013 Integration
Microsoft Lync 2013 Now integrates more tightly with OneNote 2013 and in this blog we’ll
go over how this functionality works. There are basically 2 OneNote integration modes:
My Notes
Shared Notes
My Notes
My Notes in Lync 2013 is a quick way to start your own personal notes about this Lync
Meeting. Not a super exotic feature, but handy. Hover Over/ClickOn Share | OneNote | My
Notes (or CTRL+N)
NOTE: With Shared Notes, The first thing to note (no pun intended) is that you will need to
share your OneNote and give access to this this OneNote Notebook apart from Lync. In other
words, you are sharing OneNote largely like you do if there is no Lync 2013 involved, and
Lync just distributes the link to the meeting participants.
Before you do anything in Lync 2013, I suggest you open Open OneNote and Login to your
Skydrive (or other online account) In OneNote click File | Share. Now click on Invite People
and type in the people you want to have access to this OneNote and when done click Share.
Participants in this will get a Sharing Request. They can Accept. Next they can click Share |
OneNote and click on the shared OneNote. (click Yes, to the Security Notice)
(Notes: One Lync Meeting can actually have more than one Meeting Notes PAGE shared.
Actually one person can share more than one page in one meeting! Also, note that the last
shared meeting is at the top of this list of meetings)
If there is a participant in the meeting who doesn’t have access to the shared
notebook, they will get a Lync notification that a notebook has been shared with
them, but they will get an error if they try to open it.
If you share a notebook, those you shared it with can see the WHOLE OneNote
Notebook.
If you are an Attendee, you cannot Share OneNotes, nor can you remove
Note that SHIFT+F9 pushes/pulls updates right now. If they press SHIFT+9 they
will get the changes quicker as well.
If the presenter changes pages in the notebook, this does NOT change the page for
other participants.
if the participants open the OneNote too soon after the presenter made it, they may
not land on today’s meeting page if there is more than one meeting/page in the
notebook
If you rejoin a meeting from conversation history, the link to OneNote will be
available.
Continue your lab with more articles in this Lync Server 2013 Step by Step Series:
UC holds the promise of a new model of communication where being "on hold"
happens less often. In the real world sometimes there is no other option but
"holding" and because of this soothing music on hold to keep our callers happy
is expected.
With Lync Server there are some questions I see coming up about music on hold
and I thought I would take a crack at trying to answer some of them and clear
some of the smoke and fog rolling across some new Lync administrators minds.
NOTE: After you make these changes you MAY need to wait an hour or
more till the changes propagate the whole way down to your client. A
great way to ensure the changed came down to your client is to change the
WMA file to some location other than the default. You can see then in
Lync client exactly when the change has occurred.
When you configure the MOH for a Response Group you are defining the
MOH the caller will hear while waiting in the queue, NOT what they will
hear when a Lync User presses the hold button. Remember, the
endpoint/Lync Client provides the MOH delivered when Hold button is
pressed.
Lync Phone Edition Aries devices can now provide MOH by simply
upgrading the LPE device. If you update your Lync Phone Edition “Aries”
devices to 7577.4366, putting calls on hold will now play the
DefaultHold.wma file to callers. At the moment you either use this MOH
file or nothing on LPE, there is not way to change this file by admins or
users.
Below are my steps to get MOH working on your LPE devices. Using the
below instructions instead of KB 2703325 will help avoid a possible snafu
related to pre-existing Lync client music on hold set centrally using the
MusicOnHoldAudioFile setting in the csClientPolicy commandlet.
Onward…
You cannot change the preset MOH file on the Aries device.
o It is set to the DefaultHold.wma music file, which is the same as
the default Lync Client Music on hold file. (click here to listen to
the defaulthold.wma)
If you want to use the MOH on the Aries device, you cannot centrally
configure the MOH file for the Lync client. The client policy setting
“MusicOnHoldAudioFile” MUST equal “”.
The new LPE/Aries MOH features works fine with Lync Server 2010 or
Lync Server 2013 since it is totally a feature of the LPE device.
There are 2 ways that MOH can be provided by Mediant & MediaPack
gateways:
o by the Call Progress Hold Tone (fixed BEEP, no music)
o or by the prerecordedtones.dat file. (this can be an actual MOH
file, of very limited size, in supported gateways) (Note that the
changing the Call Progress tones requires a gateway reboot and
changing the prerecordedtones.dat does not.)
By default the Mediant 800 will play the Call Progress Hold Tone when a
Lync device put on hold and Lync is not providing MOH
o When a call is transferred this same (irritatingly loud beep) is
played to the caller before the transfer happens. Not a good
experience and your users will likely ask you to remove it.
The size allowed for prerecordedtones.dat is as follows
o Mediant 1000 = 2MB
o Mediapack gateways = 200K
o Crazy as it sounds, Audiocodes support (as of 7/24/2012) says
Mediant 800 does not support prerecordedtones.dat.But
(whisper) we’ve used a 76k file filled with silence and it seems
to work—use this tip at your own risk. (8/30/2012 Note: music
on hold via prerecordedtones.dat stopped working in the latest
FW. Audiocode’s support says it will be added back in at version
6.6 or 6.8 Msbg800 FW but that is several months out.)
How to setup MOH on Audiocodes by UnplugthePBX:
o http://blog.unplugthepbx.com/2011/11/22/lync-music-on-hold-
for-aries-and-other-phones/
I’ve been told by Ferrari support (NOTE: there are no support URLs to
reference ATM and I have not tested this) that OfficeMaster Gate can
provide MOH with no file size limitations. (Note: the OfficeMaster Gate
product uses a standard HP rackmount server to explain why there are
not the normal space restrictions)
How to setup music on hold on OfficeMaster Gate gateway:
http://ucblog.deutinger.de/?p=278
OfficeMaster Gate: http://www.ferrari-
electronic.com/en/products/officemaster-gate.html
If a UserA, using Lync 2010 client, is put on hold and the other side does
not provide music on hold, the Lync 2010 client will provide a default
“KerChung” sound every 30 seconds. Where does this come from? It may
be a little confusing/unituitive, but it comes from the User A’s Lync client.
Microsoft Lync Server 2013 Step by Step for Anyone
163
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
So to put it another way, if you want to change the standard “KerChung”
YOU hear when someone else puts you on hold (and doesn’t provide
MOH to you), go into “Change Windows Sounds” on your PC. (Sounds |
Program Events | Microsoft Lync 2010 | On Hold) Also be aware that
whatever sound you select will be played, then 30 seconds of silence, then
repeated.
Free: http://opsound.org/genre/classical/
iTunes: https://itunes.apple.com/us/album/on-hold-music-vol.-
1/id445328651
If anyone else has Lync music on hold real life experience they wish to
share, please do so in the comments.
I’ve been spending the last couple days on and off getting familiar with Sonicwall VoIP
features. since there are lot of Sonicwall devices in the field you most likely are going to
meet up with one sooner or later. (and this will only get worse with Dell’s acquisition of
Sonicwall) (grin) Another challenge is that most Sonicwall engineers are not spending their
days thinking about VoIP, much less Microsoft Lync and SIP over TCP. (smile)
This is the exact question I had. I’ve noticed that goggling seems to often return old
Sonicwall HowTo’s that are a bit hard to follow since the older Sonicwall firmware is just a
little different looking. I came across this short PDF manual that I think encapsulates doing
simple tasks in Sonicwall well:
The simple answer is that Sonicwall firewall VoIP features only work on SIP UDP traffic, not
TCP traffic that Microsoft Lync uses. (This does not mean that Sonicwall will not work Lync, it
just means that there is no need to try to use the Sonicwall VoIP features with Lync at this
time.)
Want a source? Open this document and notice on page 15 that you can set another SIP
signaling port if it is not the standard 5060…but only for UDP traffic…and Microsoft Lync uses
TCP for signaling.
If you want to do some more reading about the Sonicwall VoIP module click here.
The reason Lync calls are missing from the “Call Status” screen is because Sonicwall (as
noted above) only displays UDP VoIP calls here and Microsoft Lync uses TCP for call signaling.
“SIP Transformations” is Sonicwall’s language for what many others call ALG. Should this be
turned on or off?
Actually, it doesn’t matter at ALL how you set these items because Sonicwall firewalls can
only do “Enable SIP Transformations” (aka ALG, or VoIP/SIP ALG) on UDP traffic and Lync only
uses TCP.
So don’t sweat it and you can ignore all the dire warning on the on forum that tell you to turn
these settings off. (grin) Well, just to be safe…let’s uncheck them. (just in case some future
firmware upgrade does enable them)
”The Current Implementation of SIP Transformations only affects UDP and not TCP hence we
cannot transform SIP over TCP. There is an Enhancement Filed for the same and can be
expected in future. No ETA.”
Yes. This is a security device, if you aren’t up to date---you are not being responsible.
Absolutely. The Sonicwall AppFlow Monitor lets you easily setup a filter to show in realtime
just the traffic you want to see: For example you can easily see SIP Trunk traffic from your
Lync Mediation Server, or your Lync Edge Server traffic through your Sonicwall.
Below we have a screenshot of the AppFlow Monitor showing the traffic to a Lync Mediation
Server. As you can see, at first there was merely SIP signaling traffic, then 1 SIP trunk call
and then after a bit a 2nd SIP trunk call. At any time you can hover over the traffic types
(lower left corner of chart) to get how much traffic is passing using that port/ports.)
Sonicwall devices can tag traffic with DSCP tags, but the Sonicwall device itself will not
prioritize traffic based on DSCP if it is going LAN > WAN. So if you have a Lync Mediation
server that is sending traffic to your ISP (and ultimately to a SIP Trunk provider), even if the
Lync Mediation server tags this traffic with DSCP, the traffic will not be prioritized through
the Sonicwall Firewall Rule. (Use Sonicwall Bandwidth Management to achieve this.) If the ISP
honors DSCP the packets will be prioritized once it reaches the ISP.
Conclusion
Bottom Line: Sonicwall and Lync work together just fine, but you need to understand both
well.
Sonicwall will do 1 to 1 NAT’s just fine. Sonicwall currently does not do ALG but Lync
Certified SIP trunk providers should be able to configure their side to avoid the need for ALG
on your firewall. The biggest take away is that Sonicallwall VoIP features do not work on TCP
traffic at this time.
Misc Links:
QOS:
http://help.sonicwall.com/help/sw/eng/6800/25/8/1/Firewall_qosSettings.html#1080295
PSTN Echo Test:+1 703-376-ECHO (3246)
RTP seems to always use Sonicwall LAN>WAN rule. (Egress=From Lync Server;
Ingress=From SIP Trunk/Remote Party)
o SDP tell Lync to do this
Appears SIP signaling uses Sonicwall WAN>LAN rule
I wondered around in the “pineapple fields” a bit trying to get all these PIC pieces together
so I thought I’d compile them here. Open your Lync users to millions of Skype users via Live
Messenger PIC!
Since Skype to Lync federation is already working at the IM/P level and will get audio around
the June 2013 time frame, you will want to start getting your Lync Server 2013 Live
Messenger PIC provisioned to take advantage of this.
NOTE: For the purposes of this blog we will use the names Live Messenger and Microsoft
Account. Live Messenger might also be know to some users as WLM or Windows Live
Messenger. Microsoft Account might also be know to some users as Windows Live ID or Live
ID. There is some ambiguity as to whether everything we reference as Live Messenger will be
be changed to Skype in the future, but at this time the labels are still Live Messenger.
Make sure your Lync Edge server is working “ship shape” before even trying to federate to
Live Messenger. Here is a TechNet article on some tests you can do to ensure your edge
server is working correctly.
Microsoft Lync Server 2013 Step by Step for Anyone
171
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
Make Sure NO Live Messenger Usernames Are Using Your Lync Domain
Name
Before getting starting this PIC Registration process, make sure you have no users who’s Live
Messenger usernames that are using your Lync domain. To fix these usernames, have the
users login to their Microsoft Account to change the username domain to something other
than the Lync domain.
1. For example if your Lync Server is at “house.com” you need to change any Live
Messenger usernames that have “vanity” domain ending in “@house.com” to
something else. (preferably to a default Microsoft Account domain like "@live.com")
2. REMEMBER: you can only change your Microsoft Account username once every 6
months—so you will want to be VERY CAREFUL and get it right the first time!
Proceed with caution.
3. To change a Microsoft Account username, login with the Microsoft Account that
needs the username changed and go to:
https://account.live.com/summarypage.aspx and click on “Rename account”
NOTE: Currently Microsoft Account users are noting that MSA usernames cannot be changed
(as shown below) It appears changing usernames caused some issues and Microsoft is looking
into the issue. Microsoft has no ETA on at this time. Click Here
To avoid issues later, (the issue: those who don’t remove and re-add see this contact’s
presence as offline) I recommend that you have Live Messenger users whose username’s have
been change, to notify others who have them on their contact list (whether Lync, Live
Messenger, Skype or other IM clients) to remove them and add them again with their new
Live Messenger username.
Provision Live Messenger PIC Federation for Your Lync Domain With
Microsoft
Get Microsoft Live Messenger (Skype?) PIC provisioning started with Microsoft by heading over
to http://pic.lync.com
1. Microsoft says it could take 30 days: My experience was 7hrs later Live Messenger
was provisioned. Microsoft Lync PIC provisioning team noted that AIM typically takes
a bit longer.
Under Federation and External Access | Access Edge Configuration | Enable federation and
public IM connectivity (shown below)
A final step to enable Live Messenger PIC you need set Lync to not force encryption. Do this
by following these instructions.
To add Live Messenger clients to your Lync contact list add them to Lync just like Lync
clients!
1. Note: If the Live Messenger username you want to add is using a vanity Live
Messenger username domain, enter the contact like this: live-messenger-
username(live-messenger-username-vanity-domain)@msn.com. For example:
john.martin@xyz.com would be john.martin(xyz.com)@msn.com.
How Do I Enable Lync <-> Skype Federation from Skype Side? Click Here
How Much Will Lync <-> Skype Federation Cost? Click Here
How Does Lync <-> Skype Federation Work Under the Hood? Click Here
Microsoft Lync Server 2013 Step by Step for Anyone
180
Get a free Lync Proposal in 1 Day! http://bit.ly/MBmd09
Nov 2012: Lync <-> Skype IM/P Has Started Working: Click Here
Feb 2013: Lync <-> Skype Voice Has Started Working for Some: Click Here
Sources:
http://technet.microsoft.com/en-us/library/ff945947.aspx