Monthly Archives: December 2013
The year 2013 is almost finished, and has been a great year, and a very busy year for me.
I have been working almost full time with Lync this year, which was one of my goals back in 2012. I have been on both small Lync projects, larger projects but also maintaining my current Lync installations.
This year was also the year where I decide to do a lot more blogging, which I been doing for almost 5 years now, because I see that there is a need for IT Pro’s like myself, to find relevant blogs about Unified Communications, and because I love to share what I know with my fellow colleagues.
On an average day, my blog has 350 visitors and 30+ email followers, which I am extremely proud of, and I hope that my guides will help others in their jobs, and it will contribute in a lot more UC solutions.
In the last few months if have made my first big series, which was a how to guide on deploying Lync Server 2013 High Availability solution which until now has had over 10.000 page views.
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: →']);" class="more-link">Continue reading
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. →']);" class="more-link">Continue reading
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.
Exchange is a great product, but have you ever missed a feature that it really needs to make it even better.
Submit your idea at Ideascale and perhaps you are lucky that the Exchange Team will pick it up and implement it in a future version.
Microsoft has released a critical security update which, if not implemented could lead to remote code execution on the Exchange Server.
They problem affects both Exchange 2007, Exchange 2010 and Exchange 2013.
Read about it here: MS13-105
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/