PUBLISH NEW APPLICATION WIZARD WINDOWS
Windows Certificate Services – Setting up a CRL In this example that’s what I am doing, this means that all my remote clients need the root certificate installing on them, so for production I suggest you purchase a publicly signed wildcard certificate for simplicity.ĭNS Requirements: For your internal domain and the DMZ it’s simple enough but your external clients will need to be able to resolve your public URL (and the URL of your CRL is used).Ĭertificate Services ( Optional): If you want to deploy self signed wildcard certificates you will need a PKI environment and a published CRL. Here is the topology that I’m going to deploy įirewall Rules: You will see I’ve labelled all the Certificate/CRL rules as optional, this is because you would only need them if you were using self signed certificates. Topology: Simply getting your ‘ducks in a row’ will take a lot longer than actually deploying the service. I’ll be using Active Directory Federation Services, (you don’t have to, but it’s more secure than simply using ‘pass-though’ security). Getting this article to completion has been a bit of a journey! This is the final post that will stitch together all the others I’ve posted over the last couple of weeks, that will enable you to publish your RemoteApps with ‘Remote Desktop Web Access’, and have that service presented securely from your DMZ.
0 kommentar(er)
