Free Seminars

Keep an eye here, or register to be informed of OUR FREE events ...

Read more


Step by Step guide’s or How to documentations can be found here...

Read more

Our Sponsors

Better Together User Group,info & sponsors

Read more

About Erdal Ozkaya

Who is Erdal Ozkaya?
To learn more about him, click here...

Read more

Video Tutorial

Watch and learn the easy way...

Read more


Lync servers provide both local and remote access to enterprise Unified Messaging and Voice workloads such as IM, Conferencing, Voice calls and Application Sharing. When it comes to remotely accessing workloads such as Join a meeting, find local dial-in phone numbers, access to address book and meeting content such as PowerPoint presentations, a reverse proxy is required to provide such functionality. Since Forefront Threat Management Gateway (TMG) was discontinued in 2012, customers have been looking for alternatives. KEMP LoadMaster products can be that alternative which not only acts as a load balancer for your Lync workloads but can also serve as much needed reverse proxy for abovementioned workloads.

Read more ...

Exchange 2007, Exchange 2010 and Exchange 2013 – How to design name spaces and certificates for simplicity and redundancy

In this webinar Nicolas will cover
• What a name space is and why you should care
• Types of name spaces for each version of Exchange
• Name space considerations for multiple datacentres or locations
• Hybrid mode considerations, and eliminating single points of failure

Read more ...

As Microsoft Lync get's more and more popular, it's time for you to learn it better , but how ?

Are you going to spend thousands in useless Training Providers ( not all of them of course), which most probably you dont have any budget anyway.

Don't worry, this blog post has everything to make you a Lync 2013 ready for free

Read more ...

KEMP Redefines Entry Level Load Balancer Performance with the New LoadMaster 2400

The LoadMaster 2400 Addresses Growing Demand for Scalable, Secure Web Applications


New York, NY – October 1, 2013 – KEMP Technologies today announced the availability of the LoadMaster 2400, the newest addition to KEMP’s hardware load balancer portfolio. As more web-based applications are being deployed, the demand for scalable and secure application delivery has risen. The LM 2400’s improved SSL acceleration engine and increased throughput delivers on this need with support for 1,000 SSL transactions per second and 1.2 Gbps throughput.

The LM 2400 intelligently and efficiently manages web traffic distribution among physical and virtual servers to ensure end users receive optimal application performance and user experience.

The LM 2400 is an essential component to include for high availability of critical application infrastructures with diverse application delivery and load balancing needs. Combing the latest advancements in Layer 4 and Layer 7 application delivery technology, the LM 2400 delivers application optimization, server load balancing, SSL acceleration and Layer 7 content switching for up to 1,000 servers and 256 virtual clusters.

Read more ...


Since I have starterd to work for Kemp Technologies ( i started to get lots of questions abot the Microsoft Load Balancer versus Kemp Load Balancer.


Read more ...

Jonas Andersson – wrote a very useful article which i would like to share here in my blog. Jonas is taking you step by step through the configurations based on Exchange 2013 RTM

I decided to write a post that included both the KEMP configuration together with the Exchange 2013 configuration. I’ve also seen that Jaap Wesselius have posted an article regarding this topic already, it’s my hope that I can fill the gap regarding the complete configuration of both Exchange and the load balancer.



Read more ...

Load Balancing in Exchange 2013 is an article written by Jaap Wesselius who is Microsoft MVP on Exchange server. And this article will show you how you can Load Balance Exchange 2013 …

I wrote about load balancing in Exchange 2013 earlier, but that blog was based on the beta of Exchange 2013. Time have passed and there’s some more insight so I decided to update this blog…

In an earlier article I explained about load balancing in Exchange 2010. The important topics are the setup of the load balancer (one arm vs two arm), but also routing, persistence, distribution and SSL offloading of the client traffic is important.

One thing to note is that in Exchange 2010 the connection between the client and the Exchange 2010 CAS server is very important. The CAS server is where all the rendering takes place, so the connection between the client and the CAS server is a state-full connection, one that you want to maintain during the lifetime of the connection. Therefore persistence is important in load balancing Exchange 2010.

In Exchange 2013 things are different. All rendering takes place in the Exchange 2013 Back-End (i.e. the Mailbox Server) while the Exchange 2013 Front-End is nothing more than a protocol proxy. The connection between the client and the Exchange 2013 Front-End server is therefore a state-less connection. Don’t interpret this as a ‘clue-less’ connection, the Front-End server is authenticating the client connection and proxying to the correct Mailbox Server and is such is 100% aware of the connection. But if the connection is somehow lost and reconnected through another Exchange 2013 Front-End server it is not such a big deal since the connection with the Mailbox Server is automatically restored.

Read more ...
Template Settings
Select color sample for all parameters
Red Green Blue Gray
Background Color
Text Color
Google Font
Body Font-size
Body Font-family
Scroll to top