Can You Use Terminal Services In A Workgroup

This article describes how to install and configure a concluding server role Remote Desktop Session Host in a workgroup (without an Agile Directory domain) and without whatever other additional roles (Connection Broker, Remote Desktop Web Admission, RDS Gateway). This volition exist a single server RDS deployment on Windows Server 2019/2022.

Windows Server with the RDSH (Remote Desktop Session Host) role allows multiple users to connect to a server simultaneously using RDP (by default, only 2 administrative Remote Desktop connections are immune on Windows Server). A split session is created for each user, and they admission their personal desktop environment.

If you are going to use a separate RDS host in a workgroup, note that its functionality is limited. Information technology cannot be scaled to a full-featured RDS farm, yous cannot create carve up collections or a RemoteApp, at that place is no Connection Broker, you cannot use User Profile Disks, at that place are no centralized direction tools, RDS service won't be available to users during maintenance operations if the host is in the drain manner.

Contents:

• How to Install Remote Desktop Services Office on Windows Server 2019/2022?
• Configure Remote Desktop Licensing Part and Add RDS Licenses (CALs)
• Configure Remote Desktop Session Host in a Workgroup

How to Install Remote Desktop Services Role on Windows Server 2019/2022?

It is supposed that you accept already installed Windows Server and configured basic settings (IP accost, server name, time/appointment, installed updates, etc.). Then y'all tin install the RDS function. To do it, yous can use either Server Manager or PowerShell.

To install the RDS using Server Manager, select Remote Desktop Session Host and Remote Desktop Licensing in Role-based or Feature-based installation -> Server roles -> Remote Desktop Services in RDS components (agree to the installation of RSAT features to manage the roles).

Note that if y'all accept selected Remote Desktop Services installation in Server Manager, the wizard will automatically install RD Connection Broker and Web Access in the Standard deployment or Quick Start modes. In our instance, we don't demand these roles since nosotros are installing a standalone RDS host.

You can also install Windows Server roles using PowerShell:

Install-WindowsFeature -Proper noun RDS-Licensing, RDS-RD-Server –IncludeManagementTools

Check which RDS roles are installed on your server:

Get-WindowsFeature -Name RDS* | Where installed

Restart your server:

Restart-Reckoner

Configure Remote Desktop Licensing Role and Add RDS Licenses (CALs)

The next stride is to configure the Remote Desktop Licensing role, which provides licensing for user RDP connections. Yous can install and activate Remote Desktop Licensing on this host (if you have only one host in your network) or place the RDLicensing function on another server. One server with the RDS Licensing role can issue licenses to whatsoever number of RDS hosts.

If yous have decided to use a local RDLicensing server, activate the RDS Licensing host and install client licenses (RDS CALs) post-obit this guide.

In a workgroup, you should use Per Device RDS CALs. If your licensing server problems Per User licenses only, users volition see the following error when connecting to the server via RDP:

Remote Desktop License Issue There is a problem with your Remote Desktop license, and your session will be disconnected in threescore minutes.

Configure Remote Desktop Session Host in a Workgroup

Get to Control Panel -> System and Security -> Administrative Tools -> Remote Desktop Services -> Remote Desktop Licensing Diagnoser. Annotation that your server is non yet configured to receive RDS CALs from the licensing server. The following messages prove it:

• The licensing way for the Remote Desktop Session Host server is not configured
• Number of licenses available for clients: 0

If you don't target your RDSH server to the RDS licensing server able to effect CALs to your users, your server will stay in the trial mode. In this way, RDS services work for 120 days merely (at each connexion, you lot volition run across this bulletin in the tray: "The Remote Desktop service volition stop working in thirty days"). After the grace menses is over, users won't be able to connect to RDS due to the following mistake:

Remote session was asunder because in that location are no Remote Desktop customer access licenses available for this computer.

The main disadvantage of Remote Desktop Services on Windows Server 2019 in a workgroup (without a domain), is that you don't accept any convenient administrative tools to manage the RDS role. You will take to configure any RDSH office settings in the Local Group Policy Editor (gpedit.msc).

Configure RDS licensing settings with the Local Group Policy Editor (gpedit.msc):

1. Get to Reckoner Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing;
2. Alter Set the Remote Desktop licensing mode to Per Device;
3. In Use the specified Remote Desktop license servers option, specify the IP accost of the server RDLicensing server is installed on. If the licensing server is installed locally, enter localhost or 127.0.0.i;
4. Update local Group Policy settings and run the Remote Desktop Licensing Diagnoser. Make sure that it sees your RDS CALs.

In the local GPO, you lot tin also set RDP session limits (timeouts) and rules of disconnecting users when they are inactive.

If you lot desire to configure different Group Policies for local users and administrators, utilise the multiple GPO (MLGPO) characteristic.

Then create local user accounts on your RDS server. You can create users in lusrmgr.msc or with PowerShell:

$UserPassword = ConvertTo-SecureString "PaSS123!" -AsPlainText -Force
New-LocalUser a.chocolate-brown -Password $UserPassword -FullName "Andi Brown"

To allow a user to connect to a server through Remote Desktop Services, add together the user account to the local Remote Desktop Users grouping. Add together users manually using the calculator management console or with PowerShell:

Add-LocalGroupMember -Group "Remote Desktop Users" -Member a.brown

This user group is allowed to logon remotely through the Allow logon through Remote Desktop Services GPO option (Reckoner Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment). The same policy allows RDP access for non-admin users even to the domain controller.

At present users can try to connect to your RDS host using mstsc.exe (or any other RDS customer) from their computers. Make sure that more than two agile users can connect to the server simultaneously.

At the first login, a temporary license is issued for a user device (an RDS Per Device licensing feature). At the 2nd logon, a permanent license is issued that appears in the Remote Desktop Licensing Director. The license is issued for the menses of 52-89 days (a random number).

If there are no free Per Device licenses, you can manually revoke licenses for some user devices. Use the RDSLicensing panel or this PowerShell script:

$licensepacks = Get-WmiObject win32_tslicensekeypack | where {($_.keypacktype -ne 0) -and ($_.keypacktype -ne four) -and ($_.keypacktype -ne 6)}
# the total number of per device licenses
$licensepacks.TotalLicenses
# the number of licenses issued to the devices
$TSLicensesAssigned = gwmi win32_tsissuedlicense | where {$_.licensestatus -eq ii}
# the computer name you desire to revoke a license from
$compname="wksmun2a15"
$RevokePC = $TSLicensesAssigned | ? sIssuedToComputer -EQ $compname
$RevokePC.Revoke()

If you lot demand to connect to a user RDP session, you can apply the RDS shadow connection mode (information technology likewise works on an RDSH in a workgroup).

Can You Use Terminal Services In A Workgroup,

Source: http://woshub.com/install-remote-desktop-services-rdsh-workgroup-without-domain/

Posted by: williamsonlikeethimp.blogspot.com

Share this post