It’s Not Always a Holiday for the IT Department

It’s that time of year again and everyone is busily preparing for the holiday season. There are trips to plan, Black Friday gifts to buy, and last minute preparation for the arrival of friends and family. This time of year sees a measureable increase in economic activity; part-time workers are hired, more shipments are made, and finally – an increase in network utilization.

Behind every merchant website (and network) is a backend system managed by an Administrator or Systems Engineer. These individuals are the ones who must deal with the numerous helpdesk issues – issues that escalate this time of year and are not easily resolved. These support professionals are often tasked with working late into the night and early in the morning. This rigorous holiday schedule is par for the course when it comes to keeping the network functioning smoothly for the customers. Downtime is directly correlated to lost sales, so a sense of urgency exists among the network support personnel.

An Engineer may be in the middle of Thanksgiving dinner, but if they get a call that the network is down they must immediately respond. These IT professionals are the unsung holiday heroes behind network connectivity. This can be a thankless job; customers don’t often recognize how quickly the problem was solved, just that there was a problem in the first place. Most support staff tend to be salaried employees, with after hours work remaining unpaid. You could call these holiday fixes “random acts of IT kindness”.

In gratitude, Centrinet would like to wish a Happy Holidays to all those hardworking IT professionals – thank you for making sure everything continues to run smoothly throughout the season!

Configuring the RD Gateway Server for a 2012 RDS farm with HA enabled for the RD Connection Brokers

Applies to: Windows Server 2012 and 2012 R2

In a previous article, we demonstrated the steps needed to configure HA for the RD Connection Broker servers in an RDS 2012 farm. If you are using an RD Gateway server for a farm where HA is configured for the brokers, there are a few steps you will need to do in order for users to be able to successfully connect through the RD Gateway server(s).

When a user connects through the RD Gateway server, the gateway server will initially connect the user to one of the RD connection broker servers in order for the broker to determine what server or desktop the user will be connecting to. When HA is enabled for the farm, the gateway server will try to connect the user to the brokers using the DNS Round Robin name when HA was configured for the farm. By default, the DNS name used is not on the gateway’s allowable resource list for users to connect to. So for any user trying to connect to the farm through the RD Gateway, their access will be denied. To get around this, we will simply need to add a new resource authorization policy which will allow users to access resources through the gateway server using the designated DNS round robin name.

Read more

Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm

Applies to: Windows Server 2012 and 2012 R2

One of the biggest issues with Remote Desktop Services on Windows 2008 R2 was the limitation of only having a single active RD Connection Broker server per RDS farm. Yes, you still could have multiple broker servers, however they would run in an Active/Passive mode. This was a major problem since it would limit the size of the farm. The more servers, resources, and users added to the farm put a strain on the single active RD broker server. In most cases, you would have to create multiple RDS farms to get around this problem. This has changed with RDS for 2012. You can now have multiple active brokers in a single RDS farm.

As per Microsoft, the RD Connection Broker provides the following functionality: Read more