![]() ![]() You have now successfully configured the RD Gateway. This is what you want for any real-world setup. It would look more like what you see here. ![]() Had a certificate from a Public CA or my own CA been issued and used. This once again is because it isĪ self-signed certificate and should not be used in production. You must allow the certificate to be added to the destination clients Trusted stores.Īs you can see I have applied the cert to both Roles here and it is Untrusted. Not necessary here but a good idea if you back up On the hard drive where we can import it to other machines. Pick the certificate name, which needs to match the external FQDN of the server. Since we do not have a purchased certificate or a CA of our own, we will click Create new certificate… Here it is possible to run in to some issues if using self-signed certificates Since all roles are installed on a single server in this deployment, we need to be sure to use the same certificateįor Web Access and Gateway. Our concern now is specifying a certificate. Next click on Tasksand click Edit Deployment Properties.įrom here we can edit many of the deployment settings. ![]() Purposes we will navigate to those settings an alternate way to show you how to get it to it in the future should you ever need ![]() If you click "Configure certificate" you will be able to configure each roles needed certificate, however for informational The information at the bottom lets us know the deployment was successful however a certificate needs to be configured. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |