If you have an Lync Server Infrastructure today and want to upgrade it to Skype for Business here is how to:
Updating to Skype for Business Server 2015 can be done in a couple of different ways, but you need to plan how you will do.
One of the new features in Skype for Business is that you can do an in-place upgrade from Lync Server 2013, meaning that you perhaps do not need to create new servers, and move users like we have been used to.
So why do I write perhaps… You need to look at your environment and see if you meet the pre-requisites:
The Server OS and Hardware
Your Lync servers need to be Windows Server 2012 or Windows Server 2012 R2, to have Windows Fabric ver. 3
If you are on a Windows 2008 R2 platform with your Lync servers, it might be a good time to create new Windows Server 2012 R2 Servers, and do a side-by-side installation.
Also your servers might also be a bit small – so consider if they need more resources. When I create new Lync/SfB servers they usually have the below specs (depending of course of the customer usage and size):
Single Frontend: (up-to 500-1000 Users)
4 x vCPU
16 GB RAM
100 GB disk for the OS (Windows Server 2012 R2)
100 GB for the Lync/SfB files
Other Sfb Servers roles (up-to 500-1000 Users)
2 x vCPU
8 GB RAM
100 GB disk for the OS (Windows Server 2012 R2)
On Enterprise pools I typically have much larger servers and the customer usage is also very different.
The Lync Server version
You need to have Lync Server 2013 patched with all the latest updates from Windows Update, to be able to do an in-place upgrade.
If you have Lync Server 2010, you need to do an side-by-side installation.
If you have a mixed environment with Lync Server 2010 and 201, then it’s not supported to have SfB 2015 in the same topology – In this scenario you need to move the users and services to Lync Server 2013 and decommission the old Lync Server 2010 before you install SfB 2015.
When you do an in-place upgrade from Lync Server 2013 you must schedule to have downtime, as the pool or server that you upgrade needs to be taken offline doing the upgrade.
So if you cannot afford to have the servers offline – make an side-by-side installation and move users and services.
If the upgrade process fails – the procedure to revert back is to have a good backup of your Lync configuration, and then deploy new Lync servers and restore your lync topology – so again consider if can you afford to have the pool or servers offline for a longer period (the time to restore), if something goes wrong.
If you have more than one pool, you have the option to move all users from one pool to the others, and then do an in-place upgrade of the empty pool.
When you are doing the planning, also consider that have the option to do both an in-place upgrade and the side-by-side installation, depending on the server or role that you are upgrading.
For the frontend you might do an side-by-side installation to avoid the risk of restoring if something goes wrong and “long” downtime – but for Edge or mediations servers you might choose to do the in-place upgrade, because they are easily restored or you can have the down for longer time.
In the next post we will start to upgrade to Skype for Business from Lync Server 2013, starting with the frontend pool.
Other Posts in this Serie
If you want to try the new Skype for Business client, you can download a preview version here.
Just install it and it will work with both Lync Server 2010 and 2013.
Friday the 5th December 2014 was a very big day – this was the day that Microsoft finally added video support between Lync and Skype.
Since it was maked possible to do audio calls last year between Lync and Skype, many has missed the video part, which is native when doing Skype calls.
In the first version the video calling is possible from the Skype Desktop Client and to and from the Lync 2013 for Windows and Windows Phone.
Lets see if the iPhone, Android, Windows App etc. clients is updated soon so they also get this possibility.
So how does it look ?
And from Lync Mobile – also Great J
So what do you need to set it up – not much…
If you already have federation with Skype, then you are good to go, and you just need to click the video button make and make your first lync to skype video call.
If you haven’t setup up the Skype federation yet, then look here: http://exchangepro.dk/2013/05/30/lync-skype-integration-now-available/
So when looking at the Lync monitor server reveals this:
Which is not much other that Microsoft has a fine new Lync to Skype Gateway…but the audio stream shows that we are using the Silk Codec from the Lync mobile which is native to Skype and used by millions of users.
And the video stream is H.264
In the comings months we will properly begin to see more to the Silk codec, which should perform better on Wifi networks and other connections.
This is all for now – go happy-skyping with your favorite skype friends and keep support Lync (or Skype for business) when you really want a 1st class Collaboration solution.
Microsoft has just released CU7 for Lync Server 2013, which contains some new fixes, especially the clslogging bug that was introduced in the August security update is fixed now.
The update contains these fixes:
3003346 Cannot see presence status or send instant messages when OWA is integrated with Lync Server 2013 instant messaging
3003347 User cannot dial out to a PSTN number as a guest in an online meeting in a Lync Server 2013 environment
3003350 Cannot search users by using a keyword that differs from Lync Server 2013 AD DS display name format in a Lync client
3008181 Centralized Logging Service Agent Service cannot start after you install a September 2014 update for Lync Server 2013
Get the update here
Microsoft has released the august 2014 update for the Lync 2013 client, which resolves these issues:
- 2985514 Lync 2013 signs out and then signs in every 30 minutes
- 2985513 Lync 2013 crashes when you manipulate a pivot table field during an Excel worksheet presentation
- 2985512 Error “Event ID from source Lync cannot be found” instead of event logs from Lync 2013 appears in Event Viewer
- 2981755 Cannot join a meeting by using Lync 2013 when the ACP MCU services are running on multiple front-end servers
- 2981754 Cannot send CER data when a user cannot join meetings in Lync 2013
- 2981753 Lync 2013 meeting issues after you install Lync Meeting Add-in for Office 2013
- 2981752 Cannot select audio device during a VoIP call in Lync 2013 when a user is enabled for RCC
- 2981751 Lync 2013 does not display telephone number of an Outlook 2010 contact in the contact card
- 2981750 An update enables Lync 2013 users to select the default unselected check boxes for saving instant message and call logs
- 2981749 Artifacts remain in chat input area in Lync 2013 after an instant message is sent
- 2981748 Lync 2013 dials the number that calls are forwarded to instead of the last dialed number
- 2981747 A user’s work number is listed in the “Forward Calls To” list in Lync 2013
- 2981746 Cannot paste data from a webpage to Lync 2013 conversation window
- 2981745 Can’t join online meeting that is created in a non-federated organization by using Lync 2013
- 2981743 Can’t sign in to Lync 2013 by using a cached certificate in Lync online hybrid deployment
Get the update here
Microsoft has released a long waiting update for Lync Server 2013, which is the first one since January 2014.
It fixes these issues:
Frontend and Edge Servers
- 2976568 Address book delta files are not generated in a Lync Server 2013 Enterprise Edition environment
- 2967626 Error “creating procedure RtcResetAbAttributes” when you run “Install-CsDatabase” for rtcab database in Lync Server 2013
- 2967629 Significant bandwidth usage increase by SIP traffic in a Lync Server 2013 environment
- 2967630 Callee receives a missed call notification after answering a call on an IP telephone in a Lync Server 2013 environment
- 2979931 Error “I can’t find the meeting with that number” when PSTN user dials in to conference in Lync Server 2013 environment
- 2978444 Update for Lync Server 2013 to disable Lync Web App users’ ability to upload and show PPT in online meetings
- 2976906 Incorrect time zone is displayed when you create a meeting by using Web Scheduler in a Lync Server 2013 environment
- 2967623 Error “This content cannot be displayed” or blank webpage when you click a dial-in URL in a Lync Server 2013 environment
- 2967624 HD video stutters in a Lync Server 2013 based video conference in Lync 2013
- 2967628 Telephone numbers are missing in a contact card in a Lync Server 2013-based Lync mobile client
- 2967621 Error 404 when Lync phones sign in to Lync Server 2013 front-end servers during SBS failure recovery
- 2967631 Error “”DistributionGroupAddress” and “AgentsByUri” must be set.” when you migrate the RG service to Lync Server 2013
And reliability, stability, and performance Updates to UCMA 4, Administrative tools and Web Conferencing Server
Get the update here
Microsoft has released new updates for the Lync 2013 client, which includes one of my bug reports from last year
- 2941631 Cannot drag a distribution group to change position in your contact list in Lync 2013
- 2941639 Call forwarding to the Response Group fails in Lync 2013
- 2941640 Desktop sharing session stops in Lync 2013 when all screen data is updated
- 2941643 Caller cannot close the window of a transferred call in Lync 2013
- 2941654 Update sorts and searches contacts by Furigana in Lync 2013
- 2941658 CTRL+TAB does not work when you switch between conversation windows in Lync 2013
- 2941682 Instant message appears using incorrect text format when the DisableRTFIM setting is enabled in Lync 2013
- 2941659 Callee’s name and detailed information is missing from the conversation history of a Lync 2013 outgoing call (reported by me J)
- 2941636 Search fails in Lync 2013 when non-Latin characters are used in a different case from the AD DS attributes
- 2941635 Can’t sign in to Lync 2013 when Office 365 account UPN differs from domain account UPN
- 2954951 Slow screen update in application sharing or desktop sharing session in Lync 2013
- 2955577 Lync 2013 takes a long time to sign in after reconnect to the network
- 2955579 Lync 2013 displays un-encoded texts in a toast notification or an instant message sent to another messaging client
- 2955580 Update adds a button to show details about limited functionalities when Lync 2013 connects to a backup pool
I recently had two issues at a customer that I would like to share with you:
The first one is about PSTN call looping and the second one is about Unassigned numbers which don’t work for external PSTN users:
PSTN Call is Looping
I had an issue where an PSTN user calls a phone number which belongs to the organization but is not assigned to any users or services in Lync.
In this case the customer was using a sip trunk from a Danish Vendor called Cirque, and we experience that when a call was made to an unassigned number, that call would cause a loop and in some cases causes the mediation server to fail. →']);" class="more-link">Continue reading
I stopped by one of the vendors today that I’m preferring for switchboard and contact center solutions at my customers, to talk with Bjarne Henriksen, Partner from Competella about a new product they will release within a couple of months.
The product is called: Competella Call Distributor
The Call Distributor is essential an replacement for response group service in Lync Server 2013, which in many areas are good, but after my opium is also missing some more advanced controls and call handling.
When you are using response groups in Lync, it will not be able to leverage the settings you have made like call forwarding or sim-ring etc. which for some customers is annoying because they can’t answer response group calls on their mobile phone. →']);" class="more-link">Continue reading
In my series about using Lync and Exchange better together, we will in this post, be looking at integrating Lync and Exchange so that we can use Exchange as a unified contact store.
What is Unified Contact store you might ask?
Before we got Lync 2013 and Exchange 2013, both products have there own way of storing the users contacts.
Lync can store contacts in Exchange or actually in Outlook in a Lync Contact folder, which is synchronized, and this sometimes can cause problems if they get out of sync. →']);" class="more-link">Continue reading