Custom port settings are not added to boot media in System Center Configuration Manager

Applies to: Microsoft System Center 2012 R2 Configuration ManagerSystem Center Configuration Manager (current branch)


Boot media that is created at a central administration site (CAS) server in a Microsoft System Center Configuration Manager 2012 or later versions hierarchy will not contain the custom client communication port numbers of a child site. This occurs with dynamic or site-based media. However, this occurs only when the media is created on a site that has port numbers that are different from the port numbers of the site on which the client will be deployed. 

Errors that resemble the following will be recorded in the Smsts.log file on the destination computer. Notice that the port reference will continue to read ":80" instead of the custom port that was previously defined for the site.
CLibSMSMessageWinHttpTransport::Send: URL:  GET /SMS_MP/.sms_aut?MPLOCATION&ir=

Error. Status code 404 returned

Boot media contains custom port information only for the site at which the media was created. For a site that has different port settings, client computers will not connect to the management point for that site. Media that is created at a stand-alone site is not affected and contains custom port information.

More Information

For more information about how to customize client port settings and boot images, see the following Microsoft TechNet articles: