GPO hide drive C

Lecteur C masqué

Presentation In this tutorial, we’ll see how to hide drive C using Group Policy (GPO). This GPO is often used to hide drives on RDS farms. Hiding the reader does not prevent access, it is possible to access the reader by the browser directly entering his address. If you want to apply the GPO to …

Read moreGPO hide drive C

RDS Farm: High Availability Service Broker Configuration

server switched

As a follow-up to the article: Deploy a RDS Windows 2012 R2 / 2016/2019 farm, we will see in this tutorial how to configure the high availability service broker. This configuration is optimized for clients use as address of connection to the RDS services, the address of the broker. The tutorial: Connecting to Remote Desktop …

Read moreRDS Farm: High Availability Service Broker Configuration

SOPHOS XG: clientless access

Clientless access presentation Client-free access to Sophos XG firewalls allows connections to corporate servers without a VPN client by going directly through an internet browser as Citrix does. Clientless access configure Firewall configuration 1. Go to the firewall administration interface. 2. From the navigation menu go to Administration 1 / Device Access 2 and verify …

Read moreSOPHOS XG: clientless access

GPO : Loopback Processing

In this tutorial, I will try to simply introduce you to how reminder loops work in GPOs.

It quickly becomes a joke when we have a mixed environment with local users, RDS users and mobile users.

Context

To illustrate this article, I am going to assume that I have a company with two remote sites of about thirty kilometers and that the HR has a fixed position on each site and 3 days work on site A and 2 days on site B .

Each site has two servers:

  • An Active Directory
  • A file server with the folders replicated by using the DFS service.

Read moreGPO : Loopback Processing

How to deploy a rds farm Windows 2012R2/2016/2019

In this article, I will explain the step-by-step roll-out of a Windows 2012 R2 / 2016 RDS farm with the following features:

  • Remote Desktop Session Host (x2)
  • Service broker for distribution of connections
  • Setting up a collection;
  • Publishing RemoteApp on a web portal;
  • Remote Desktop Gateway
  • User Profile Disk (UPD)

To set up a complete rds farm, you need at least 4 servers without counting the domain controller and file and print server. All the servers on the farm must be in the field.

Composition:

Name IP Role
LAB-RDS1.rdr-it.intra 172.16.0.184 Remote Desktop Session Host
LAB-RDS2.rdr-it.intra 172.16.0.185 Remote Desktop Session Host
LAB-RDS-BRK.rdr-it.intra 172.16.0.186 Service Broker / License Manager
LAB-RDS-GW-WEB.rdr-it.intra 172.16.0.187 Gateway Remote Desktop / Web Access

For the realization of this lab, I also used an AD server, LAB-AD1.rdr.it.intra with the IP address 172.16.0.100. DC will also be used to store UPDs.

Server role definitions that are part of an RDS farm.

Remote Desktop Session Host: On these servers, the user sessions are open and allow them to work.

Service broker: This is the circulation agent for sessions in an environment with multiple remote desktop session hosts.

Remote Desktop Gateway: Its primary role is to provide secure access to the RDS infrastructure from the Internet. It connects to the farm using the HTTPS protocol and filters connections using access policy.

License Manager: This service is used for license distribution (CAL RDS).

Read moreHow to deploy a rds farm Windows 2012R2/2016/2019