When using a Custom Web Site with System Center Configuration Manager 2007 SP1 or SP2 and manually installing Secondary Sites, the Secondary Site installation may not update the following properties in the Sitectrl.ct0 file on the Secondary Site:
PROPERTY <IISWebSiteName><SMSWEB><><1>
This property has no entry for the website name on the affected sites: PROPERTY <IISWebSiteName><><><1>
PROPERTY <DisabledPortList>< #Client Requests-HTTP (TCP) #1 #0 # #False #False #Client Requests-HTTPS (TCP) #3 #0 # #False #False><><0>
The DisabledPortList property is missing all together on the affected sites.
When this issue occurs, all roles with IIS functionality have their respective Virtual Directories created under the SMSWEB website as expected except for the Distribution Point. When you deploy the first package to the DP on one of the affected Secondary Sites, the Virtual Directories get created under the Default Website instead of the SMSWEB Custom Web Site as expected.
Also, in some instances the custom ports that are configured for the custom web site get bound to the Default Web Site as well, causing the site to not start. This can also cause the Management Point to not function.
PROPERTY <IISWebSiteName><SMSWEB><><1>
This property has no entry for the website name on the affected sites: PROPERTY <IISWebSiteName><><><1>
PROPERTY <DisabledPortList>< #Client Requests-HTTP (TCP) #1 #0 # #False #False #Client Requests-HTTPS (TCP) #3 #0 # #False #False><><0>
The DisabledPortList property is missing all together on the affected sites.
When this issue occurs, all roles with IIS functionality have their respective Virtual Directories created under the SMSWEB website as expected except for the Distribution Point. When you deploy the first package to the DP on one of the affected Secondary Sites, the Virtual Directories get created under the Default Website instead of the SMSWEB Custom Web Site as expected.
Also, in some instances the custom ports that are configured for the custom web site get bound to the Default Web Site as well, causing the site to not start. This can also cause the Management Point to not function.