SPLA/en: Unterschied zwischen den Versionen

Aus TERRA CLOUD WIKI

(Die Seite wurde neu angelegt: „=== Microsoft Project ===“)
(Übernehme Bearbeitung einer neuen Version der Quellseite)
 
(24 dazwischenliegende Versionen von 2 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
<languages/>
SPLA stands for Service Provider License Agreement. <br>
SPLA stands for Service Provider License Agreement. <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>
It is a special form of license in which you can rent software licenses and re-rent them in accordance with licensing law. <br>
Zeile 59: Zeile 60:
Applies to all SPLA licenses (except RDS users): <br>
Applies to all SPLA licenses (except RDS users): <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>
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>
<br>
<b>Note:<br></b>
Our FTP server requires a connection with a certificate and explicit TLS.<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>
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/Exchange/plan-and-deploy/deploy-new-installations/deploy-new-installations?view=exchserver-2016 Exchange 2016] <br>
Zeile 64: Zeile 73:
- [https://docs.microsoft.com/de-de/sharepoint/install/install Sharepoint 2016]
- [https://docs.microsoft.com/de-de/sharepoint/install/install Sharepoint 2016]
<br />
<br />
<span id="Lizensierung"></span>
<span id="Lizensierung"></span>
== Licensing ==
== Licensing ==
=== 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 ===  
=== Microsoft Office Standard / Professional Plus ===  
Zeile 72: Zeile 109:
[https://learn.microsoft.com/de-de/deployoffice/ltsc2021/deploy Deploy Office]
[https://learn.microsoft.com/de-de/deployoffice/ltsc2021/deploy Deploy Office]
<br />
<br />
<span id="Office-Varianten:"></span>
<span id="Office-Varianten"></span>
=== Office variants: ===
=== Office variants ===


'''Standard''' <br>
'''Standard''' <br>
Zeile 92: Zeile 129:
=== Microsoft Exchange ===
=== Microsoft Exchange ===


Please contact Terra Cloud Support [mailto:support@terracloud.de support@terracloud.de] stating the order number and the server name on which Exchange is installed. Support will attach a VHD to the server and give you feedback. You need to take the VHD online under Disk Management and run the EXE file. The disk will automatically be removed from the system after 7 days.
A TeamViewer remote session must be carried out to activate your Exchange server.<br>
<br />
Therefore, please install the Exchange server and prepare a TeamViewer on the server.<br>
Then please contact Terra Cloud Support by phone: +49 (0)5744 944-850.<br>
They will then carry out the Exchange server activation.
 
=== Microsoft SQL Server ===
=== Microsoft SQL Server ===


Zeile 101: Zeile 141:


To activate RDS licenses, a license server ID is required to create a license package ID.
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 [[SPLA#Remote_Desktop_Server_Aktivierung|here]].
Further information on the subject of RDS licenses can be found [[SPLA/en#Remote_Desktop_Server_Activation|here]].
<br />
<br />
=== SharePoint ===
=== SharePoint ===
Zeile 107: Zeile 147:
After completing the setup, you will be asked to enter a product key, which you will receive from Terra Cloud Support upon request.
After completing the setup, you will be asked to enter a product key, which you will receive from Terra Cloud Support upon request.
<br />
<br />
<span id="Remote_Desktop_Server_Aktivierung"></span>
<span id="Remote_Desktop_Server_Aktivierung"></span>
= Remote Desktop Server Activation =
= Remote Desktop Server Activation =
Zeile 113: Zeile 154:
== Requirement ==
== Requirement ==


<div lang="de" dir="ltr" class="mw-content-ltr">
A Terminal Server Remote Desktop Service - Subscriber Access License (RDS-SAL) is required if RDS functions are used directly or indirectly.<br>
Eine Terminal-Server Remote Desktop Service - Subscriber Access License (RDS-SAL) ist erforderlich, wenn direkt oder indirekt RDS Funktionen genutzt werden.<br>  
This includes functions and services that are used with the Remote Desktop Services role activated:<br>
Dazu gehören Funktionen und Dienste die mit aktivierter Remote Desktop Services Rolle genutzt werden:<br>
• Remote Desktop Gateway<br>
• Remote Desktop Gateway<br>
• RemoteApp Network Software<br>
• RemoteApp Network Software<br>
• Remote Desktop Web Access<br>
• Remote Desktop Web Access<br>
• Remote Web Access<br>
• Remote Web Access<br>
• Remote Desktop Connection Broker<br>
• Remote Desktop Connection Broker<br>
• Remote Desktop Session Host<br>
• Remote Desktop Session Host<br>
• Remote Desktop Virtualization Host<br>
• Remote Desktop Virtualization Host<br>
• RemoteFX<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>
Um nun technisch festzustellen, ob eine dieser Funktionen genutzt wird, kann im Windows Server geprüft werden, welche Features und Rollen installiert sind:<br>
[[File:Serverrollen.png|border]]<br>
[[Datei: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>


<div lang="de" dir="ltr" class="mw-content-ltr">
Activating Terminal Server RDS SALs as a SPLA contract partner requires entering your SPLA contract number during the Terminal Server role activation process.<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>
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>
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>
This process is critical to legally offering and managing Microsoft Hosted Services.
Dieser Prozess ist entscheidend, um Microsoft-Hosted-Dienste rechtmäßig anzubieten und zu verwalten.
<span id="Aktivierung_unter_Windows_Server_2022"></span>
</div>
=== Activation in Windows Server 2022 ===
<div lang="de" dir="ltr" class="mw-content-ltr">
== Aktivierung RDS für nicht SPLA Vertrags-Partner (bei Buchung über die Terra Cloud)==
</div>


<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>
=== Aktivierung des RDS Server Host ===
[[https://spheremedia.de/windows-server-2022-terminalserver-einrichten-anleitung-einfach/windows-server/ Link]]<br>
</div>
<br>
'''Note:''' This link and its content are without guarantee.<br>
<span id="Aktivierung_RDS_für_nicht_SPLA_Vertrags-Partner_(bei_Buchung_über_die_Terra_Cloud)"></span>
== Activation of RDS for non-SPLA contract partners (when booking via the Terra Cloud)==


<div lang="de" dir="ltr" class="mw-content-ltr">
<span id="Aktivierung_des_RDS_Server_Host"></span>
Für die Aktivierung der Remote Desktop Services auf einem Windows Server müssen die folgenden Schritte durchgeführt werden. <br>
=== Activation of the RDS Server Host ===
1. Bitte starten Sie den Server-Manager. <br>
 
[[Datei:ServerManager.png|border|Server Manager]] <br>
To activate Remote Desktop Services on a Windows Server, the following steps must be carried out. <br>
1. Please start Server Manager. <br>
[[File: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>
<br>
2. Jetzt den Punkt Lizenzen installieren auswählen. <br>  
2. Now select Install licenses. <br>
[[Datei:Lizenzen installieren.png|border|Lizenzen installieren]] <br>
[[File:Lizenzen installieren.png|border|Install Licenses]] <br>
<br>
<br>
3. Jetzt startet der Lizenzinstallations-Assistent, diesen mit „Weiter“ fortfahren. <br>  
3. Now the license installation wizard starts, continue with “Next”. <br>
[[Datei:Lizenzinstallierungsassistent.png|border|Lizenzinstallierungsassistent]] <br>
[[File:Lizenzinstallierungsassistent.png|border|License Installation Wizard]] <br>
<br>
<br>
4. In dem unten abgebildeten Fenster erscheint die Lizenzserver-ID. Bitte senden Sie uns eine formlose Mail mit dem Betreff: <br>
4. The license server ID will appear in the window shown below.<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>
Please send this to us in an informal email with the following subject to [mailto:support@terracloud.de support@terracloud.de]: <br>
[[Datei:Lizenzschluesselpaket-ID.png|border|Lizenzschlüsselpaket-ID]] <br>  
''''''RDS licenses package number/order number, number '<br>
<br>
<br>
6. Nach erfolreicher Registrierung der Lizenz sind die Benutzer-Zugriffslizenzen aktiviert. <br>
The team creates the necessary license key package ID. <br>
[[Datei:Zugriffslizenzen aktiviert.png|border|Zugriffslizenzen aktiviert]] <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>
[[File:LizenzserverID.png|border|LicenseServerID]] <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>
5. Enter the license key package ID received from the TERRACLOUD team in the fields and continue with “Next”. <br>
[[Datei:Lizenzierungsmodus konfigurieren.png|border|120 Tage Karenzzeit - Fehlende Konfiguration]]<br>
[[File:Lizenzschluesselpaket-ID.png|border|License key package ID]] <br>
<br>
<br>
Dazu öffnet man die Bereitstellungseigenschaften:<br>
6. After successfully registering the license, the user access licenses are activated. <br>
[[Datei:Server Manager RDS.png|border|Bereitstellungseigenschaften im Server-Manager]]<br>
[[File:Zugriffslizenzen aktiviert.png|border|Access licenses activated]] <br>
<br>
<br>
Dort wird die IP des Lizenzservers eingetragen und der Remotedesktop-Lizenzierungsmodus auf „Pro Benutzer“ gesetzt.<br>
7. After successful activation, the activated user access licenses will be displayed in the licensing manager. <br>
In unserem Beispiel wurde der Lizenzserver auf einem separaten Server installiert, entsprechend wird deren IP-Adresse eingetragen.<br>
[[File:Anzeige im Lizenzmanager.png|border|Display in the license manager]] <br>
[[Datei:Bereitstellung konfigurieren.png|border|Bereitstellung konfigurieren]]<br>
<br>
If a “per device” RDS CAL is displayed here, please contact our support. <br>
<br>
8. After importing, two adjustments must be made, otherwise the license server will stop functioning after the grace period of 120 days.<br>
[[File:Lizenzierungsmodus konfigurieren.png|border|120 days grace period - Missing configuration]]<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.