How to enable Multiple RDP Sessions in Windows Server?

Поделиться
HTML-код
  • Опубликовано: 19 июн 2023
  • How to enable Multiple RDP Sessions in Windows Server?
    #windows #microsoft #rdp #hpe #session #server #howto
    Please refer to the following playlist for your review.
    Gnan Cloud Garage Playlists
    www.youtube.com/@gnancloudgar...
    VMware vSphere 7 & VMware vSphere Plus (+) | Data Center Virtualization
    • VMware vSphere |VCP - ...
    vSphere 7.x - Home lab - Quick Bytes | Data Center Virtualization
    • vSphere 7.x - Home lab...
    VMware vSphere 8
    • VMware vSphere 8
    VMware vSAN 8
    • VMware vSAN 8
    VMware NSX 4.x | Network Virtualization
    • VMware NSX 4.0.0.1 | N...
    VMware Cloud Foundation (VCF)+
    • VMware Cloud Foundatio...
    VMware Aria Automation (formerly, vRealize Automation) | Unified Multi-Cloud Management
    • VMware Aria Automation...
    Interview Preparation for Technical Consultants, Systems Engineers & Solution Architects
    • Interview Preparation ...
    VMware Tanzu Portfolio | Application Modernization
    • VMware Tanzu Portfolio...
    Modern Data Protection Solutions
    • Modern Data Protection...
    Storage, Software-Defined Storage (SDS)
    • Storage, Software-Defi...
    Zerto, a Hewlett Packard Enterprise (HPE) Company
    • Zerto, a Hewlett Packa...
    The Era of Multi-Cloud Services|HPE GreenLake Solutions|Solution Architectures|Solution Designs
    • The Era of Multi-Cloud...
    Gnan Cloud Garage (GCG) - FAQs |Tools |Tech Talks
    • Gnan Cloud Garage (GCG...
    VMware Aria Operations (formerly, vROps)
    • VMware Aria Operations...
    PowerShell || VMware PowerCLI
    • PowerShell || VMware P...
    Hewlett Packard Enterprise (HPE) Edge to Cloud Solutions & Services
    • Hewlett Packard Enterp...
    DevOps || DevSecOps
    • DevOps || DevSecOps
    Red Hat Openshift Container Platform (RH OCP)
    • Red Hat Openshift Cont...
    Windows Server 2022 - Concepts
    • Windows Server 2022, 2...
    Red Hat Enterprise Linux (RHEL) 9 - Concepts
    • Red Hat Enterprise Lin...
    Microsoft Azure Stack HCI
    • Microsoft Azure Stack HCI
    NVIDIA AI Enterprise
    • NVIDIA AI Enterprise
    Gratitude | Thank you messages
    • Gratitude | Thank you ...
  • НаукаНаука

Комментарии • 48

  • @niamatullah9324
    @niamatullah9324 8 месяцев назад +2

    Thank you dear Gnan. It was an extraordinary effort explained comprehensively to a first time user like me. All the best

  • @bidkarpaez8385
    @bidkarpaez8385 5 месяцев назад +1

    Very useful and easy to follow, thanks for sharing!

  • @gnancloudgarage5238
    @gnancloudgarage5238  Год назад +2

    How to enable Multiple RDP Sessions in Windows Server?
    #windows #microsoft #rdp #hpe #session #server #howto

  • @mikebeech0671
    @mikebeech0671 5 месяцев назад +1

    great video thanks so much

  • @GauravKumar-fj7tp
    @GauravKumar-fj7tp 29 дней назад +1

    Lovely

  • @malli591
    @malli591 Год назад +1

    Hi
    Please do more videos on windows servers troubleshooting issues
    Thanks

    • @gnancloudgarage5238
      @gnancloudgarage5238  Год назад +2

      Hi Mallikarjuna,
      Sure, will do that.
      Thank you
      FYI.
      Troubleshooting issues on Windows servers can involve various aspects of the system. Here are some common troubleshooting steps for Windows server issues:
      1. Identify the Problem: Start by gathering information about the issue and its symptoms. Determine if it's a performance problem, application error, network connectivity issue, or any other specific problem.
      2. Check Event Logs: Windows Event Viewer stores various system logs and can provide valuable information about errors, warnings, and other events. Look for any relevant error messages or warnings that can help identify the root cause.
      3. Review System Resources: Check the server's resource utilization, such as CPU, memory, and disk usage. Use Task Manager or Performance Monitor to identify any resource bottlenecks or abnormal behavior.
      4. Verify Network Connectivity: Ensure the server has proper network connectivity. Check network settings, IP configurations, DNS resolution, and firewall rules. Use tools like ping, tracert, or nslookup to diagnose network connectivity issues.
      5. Restart Services and Processes: Sometimes, restarting specific services or processes related to the problem can resolve issues. Use the Services Management Console (services.msc) to stop and start relevant services.
      6. Apply Updates and Patches: Ensure the server has installed the latest updates and patches. Use Windows Update or Windows Server Update Services (WSUS) to check for and apply available updates.
      7. Check Hardware: If the issue persists, consider hardware-related problems. Verify that all hardware components are functioning correctly, including disks, memory modules, network cards, etc. Run hardware diagnostics tools or consult with the server manufacturer's documentation.
      8. Analyze Application-specific Logs: If the issue is related to a specific application, check its logs for error messages or warnings. Consult the application's documentation or contact the vendor for troubleshooting guidance.
      9. Review Security Settings: Verify that security settings, permissions, and access controls are properly configured. Check group policies, user rights assignments, and firewall settings to ensure they align with the desired configuration.
      10. Seek Online Resources and Communities: Utilize online resources such as Microsoft's knowledge base, support forums, or communities like Server Fault to search for similar issues and possible solutions.
      11. Engage Support: If the issue persists or is critical to your operations, consider contacting the respective software or hardware vendor's support team for further assistance. Provide them with relevant information and logs to expedite the troubleshooting process.
      Remember to always exercise caution when making changes to your server and consider taking backups before implementing any significant changes.

  • @redampsmining
    @redampsmining 3 месяца назад +1

    nice, thanks just trying now. You have to reboot after any gpedit change windows2022 standard server here.

    • @gnancloudgarage5238
      @gnancloudgarage5238  3 месяца назад +1

      Thank you too

    • @redampsmining
      @redampsmining 3 месяца назад

      @@gnancloudgarage5238 gpupdate /force from command prompts does same thing as rebooting - for group policy updates (Without rebooting).

  • @harishsaini85
    @harishsaini85 2 месяца назад +1

    Thanks Gnan, i have tried same steps on windows 11 enterprises version, and using (V:12.80.6.12) of TSPlus for RDP, when i try to connect from client system, Another User signed in, if you continue, they will be disconnected, Do you want to sign in anyway? Please help

    • @gnancloudgarage5238
      @gnancloudgarage5238  2 месяца назад +1

      Hi Harish,
      Thanks for trying out the steps!
      It seems like you're encountering a common issue with multiple RDP sessions on Windows 11 Enterprise. The message you're seeing typically indicates that another user is already logged in, and attempting to connect will disconnect them.
      To enable multiple RDP sessions on Windows 11 Enterprise, you may need to modify the group policy settings or RDP Wrapper or use a third-party tool specifically designed for this purpose. However, please note that modifying system settings may affect security and stability, so proceed with caution.
      As for TSPlus, ensure that you've configured it properly for multiple sessions. You might want to check the documentation or reach out to their support for assistance tailored to your setup.
      Hope this helps!

  • @arnoldmontebon9798
    @arnoldmontebon9798 3 месяца назад +1

    @gnan Cloud Garage, i tried but the other user will be disconnected if i connect the other user, please help!, the everytime i remote the other user it disconnected the other one

    • @gnancloudgarage5238
      @gnancloudgarage5238  3 месяца назад +1

      Hi Arnold,
      Please retry the following steps
      1. Log into the server where the Remote Desktop Services are installed.
      2. Open the start screen (press the Windows key) and type 'gpedit.msc', then open it.
      3. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
      4. Set 'Restrict Remote Desktop Services users to a single Remote Desktop Services session' to 'Disabled'.
      5. Double click 'Limit number of connections' and set the 'RD Maximum Connections' allowed to 999999.
      After completing these steps, restart your system and then test the Remote Desktop sessions again.

  • @leejarvie1836
    @leejarvie1836 21 день назад +1

    If I'm just looking to increase the default 2 administrative connections to something larger on my machine, and I already have a licensing server, is the Host service the only piece I need to install to my server? Do I need connection broker?

    • @gnancloudgarage5238
      @gnancloudgarage5238  21 день назад +2

      If you are looking to increase the default 2 administrative connections for Remote Desktop Services (RDS) on your machine and you already have a licensing server, installing the Remote Desktop Session Host (RDSH) service is indeed a critical component. Here is a detailed answer:
      Components Needed:
      1. Remote Desktop Session Host (RDSH):
      - This is the primary component that needs to be installed. The RDSH allows a server to host Windows-based programs or the full Windows desktop for Remote Desktop Services clients. By installing the RDSH role, you can support more concurrent sessions beyond the default administrative limit of 2.
      2. Remote Desktop Licensing (RDS Licensing):
      - Since you already have a licensing server, you should ensure it is properly configured and that you have enough Remote Desktop Services Client Access Licenses (RDS CALs) to cover the number of users or devices that will connect. The RDSH server will need to be pointed to your licensing server to manage the licenses.
      Additional Components (Optional):
      1. Remote Desktop Connection Broker (RD Connection Broker):
      - The RD Connection Broker is not strictly necessary if you are only looking to increase the number of connections on a single server. However, it becomes essential if you are managing a farm of RDSH servers to balance the load and provide session reconnection.
      - If you plan to scale out to multiple RDSH servers in the future, the RD Connection Broker can help distribute the load and manage user sessions efficiently.
      2. Remote Desktop Web Access (RD Web Access):
      - This component is useful if you want to provide access to RemoteApp programs or full desktops via a web browser. It is not required just to increase the connection limit.
      Steps to Install RDSH:
      1. Install the Remote Desktop Session Host:
      - Open the Server Manager on your server.
      - Navigate to `Manage` > `Add Roles and Features`.
      - Proceed through the wizard, selecting the `Remote Desktop Services installation` option.
      - Select `Session-based desktop deployment` if asked.
      - Add the `Remote Desktop Session Host` role.
      - Follow the prompts to complete the installation and restart the server if necessary.
      2. Configure the Licensing Mode:
      - After installation, you need to configure the RDSH to use your existing licensing server.
      - Go to `Server Manager` > `Remote Desktop Services` > `Overview`.
      - Click on `RD Licensing` and specify your licensing server.
      - Ensure the licensing mode (Per User or Per Device) matches your licenses.
      By following these steps and ensuring your licensing server is properly set up, you can increase the number of concurrent connections on your server. The RD Connection Broker and other components can be added later if you decide to expand your infrastructure.

    • @leejarvie1836
      @leejarvie1836 21 день назад

      @@gnancloudgarage5238 Thank you so much for clarifying this. I will try it tomorrow!

  • @SerwaRiac
    @SerwaRiac 4 месяца назад +2

    Is it also possible to do in windows 11? I heard that only windows server supports multiple users remote desktop connections...

    • @gnancloudgarage5238
      @gnancloudgarage5238  4 месяца назад +2

      Yes, it's possible to enable multiple remote desktop connections in Windows 11, similar to Windows Server.
      However, it's important to note that the ability to do so may depend on the specific edition of Windows 11 you're using and your system's configuration

    • @SerwaRiac
      @SerwaRiac 4 месяца назад +1

      @@gnancloudgarage5238 Thanks, bro for your time and attention!

  • @Khabraypak
    @Khabraypak 6 дней назад

    This command in run doesn't work in win 11

  • @SerwaRiac
    @SerwaRiac 4 месяца назад +2

    I wonder if there's a way to make this all with batch scripting so that not to mess inside those multiple folders and subfolders and stuff...

    • @gnancloudgarage5238
      @gnancloudgarage5238  4 месяца назад +2

      Absolutely! Batch scripting can be a powerful tool for automating tasks across multiple folders and subfolders.
      With batch scripting, you can write scripts to perform various operations such as file copying, moving, renaming, and more, without the need to manually navigate through each folder.

    • @SerwaRiac
      @SerwaRiac 4 месяца назад +1

      @@gnancloudgarage5238 Subscribed to you, bro! Another nice thing about your videos is that you have a very nice Indian accent unlike some others.

    • @gnancloudgarage5238
      @gnancloudgarage5238  4 месяца назад +2

      @@SerwaRiac Thank you bro

  • @yermanskt
    @yermanskt 2 месяца назад +1

    Hi ! In term of microsoft licencing. Having more than 2 concurrent sessions is legal or not ? Do we need RDP CAL's?

    • @gnancloudgarage5238
      @gnancloudgarage5238  2 месяца назад +2

      Hi there!
      Regarding Microsoft licensing, having more than two concurrent sessions can depend on various factors, such as the specific Microsoft products being used and the licensing agreements in place.
      Generally, Remote Desktop Protocol (RDP) Client Access Licenses (CALs) are required for each user or device accessing the Remote Desktop Services (RDS) server.
      However, it's essential to review the Microsoft licensing terms and consult with a licensing expert or Microsoft representative to ensure compliance with the licensing requirements for your specific use case.
      Hope this helps!

  • @Imrankhan-wq6nm
    @Imrankhan-wq6nm 4 месяца назад +1

    All done but when i tried to login 2nd user error is "the connection was denied because the user account is not authorized for remote login" Please can you tell me how to do this. Thanks for help

    • @gnancloudgarage5238
      @gnancloudgarage5238  4 месяца назад +1

      Sure! It sounds like the second user account doesn't have permission for remote login.
      Here's how you can fix it:
      1. Go to your computer's Control Panel.
      2. Navigate to 'Administrative Tools' and then 'Computer Management.'
      3. In the left panel, expand 'Local Users and Groups' and select 'Users.'
      4. Find the user account experiencing the issue and double-click it to open its properties.
      5. Go to the 'Member of' tab and ensure that the user is a member of the 'Remote Desktop Users' group.
      6. If the user is not listed, click 'Add' and type 'Remote Desktop Users' into the object names box, then click 'Check Names' and 'OK.'
      7. Click 'Apply' and 'OK' to save the changes.
      Now, try logging in with the second user account again. It should work without any issues.

  • @juvanthomas7022
    @juvanthomas7022 2 месяца назад +1

    worked for 2 users , but more than 2 not working in windows server 2022 hosted in EC2

    • @gnancloudgarage5238
      @gnancloudgarage5238  2 месяца назад +1

      Yes, that's correct. It requires an RDP license for access by more than two users.

  • @bestmoney17
    @bestmoney17 21 день назад +1

    how to create on desktop Shortcut and I want to connect every time without entering a password that will be saved

    • @gnancloudgarage5238
      @gnancloudgarage5238  21 день назад +1

      To create an RDP (Remote Desktop Protocol) desktop shortcut that connects automatically without requiring you to enter your password every time, follow these steps:
      Step 1: Create the RDP Shortcut
      1. Open Remote Desktop Connection:
      - Press `Windows + R` to open the Run dialog box.
      - Type `mstsc` and press Enter to open Remote Desktop Connection.
      2. Set Up Your Connection:
      - Enter the computer name or IP address of the remote PC you want to connect to in the "Computer" field.
      - Click on "Show Options" at the bottom left of the Remote Desktop Connection window.
      3. Save Your Credentials:
      - Enter your username in the "User name" field.
      - Check the box labeled "Allow me to save credentials."
      4. Save the RDP File:
      - Click on the "Save As" button to save the current connection settings to an RDP file.
      - Choose a location to save the RDP file (e.g., your desktop) and give it a name.
      - Click "Save."
      Step 2: Save the Password
      1. Open the RDP File:
      - Right-click the RDP file you just created and select "Edit."
      2. Enter and Save the Password:
      - In the Remote Desktop Connection window, enter your password when prompted.
      - Click "OK."
      - To save the password, connect to the remote PC once and check the box that says "Remember me."
      Step 3: Create a Desktop Shortcut
      1. Create the Shortcut:
      - Right-click on your desktop, select "New," and then "Shortcut."
      - In the "Type the location of the item" field, type the path to the RDP file you saved earlier, or browse to it.
      - Click "Next."
      2. Name the Shortcut:
      - Enter a name for your shortcut (e.g., "My Remote Desktop").
      - Click "Finish."
      Step 4: Configure Shortcut to Use Saved Credentials
      1. Right-click the Shortcut:
      - Right-click the shortcut you created and select "Properties."
      2. Set Target to Use Saved Credentials:
      - In the "Target" field, ensure the path to your RDP file is correct.
      - Add the `/savecred` parameter to the end of the target path. It should look something like this:
      "C:\path\to\your\file.rdp" /savecred
      3. Apply and Close:
      - Click "Apply" and then "OK."
      Additional Tips:
      - Security Considerations: Be aware that saving your credentials can pose a security risk. Ensure your computer is secure and has up-to-date antivirus software.
      - Credential Manager: If you need to manage your saved credentials, you can do so through the Windows Credential Manager. Open the Control Panel, go to "User Accounts," and then "Credential Manager."
      By following these steps, you should be able to create an RDP desktop shortcut that connects automatically without needing to enter your password each time.

    • @bestmoney17
      @bestmoney17 20 дней назад

      @@gnancloudgarage5238 thanks

  • @IT_BOX_
    @IT_BOX_ 7 месяцев назад +1

    for multiple windows rdp session you need the (RDP wraper)

    • @gnancloudgarage5238
      @gnancloudgarage5238  7 месяцев назад +2

      Yes, RDP Wrapper on Windows Server OS refers to a third-party tool designed to modify the Remote Desktop Protocol (RDP) configuration on Windows operating systems. By default, Windows Server editions have restrictions on the number of simultaneous remote desktop connections allowed. RDP Wrapper essentially acts as a wrapper around the termsrv.dll file, making it possible to enable multiple concurrent RDP sessions on a Windows Server.
      The primary purpose of RDP Wrapper is to extend the built-in Remote Desktop functionality, allowing more users to connect to a Windows Server simultaneously. This can be particularly useful in environments where there is a need for multiple remote users to access and manage a server concurrently.
      It's important to note that while tools like RDP Wrapper provide additional flexibility, users should be aware of licensing and legal considerations to ensure compliance with Microsoft's terms and conditions. Using such third-party tools may have implications on the system's security and stability, so caution and thorough understanding of the consequences are advisable.

  • @ajaypandey-qh9jc
    @ajaypandey-qh9jc 14 дней назад +1

    Hi,
    The setting is also working with licence server ?

    • @gnancloudgarage5238
      @gnancloudgarage5238  13 дней назад +1

      Hi,
      To enable multiple RDP sessions on a Windows Server, you need to configure the Remote Desktop Session Host settings and ensure you have the necessary Remote Desktop Services (RDS) Client Access Licenses (CALs). The process involves setting the maximum number of connections in the Remote Desktop Session Host Configuration and adjusting Group Policy settings to allow multiple concurrent sessions. Ensure your Remote Desktop Licensing server is configured correctly to manage and distribute the RDS CALs. This setup ensures compliance with Microsoft licensing requirements while allowing multiple users to connect simultaneously
      License Server Configuration:
      Ensure that your Remote Desktop Licensing server is properly configured to distribute RDS CALs.
      In Server Manager, go to Remote Desktop Services > Remote Desktop Licensing Manager.
      Check the availability and issuance of RDS CALs.
      Make sure the licensing mode is set correctly (Per User or Per Device).

  • @user-nj9mn9yl3y
    @user-nj9mn9yl3y 7 месяцев назад +3

    What about licensing issues?

    • @gnancloudgarage5238
      @gnancloudgarage5238  7 месяцев назад +1

      Yes, This option will helps Windows will allow for up to 2 Remote Desktop Admin connections at a time, in all editions of Windows server.
      In order to allow more users (for example. 5 users logging in at the same time), we must install the Remote Desktop Session Host Role, to allow for more than two concurrent connections. Without this role, we will be limited to only two concurrent sessions to our Windows server at a time.
      Resources:-
      Activating Remote Desktop License Server:
      docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-activate-license-server
      Licensing Remote Desktop Services:
      docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license

  • @user-dh9rc9df7q
    @user-dh9rc9df7q 8 месяцев назад +3

    Its only work for two sessions.

  • @necronmaster
    @necronmaster 3 месяца назад +1

    W10 & 11 enterprise works?