A few days ago, we cleared some time. Ready to test the new In-Place Upgrade by upgrading our in-house Lync Server 2013 to Skype for Business Server 2015.
(Details, once again: System is a single Lync Server 2013 Standard Edition with one Edge Server and a SIP Trunk for Enterprise Voice. SQL Server 2012 backend database.)
Almost immediately though, we hit a snag and had to stop. Reading our documentation, we came across a requirement that almost seemed to contradict the whole notion of an “In-Place” upgrade.
In-Place Upgrade Can’t Run on a Server with Lync Core Components or Admin Tools On It!
I’ll quote the TechNet page Upgrade to Skype for Business Server 2015 for an explanation.
Step 1: Install Administrator tools and download topology
Connect to computer in the topology that does not have Lync OCSCore or any other Lync components installed.
According to Microsoft, Lync 2013 Admin Tools cannot be installed on the Lync Server before Skype for Business In-Place Upgrade proceeds.
You’ll also find this referenced on other Lync blogs with Skype for Business Server install walkthroughs.
- Mark Vale’s Blog: Skype for Business Server In-Place Upgrade Step by Step. Under Front End Server Pre-Requisites, “A server or workstation without Lync 2013 Admin Tools installed.”
- Jaap Wesselius: Upgrade Lync 2013 to Skype for Business 2015 Step-by-Step. Under Upgrade Process, “It is not possible to install these on the existing Lync 2013 server, so a (temporary) server needs to be used. It is important that this server does not contain any Lync 2013 binaries.”
- Guy Bachar’s “Just a Lync Guy” Blog: Lync Server 2013 Standard to Skype for Business Server 2015 Standard In-place Upgrade (Offline Method). Under Step-by-Step Upgrade, “Connect to a computer which is part of the domain but does not have any Lync core components or admin tools installed on it.”
The important question: Why?
What is Microsoft up to with this snag?
We might have a partial answer in a related issue.
LRS Admin Tool Not Compatible with Skype for Business – The Old Version, Anyway
As it turns out, you can’t have the LRS Admin Tool running on the Lync Server either. According to the Plan to Upgrade to Skype for Business Server 2015 page:
Be sure to uninstall LRS Admin tool for Lync Server 2013 before running In-Place Upgrade. The LRS Admin Tool for Lync Server 2013 cannot coexist with Skype for Business Server 2015. After running In-Place Upgrade install the new LRS Admin tool, see Microsoft Lync Room System Administrative Web Portal for Skype for Business Server 2015.
So a new version of the LRS (Lync Room System) Admin Tool is available in Skype for Business. They want you to remove the old version first, to avoid conflicts. Okay. That makes sense.
Is this the case for the Lync 2013 Core Components/Admin Tools too? Another version conflict? Does Skype for Business’ new Administrative Tools conflict with Lync’s?
After some more digging, I determined this is indeed the case.
- Skype for Business’ Administration Tools need to replace the Lync 2013 Admin Tools, in order to begin In-Place Upgrade.
- If the Lync Admin Tools are NOT removed, you could end up with an error which halts In-Place Upgrade.
#2 is important. Take a look at this recent TechNet support thread: Upgrade to Skype for Business Server – TechNet Support Forums
Reply #10 contains some screenshots and a description of the error you’d hit with Core Components. The error text is as follows:
“The MSI OcsCore.msi returned error code 1603, log file location: C:\Users\LYNCADMIN\AppData\Local\Temp\OcsCore.msi-[2015_05_14][19_15_33].log”
(You’ll see different date & number stamps in the log filename.)
Reply #10 was able to fix this by using Revo Uninstaller on Lync’s Core Components…but was immediately faced with another installation error. Troublesome.
And seemingly avoidable, if you remove the Lync Core Components/Admin Tools first.
What We Recommend – Use a Fresh Server or Desktop for Installing Administrative Tools
But what if your Lync Server is a Standard Edition like ours? The Core Components are on the same server as the Front End Role – it’s rather hard to do an In-Place Upgrade like that!
The alternative (and what we’d recommend if you’re starting an In-Place Upgrade) is:
Don’t use a computer with Lync Core Components or Admin Tools on it.
- A fresh Windows Server (no Lync Server 2013 components installed) added to your domain, OR
- A desktop already on the domain.
Not entirely sure why Microsoft couldn’t auto-remove Core Components right before installing Skype for Business Administration Tools. For whatever reason they opted not to.
But that’s why we have blogs like this one – to help the rest of us work with Lync, now Skype for Business, and its related tech.
Speaking of blogs, if you’re eager to do an In-Place Upgrade, I recommend reading all 3 of the above-referenced blog posts. Mark, Jaap and Guy all did a great job of laying out step-by-step walkthroughs.
Have you done a Skype for Business In-Place Upgrade? How did it go? Please comment or email me your experience. Every installation is unique; I’d love to hear what happened for yours.