In order to get Remote Desktop ready for CAL installation on a stand-alone server, the following will need to be done.
This process requires some time, and following the below steps. Note that a few reboots are required for software installations to be completed.
Installation of Active Directory
First, you will need to add the role, for Active Directory, Domain Services. You can open the "Add Roles and Features Wizard", from the Server Manager window, under the "Manage" section
Once you're in there, you will need to select a "Role-based" installation type, and click next.
On the next page, "Server Selection", click Next.
In Server Roles, you will select "Active Directory Domain Services", and then click next
On the next page, "Features", click Next.
On the next page, "AD DS", click Next.
On the next page, "Confirmation", Check the box next to "Restart the destination server automatically ...", and then click Install.
In many cases, it won't need a reboot at that stage, but once it's completed, the Server Manager will show the below icon, and request you to promote the server to a domain controller. Click the Promote message, and it will take you to the next step.
Configuration of Active directory, and a new "Forest"
Now that the Active Directory services are installed, you will need to create a new forest. Generally, you can do this based on your domain name, which is assigned to each order.
For example; sau-abc12-or.servercontrol.com.au
You will now choose Add a new forest, and choose the root domain name. Then click Next
On the next page, you will need to generate a DSRM password. This can be of your choosing, but store it somewhere safe, as you may need it in future. Once chosen, click next.
On the next page "DNS Options", click Next.
On the "Additional Options" page, you can choose your NETBIOS name, this will be required before the username in some instances. eg, SAUABC12OR\username when logging in from legacy machines. When you're happy with it, click next.
On the next page "Paths", click Next.
On the next page "Review Options", click Next.
On the next page "Prerequisites Check", wait for it to finish it's checks, then click Install. Usually, there's no major issues on that page, for a fresh server. The server will reboot as it configures the domain controller.
The install will complete after a few minutes, and then reboot. Once it's back online, we can start remote desktop services installation.
Installation of Remote Desktop Services, and Licensing Manager
Now that Active Directory installation is working, we want to install the Remote Desktop services role (this is done separately after Active Directory, to avoid some bugs which have occurred in the past).
Navigate to the Roles and features wizard before, but on Server Roles, select Remote Desktop Services, and click Next.
On the next page "Features", click Next.
On the next page, "Remote Desktop Services", click Next.
On the next page, Role Services, we need to select "Connection Broker", "Licensing", and "Session Host", then click Next.
On the next page "Confirmation", select the "Restart the destination server automatically ..." option, and click Install.
Once the server has completed rebooting, you will now need to go back into the Add Roles and Feature Wizard, and select "Remote Desktop Services Installation", then click Next.
On the next page, "Deployment Type", click "Quick Start".
On the next page, "Deployment Scenario", select "Session Based desktop deplyoment", and click Next.
On the next page "Server Selection", click Next.
On the next page "Confirmation", select the "Restart the destination server automatically ..." option, and click Deploy.
Once the server reboots, you can log back in, and proceed to the final step, of configuring the Session collective.
Configuration of default Session Collective for Licensing
After the service is ready, you can simply go into the Server Manager again, and open the "Remote Desktop Services" section.
If this stage hangs attempting to connect to RDP broker, then check that IPv6 is disabled on the Primary interface; otherwise, it may receive an APIPA IPv6 address, and attempt to connect giving IPv6 precedence.
Once in that section, click on "Collections", then click on "Tasks" on the top right of the page, and select "Edit Deployment Properties".
On the RD Licensing Section, Change the licensing Mode to Per User, and enter "localhost", into the "Specify a License Server" section, and click Add.
Once that's done, you can click OK to apply changes, and the setup is ready to be licensed!