Follow my journey to Las Vegas for the LyncConf14, and learn what’s happen and see why you should have been there.
Now that looked at the planning for upgrading to Skype for Business, let’s do the actual upgrade of a Lync Server 2013 topology.
In this post we will make an offline upgrade, meaning that we will take the existing frontend pool offline, and do an in-place upgrade of the frontend server.
Before you start the upgrade process you need to update the Lync servers to the latest CU
And for Windows Server 2012 R2, you also need to install this hotfix.
First you need to mount the SfB Server ISO on a server that don’t have any Lync or Skype components install (ocscore)
Run setup.exe to install the deployment tools.
Read the EULA and Accept it to continue
When the Deployment Wizard is installed and started – install the Administration Tools
When it finish, close the Deployment Wizard and start the topology builder
Click OK to download the topology
Type a name for the topology file and click Save
Navigate to your frontend pool and right click and select “Upgrade to Skype for Business Server 2015″
The Frontend server is now moved to Skype For Business Server 2015.
Right Click and Publish the topology
Click Finish and close the Topology builder.
Wait for replication to finish
Next on the frontend server, start powershell and run this command
This will prevent the Lync services to start should the server be rebooted.
Run the same command on all Lync servers in the pool, that is going to be upgraded.
Next mount the SfB DVD on the frontend server and start setup.exe
Read the EULA ones again and click OK.
After an hour or so the update to finish on the frontend server
Next go to powershell (remember to open the management shell) and start the pool with the below command
Start-CsPool –PoolFqdn fe01.exchangepro.dk
Type Y to start it
The upgrade of the frontend pool is now completed, and you can continue with the other Lync servers that you have in your pool, like the edge and mediation servers.
In the next post we will look at upgrading the Edge, Mediation and Director servers.
Other Posts in this Serie
The big date has arrived – the Skype for Business Client has finally arrived, in form of an update on Windows Update.
The Skype for Business client formerly known as Lync will properly also shown up a single download on MSDN and Premier download in a near future.
So head over to the Windows Update and check for new updates and get the new Skype for Business Client
If you haven’t updated your Lync 2013 servers to the December or February patch then, the SfB client will auto revert to the old GUI when it starts up
I have been running the preview version of SfB the last couple of months, and I absolutely love it – I have for now two features that I love.
The first one is the smileys which are now animated, and super cool
The second think I love is call control which is always shown – also when you switch you other programs or are in a remote session with a server.
So the days where you struggle to end a call after talking with a user is finally over.
If you want to know more about the other new features in the new client, head over here to read more.
Around May 1st the Skype for Business Server will arrive, which is also going to be cool – if you haven’t heard about it yet – then look forward to all my new blog posts.
Skype for Business is almost here – according to this Microsoft blog it will be generally available in starting of April.
I case you have experience problems with the Lync-Skype video integration the last couple of days, then it is because Microsoft has disabled the feature.
Accordingly, to Microsoft they expect to enable it again next week, when a new Skype version has been released
See here for more information
Microsoft revealed today some news about the next version of Lync – namely that it will get a new name: Skype for Business.
Read about it here and what is comming next year.
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
If you ever make drawings of a Lync or Exchange then you should get the updated Visio stencils, which has been updated.
Microsoft has released new updates to Lync 2010:
Lync Server 2010
- 2954538 Application and desktop sharing features are missing when Lync Web App runs on Internet Explorer 11 or Firefox
- 2884800 Can’t join a meeting in Lync Web App when the Region and Language format is Turkish in a Lync Server 2010 environment
- 2954865 Conference Auto Attendant fails when users join PSTN conferences at the same time in Lync Server 2010 or Lync Server 2013
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. more »
Microsoft has updated the Lync mobile 2013 apps
It has changed slightly in the appearance:
The new version is: 5.4.1087.0 more »
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. more »
The time is near… In only one week, I will be in Las Vegas and waiting for the Lync Conference of the year – #LyncConf14 to start.
My expectation to the conference is very high, and I defiantly hope that I will learn something new at my stay.
I will on Friday the February 14 depart from Copenhagen to London – a small 2 hour flight – more »
In my series of using Lync and Exchange better together, I’m showing how to integrate these two great products with each other.
Use Voicemail in Office 365
In part 2 we were setting up Lync to use voicemail in Exchange 2013 and that works great, but when I wrote that post, I realized that not all companies have an on premises Exchange but instead are using Exchange in Office 365.
So in this post we will have a look on how to integrate an onpremises Lync Server 2013 with Exchange Online, and place the voicemail in there. more »
In my new series we started by looking at integrating Lync and Exchange so that we could use Chat and Presence in Outlook Web Access and get a more rich experience when these great products is used together.
In this post we will have a look at the Voicemail capabilities in Exchange Unified Messaging and how to set it up.
I will be using Exchange 2013 and Lync 2013, but the process for using Exchange 2010 is almost the same.
As you might know, in Exchange 2013 the Unified Messaging role is installed on all servers as default whereas in Exchange 2010 it was a role you need to install, either separate or together with some of the other roles. more »
If not, then it is time to talk to Lync and tell it what to do.
What I’m I talking about? The Lync Mobile 2013 client has been updated to version 5.3.1037.0 on Windows Phone edition, and now you can give the phone voice commands by holding down the Windows Logo.
Below is a screen dump of the commands it understand.
This is my brand new series on how to use Lync and Exchange better together and get the riches experience with these great products together.
I will in this series show you how Lync and Exchange can integrate with each other, so you can get the full potential with the products.
Chat and Presence in OWA
Let us start by the basic and setup chat and presence in Outlook Web Access.
When I look in my OWA, I don’t have any presence status on my contacts:
And also I’m not able to sign to Lync from OWA more »
I have in the last couple of month’s two customers, who wanted almost as many sip domains as possible in Lync, besides the usual 2-3 sip domains I normally see.
This post is what I found and what I had setup up, at one of the customers.
I found these restrictions:
- An internal SIP certificate has a limit of 4096 characters.
- Globalsign (my public cert provider) has a limit of 100 SAN names.
First of all 100 names sub in a public certificate – that will cost a million $ K more »
The Lync phone edition has also been updated here in January.
Lync Phone Edition for HP 4110 and HP 4120
The update contains these fixes:
Microsoft has released new updates to Lync Server 2013.
Lync Server 2013 CU4
There is no reports yet if it contains any new features – perhaps they are saying them for Service Pack 1 which is expected soon.
But the update fixes these issues:
As a continuation to my previous post (Use Location Service on Wifi in Lync), I will in this post tell you what is hot and what is not so hot when using location service on a wired network.
So as I my previous post a customer asked me to enable location service in Lync so that the colleagues could locate each other in there fine new building.
Before I started, I might have promised the customer that Location Service was the 8 wonder in world and it was SO cool – I knew only the theory – or most of it K
Back to the customer, which is located in Denmark, Europe – so we can’t use location service for cool stuff like E911 (it’s a wonder that the ambulance can find us J)
Before Christmas, I had a customer, which want to use location service in Lync to display where the users is located within the building.
Because we are located in Denmark, and we don’t have Enhanced 911 or Enhanced 112 as it is called in Europe, the location information is only information to the colleagues.
You can define location service in different ways – by Wifi Access Points, By Switch, Switch port or by Subnets.
I will in this post only show how to define the locations on wifi – but with location service it’s also possible to assign polices which restrict the users bandwidth usage.
We have now come to the final part in the Lync Server 2013 High Availability series, which is Hardware Load Balance the external Nic on the Acccess Edge Servers.
We have defined the Edge server setup in part 11 – so this part will only focus on the HLB setup.
As for my previous posts, I will use Kemp Load Balancers for the External network, which is placed in a special DMZ zone where I’m not using NAT for the Edge servers.
This means that I have public IP Addresses on my edge servers and will have it on my HLB’s as well.
The network looks like this: more »
In this part, we will continue to Load Balance our Lync Server 2013 High Availability solution, and will look at the first part of load balancing the Access Edge Servers.
When you are deciding to use load balancing for the Access Edge Servers, you should consider these things:
Is external Edge communication critical for my organization?
If you can answer no, you might only need one Edge server, which makes everything much easier, because you can use NAT, and do not need a special network for the edge servers.
If you answer yes, then ask this question:
Is communication with Public IM and/or OCS 2007 partners critical?
If you answer no, you can save the money for the hardware load balancers and just use DNS load balancing for the edge servers. more »
In this post we will be looking on how to load balance the Lync Sever 2013 Director Servers.
We have in the last couple of posts been dealing with hardware load balancing of the internal servers:
In Part 14 we have setup the Kemp Load Balancers that is uses internally.
In Part 15 we have setup Load Balancing of the Office Web Apps Servers.
In Part 16 we have setup a combination of DNS Load Balancing for the Lync Services and Hardware Load Balancing for the Web Services.
In Part 17 we have setup Load Balancing of all the frontend services.
Have you ever got a great idea for Lync and a feature that is really missing.
Share your idea and vote for others – perhaps you could be lucky at the Lync team will implement it at some point and make Lync even better,
Have a look here: http://lync.ideascale.com/
In my series of building a Lync Server 2013 High Availability environment, we have in the last three parts been setting up Load Balancing for the internal Lync Servers.
In Part 14 we have setup the Kemp Load Balancers that is uses internally
In Part 15 we have setup Load Balancing of the Office Web Apps Servers
In Part 16 we have setup a combination of DNS Load Balancing for the Lync Services and Hardware Load Balancing for the Web Services.
In this part we will look on how to setup the other alternative to the load balancing method in part 16, which is Load Balancing of all the Lync Services.
When using this method you must be sure that the Load Balancers can handle all the load of all the Lync Services.
Let’s first have a look at the topology builder, which you should configure like this: more »
As I started with in Part 14 you can load balance the frontend servers in two ways.
- DNS Load Balancing and Hardware Load Balancing the Web Services
- Hardware Load Balancing all Lync Services
This post is the first part where we uses both DNS load Balancing for the native Lync services (like sip) and the hardware load balancer for the web services in Lync.
First we need to change to topology so that the internal web services uses another name that the pool name – in this case cswebint.exchangepro.local
I the last post we installed and configured the internal kemp load balancers. In this post we will be setting up load balancing for the Office Web Apps servers
The Lync HA setup contains two Office Web Apps Servers.
Start by exporting the WAC server certificate from one of the WAC servers. The certificate should contain the WAC farm name (both internal and external), and the two server names.
Navigate to Certificates -> SSL Certificates and click Import certificate.
In the last post, we installed two additional frontend servers to the Lync High Availability environment that we has been creating for quite some time now.
In part 7 when we installed the first frontend server, we made the configuration on the Frontend pool dns records, so that the pointed to the first frontend server, which we had at that time. We did the same for the Office Web Servers and Directors servers.
Lets start by talking a little bit about how to load balance Lync.
Both the Lync clients and Lync Servers can be using DNS Load Balancing. This is achieved by configuring multiple records in DNS to point to the same name.
When the clients and servers query DNS for a records – it gets all results for a record returned – so if three records points to the same name, the result will include these three records.
The client and server will then contact the first server and if no response is received, it will contact the next.
The Lync servers will load balance the clients automatically between the available servers though an algorithm, which also will redirect clients to the other servers in the pool.
But there is a catch – DNS load balancing only works for Lync traffic like the sip traffic (5061/TCP), it doesn’t work for web traffic like https (443/tcp), and that is why you need a load balancer for the web traffic. more »
Windows Server 2012 R2 contains a new feature called Web Application Proxy. WAP is a very simple reverse proxy which can be used to publish the Simple URLs in Lync Server 2013.
In this post, I will guide you through how to setup and use it as a reverse proxy for Lync and the Office Web Apps Server.
I have in my setup defined these public DNS names:
- Csweb.exchangepro.dk (Frontend Server external name)
- Cswebapp.exchangepro.dk (Office Web App External name)
- Cswebdir.exchangepro.dk (Director Server external name)
- Lyncdiscover.exchangepro.dk (Lync Discover url) more »
In my Lync Server 2013 High Availability environment series, we have now deployed most of our Lync servers, but we still need to deploy two more frontend servers.
The topology that we have deployed so fare consist of an Enterprise Pool with one frontend server.
The minimum recommend number of frontend servers in an Enterprise Pool is three – Have a look at this Microsoft page for guidelines about planning for frontend servers: http://technet.microsoft.com/en-us/library/gg412996(v=ocs.15).aspx
At this point I assume that you have installed the two new frontend servers with the same specification has the first server (see part 5: http://exchangepro.dk/2013/09/19/prepare-your-servers-for-lync-server-2013-ha-part-5/).
Before you start I will recommend that you do this in maintenance window, because you will need to reboot the frontend servers, which can cause disruption for the users.
The new November update for the Lync 2013 client has been released which contains some new features:
The first thing you will notice is that the profile pictures is in lined in chat communications, like you have it on Lync Mobile:
We have now come to the part where we are going to deploy the reverse proxy servers. Because we are deploying a high availability Lync environment, the reverse proxy servers should of course also be redundant.
In my redundant reverse proxy setup, I will use two virtual hardware load balancer from Kemp Technologies in an active/passive setup.
I will deploy two VLM’s, which is going to be placed in the DMZ Internal zone.
With the October update Lync Server 2013 is now supported on Windows Server 2012 R2 according to Doug Deitterick’s blog http://blogs.technet.com/b/dodeitte/archive/2013/10/25/lync-server-2013-now-supported-on-windows-server-2012-r2.aspx.
We have now come to the step where we are going to install the Access Edge Servers.
In our topology, we are going to have two servers, which we have defined and created in an earlier post, but you can make use of the tips that I will come with in this post even though you are only installing a single Edge Server.
The Access Edge Servers is actually one of the parts that is often causing problems in a Lync installation, not because the servers is not function or the software is broken, but simply because it’s not set up correctly, and with that I mean the servers, but also the surrounding components like the firewalls, dns etc.
The servers is placed in two different DMZ zones, like in the below illustration: more »
In this post you will learn how to install the director servers in our Lync Server 2013 High Availability environment.
The Director role is an optional server in Lync Server 2013, which means that it is not an requirement to have it in an environment like the one I’m building in this series.
But I like the director in an environment where I have enterprise voice enabled, as an extra protection for the frontend servers, to protect them from Denial of Servcie attacks from the Internet.
In case of a DoS attack it will be the director that is affected and not the frontend and thereby my enterprise voice will continue to run.
We now have our backend servers up and running and one of the frontend servers, so in this post we will install the two WAC servers in a farm. (see the topology in http://exchangepro.dk/2013/09/21/creating-the-lync-server-2013-ha-topology-part-6/).
The Office Web Apps Servers or WAC is used in Lync Server 2013 for streaming PowerPoint content from Lync meetings to the participates. This means that the participants can see the nice features like animations, sounds, videos that might be inside the presentations.
When a presenter starts a presentation from a Lync meeting the content is uploaded to the Lync FileStore. From there the WAC servers will access the content, and begin to stream the PowerPoint to the participants.
The same WAC servers that we use in Lync can also be used by Exchange 2013 and SharePoint 2013, to provide an web experience for the Office applications. For now, I will only use them for Lync. (but keep coming back and I will show you how to use them with Exchange 2013).
Microsoft has relased Lync Server 2013 CU3 (October 2013), which contains a number of fixes (one of them I reported to MSJ)
You can get the updates here: http://exchangepro.dk/updates/lync/lync-2013-updates/
The biggest update in the release seems to be to the Call Park Service, where it now possible to get transferred to a operator when pressing *0 in a dialin conference.
The other updates includes this:
Windows Server 2012 R2 is soon reaching the GA state, so I decided that I would test how Lync Server 2013 behave on a Windows Server 2012 R2 RTM Server.
So this guide will take you though on how to install Lync Server 2013 on a Windows Server 2012 R2 Server, RTM.
I have created a virtual server in my HyperV lab with these specs:
- 3 vCPU
- 8 GB RAM
- 100 GB Disk space
I my prevoius post we installed the first frontend server and started the services for the first time.
As with all new Lync Servers it’s very important to keep the updated with the latest fix from Microsoft
So lets start by updating the first frontend server with CU2 (http://exchangepro.dk/updates/lync/lync-2013-updates/).
Download the “LyncServerUpdateInstaller.exe”
Right click on the file and select “Run as administrator” more »
In the seventh part of the series of installing a Lync 2013 HA, we have come to the point where we are ready to install the first frontend server in our Lync Server 2013 High Availability solution.
We are going to have three frontend servers, but for now we have only defined one frontend server in the Enterprise Pool. When Lync is up and run we will later on add the two other frontend servers and hardware load balancing.
When we are installing the Lync servers, the deployment wizard will read information from the central management store and thereby determines what needs to be installed on the server.
Start the Deployment Wizard on the first frontend server. more »
Today I had very nice day together with my good colleague Rune, which is taking care of a big Lync 2013 environment at one of our customers.
We were making some changes of the frontend servers, which require that we should run the Enable-CScomputer.
However, that failed on two of the three frontend servers with this error:
Alter failed for Server ‘LYNCSERVERlynclocal’ more »
Today I had a case at a customer where the PSTN users, which dial in to a Lync Conference, was only shown as “Guest Guest” like below:
The number which is normally shown on mobile users wasn’t there. more »
If you experience problems when you try to sign in to Lync Phone Edition, with this error:
“An account matching this phone number cannot be found. Please contact your support team.”
The new September update for the Lync 2013 reveals new features besides bug fixes that it also contains.
The first new feature is Spell checking in the Lync Client, which is a feature that many users will love.
Hopeful this can help remove all the spelling errors when using IM J but time will show.
The spell check follow the language on your computer – In my case its Danish, so my spell check is in Danish. more »
In the sixths post in my series of installing a High Availability solution for Lync Server 2013 we are now going to create the Lync topology.
In the previous posts we have been making some of the fundamentals ready for the Lync installation, by creating a SQL 2012 mirroring cluster, a DFS file share and making a bunch of servers ready.
I will start by the drawing below, which will summarize how the servers is placed and how the servers is named.
In the Fifth post in my little series of deploying a Lync Server 2013 High Availability environment, we have now come to the fun part were we almost can begin to deploy Lync.
In the previous post we have been setting up a SQL Server 2012 mirroring cluster and a DFS file share.
As a prerequisite to use Lync, you should have deployed an internal PKI infrastructure, because Lync uses certificates to secure its communications. You could in theory use public certificates if you have a lot of money, but I will not recommend it.
As a start, we need to create the servers, which we are going to be used in the installation of Lync, which will include more »
This is my fourth post in the series of deploying a Lync 2013 HA environment.
In the previous article, we have been deploying SQL Server 2012, which we are going to use for a mirroring cluster in Lync 2013.
Before starting the Lync installation, we need to deploy a Lync file store. A Lync file store is a file share where Lync stores replication data, the address book, Conference content etc.
Because we are deploying a HA solution the file store should be deployed on a DFS share which replicates the data between two or more file servers. You could also deploy a File Server cluster.
I this post I will use a DFS share.
In Lync 2013 Enterprise users is allowed to make PSTN dial out from a Lync conference without a plus CAL license.
This feature is controlled, in the Conference Policy for the user
I like to use windows firewall on my servers – many disable it, but I will rather use a little bit more time to figure out to configure it, so the first part is to add exceptions to the default rules, so that the SQL cluster will work.
I will run the below cmdlets on all three SQL servers (you could get more restrictive on the witness server).
Before running it on the servers you should adjust the IP ranges so it fit your environment and subnets.
New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQLServer)” -Direction Inbound –Protocol TCP –LocalPort 1433 -RemoteAddress LocalSubnet -Action Allow more »
In this guide I will continue the installation of the SQL 2012 Mirroring cluster which I will use for my Lync 2013 High Availability installation.
You can see the first part here
When using an SQL mirroring cluster you will need a witness server – This is how to install that.
The specs for my witness server is:
- 1 x CPU
- 4 GB RAM
- 100 GB Disk
- Windows Server 2012
If you have ever seen the dialin page in Lync Server 2013, you might found that it looks terrible in its native format, and especially the formatting around the dial in numbers.
Below is an example (which actually looks okay)
But with a little change to the dialin page it’s actually possible to make it look nice. more »