Sakthi's Blogs

Tag: security

  • Microsoft RDS Configuration and Operations Guide

    ๐Ÿ”ง 1. Introduction to RDS

    Remote Desktop Services (RDS) allows users to connect to centralized desktops and applications from remote locations. It enables:

    • Centralized management of desktops and apps
    • Improved security and compliance
    • Reduced hardware costs using thin clients

    ๐Ÿ“‹ 2. RDS Deployment Overview

    Key RDS Roles:

    RoleDescription
    RD Session Host (RDSH)Hosts Windows-based programs or the full desktop
    RD LicensingManages RDS Client Access Licenses (CALs)
    RD Connection BrokerManages user sessions and load balancing
    RD Web AccessProvides a web portal for users to access RemoteApps and desktops
    RD GatewayProvides secure access via HTTPS over the Internet

    โš™๏ธ 3. Prerequisites

    • Windows Server (2016, 2019, or 2022)
    • Domain-joined servers (Active Directory environment)
    • Proper RDS CALs
    • Static IP and hostname for each RDS role server
    • Certificates (public or internal CA) for secure access

    ๐Ÿงฑ 4. Installing RDS Roles

    Via Server Manager:

    1. Open Server Manager > Add Roles and Features
    2. Choose Role-based or feature-based installation
    3. Select your server
    4. In the Roles list, choose Remote Desktop Services
    5. Select one or more:
      • RD Connection Broker
      • RD Web Access
      • RD Session Host
    6. Install and reboot if required

    ๐Ÿ’ก In production, install roles on separate servers for scalability and security.


    ๐Ÿ”‘ 5. Configuring RD Licensing

    1. Go to Server Manager > Remote Desktop Services > Overview
    2. Click on RD Licensing
    3. Right-click the licensing server โ†’ Activate Server
    4. Follow the wizard to activate via Internet or phone
    5. Install CALs (Per User or Per Device)
    6. On each Session Host:
      • Run gpedit.msc
      • Navigate to:
        Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > RD Session Host > Licensing
      • Set the licensing mode and specify the license server

    ๐Ÿ’ผ 6. Creating a Session Collection

    1. In Server Manager > Remote Desktop Services
    2. Click Collections > Tasks > Create Session Collection
    3. Provide:
      • Name & description
      • Session Host servers
      • User groups
      • Profile disk config (optional)
    4. Finish wizard to deploy

    ๐Ÿ“ฆ 7. Publishing RemoteApps

    1. Inside the created collection:
      • Click Tasks > Publish RemoteApp Programs
    2. Choose programs to publish
    3. Confirm and finish
    4. Applications will be available via:
      • RD Web Access portal
      • RDP shortcut (.rdp file)
      • RemoteApp and Desktop Connections

    ๐ŸŒ 8. Configuring RD Gateway (Optional)

    1. Add RD Gateway role via Add Roles and Features
    2. Configure HTTPS certificate
    3. In RD Gateway Manager:
      • Create a Connection Authorization Policy
      • Create a Resource Authorization Policy
    4. Update DNS to resolve externally (e.g., rds.yourcompany.com)

    ๐Ÿ–ฅ 9. Accessing RDS as a User

    • Open a browser: https://<your-RDWeb-server>/RDWeb
    • Or use Remote Desktop Connection (mstsc):
      • Enter rds.yourdomain.com
      • Authenticate with domain credentials

    ๐Ÿ“Š 10. Monitoring and Operations

    Tools:

    • Server Manager > Remote Desktop Services Dashboard
    • Event Viewer for RDS-related logs
    • Performance Monitor (perfmon.msc)
    • Task Manager > Users (on Session Hosts)

    Common Tasks:

    TaskTool
    Add/remove usersActive Directory
    Reboot sessionsServer Manager or taskkill
    Add programsInstall on Session Host, republish if needed
    License checkRD Licensing Diagnoser

    ๐Ÿ”„ 11. Backup and Recovery

    • Use Windows Server Backup or third-party tools
    • Backup:
      • RD Connection Broker DB
      • RD Licensing data
      • User profile disks (if enabled)
    • Document server settings and collections for disaster recovery

    โœ… 12. Best Practices

    • Use SSL certificates from a trusted CA
    • Limit access via security groups
    • Regularly patch servers and clients
    • Monitor licensing usage and compliance
    • Use User Profile Disks (UPD) for user data consistency
    • Scale out Session Hosts with Connection Broker load balancing