Remote Desktop Domain Controller Guide Overview This guide is a walkthrough of necessary steps for creating domain on windows server 2012 R2.

Domain controller and Remote app Steps 1. Go to server manager -> Dashboard-> Add roles and features.

2. Add role and feature wizard will appear click next.

3. Select role based access and click next

4. Select a server from the server pool (You may have more than one server). Select your server name and click next.

5. Check the active directory domain service

6. Click add features

7. Click Next

8. Click Next

9. Click Next

10. Check Restart the destination server automatically if required and click Yes

11. Click Install

12. Installation will start and wait for a moment don’t click close.

13. After completing the installation click on Promote this server to a domain controller.

14. Active Directory Domain Services Configuration Wizard will appear ; click on Add a new forest -> type a valid root domain name (like: ourcompany.com, or anyorganization.org …etc.) -> click Next.

15. Type the Directory services Restore Mode Password (password must contains at least an uppercase, a lowercase, a number and a special symbol); then click next.

16. On DNS Options Click next

17. The NetBIOS domain name will appear the domain name. Nothing to change click next.

18. On the Folder path click next

19. On the review option click next

20. On the Prerequisites Check click Install

21. Wait for moment system will automatically restart 22. Now login with your domain controller: daaenterprises\administrator. You will see:

23. Your domain configuration is done now we will configure the remote access. 24. Go to Server Manager - > Manage (on top-right menu) -> Add Roles and Features

25. Before you begin wizard click next

26. Select installation type choose Remote Desktop Services Installation -> click Next

27. Select deployment type choose Quick Start and click Next

28. On Development scenario choose session – based desktop deployment and click Next

29. Select a server your current computer then click Next.

30. Confirm section: Click Restart the destination server automatically if required -> click Deploy.

31. On view progress, it will take some time for installation.

32. Computer will be restart automatically and complete the pending setup tasks.

33. After completing the installation you can click the URL/copy the URL in a notepad. Then click close.

34. Now go to the server network adapter properties. Either you can set IP manually or set option automatically.

35. To see the IP address of this server PC, open Command Prompt or PowerShell, type ipconfig. Keep the IPV4 Address in a notepad because for every client computer under this domain server, you must need to set the DNS manually. (my IP address is : 192.168.10.147)

36. Now go to your client PC’s network adapter setting. Set the DNS of server IP

37. Go to client pc’s Advanced System Settings (open Start and type “view advanced system settings”) -> Computer Name tab -> Change -> Type domain name (Server domain name).

When you click ok it will appear the domain (server pc) user’s username and password. After adding the client PC, restart your Client computer.

Note: For Every Client PC you must follow step 36 and 37. 38. Now open your client pc’s browser. Enter the server IP address/rdweb then click continue to this this website.

39. Type user name and password of the server pc

40. All the publish applications will appear (I have only one application. We will change the publish settings)

41. Click on the paint application a popup window will appear, click connect.

42. For the first time it will again show the user credential.

43. Wait for a second paint application will run from the server PC.

44. As you can see the deployment is missing a RD Gateway server and a RD Licensing server. In Server Manager click Remote Desktop Services and scroll down to the overview. As you can see the deployment is missing a RD Gateway server and a RD Licensing server. Click the Add RD Licensing server button (big green ‘+’ plus button).

45. Under the server pool list there will be the domain controller name. Click the domain controller and click the Add button (). Click Next.

46.

In ‘Confirm selections’ step click add and wait for installation.

47. Click close

48. Click the Add RD Gateway server button.

49. Under the server pool list there will be the local server name. Click the add button and click next.

50. Name the self-signed SSL certificate-step will come. This is a very sensitive point whenever you will give a name to the certificate. In fact, with original OS a demo certificate comes. However we will have to buy a trusted certificate from Go-Daddy.com or from some other 3 rd party vendors. Till then we will have to use self-signed certificate. In case of naming the certificate, please remember to include your FQDN. For example if your domain name is SOMEDOMAIN.com, you will have to name the certificate like ‘SOMEDOMAIN.com-it.cl’. Do not name the certificate from web tutorial. Click next.

51. ‘Confirm selections’ – step will come. Click the add button.

52. Click close

53. Click on TASKS -> Select Edit Deployment Properties as shown below:

54. Go To RD licensing tab and choose Per User

55. Go to Certificates tab – click create new certificates. 56. Notice that the certificate level currently has a status of Not Configured. As you can see, certificates are used for different goals within the deployment. The RD Gateway certificate is used for Client to gateway communication and needs to be trusted by the clients. Either install the self-signed certificate on all clients, or use a certificate for which the complete certificate chain is already trusted by all clients.

Here we will create one certificate and apply for all of them. Remember about certificate naming convention discussed earlier. Select “RD Connection Broker – Enable Single Sign On” and click Create New Certificate button. Name the certificate and save it. Password: asd123

57. Click Apply button to apply that certificate and make it available for other three role services.

This password will be used for certificate export from server PC and import to client PC For the other three roles – select each item and click Select Existing Certificate. Browse the certificate you saved earlier.

Click apply and wait. The Level will be untrusted and the status will be ok. This configuration will work for our purpose. There will be some warning issues. However, when we purchase a certificate from 3 rd party vendor these issues will be solved. When all are done click ok. Don’t worry if you see RD Gateway is giving an error warning.

58. Now we will Import the self-sign certificate from server. Open PowerShell -> Type mmc-> File>Add Remove Snap In:

59. Select certificate and click add.

60. Select My Computer and click next.

61. Click Finish

62. Click ok.

63. Expand Certificates -> Trusted Root Certificate-> Certificate. Right Click-> All Tasks->Import…

64. Certificate Import wizard will appear click next

65. Brows the self-sign created certificate and click open.

66. Click Next

67. Enter the password which we give during self-sign created password asd123 and click next.

68. Click Next

You imported certificate will appear in to the certificate list.

69. Now we will export this certificate for client PC. Right click -> all task -> Export

70. Certificate export wizard will appear click next.

71. Give Certificate name

72. Now copy this certificate in to client PC

73. Now we will import the certificate into client PC. GO to mmc

Same as server import

Brows the certificate from desktop.

This certificate will appear in to the certificate list

Now if you browse the URL from client PC you will see the publisher name without warning.