Before you start a connection, it's a good idea to look up the name of the computer you're connecting to and to make sure Remote Desktop connections are allowed through its firewall. For permission to connect, you must be on the list of users. To connect to a remote PC, that computer must be turned on, it must have a network connection, Remote Desktop must be enabled, you must have network access to the remote computer (this could be through the Internet), and you must have permission to connect. You can't connect to computers running a Home edition (like Windows 10 Home).
I did see further down some netsh commands regarding setting the certificate, but this doesn't really do anything as the port already has the certificate and it doesn't seem to matter for whatever is required to run the publish command.You can use Remote Desktop to connect to Windows 10 Pro and Enterprise, Windows 8.1 and 8 Enterprise and Pro, Windows 7 Professional, Enterprise, and Ultimate, and Windows Server versions newer than Windows Server 2008. The certificate I have in place is one that I'm already using on the same server for the connection broker and session host roles.
Publish-RDWebClientPackage -Type Production -Latest Is there any other possible way to reference and use a certificate that is already on the server? I found I can't run the last command to publish until I do the certificate import: However, we already have a certificate seeded and setup on the certificate store on the server that I want to use, but this command provides no way to reference or use said certificate by thumbprint. I am also working to automate this process with some server deployments, which I can mostly do up to the step to import the certificate, which is this command: I am working through the process to setup the Remote Desktop Web Client as documented here, which all works fine when manually working through these steps:
0 kommentar(er)
