RemoteApp change remote computer name.
I am setting up a 2016 RDS server hosting a few apps and want to change the "Remote computer" name from the actual server name to something more generic like rds.domain.com. I have attached a pic that shows what I want to change. I figured out where to change the Gateway server name, but not the remote computer name. Any help you can provide would be greatly appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Could this be what I am looking for? I am reluctant to use it because I don't want to mess anything up. Thoughts?
https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
EDIT: This script won't work for 2016 as some of the commands used are not available in 2016.
https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
EDIT: This script won't work for 2016 as some of the commands used are not available in 2016.
That is the primary item I was referring to when I mentioned that there are unsupported ways and those ways have side-effects. This will solve your immediate need, but it'll break other things and cause some security warnings on most cases.
And it does not fix the RDCB/collection issue I mentioned. Which is the primary mistake 2012+ RDS users don't realize since 2008 and earlier didn't use collection names.
And it does not fix the RDCB/collection issue I mentioned. Which is the primary mistake 2012+ RDS users don't realize since 2008 and earlier didn't use collection names.
ASKER
So there is no way of hiding or creating an alias for the actual server name? That seems very short sighted. I know I was able to do this in 2008.
Which is why I explicitly said this is different in 2012.
It is an architectural decision. I don't know if I'd say it is short sighted. But it is generic by design and is meant to be adaptable for 3rd parties to build on such as citrix and as cloud hosting ramps up, that is only going to increase.
It is an architectural decision. I don't know if I'd say it is short sighted. But it is generic by design and is meant to be adaptable for 3rd parties to build on such as citrix and as cloud hosting ramps up, that is only going to increase.
As for your initial concernz you shouldn't be opening RDP to the public. That's what the RD Gateway role is for. And that name *is* changeable right in the GUI. Exposing RDP directly is absolutely a bad security posture. So the reason you want I change the server name doesn't really apply in a good security stance setup, as the server would be behind RDGW and therefore wouldn't need public DNS records at all.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: 'Cliff Galiher' (https:#a42753949)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: 'Cliff Galiher' (https:#a42753949)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
ASKER