SPLA/en: Unterschied zwischen den Versionen

Aus TERRA CLOUD WIKI

(Übernehme Bearbeitung einer neuen Version der Quellseite)
 
(Übernehme Bearbeitung einer neuen Version der Quellseite)
 
(26 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
<div lang="de" dir="ltr" class="mw-content-ltr">
<languages/>
SPLA steht für Service Provider License Agreement. <br>
SPLA stands for Service Provider License Agreement. <br>
Es handelt sich um eine spezielle Lizenzform, bei der man Software Lizenzen mieten und lizenzrechtlich einwandfrei weitervermieten kann. <br>
It is a special form of license in which you can rent software licenses and re-rent them in accordance with licensing law. <br>
SPLA ermöglicht es, die Lizenzen von Microsoft-Produkten auf monatlicher Basis abzurechnen - und zwar immer nur das, was dem Kunden im jeweiligen Monat an Diensten angeboten wird.<br>
SPLA makes it possible to bill the licenses of Microsoft products on a monthly basis - and only the services offered to the customer in the respective month.<br>
<br>
<br>
Allgemeiner Kontakt SPLA<br>
General contact SPLA<br>
E-Mail: spla@wortmann.de<br>
Email: spla@wortmann.de<br>
Telefon: 05744 944-254<br>
Telephone: 05744 944-254<br>
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
== Microsoft SPLA (Services Provider License Agreement) ==
== Microsoft SPLA (Services Provider License Agreement) ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
is a program for service providers and ISVs (Independent Software Vendors). <br>
ist ein Programm für Service Provider und ISVs (Independent Software Vendors). <br>
This program lets you license Microsoft products on a monthly basis - under a three-year contract - to host software services and applications for your customers. <br>
Mit diesem Programm können Sie Microsoft Produkte auf monatlicher Basis lizenzieren - im Rahmen eines Vertrages mit drei Jahren Laufzeit - um Software Services und Applications für Ihre Kunden zu hosten. <br>
SPLA offers a variety of hosting scenarios with which you can offer your customers highly individual and robust solutions. <br>
SPLA bietet eine Vielfalt an Hosting Szenarien, mit denen Sie Ihren Kunden höchst individuelle und robuste Lösungen anbieten können. <br>
Volume Licensing Customers can license their server applications on-premise and in the cloud. <br>
Volume Licensing Kunden können ihre Server Applikationen On-Premise sowie in der Cloud lizenzieren. <br>
The latter usually happens within the framework of a qualified shared hardware environment for the service provider's specific applications. <br>
Letzteres geschieht in der Regel im Rahmen einer qualifizierten Shared-Hardware Umgebung für spezifische Applikationen des Service Providers. <br>
<br>
<br>
Was ist der Unterschied zwischen SPLA und den anderen Microsoft Volume Licensing Programmen? <br>
What is the difference between SPLA and the other Microsoft Volume Licensing programs? <br>
Microsoft Volume Licensing Programme bieten verschiedene Lizenzierungsoptionen zum Erwerb von Microsoft Software Lizenzen für den internen Gebrauch.<br>
Microsoft Volume Licensing Programs offer various licensing options for purchasing Microsoft software licenses for internal use.<br>
Hosting Provider, die ihren Kunden Software Services anbieten möchten und die Software-Lizenzen als Teil ihres Service-Angebots anbieten, sollten SPLA nutzen.<br>
Hosting providers who want to offer software services to their customers and who offer software licenses as part of their service offering should use SPLA.<br>
Microsoft SPLA ist das einzige Microsoft Volume Licensing Programm, das es erlaubt, Microsoft Produkte für kommerzielles Hosting zu nutzen.<br>
Microsoft SPLA is the only Microsoft Volume Licensing program that allows you to use Microsoft products for commercial hosting.<br>
<br />
<br />
</div>
<span id="Diese_Vorteile_bietet_Ihnen_SPLA"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
== SPLA offers you these advantages ==
== Diese Vorteile bietet Ihnen SPLA ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
*Customized Service: Get the flexibility to offer your customers customized IT services through a dedicated or shared hosting environment.
*Customized Service: Erhalten Sie die Flexibilität, Ihren Kunden maßgeschneiderte IT Services durch eine dedizierte oder shared-hosting Umgebung anzubieten.
*"Pay as you go" without upfront payment: Only pay for the licenses you need each month for your software services. There are no upfront costs or long-term commitments.
*"Pay as you go" ohne Vorauszahlung: Zahlen Sie nur für die Lizenzen, die Sie jeden Monat für Ihre Software Services benötigen. Es gibt keine Vorabkosten oder langfristige Commitments.
*Access to the latest product versions: Provide your customers with the most current and powerful platform. Easily download your products for free from the Microsoft Volume Licensing Service Center (VLSC) instead of ordering physical media.
*Zugang zu den neuesten Produkt Versionen: Stellen Sie Ihren Kunden die aktuellste und leistungsfähigste Plattform zur Verfügung. Laden Sie ganz bequem Ihre Produkte ohne Gebühr von dem Microsoft Volume Licensing Service Center (VLSC) herunter anstatt :physische Medien zu ordern.
*Try before you buy: Test and evaluate products internally before offering them as a service to your customers.
*Testen Sie bevor Sie kaufen: Testen und evaluieren Sie Produkte intern bevor Sie sie Ihren Kunden als Service anbieten.
*Install directly at the customer's site: Install Microsoft products on servers located at your end customer's - under your management and control.
*Installieren Sie direkt beim Kunden: Installieren Sie Microsoft Produkte auf Servern, die bei Ihrem Endkundenstehen - unter Ihrem Management und Ihrer Kontrolle.
*Offer demonstrations and evaluations: You have up to 50 user product demos for Microsoft software. Offer your customers a 60-day trial free of charge.
*Bieten Sie Demonstrationen und Evaluationen an: Sie haben bis zu 50 User Product Demos für Microsoft Software. Bieten Sie Ihren Kunden kostenfrei einen 60-Tage Test an.
*All your locations under a single contract
*Alle Ihre Standorte unter einem einzigen Vertrag
*Expand your audience: Expand your business with special offers for academic end customers.
*Erweitern Sie Ihre Zielgruppe: Erweitern Sie Ihr Geschäft mithilfe von speziellen Angeboten für akademische Endkunden.
<br />
<br />
</div>
<span id="SPLA-Vertragspartner_werden_oder_bequem_über_das_TERRA_CLOUD_Center_beziehen"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
== Become a SPLA contractual partner or obtain it conveniently via the TERRA CLOUD Center ==
== SPLA-Vertragspartner werden oder bequem über das TERRA CLOUD Center beziehen ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
Wortmann AG offers you two purchasing options. Here you can decide which path you take.<br>
Die Wortmann AG bietet Ihnen 2 Bezugswege an. Hier können Sie entscheiden, welchen Weg Sie gehen.<br>
<br>
<br>
Sie haben die Möglichkeit SPLA-Lizenzen direkt im TERRA CLOUD Center bei z. B. einer Konfiguration einer virtuellen Maschine zu buchen. <br>
You have the option of purchasing SPLA licenses directly in the TERRA CLOUD Center at e.g. B. to book a configuration of a virtual machine. <br>
Im Hosting und im IaaS bieten wir alle aktuell von Microsoft bereitgestellten SPLA-Lizenzen an. Ohne SPLA-Vertrag Lizenzen dieser Art zu buchen ist in Deutschland nur bei der Telekom AG und der Wortmann AG möglich.<br>
In hosting and IaaS, we offer all SPLA licenses currently provided by Microsoft. In Germany, booking licenses of this type without an SPLA contract is only possible with Telekom AG and Wortmann AG.<br>
Die Abrechnung erfolgt mit der TERRA CLOUD Rechnung.<br>
Billing is done using the TERRA CLOUD invoice.<br>
<br>
<br>
Wenn Sie SPLA-Lizenzen günstiger, direkt beim Endkunden und noch flexibler auf monatlicher Basis mieten / vermieten möchten, können Sie SPLA-Vertragspartner bei der Wortmann AG werden.<br>
If you would like to rent SPLA licenses cheaper, directly from the end customer and even more flexibly on a monthly basis, you can become a SPLA contractual partner with Wortmann AG.<br>
Sie bekommen durch Microsoft selbst den Zugang zu allen aktuell von Microsoft bereitgestellten SPLA-Lizenzen über das VLSC (Volume Licensing Service Center).<br>
Microsoft itself gives you access to all SPLA licenses currently provided by Microsoft via the VLSC (Volume Licensing Service Center).<br>
Bei dieser Option müssen Sie selbst monatlich an die Wortmann AG reporten, welche Lizenzen Sie nutzen bzw. vermieten. <br>
With this option, you must report to Wortmann AG on a monthly basis which licenses you use or rent. <br>
Hier prüfen wir den Report auf evtl. offensichtliche Lizenzierungsfehler und lösen diese gemeinsam vor der Abgabe des Reports beim Hersteller. <br>
Here we check the report for any obvious licensing errors and resolve these together before submitting the report to the manufacturer. <br>
</div>
<span id="SPLA_Lizenzierung"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
== SPLA licensing ==
== SPLA Lizenzierung ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="User-CAL&#039;s_bzw._SAL&#039;s"></span>
=== User-CAL's bzw. SAL's ===
=== User CAL's or SAL's ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
User CALs as you know them do not exist in SaaS and IaaS for Windows servers. <br>
User-CAL’s so wie Sie diese kennen gibt, es im SaaS und IaaS für die Windows Server nicht.   <br>
With SPLA licensing there are no longer any CALs, only SALs. With Exchange, you only have to license the users who access the Exchange server. <br>
Bei der SPLA-Lizenzierung gibt es keine CAL’s mehr sondern nur noch SAL’s. Bei dem Exchange ist es so, dass Sie hier nur die User lizenzieren müssen, die auf den Exchange-Server zugreifen. <br>
If this VM is a terminal server environment, you would only have to think about the RDS CALs. These still exist.
Sollte diese VM eine Terminal-Serverumgebung sein, müssten Sie nur noch an die RDS-CAL’s denken. Diese gibt es nach wie vor.  
<br />  
<br />
== Installation ==  
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
== Installation ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
Applies to all SPLA licenses (except RDS users): <br>
Gilt für alle SPLA-Lizenzen (außer RDS-Benutzer): <br>  
You can find the installation files in ISO format on our FTP server (ftp44.terracloud.de). Please note that you only have explicit access to this server within our data center. No access data is required to log in to the server. Here you can download the corresponding ISO file and then run the setup EXE on the ISO.<br>
Die Installationsdateien finden Sie im ISO-Format auf unserem FTP-Server (ftp44.terracloud.de). Hierbei ist zu beachten, dass Sie nur explizit innerhalb unseres Rechenzentrums Zugriff auf diesen Server haben. Es sind keine Zugangsdaten nötig um sich auf dem Server anzumelden. Hier können Sie die entsprechende ISO-Datei herunterladen und anschließend die Setup-EXE auf der ISO ausführen.<br>  
<br>
Installationsanleitung: <br>  
<b>Note:<br></b>
- [https://docs.microsoft.com/de-de/Exchange/plan-and-deploy/deploy-new-installations/deploy-new-installations?view=exchserver-2016 Exchange 2016] <br>  
Our FTP server requires a connection with a certificate and explicit TLS.<br>
- [https://docs.microsoft.com/de-de/sql/database-engine/install-windows/install-sql-server?view=sql-server-2017 SQL Server 2016]<br>  
Therefore, connecting via File Explorer will not work. We recommend using the tool FileZilla instead.<br>
<br>
If you experience DNS problems establishing a connection, you can also access the FTP44 server via the IP address: 185.35.12.116.<br>
Please note, however, that the IP address can change at any time, so we recommend using the DNS name whenever possible.<br>
<br>
Installation instructions: <br>
- [https://docs.microsoft.com/de-de/Exchange/plan-and-deploy/deploy-new-installations/deploy-new-installations?view=exchserver-2016 Exchange 2016] <br>
- [https://docs.microsoft.com/de-de/sql/database-engine/install-windows/install-sql-server?view=sql-server-2017 SQL Server 2016]<br>
- [https://docs.microsoft.com/de-de/sharepoint/install/install Sharepoint 2016]
- [https://docs.microsoft.com/de-de/sharepoint/install/install Sharepoint 2016]
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
== Lizensierung ==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Lizensierung"></span>
=== Microsoft Office Standard / Professional Plus ===
== Licensing ==
</div>
 
=== Microsoft Windows Server ===
 
This activation procedure <b>only</b> works for Windows servers that are running in our cloud.<br>
<br>
'''Check port'''<br>
Please first check whether the necessary TCP network port for Windows activation is open:<br>
<br>
<code>Test-NetConnection 185.35.12.116 -port 1688</code><br>
<br>
If the result is True, activation can be carried out.<br>
<br>
'''Activation'''<br>
To activate, please use the following commands:<br>
<br>
<code>slmgr.vbs /skms 185.35.12.116:1688 </code> <br>
<code>slmgr.vbs /ato </code><br>
<br>
If an error message occurs with the above commands, please use the following commands:<br>
<br>
<code> slmgr.vbs /upk </code><br>
<code> slmgr.vbs /ipk WINDOWS_KEY </code><br>
<code> slmgr.vbs /skms 185.35.12.116:1688 </code><br>
<code> slmgr.vbs /ato </code> <br>
<br>
You can find the appropriate <code>WINDOWS_KEY</code> [https://learn.microsoft.com/de-de/windows-server/get-started/kms-client-activation-keys here].<br>
<br>
 
=== Microsoft Office Standard / Professional Plus ===  


<div lang="de" dir="ltr" class="mw-content-ltr">
To activate Microsoft Office Standard / Professional Plus, run the Powershell commands that you received from us in the deployment email. Activation takes place via our KMS server. <br>
Um Microsoft Office Standard / Professional Plus zu aktivieren, führen Sie die Powershell-Befehle aus, die Sie in der Bereitstellungs-Mail von uns bekommen haben. Es erfolgt eine Aktivierung über unseren KMS-Server. <br>
[https://learn.microsoft.com/de-de/deployoffice/ltsc2021/deploy Deploy Office]
[https://learn.microsoft.com/de-de/deployoffice/ltsc2021/deploy Deploy Office]  
<br />
<br />
</div>
<span id="Office-Varianten"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
=== Office variants ===
=== Office-Varianten: ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
'''Standard''' <br>
'''Standard''' <br>
In einer Office Standard Lizenz sind die folgenden Programme und Apps enthalten:<br>
An Office Standard license includes the following programs and apps:<br>
Word, Excel, PowerPoint, OneNote, Outlook, Publisher, Office Web Apps <br><br>  
Word, Excel, PowerPoint, OneNote, Outlook, Publisher, Office Web Apps <br><br>
'''Standard / Professional Plus''' <br>
'''Standard / Professional Plus''' <br>
In einer Office Standard Plus Lizenz sind die folgenden Programme und Apps enthalten:<br>
An Office Standard Plus license includes the following programs and apps:<br>
Word, Excel, PowerPoint, OneNote, Outlook, Publisher, Office Web Apps, <span style="Color:green">Access, InfoPath, Skype for Business</span> <br>
Word, Excel, PowerPoint, OneNote, Outlook, Publisher, Office Web Apps, <span style="Color:green">Access, InfoPath, Skype for Business</span> <br>
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
=== Microsoft Project ===
=== Microsoft Project ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
To activate Microsoft Project, run the Powershell commands that you received from us in the deployment email. Activation takes place via our KMS server.
Um Microsoft Project zu aktivieren, führen Sie die Powershell-Befehle aus, die Sie in der Bereitstellungs-Mail von uns bekommen haben. Es erfolgt eine Aktivierung über unseren KMS-Server.
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
=== Microsoft Visio ===
=== Microsoft Visio ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
To activate Microsoft Visio, run the Powershell commands that you received from us in the deployment email. Activation takes place via our KMS server.
Um Microsoft Visio zu aktivieren, führen Sie die Powershell-Befehle aus, die Sie in der Bereitstellungs-Mail von uns bekommen haben. Es erfolgt eine Aktivierung über unseren KMS-Server.
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
=== Microsoft Exchange ===
=== Microsoft Exchange ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
A TeamViewer remote session must be carried out to activate your Exchange server.<br>
Bitte wenden Sie sich an den Terra Cloud Support [mailto:support@terracloud.de support@terracloud.de] mit der Angabe der Bestellnummer und des Servernamens auf dem Exchange installiert ist. Der Support wird eine VHD an dem Server anhängen und Ihnen eine Rückmeldung geben. Sie müssen die VHD unter der Datenträgerverwaltung online nehmen und die EXE-Datei ausführen. Die Disk wird automatisch nach 7 Tagen vom System abgehangen.   
Therefore, please install the Exchange server and prepare a TeamViewer on the server.<br>
<br />
Then please contact Terra Cloud Support by phone: +49 (0)5744 944-850.<br>
</div>
They will then carry out the Exchange server activation.
<div lang="de" dir="ltr" class="mw-content-ltr">
 
=== Microsoft SQL Server ===
=== Microsoft SQL Server ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
Since the license is included in the ISO, SQL does not need to be activated separately.
Da die Lizenz in dem ISO enthalten ist, muss SQL nicht gesondert aktiviert werden.  
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
=== Windows RDS ===
=== Windows RDS ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
To activate RDS licenses, a license server ID is required to create a license package ID.
Für die Aktivierung von RDS-Lizenzen wird eine Lizenzserver-ID benötigt um eine Lizenzpaket-ID zu erstellen.  
Further information on the subject of RDS licenses can be found [[SPLA/en#Remote_Desktop_Server_Activation|here]].
Weitere Informationen zu dem Thema RDS Lizenzen finden Sie [[SPLA#Remote_Desktop_Server_Aktivierung|hier]].
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
=== SharePoint ===
=== SharePoint ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
After completing the setup, you will be asked to enter a product key, which you will receive from Terra Cloud Support upon request.
Nach der Ausführung des Setups werden Sie aufgefordert einen Produkt Key einzugeben, welchen Sie vom Terra Cloud Support auf Nachfrage erhalten.
<br />
<br />
</div>
<div lang="de" dir="ltr" class="mw-content-ltr">
= Remote Desktop Server Aktivierung =
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Remote_Desktop_Server_Aktivierung"></span>
== Voraussetzung ==
= Remote Desktop Server Activation =
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Voraussetzung"></span>
Eine Terminal-Server Remote Desktop Service - Subscriber Access License (RDS-SAL) ist erforderlich, wenn direkt oder indirekt RDS Funktionen genutzt werden.<br>  
== Requirement ==
Dazu gehören Funktionen und Dienste die mit aktivierter Remote Desktop Services Rolle genutzt werden:<br>
 
• Remote Desktop Gateway<br>
A Terminal Server Remote Desktop Service - Subscriber Access License (RDS-SAL) is required if RDS functions are used directly or indirectly.<br>
• RemoteApp Network Software<br>
This includes functions and services that are used with the Remote Desktop Services role activated:<br>
• Remote Desktop Web Access<br>
• Remote Desktop Gateway<br>
• Remote Web Access<br>
• RemoteApp Network Software<br>
• Remote Desktop Connection Broker<br>
• Remote Desktop Web Access<br>
• Remote Desktop Session Host<br>
• Remote Web Access<br>
• Remote Desktop Virtualization Host<br>
• Remote Desktop Connection Broker<br>
• RemoteFX<br>
• Remote Desktop Session Host<br>
Um nun technisch festzustellen, ob eine dieser Funktionen genutzt wird, kann im Windows Server geprüft werden, welche Features und Rollen installiert sind:<br>
• Remote Desktop Virtualization Host<br>
[[Datei:Serverrollen.png|border]]<br>
• RemoteFX<br>
In order to technically determine whether one of these functions is being used, you can check in Windows Server which features and roles are installed:<br>
[[File:Serverrollen.png|border]]<br>
<br>
<br>
[[Datei:Rollendienste.png|border]]<br>
[[File:Rollendienste.png|border]]<br>
<br>
<br>
Auch andere Produkte wie VMWare oder Citrix benötigen eine RDS CAL sofern sie diese o.g. Funktionen nutzen.<br>
Other products such as VMWare or Citrix also require an RDS CAL if they use these above-mentioned functions.<br>
Im folgenden Dokument sind Beispielhostnamen verwendet worden, dieses kann von Ihrer bereitgestellten Umgebung abweichen.<br>
Sample hostnames have been used in the following document, this may differ from your deployed environment.<br>
</div>
<span id="Aktivierung_RDS_für_SPLA_Vertrags-Partner"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
== Activation RDS for SPLA contract partners==
== Aktivierung RDS für SPLA Vertrags-Partner==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Einleitung"></span>
===Einleitung===
===Introduction===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
Activating Terminal Server Remote Desktop Service - Subscriber Access Licenses (RDS-SALs) as an SPLA contract partner is a crucial step in offering Microsoft Terminal Server services in a hosting environment.<br>
Die Aktivierung von Terminal-Server Remote Desktop Service - Subscriber Access Licenses (RDS-SALs) als SPLA-Vertragspartner ist ein entscheidender Schritt, um Microsoft Terminal-Server-Dienste in einer Hosting-Umgebung anzubieten.<br>
This wiki entry provides detailed instructions for SPLA contract partners on how to activate RDS-SALs and correctly record them in their monthly SPLA reporting.<br>
Dieser Wiki-Eintrag bietet eine ausführliche Anleitung für SPLA-Vertragspartner, wie sie RDS-SALs aktivieren und in ihrem monatlichen SPLA-Reporting korrekt erfassen können.<br>
<p style="color: red">
</div>
<b>'''Important:'''</p>
<div lang="de" dir="ltr" class="mw-content-ltr">
These instructions assume that you are a SPLA contract partner with Microsoft and have your own SPLA contract number.<br>
===Schritte zur Aktivierung von Terminal-Server RDS-SALs===
If you use the SPLA services via the Terra Cloud, please use the following instructions: [[https://wiki.terracloud.de/index.php/SPLA/en#Activation_of_RDS_for_non-SPLA_contract_partners_(when_booking_via_the_Terra_Cloud) Link]]
</div>
.</b><br>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Schritte_zur_Aktivierung_von_Terminal-Server_RDS-SALs"></span>
;1. SPLA-Vertragsnummer:
===Steps for Activating Terminal Server RDS SALs===
:Als SPLA-Vertragspartner verfügen Sie über eine eindeutige SPLA-Vertragsnummer, die für die Lizenzierung und Abrechnung verwendet wird. Stellen Sie sicher, dass Sie diese Nummer zur Hand haben.
 
;2. Terminal-Server-Rolle aktivieren:
;1. SPLA contract number:
:Loggen Sie sich auf dem Terminal-Server-Host ein und öffnen Sie die Server Manager-Anwendung. Navigieren Sie zu den "Rollen" und "Funktionen" und wählen Sie die Terminal-Server-Rolle zur Aktivierung aus.
:As an SPLA contract partner, you have a unique SPLA contract number that is used for licensing and billing. Make sure you have this number handy.
;3. Eingabe der SPLA-Vertragsnummer:
;2. Activate terminal server role:
:Im Aktivierungsvorgang der Terminal-Server-Rolle werden Sie aufgefordert, Ihre SPLA-Vertragsnummer einzugeben. Stellen Sie sicher, dass diese Nummer korrekt und ohne Fehler eingegeben wird, da sie zur Identifizierung Ihres Vertrags und der damit verbundenen RDS-SALs verwendet wird.
:Log in to the Terminal Server host and open the Server Manager application. Navigate to "Roles" and "Capabilities" and select the Terminal Server role to activate.
;4. Services Provider License Agreement (SPLA) wählen:
;3. Entering the SPLA contract number:
:Wählen Sie während des Aktivierungsvorgangs die Option "Services Provider License Agreement" aus. Dies ist erforderlich, um die RDS-SALs als SPLA-Vertragspartner zu aktivieren.
:In the Terminal Server role activation process, you will be asked to enter your SPLA contract number. Make sure this number is entered correctly and without errors as it is used to identify your contract and associated RDS SALs.
;5. Bestätigung und Abschluss:
;4. Select Services Provider License Agreement (SPLA):
:Nachdem Sie Ihre SPLA-Vertragsnummer und die Auswahl des SPLA-Vertrags getroffen haben, klicken Sie auf "Weiter" und folgen Sie den Anweisungen, um den Aktivierungsvorgang abzuschließen.
:Select the "Services Provider License Agreement" option during the activation process. This is required to activate the RDS SALs as SPLA contractors.
;6. Lizenzaktivierung:
;5. Confirmation and completion:
:Nach erfolgreicher Aktivierung der Terminal-Server-Rolle sind die RDS-SALs auf dem entsprechenden Terminal-Server aktiviert und bereit zur Nutzung.
:After you have made your SPLA contract number and SPLA contract selection, click "Next" and follow the instructions to complete the activation process.
;7. Monatliches SPLA-Reporting:
;6. License activation:
:Als SPLA-Vertragspartner sind Sie verpflichtet, die Anzahl der genutzten Terminal-Server-Zugriffslizenzen (RDS-SALs) in Ihrem monatlichen SPLA-Reporting korrekt zu erfassen und zu melden. Dies ist wichtig, um die Lizenzgebühren korrekt abzurechnen.
:After successful activation of the terminal server role, the RDS SALs are activated on the corresponding terminal server and ready for use.
[[Datei:RDS.jpg|border|Wizard]]
;7. Monthly SPLA reporting:
:As a SPLA contractual partner, you are obliged to correctly record and report the number of terminal server access licenses (RDS SALs) used in your monthly SPLA reporting. This is important in order to bill the license fees correctly.
[[File:RDS.jpg|border|Wizard]]
<br>
<br>
</div>
<span id="Zusammenfassung"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
===Summary===
===Zusammenfassung===
 
</div>
Activating Terminal Server RDS SALs as a SPLA contract partner requires entering your SPLA contract number during the Terminal Server role activation process.<br>
Once activated, you must ensure that you document the RDS SALs used in your monthly SPLA reporting to properly meet legal requirements and billing.<br>
This process is critical to legally offering and managing Microsoft Hosted Services.
<span id="Aktivierung_unter_Windows_Server_2022"></span>
=== Activation in Windows Server 2022 ===


<div lang="de" dir="ltr" class="mw-content-ltr">
We have found a very good and detailed guide for Windows Server 2022 on the Internet, which we do not want to withhold from you:<br>
Die Aktivierung von Terminal-Server RDS-SALs als SPLA-Vertragspartner erfordert die Eingabe Ihrer SPLA-Vertragsnummer während des Aktivierungsvorgangs der Terminal-Server-Rolle.<br>
[[https://spheremedia.de/windows-server-2022-terminalserver-einrichten-anleitung-einfach/windows-server/ Link]]<br>
Nach der Aktivierung müssen Sie sicherstellen, dass Sie die genutzten RDS-SALs in Ihrem monatlichen SPLA-Reporting dokumentieren, um die rechtlichen Anforderungen und Abrechnungen ordnungsgemäß zu erfüllen.<br>
<br>
Dieser Prozess ist entscheidend, um Microsoft-Hosted-Dienste rechtmäßig anzubieten und zu verwalten.
'''Note:''' This link and its content are without guarantee.<br>
</div>
<span id="Aktivierung_RDS_für_nicht_SPLA_Vertrags-Partner_(bei_Buchung_über_die_Terra_Cloud)"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
== Activation of RDS for non-SPLA contract partners (when booking via the Terra Cloud)==
== Aktivierung RDS für nicht SPLA Vertrags-Partner (bei Buchung über die Terra Cloud)==
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Aktivierung_des_RDS_Server_Host"></span>
=== Aktivierung des RDS Server Host ===
=== Activation of the RDS Server Host ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
To activate Remote Desktop Services on a Windows Server, the following steps must be carried out. <br>
Für die Aktivierung der Remote Desktop Services auf einem Windows Server müssen die folgenden Schritte durchgeführt werden. <br>
1. Please start Server Manager. <br>
1. Bitte starten Sie den Server-Manager. <br>
[[File:ServerManager.png|border|Server Manager]] <br>
[[Datei:ServerManager.png|border|Server Manager]] <br>
<br>
<br>
2. Danach wählen Sie den Punkt Remotedesktop-Dienste aus. <br>
2. Then select Remote Desktop Services. <br>
[[Datei:Remotedienste.png|border|Remotedesktop-Dienste]] <br>
[[File:Remotedienste.png|border|Remote Desktop Services]] <br>
<br>
<br>
3. Den Unterpunkt Server auswählen und es wird der installierte RDS-Server dargestellt. <br>
3. Select the Server sub-item and the installed RDS server will be displayed. <br>
[[Datei:Installierte RDS-Serve.png|border|Installierte RDS-Server]] <br>
[[File:Installierte RDS-Serve.png|border|Installed RDS Servers]] <br>
<br>
<br>
4. Auf dem RDS Server mittels Rechtsklick den Remotedesktoplizensierungs-Manager starten. <br>
4. Start the Remote Desktop Licensing Manager on the RDS server by right-clicking. <br>
[[Datei:Kontextmenue.png|border|Kontextmenü]] <br>
[[File:Kontextmenue.png|border|Contextmenu]] <br>
<br>
<br>
5. Der Lizenzierungsmanager sollte wie folgt aussehen. <br>
5. The licensing manager should look like this. <br>
[[Datei:Remotedesktoplizensierungsmanager.png|Remotedesktoplizensierungsmanager]] <br>
[[File:Remotedesktoplizensierungsmanager.png|Remote Desktop Licensing Manager]] <br>
<br>
<br>
6. Server aktivieren auswählen. <br>
6. Select Activate Server. <br>
[[Datei:Server aktivieren.png|border|Server aktivieren]] <br>
[[File:Server aktivieren.png|border|Activate Server]] <br>
<br>
<br>
7. Der Serveraktivierungs-Assistent wird gestartet mit „Weiter“ fortfahren. <br>
7. The server activation wizard will start and continue with “Next”. <br>
[[Datei:Serveraktivierungs-Assistent.png|border|Server aktivieren]] <br>
[[File:Serveraktivierungs-Assistent.png|border|Activate Server]] <br>
<br>
<br>
8. Vorausgewählte Verbindungsmethode „Automatische Verbindung“ muss ausgewählt sein und mit „Weiter“ fortfahren. <br>
8. Preselected connection method “Automatic connection” must be selected and proceed with “Next”. <br>
[[Datei:Automatische Verbindung.png|border|Automatische Verbindung]] <br>
[[File:Automatische Verbindung.png|border|Automatic Connection]] <br>
<br>
<br>
9. Firmeninformationen der Seite 1 mit Daten befüllen und mit „Weiter“ fortfahren. <br>
9. Fill in company information on page 1 with data and continue with “Next”. <br>
[[Datei:Firmeninformation.png|border|Firmeninformationen eintragen]] <br>
[[File:Firmeninformation.png|border|Enter company information]] <br>
<br>
<br>
10. Firmeninformationen der Seite 2 mit Daten befüllen und mit „Weiter“ fortfahren. <br>
10. Fill in company information on page 2 with data and continue with “Next”. <br>
[[Datei:Firmeninformationen1.png|border|Weitere Firmeninformationen]] <br>
[[File:Firmeninformationen1.png|border|More company information]] <br>
<br>
<br>
11. Die Aktivierung wird durchgeführt und ist mit „Schließen“ beendet <br>
11. Activation is carried out and ends with “Close” <br>
[[Datei:Serveraktivierungsassistent.png|border|Fertigstellen]] <br>
[[File:Serveraktivierungsassistent.png|border|Finish]] <br>
<br>
<br>
[[Datei:Aktivierungsstatus.png|border|Übersicht]] <br>
[[File:Aktivierungsstatus.png|border|Overview]] <br>
<br />
<br />
</div>
<span id="Aktivierung_der_RDS_Server_CALs"></span>
<div lang="de" dir="ltr" class="mw-content-ltr">
=== Activation of the RDS server CALs ===
=== Aktivierung der RDS Server CALs ===
</div>


<div lang="de" dir="ltr" class="mw-content-ltr">
To activate the user access licenses (User CAL), it is necessary to adapt the server activation connection method. The following steps are required for this: <br>
Für die Aktivierung der Benutzer-Zugriffslizenzen (User-CAL) ist es erforderlich die Verbindungsmethode der Serveraktivierung anzupassen. Hierfür sind folgenden Schritte erforderlich: <br>
1. In the Licensing Manager, go to the properties of the RDS server and set the connection method to web browser as shown below. <br>
1. Im Lizensierungs-Manager die Eigenschaften des RDS Server aufrufen und die Verbindungsmethode wie unten abgebildet auf Webbrowser stellen. <br>
[[File:EigenschaftenRDSSRV.png|border|Properties]] <br>
[[Datei:EigenschaftenRDSSRV.png|border|Eigenschaften]] <br>  
<br>
2. Now select Install licenses. <br>
[[File:Lizenzen installieren.png|border|Install Licenses]] <br>
<br>
3. Now the license installation wizard starts, continue with “Next”. <br>
[[File:Lizenzinstallierungsassistent.png|border|License Installation Wizard]] <br>
<br>
<br>
2. Jetzt den Punkt Lizenzen installieren auswählen. <br>
4. The license server ID will appear in the window shown below.<br>
[[Datei:Lizenzen installieren.png|border|Lizenzen installieren]] <br>
<br>
<br>
3. Jetzt startet der Lizenzinstallations-Assistent, diesen mit „Weiter“ fortfahren. <br>  
Please send this to us in an informal email with the following subject to [mailto:support@terracloud.de support@terracloud.de]: <br>
[[Datei:Lizenzinstallierungsassistent.png|border|Lizenzinstallierungsassistent]] <br>
''''''RDS licenses package number/order number, number '<br>
<br>
<br>
4. In dem unten abgebildeten Fenster erscheint die Lizenzserver-ID. Bitte senden Sie uns eine formlose Mail mit dem Betreff: <br>
The team creates the necessary license key package ID. <br>
'''''„RDS-Lizenzen Paketnummer/Bestellnummer, Anzahl X“''''' sowie der '''''Lizenzserver-ID''''' und '''''verwendetem RDS-Serverbetriebssystem''''' im Inhalt für die notwendigen Benutzer-Zugriffslizenzen an <br>
[mailto:support@terracloud.de support@terracloud.de]. Das Team erstellt die notwendige Lizenzschlüsselpaket-ID. <br>
[[Datei:LizenzserverID.png|border|LizenzserverID]] <br>
<br>
<br>
5. Die vom TERRACLOUD Team erhaltene Lizenzschlüsselpaket-ID in die Felder eintragen und mit „Weiter“ fortfahren. <br>
[[File:LizenzserverID.png|border|LicenseServerID]] <br>
[[Datei:Lizenzschluesselpaket-ID.png|border|Lizenzschlüsselpaket-ID]] <br>  
<br>
<br>
6. Nach erfolreicher Registrierung der Lizenz sind die Benutzer-Zugriffslizenzen aktiviert. <br>  
5. Enter the license key package ID received from the TERRACLOUD team in the fields and continue with “Next”. <br>
[[Datei:Zugriffslizenzen aktiviert.png|border|Zugriffslizenzen aktiviert]] <br>
[[File:Lizenzschluesselpaket-ID.png|border|License key package ID]] <br>
<br>
7. Nach erfolgreicher Aktivierung werden die freigeschalteten Benutzer-Zugriffslizenzen im Lizenzierungs-Manager angezeigt. <br>
[[Datei:Anzeige im Lizenzmanager.png|border|Anzeige im Lizenzmanager]] <br>
<br>
<br>
Sollte hier eine „Pro Geräte“ RDS-CAL angezeigt werden, kontaktieren Sie bitte unseren Support. <br>
6. After successfully registering the license, the user access licenses are activated. <br>
[[File:Zugriffslizenzen aktiviert.png|border|Access licenses activated]] <br>
<br>
<br>
8. Nach dem Einspielen müssen noch zwingend zwei Anpassungen vorgenommen werden, da der Lizenzserver sonst nach der Karenzzeit von 120 Tagen, seine Funktion einstellt.<br>
7. After successful activation, the activated user access licenses will be displayed in the licensing manager. <br>
[[Datei:Lizenzierungsmodus konfigurieren.png|border|120 Tage Karenzzeit - Fehlende Konfiguration]]<br>
[[File:Anzeige im Lizenzmanager.png|border|Display in the license manager]] <br>
<br>
<br>
Dazu öffnet man die Bereitstellungseigenschaften:<br>
If a “per device” RDS CAL is displayed here, please contact our support. <br>
[[Datei:Server Manager RDS.png|border|Bereitstellungseigenschaften im Server-Manager]]<br>
<br>
<br>
Dort wird die IP des Lizenzservers eingetragen und der Remotedesktop-Lizenzierungsmodus auf „Pro Benutzer“ gesetzt.<br>
8. After importing, two adjustments must be made, otherwise the license server will stop functioning after the grace period of 120 days.<br>
In unserem Beispiel wurde der Lizenzserver auf einem separaten Server installiert, entsprechend wird deren IP-Adresse eingetragen.<br>
[[File:Lizenzierungsmodus konfigurieren.png|border|120 days grace period - Missing configuration]]<br>
[[Datei:Bereitstellung konfigurieren.png|border|Bereitstellung konfigurieren]]<br>
<br>
To do this, open the deployment properties:<br>
[[File:Server Manager RDS.png|border|Deployment properties in Server Manager]]<br>
<br>
The IP of the license server is entered there and the remote desktop licensing mode is set to “Per user”.<br>
In our example, the license server was installed on a separate server and its IP address is entered accordingly.<br>
[[File:Bereitstellung konfigurieren.png|border|Configure Deployment]]<br>
<br />
<br />
</div>
<span id="Aktivierung_unter_Windows_Server_2022"></span>
=== Activation in Windows Server 2022 ===
 
We have found a very good and detailed guide for Windows Server 2022 on the Internet, which we do not want to withhold from you:<br>
[[https://spheremedia.de/windows-server-2022-terminalserver-einrichten-anleitung-einfach/windows-server/ Link]]<br>
<br>
'''Note:''' This link and its content are without guarantee.<br>

Aktuelle Version vom 18. März 2025, 14:17 Uhr

Sprachen:

SPLA stands for Service Provider License Agreement.
It is a special form of license in which you can rent software licenses and re-rent them in accordance with licensing law.
SPLA makes it possible to bill the licenses of Microsoft products on a monthly basis - and only the services offered to the customer in the respective month.

General contact SPLA
Email: spla@wortmann.de
Telephone: 05744 944-254

Microsoft SPLA (Services Provider License Agreement)

is a program for service providers and ISVs (Independent Software Vendors).
This program lets you license Microsoft products on a monthly basis - under a three-year contract - to host software services and applications for your customers.
SPLA offers a variety of hosting scenarios with which you can offer your customers highly individual and robust solutions.
Volume Licensing Customers can license their server applications on-premise and in the cloud.
The latter usually happens within the framework of a qualified shared hardware environment for the service provider's specific applications.

What is the difference between SPLA and the other Microsoft Volume Licensing programs?
Microsoft Volume Licensing Programs offer various licensing options for purchasing Microsoft software licenses for internal use.
Hosting providers who want to offer software services to their customers and who offer software licenses as part of their service offering should use SPLA.
Microsoft SPLA is the only Microsoft Volume Licensing program that allows you to use Microsoft products for commercial hosting.

SPLA offers you these advantages

  • Customized Service: Get the flexibility to offer your customers customized IT services through a dedicated or shared hosting environment.
  • "Pay as you go" without upfront payment: Only pay for the licenses you need each month for your software services. There are no upfront costs or long-term commitments.
  • Access to the latest product versions: Provide your customers with the most current and powerful platform. Easily download your products for free from the Microsoft Volume Licensing Service Center (VLSC) instead of ordering physical media.
  • Try before you buy: Test and evaluate products internally before offering them as a service to your customers.
  • Install directly at the customer's site: Install Microsoft products on servers located at your end customer's - under your management and control.
  • Offer demonstrations and evaluations: You have up to 50 user product demos for Microsoft software. Offer your customers a 60-day trial free of charge.
  • All your locations under a single contract
  • Expand your audience: Expand your business with special offers for academic end customers.


Become a SPLA contractual partner or obtain it conveniently via the TERRA CLOUD Center

Wortmann AG offers you two purchasing options. Here you can decide which path you take.

You have the option of purchasing SPLA licenses directly in the TERRA CLOUD Center at e.g. B. to book a configuration of a virtual machine.
In hosting and IaaS, we offer all SPLA licenses currently provided by Microsoft. In Germany, booking licenses of this type without an SPLA contract is only possible with Telekom AG and Wortmann AG.
Billing is done using the TERRA CLOUD invoice.

If you would like to rent SPLA licenses cheaper, directly from the end customer and even more flexibly on a monthly basis, you can become a SPLA contractual partner with Wortmann AG.
Microsoft itself gives you access to all SPLA licenses currently provided by Microsoft via the VLSC (Volume Licensing Service Center).
With this option, you must report to Wortmann AG on a monthly basis which licenses you use or rent.
Here we check the report for any obvious licensing errors and resolve these together before submitting the report to the manufacturer.

SPLA licensing

User CAL's or SAL's

User CALs as you know them do not exist in SaaS and IaaS for Windows servers.
With SPLA licensing there are no longer any CALs, only SALs. With Exchange, you only have to license the users who access the Exchange server.
If this VM is a terminal server environment, you would only have to think about the RDS CALs. These still exist.

Installation

Applies to all SPLA licenses (except RDS users):
You can find the installation files in ISO format on our FTP server (ftp44.terracloud.de). Please note that you only have explicit access to this server within our data center. No access data is required to log in to the server. Here you can download the corresponding ISO file and then run the setup EXE on the ISO.

Note:
Our FTP server requires a connection with a certificate and explicit TLS.
Therefore, connecting via File Explorer will not work. We recommend using the tool FileZilla instead.

If you experience DNS problems establishing a connection, you can also access the FTP44 server via the IP address: 185.35.12.116.
Please note, however, that the IP address can change at any time, so we recommend using the DNS name whenever possible.

Installation instructions:
- Exchange 2016
- SQL Server 2016
- Sharepoint 2016

Licensing

Microsoft Windows Server

This activation procedure only works for Windows servers that are running in our cloud.

Check port
Please first check whether the necessary TCP network port for Windows activation is open:

Test-NetConnection 185.35.12.116 -port 1688

If the result is True, activation can be carried out.

Activation
To activate, please use the following commands:

slmgr.vbs /skms 185.35.12.116:1688
slmgr.vbs /ato

If an error message occurs with the above commands, please use the following commands:

slmgr.vbs /upk
slmgr.vbs /ipk WINDOWS_KEY
slmgr.vbs /skms 185.35.12.116:1688
slmgr.vbs /ato

You can find the appropriate WINDOWS_KEY here.

Microsoft Office Standard / Professional Plus

To activate Microsoft Office Standard / Professional Plus, run the Powershell commands that you received from us in the deployment email. Activation takes place via our KMS server.
Deploy Office

Office variants

Standard
An Office Standard license includes the following programs and apps:
Word, Excel, PowerPoint, OneNote, Outlook, Publisher, Office Web Apps

Standard / Professional Plus
An Office Standard Plus license includes the following programs and apps:
Word, Excel, PowerPoint, OneNote, Outlook, Publisher, Office Web Apps, Access, InfoPath, Skype for Business

Microsoft Project

To activate Microsoft Project, run the Powershell commands that you received from us in the deployment email. Activation takes place via our KMS server.

Microsoft Visio

To activate Microsoft Visio, run the Powershell commands that you received from us in the deployment email. Activation takes place via our KMS server.

Microsoft Exchange

A TeamViewer remote session must be carried out to activate your Exchange server.
Therefore, please install the Exchange server and prepare a TeamViewer on the server.
Then please contact Terra Cloud Support by phone: +49 (0)5744 944-850.
They will then carry out the Exchange server activation.

Microsoft SQL Server

Since the license is included in the ISO, SQL does not need to be activated separately.

Windows RDS

To activate RDS licenses, a license server ID is required to create a license package ID. Further information on the subject of RDS licenses can be found here.

SharePoint

After completing the setup, you will be asked to enter a product key, which you will receive from Terra Cloud Support upon request.

Remote Desktop Server Activation

Requirement

A Terminal Server Remote Desktop Service - Subscriber Access License (RDS-SAL) is required if RDS functions are used directly or indirectly.
This includes functions and services that are used with the Remote Desktop Services role activated:
• Remote Desktop Gateway
• RemoteApp Network Software
• Remote Desktop Web Access
• Remote Web Access
• Remote Desktop Connection Broker
• Remote Desktop Session Host
• Remote Desktop Virtualization Host
• RemoteFX
In order to technically determine whether one of these functions is being used, you can check in Windows Server which features and roles are installed:




Other products such as VMWare or Citrix also require an RDS CAL if they use these above-mentioned functions.
Sample hostnames have been used in the following document, this may differ from your deployed environment.

Activation RDS for SPLA contract partners

Introduction

Activating Terminal Server Remote Desktop Service - Subscriber Access Licenses (RDS-SALs) as an SPLA contract partner is a crucial step in offering Microsoft Terminal Server services in a hosting environment.
This wiki entry provides detailed instructions for SPLA contract partners on how to activate RDS-SALs and correctly record them in their monthly SPLA reporting.

Important:

These instructions assume that you are a SPLA contract partner with Microsoft and have your own SPLA contract number.
If you use the SPLA services via the Terra Cloud, please use the following instructions: [Link] .

Steps for Activating Terminal Server RDS SALs

1. SPLA contract number
As an SPLA contract partner, you have a unique SPLA contract number that is used for licensing and billing. Make sure you have this number handy.
2. Activate terminal server role
Log in to the Terminal Server host and open the Server Manager application. Navigate to "Roles" and "Capabilities" and select the Terminal Server role to activate.
3. Entering the SPLA contract number
In the Terminal Server role activation process, you will be asked to enter your SPLA contract number. Make sure this number is entered correctly and without errors as it is used to identify your contract and associated RDS SALs.
4. Select Services Provider License Agreement (SPLA)
Select the "Services Provider License Agreement" option during the activation process. This is required to activate the RDS SALs as SPLA contractors.
5. Confirmation and completion
After you have made your SPLA contract number and SPLA contract selection, click "Next" and follow the instructions to complete the activation process.
6. License activation
After successful activation of the terminal server role, the RDS SALs are activated on the corresponding terminal server and ready for use.
7. Monthly SPLA reporting
As a SPLA contractual partner, you are obliged to correctly record and report the number of terminal server access licenses (RDS SALs) used in your monthly SPLA reporting. This is important in order to bill the license fees correctly.

Wizard

Summary

Activating Terminal Server RDS SALs as a SPLA contract partner requires entering your SPLA contract number during the Terminal Server role activation process.
Once activated, you must ensure that you document the RDS SALs used in your monthly SPLA reporting to properly meet legal requirements and billing.
This process is critical to legally offering and managing Microsoft Hosted Services.

Activation in Windows Server 2022

We have found a very good and detailed guide for Windows Server 2022 on the Internet, which we do not want to withhold from you:
[Link]

Note: This link and its content are without guarantee.

Activation of RDS for non-SPLA contract partners (when booking via the Terra Cloud)

Activation of the RDS Server Host

To activate Remote Desktop Services on a Windows Server, the following steps must be carried out.
1. Please start Server Manager.
Server Manager

2. Then select Remote Desktop Services.
Remote Desktop Services

3. Select the Server sub-item and the installed RDS server will be displayed.
Installed RDS Servers

4. Start the Remote Desktop Licensing Manager on the RDS server by right-clicking.
Contextmenu

5. The licensing manager should look like this.
Remote Desktop Licensing Manager

6. Select Activate Server.
Activate Server

7. The server activation wizard will start and continue with “Next”.
Activate Server

8. Preselected connection method “Automatic connection” must be selected and proceed with “Next”.
Automatic Connection

9. Fill in company information on page 1 with data and continue with “Next”.
Enter company information

10. Fill in company information on page 2 with data and continue with “Next”.
More company information

11. Activation is carried out and ends with “Close”
Finish

Overview

Activation of the RDS server CALs

To activate the user access licenses (User CAL), it is necessary to adapt the server activation connection method. The following steps are required for this:
1. In the Licensing Manager, go to the properties of the RDS server and set the connection method to web browser as shown below.
Properties

2. Now select Install licenses.
Install Licenses

3. Now the license installation wizard starts, continue with “Next”.
License Installation Wizard

4. The license server ID will appear in the window shown below.

Please send this to us in an informal email with the following subject to support@terracloud.de:
'RDS licenses package number/order number, number '

The team creates the necessary license key package ID.

LicenseServerID

5. Enter the license key package ID received from the TERRACLOUD team in the fields and continue with “Next”.
License key package ID

6. After successfully registering the license, the user access licenses are activated.
Access licenses activated

7. After successful activation, the activated user access licenses will be displayed in the licensing manager.
Display in the license manager

If a “per device” RDS CAL is displayed here, please contact our support.

8. After importing, two adjustments must be made, otherwise the license server will stop functioning after the grace period of 120 days.
120 days grace period - Missing configuration

To do this, open the deployment properties:
Deployment properties in Server Manager

The IP of the license server is entered there and the remote desktop licensing mode is set to “Per user”.
In our example, the license server was installed on a separate server and its IP address is entered accordingly.
Configure Deployment

Activation in Windows Server 2022

We have found a very good and detailed guide for Windows Server 2022 on the Internet, which we do not want to withhold from you:
[Link]

Note: This link and its content are without guarantee.