In the environment I tested today, there's a https://srv01/RDWeb portal where users can login with domain creds to get access to published apps. The RelayKing output identifies this server as being an ADCS server and the relaytargets.txt reports a whole done of extra URLs that make the system appear as if it's a mail server - /ews and /owa etc - among other URLs. None of these URLs/services actually exist.
I wonder if this is a logic flaw - like if RelayKing is checking its defined list of URLs and getting a login/password pop-up for many of them, and thus thinks these services are running on the box?
In the environment I tested today, there's a https://srv01/RDWeb portal where users can login with domain creds to get access to published apps. The RelayKing output identifies this server as being an ADCS server and the
relaytargets.txtreports a whole done of extra URLs that make the system appear as if it's a mail server -/ewsand/owaetc - among other URLs. None of these URLs/services actually exist.I wonder if this is a logic flaw - like if RelayKing is checking its defined list of URLs and getting a login/password pop-up for many of them, and thus thinks these services are running on the box?