How To Install Microsoft Security Essentials On Windows Server 2012

In this article, we'll consider the installation, configuration, and activation of the Remote Desktop Licensing role on Windows Server 2022 and 2022, as well as the installation and activation of the RDS client access licenses (CALs).

I remind you that subsequently the installation of the Remote Desktop Session Host role, users tin can use it just for 120 days of a trial period (evaluation license), and users can't connect to an RDS host later on. Co-ordinate to Microsoft licensing rules, all users or devices that use RDS features must be licensed. To register and issue Remote Desktop Client Access Licenses (RDS CALs), there is a dissever Windows service in the RDS office called Remote Desktop License Server.

Contents:

• Install the Remote Desktop Licensing Role on Windows Server 2022/2016
• Activating the RDS License Server on Windows Server
• RDS CALs: Types of Remote Desktop Customer Access Licenses
• Installing RDS CALs on Windows Server 2022/2016
• RDS CAL Usage Reports
• How to Remove RDS CALs from an RD License Server?
• Configuring RDS Licenses on RD Session Hosts

Install the Remote Desktop Licensing Role on Windows Server 2022/2016

Y'all tin can deploy the Remote Desktop License service on any domain server. Information technology is not necessary to install information technology on one of the servers on the RDSH farm.

Before you beginning the installation, add a new server to the Terminal Server License Servers domain security group (or make certain you take the permission to change this group membership), otherwise, the server won't exist able to issue RDS Per User CAL to the domain users.

You tin install Remote Desktop Licensing using Server Manager. To do it, select the Remote Desktop Services role in the Add Roles and Features Wizard.

Select Remote Desktop Licensing as the office service.

It remains to wait until the installation of the role is completed.

The RDS-Licensing service is managed using the Remote Desktop Licensing Manager console (licmgr.exe).

In Windows Server, it's easier to install roles and features using PowerShell. To install the RDS Licensing Service and RD Licensing Diagnoser, just run one control:

Install-WindowsFeature RDS-Licensing –IncludeAllSubFeature -IncludeManagementTools

To listing the RDS services installed on the host, utilize the command:

Get-WindowsFeature -Proper noun RDS* | Where installed

Activating the RDS License Server on Windows Server

In order to issue licenses to RDP clients, your RDS License Server must be activated. To practise it, open the Remote Desktop Licensing Manager (licmgr.exe), right-click the name of your server, and select Actuate Server.

The RDS licensing server activation wizard will start. Here you will need to select the activation method you prefer. If your server is connected to the Net, it can automatically connect to Microsoft servers and activate the RDS license server. If there is no direct Internet access from the server, you lot tin activate the server using a web browser or by phone.

So you must fill in some information about your company (some of the fields are required).

It remains to click the Finish button.

If you right-click the server proper name in the console and select Review Configuration, you lot can verify that the RDS License Server is activated and tin can be used to activate RDSH clients in your domain.

• This license server is a member of the Last Server License Servers group in Active Directory. This license server will be able to effect RDS Per User CALs to users in the domain, and you volition exist able to rails the usage of RDS Per User CALs.

• This license server is registered equally a service connection point (SCP) in Active Directory Domain Services.

RDS CALs: Types of Remote Desktop Client Access Licenses

Each user or device that connects to Remote Desktop Session hosts must have a client admission license (CAL). There are two types of RDS CALs:

• Per-Device CAL – is the permanent license type assigned to a computer (device) that connects to the RDS server more than once (when a device is starting time continued, a temporary license is issued to information technology). These licenses are non concurrent, i.e., if you accept x Per Device licenses, only ten hosts can connect to your RDS server. The electric current OVL RDS CAL is chosen: WinRmtDsktpSrvcsCAL 2022 SNGL OLV NL Each AP DvcCAL;
• Per-User CAL – is the type of license that allows a user to connect to the RDS server from whatever number of computers/devices. This type of license is associated with an Active Directory user and issued non permanently, but for a specific period of time. The license is issued for a period of 52 to 89 days (random number).  The current Open up Value license of this blazon is called WinRmtDsktpSrvcsCAL 2022 SNGL OLV NL Each AP UsrCAL.

  If you try to use RDS 2022 Per User CAL in a workgroup (not in a domain), then the RDSH server volition forcibly ending a user session every sixty minutes with a message: "Remote Desktop License Upshot: There is a trouble with your Remote Desktop license, and your session will be disconnected in 60 minutes". Therefore, for RDS servers in a Windows Workgroup environs, you need to apply the only device licensing (Per Device RDS CALs).

.

Note. We should note that the 2022 RDS CAL may exist installed only on a licensing server running Windows Server 2022 or 2022. Installing RDS CALs to the previous Windows Server versions is not supported. Those, y'all cannot install 2022 RDS CALs on a Windows Server 2022 R2 licensing host.

When trying to add together new RDS CALs 2022 on Windows Server 2022, an mistake will appear:

RD Licensing Managing director The license code is not recognized. Ensure that y'all have entered the correct license code.

Installing RDS CALs on Windows Server 2022/2016

At present you must install the pack of Remote Desktop customer licenses (RDS CAL) y'all accept purchased on the License Server.

Right-click your server in Remote Desktop Licensing Manager and select Install Licenses.

Select the activation method (automatic, online, or by phone) and the license program (in our example, it is Enterprise Understanding).

Many enterprise agreement numbers for RDS have already been leaked on the Net. I think it won't be a problem to notice the numbers (4965437), you don't even need to look for rds cracks or activators.

The next steps of the wizard depend on which license programme yous have selected. In the case of an Enterprise Agreement, you must specify its number. If you have chosen License Pack (Retail Purchase), enter the 25-character production key you got from Microsoft or a partner.

Specify the production version (Windows Server 2022/2016), license blazon (RDS Per user CAL), and the number of licenses to be installed on the server.

Later that, the server tin can outcome licenses (RDS CAL) to clients.

You can convert RDS User CALs to Device CALs (and vice versa) using the Catechumen Licenses carte du jour item in the RD Licensing Managing director console.

If you have run out of free RDS licenses, you lot tin revoke previously issued RDS Device CALs for inactive computers using the following PowerShell script:

$RevokedPCName="lon-bc1-123"
$licensepacks = Get-WmiObject win32_tslicensekeypack | where {($_.keypacktype -ne 0) -and ($_.keypacktype -ne 4) -and ($_.keypacktype -ne 6)}
$licensepacks.TotalLicenses
$TSLicensesAssigned = gwmi win32_tsissuedlicense | where {$_.licensestatus -eq 2}
$RevokePC = $TSLicensesAssigned | ? sIssuedToComputer -EQ $RevokedPCName
$RevokePC.Revoke()

Upward to twenty% of Per-Device RDS CALs can exist revoked. Per-User CALs cannot be revoked.

RDS CAL Usage Reports

In the RDS License Console, you can generate a license usage report. To practice this, select Create Report -> CAL Usage from the server context menu.

Nonetheless, I prefer to utilise PowerShell to report RDS CAL usage. The following script will show the remaining number of licenses in all RDS CAL packs:

Import-Module RemoteDesktopServices -ErrorAction Stop
Set up-Location -Path 'rds:' -ErrorAction Stop
$licenses = (Get-Item -Path RDS:\LicenseServer\LicenseKeyPacks\* | Where-Object Name -Like "-Per User-*").Name
$total=0;
$issued=0;
foreach ($license in $licenses) {
$count=(Get-Item -Path RDS:\LicenseServer\LicenseKeyPacks\$license\TotalLicenses).CurrentValue
$full= $total + $count
$count2=(Get-Item -Path RDS:\LicenseServer\LicenseKeyPacks\$license\IssuedLicensesCount).CurrentValue
$issued= $issued + $count2
}
$available = $full - $issued
Write-Host "Total Licenses bachelor: $available"

You lot can run this PowerShell script via Zabbix and set an alert if the remaining number of licenses is less, for example, 5.

The following Powershell script will let you to generate a Per User CAL Study:

Import-Module RemoteDesktopServices -ErrorAction Stop
Set-Location -Path 'rds:' -ErrorAction Terminate
$path = "C:\Reports\RDS_CAL_Usage.csv"
$fileName = (Invoke-WmiMethod Win32_TSLicenseReport -Name GenerateReportEx).FileName
$fileEntries = (Get-WmiObject Win32_TSLicenseReport | Where-Object FileName -eq $fileName).FetchReportEntries(0,0).ReportEntries
$objArray = @()
foreach($entry in $fileEntries){
$objArray += $entry | select User, ProductVersion, CALType, ExpirationDate
$objArray[-1].User = $objArray[-i].User.Split up('\') | select -Last ane
$time = $objArray[-1].ExpirationDate.Split('.') | select -offset 1
$objArray[-1].ExpirationDate = [datetime]::ParseExact($time, "yyyyMMddHHmmss", $null)
}
$objArray | Export-Csv -Path $path -Delimiter ',' -NoTypeInformation

How to Remove RDS CALs from an RD License Server?

If y'all want to motion your RDS CAL license packs from one Remote Desktop licensing server to another, y'all can remove the installed RDS CAL license pack from the licensing server using PowerShell.

Using the post-obit cmdlet, you can list all the installed RDS CAL packs on the server:

Go-WmiObject Win32_TSLicenseKeyPack|select-object KeyPackId,ProductVersion,TypeAndModel,AvailableLicenses,IssuedLicenses |ft

Detect the KeyPackId value for the RDS CAL package that you want to remove and run the control:

wmic /namespace:\\root\CIMV2 PATH Win32_TSLicenseKeyPack Phone call UninstallLicenseKeyPackWithId yourKeyPackId

Yous can as well completely remove all CALs by re-creating the RDS license database. To do this, stop the Remote Desktop Licensing service:

Stop-Service TermServLicensing

Rename the file C:\Windows\System32\lserver\TLSLic.edb to C:\Windows\System32\lserver\TLSLic.edb_bak and start the service:

Start-Service TermServLicensing

Afterwards that, all RDS CAL licenses will be removed, and y'all must reactivate them.

Configuring RDS Licenses on RD Session Hosts

After the RDS License Server is activated and beingness run, yous can reconfigure RD Session Host to obtain CAL licenses from this server. You lot can gear up the license type and specify the name of the license server from the Server Manager GUI, using PowerShell, or Group Policy.

To modify the name/address of the licensing server on the RDS host, open Server Managing director -> Remote Desktop Services -> Collections. In the upper right menu "Tasks" select "Edit Deployment Properties".

In the deployment properties, go to the RD Licensing tab, select the Remote Desktop licensing fashion, and set the RDS license server. Click Add together -> Ok.

Yous can change the RDS license server address and CAL type using PowerShell:

$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting

So specify the license blazon you need:

$obj.ChangeMode(4)

Notation. Enter 4 if the server must use Per User licensing blazon, and 2, if it is Per Device.

Then specify the name of the RDS License Server:

$obj.SetSpecifiedLicenseServerList("rdslic2016.woshub.com")

And check the current settings:

$obj.GetSpecifiedLicenseServerList()

If you want to assign the RDS licensing server parameters via Group Policy, you lot need to create a new GPO and link it to the OU with RDS servers (or you can specify the name of the RDS licensing server using the Local Group Policy Editor – gpedit.msc). The RD licensing settings are located nether the following GPO section: Figurer Configuration -> Policies -> Admin Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing.

There are two Remote Desktop settings that we need to configure:

• Utilise the specified Remote Desktop license servers – the accost of the License Server is set up;
• Set up the Remote Desktop licensing mode – select RDS CAL license type.

RDSH hosts use the following network ports to obtain an RDS license from the RDS Licensing server. Make sure that they are non blocked past firewalls (or Windows Defender Firewall):

• TCP/135 – Microsoft RPC;
• UDP/137 – NetBIOS Datagram Service;
• UDP/138 – NetBIOS Proper name Resolution;
• TCP/139 – NetBIOS Session Service;
• TCP/445 – SMB;
• TCP/49152–65535 – RPC dynamic address range

You tin can check for open up ports using the PortQry tool or the Test-NetConnection cmdlet.

Try to bank check the RD License Server status and the number of the issued licenses using the Remote Desktop Licensing Diagnoser tool (lsdiag.msc or Administrative Tools -> Remote Desktop Services -> RD Licensing Diagnoser). RD Licensing Diagnoster can be installed on RDSH servers using Server Manager (Features -> Remote Server Administration Tools -> Role Administration Tools -> Remote Desktop Services Tools -> Remote Desktop Licensing Diagnoser Tools).

If the RDSH server is not configured to use an RDS license server, the following warnings volition announced in the Licensing Diagnoser console:

• Licenses are not available for this Remoter Desktop Session Host server, and RD Licensing Diagnose has identified licensing issues for the RDSH.

• Number of licenses bachelor for clients: 0

• The licensing mode for the Remote Desktop Session Host server is non configured.

• Remote Desktop Session Host server is inside its grace period, merely the RD Session Host server has not been configured with any license server.

If yous installed RDSH on the Windows Server Evaluation edition, do non forget to catechumen it to the full version according to the guide. Without conversion, RDSH services on such a host volition simply work for 120 days, fifty-fifty if yous target it to an activated RDS license server.

If there are no warnings, and you see the message "RD Licensing Diagnoser did not identify whatsoever licensing problems for the Remote Desktop Session Host server", then the RDSH server can successfully receive RDS CALs for remote users and/or devices.

Annotation. In our case, after nosotros specified the new License Server accost the following error started to appear on the RDP customer: "The remote session was asunder considering there are no Remote Desktop License Servers available to provide a license". The trouble can exist solved past removing the L$RTMTIMEBOMB fundamental from the registry on the RDSH server.

Source: http://woshub.com/install-activate-rds-licensing-role-windows-server/

Posted by: powelllize1960.blogspot.com

Share this post