To use custom ports you need to create a new website named SMSWEB and assign which port use.
Then go to Administration workspace and select site properties.
Go to the tab labeled ports. In the lower left corner check the checkbox [Use custom web site]
It will warn you that the custom web site has to be created prior to doing this or your clients will not be able to communicate!

That was the short version ūüôā
For the long one click either the links pointing to TechNet or read the snip it from the same links.

TechNet links:
Planning for custom websites –¬†
How to Configure Client Communication Port Numbers –¬†

##### Snip it from TechNet #####

Planning for Custom Websites in Configuration Manager

Configuration Manager site system roles that require Microsoft Internet Information Services (IIS) also require a website to host the site system services. By default, case site systems use the IIS website named Default Web Site on a site system server. However, mind you can use a custom website that has the name of SMSWEB. This option might be appropriate if you must run other web applications on the same server and their settings are either incompatible with Configuration Manager, or you want the additional resilience of using a separate website. In this scenario, these other applications continue to use the default IIS website, and Configuration Manager operations use the custom website.

When you run other applications on a Configuration Manager site system, you increase the attack surface on that site system. As a security best practice, dedicate a server for the Configuration Manager site systems that require IIS.


You can use custom websites on all primary sites. When you use a custom website at a site, all client communications within the site are directed to use the custom website named SMSWEB on each site system instead of the default website on IIS. Additionally, site system roles that use IIS but do not accept client connections, such as the reporting services point, also use the SMSWEB website instead of the default website. For more information about which site systems require IIS, see Supported Configurations for Configuration Manager.

Before you configure a Configuration Manager site to use a custom website, you must manually create the custom website in IIS on each site system server that requires Internet Information Services (IIS) at that site. Because secondary sites are automatically configured to use a custom website when you enable this option on the parent site, you must also create a custom website in IIS on each secondary site system server that requires IIS.

If you enable custom websites for one site, consider using custom websites for all sites in your hierarchy to ensure that clients can successfully roam within the hierarchy.

When you select or clear the check box to use a custom website for a site, the following site system roles that are installed on each site system server in the site are automatically uninstall and reinstalled:

  • Management point
  • Distribution point
  • Software update point
  • Fallback status point
  • State migration point


The following Configuration Manager site system roles require IIS and use the default or custom website on the site system server:

  • Application Catalog web service point
  • Application Catalog website point
  • Distribution point
  • Enrollment point
  • Enrollment proxy point
  • Fallback status point
  • Management point
  • Software update point
  • State migration point

When you create a custom website, you must assign port numbers to the custom website that differ from the port numbers that the default website uses. The default website and the custom website cannot run at the same time if both sites are configured to use the same TCP/IP ports.

After the site system roles are reinstalled, verify that the TCP/IP ports configured in IIS for the custom website match the client request ports for the site.

For information about how to configure ports for client communication, see How to Configure Client Communication Port Numbers in Configuration Manager.


To use a custom website for a site, you must perform the following actions before you enable the option to use a custom website in Configuration Manager:

  • Create the custom web site in IIS for each site system server that requires IIS in the primary site and any child secondary sites.
  • Name the custom website¬†SMSWEB.
  • Configure the custom website to respond to the same port that you configure for Configuration Manager client communication.
When you change from using the default website and use a custom website, Configuration Manager adds the client request ports that are configured on the default website to the custom website. Configuration Manager does not remove these ports from the default website, and the ports are listed for both the default and custom website. IIS cannot start both websites when they are configured to operate on the same TCP/IP ports, and clients cannot contact the management point.


Use the information in the following procedures to help you configure the custom websites in IIS.

The following procedures are for Internet Information Services (IIS) 7.0 on Windows Server 2008 R2. If you cannot use these procedures because your server has a different operating system version, refer to the IIS documentation for your operating system version.


  1. On the computer that runs the Configuration Manager site system, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the Internet Information Services (IIS) Manager console, in the Connections pane, right-click the Sites node to select Add Web Site.
  3. In the Add Web Site dialog box, enter SMSWEB in the Site name box.
    SMSWEB is the required name for Configuration Manager custom websites.


  4. In the Physical path box, specify the physical path to use for the website folder.
  5. Specify the protocol and custom port for this website.
    • After you create the website, you can edit it to add additional website bindings for additional protocols.
    • When you configure the¬†HTTPS¬†protocol, you must specify a¬†SSL certificate¬†before you can save the configuration.
  6. Click OK to create the custom website.


How to Configure Client Communication Port Numbers in Configuration Manager

You can change the request port numbers that System Center 2012 Configuration Manager clients use to communicate with site systems that use HTTP and HTTPS for communication. For Configuration Manager SP1 only, you can also specify a client notification port if you do not want to use HTTP or HTTPS. Although HTTP or HTTPS is more likely to be already configured for firewalls, client notification that uses HTTP or HTTPS requires more CPU usage and memory on the management point computer than if you use a custom port number. For all versions of Configuration Manager, you can also specify the site port number to use if you wake up clients by using traditional wake-up packets.

When you specify HTTP and HTTPS request ports, you can specify both a default port number and an alternative port number. Clients automatically try the alternative port after communication fails with the default port. You can specify settings for HTTP and HTTPS data communication.

The default values for client request ports are 80 for HTTP traffic and 443 for HTTPS traffic. Change them only if you do not want to use these default values. A typical scenario for using custom ports is when you use a custom website in IIS rather than the default website. If you change the default port numbers for the default website in IIS and other applications also use the default website, they are likely to fail.


Do not change the port numbers in Configuration Manager without understanding the consequences. Examples:

  • If you change the port numbers for the client request services as a site configuration and existing clients are not reconfigured to use the new port numbers, these clients will become unmanaged.
  • Before you configure a non-default port number, make sure that firewalls and all intervening network devices can support this configuration and reconfigure them as necessary. If you will manage clients on the Internet and change the default HTTPS port number of 443, routers and firewalls on the Internet might block this communication.


To make sure that clients do not become unmanaged after you change the request port numbers, clients must be configured to use the new request port numbers. When you change the request ports on a primary site, any attached secondary sites automatically inherit the same port configuration. Use the procedure in this topic to configure the request ports on the primary site.

For Configuration Manager SP1 only:For information about how to configure the request ports for clients on computers that run Linux and UNIX, see Configure Request Ports for the Client for Linux and UNIX.


When the Configuration Manager site is published to Active Directory Domain Services, new and existing clients that can access this information will automatically be configured with their site port settings and you do not need to take further action. Clients that cannot access this information published to Active Directory Domain Services include workgroup clients, clients from another Active Directory forest, clients that are configured for Internet-only, and clients that are currently on the Internet. If you change the default port numbers after these clients have been installed, reinstall them and install any new clients by using one of the following methods:

To reconfigure the port numbers for existing clients, you can also use the script PORTSWITCH.VBS that is provided with the installation media in the SMSSETUPToolsPortConfiguration folder.

For existing and new clients that are currently on the Internet, you must configure the non-default port numbers by using the CCMSetup.exe client.msi properties of CCMHTTPPORT and CCMHTTPSPORT.


After changing the request ports on the site, new clients that are installed by using the site-wide client push installation method will be automatically configured with the current port numbers for the site.

  1. In the Configuration Manager console, click Administration.
  2. In the Administration workspace, expand Site Configuration, click Sites, and select the primary site to configure.
  3. On the Home tab, click Properties, and then click the Ports tab.
  4. Select any of the items and click the Properties icon to display the Port Detail dialog box.
  5. In the Port Detail dialog box, specify the port number and description for the item, and then click OK.
  6. Select Use custom web site if you will use the custom website name of SMSWeb for site systems that run IIS.
  7. Click OK to close the properties dialog box for the site.

Repeat this procedure for all primary sites in the hierarchy.


Leave a Reply