If you have decided to change the behavior of Configuration Manager 2007 native mode clients for HTTP communication for roaming and site assignment, follow these procedures to enable or disable this option for a native mode site.

The default setting for a native mode site is that this option is not enabled. To verify this setting for individual clients, see How to Identify Client Configuration Details for Native Mode and Internet-Based Client Management and the Https State Flags value.

There are two supported procedures you can use for this configuration. Choose the procedure that is suitable for your environment. The two procedures are as follows:

• Configure the option as a site property. Client computers that can access site properties published to Active Directory Domain Services will be automatically configured with this option on a periodic basis (including at site assignment time, every time the client starts, and every 25 hours). Clients installed using the client push installation method will be configured with the option at installation time only.
  
  For installed clients to be configured with the setting using Active Directory Domain Services, the following conditions must all apply:
  
  
  • Active Directory Domain Services must be extended with the Configuration Manager 2007 schema extensions
    
    
  • The site must be publishing to Active Directory Domain Services
    
    
  • Clients must be on the intranet
    
    
  • Clients must be from the same Active Directory forest as the site server's forest
    
    
• Specify the settings using CCMSetup.exe command line options. You can use CCMSetup options when the client is first installed, or supplied as a script to run after installation, which will reinstall the client with the new configuration. If the client is already installed, you can use the software distribution feature to send the CCMSetup commands to the client, or use a Configuration Manager 2007 task sequence to achieve this.
  
  

  Note
  If the settings supplied with CCMSetup conflict with those published to Active Directory Domain Services, and clients can access the settings in the Active Directory Domain Services, the settings from Active Directory Domain Services will take precedence and the settings specified with CCMSetup will not be used.

Additionally, you can also specify the settings using your in-house client management tools, which might include incorporating the settings in a standard build image and deploying custom scripts to edit the registry.

To configure HTTP communication for roaming and site assignment by configuring the setting as a site property:

To enable HTTP communication for roaming and site assignment by specifying the setting using CCMSetup.exe command line options:

See Also

---

To contact the documentation team, e-mail SMSdocs@microsoft.com.