MECM alternate HTTPS port for Distribution Point

Marcus Wahlstam 21 Reputation points
2021-05-27T11:58:19.587+00:00

If you look at this table of ports used by ConfigMgr Client to access a HTTPS enabled distribution point, it states that port 443 is used. But there is also a note that says an alternate port is available. And if you read the details for the note it says "You can define an alternate port in Configuration Manager for this value." But I have not found any information on how you are supposed to define this alternate port.
In the registry I can find this value: HKLM\SOFTWARE\Microsoft\SMS\DP\HttpsPort, but I suppose it's not as easy as just define another port here and change the bindings in IIS?
Does anyone know how to define a custom HTTPS port for a Distribution Point?
The reason I'm asking is that the server that holds the DP role also serves an application that listens to port 443, and we would like to enable HTTPS in the ConfigMgr environment.

Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. Jason Sandys 31,161 Reputation points Microsoft Employee
    2021-05-27T14:36:40.307+00:00

    See https://learn.microsoft.com/en-us/mem/configmgr/core/clients/deploy/configure-client-communication-ports

    The reason I'm asking is that the server that holds the DP role also serves an application that listens to port 443, and we would like to enable HTTPS in the ConfigMgr environment.

    Honestly, I would suggest using a different server then. This will most likely cause you pain in the future. And, keep in mind this doesn't change the port just for DP traffic but all client to client-facing role traffic.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful