In a production environment, implementing Internet-based client management will require interaction and collaboration with a number of different groups across the enterprise. For example, these groups might include the following:

Extending the schema for Configuration Manager is not a requirement for Internet-based client management. However, when you have clients that will be managed on both the intranet and the Internet, it is much easier to configure native mode clients on the intranet when Configuration Manager is publishing to Active Directory Domain Services.

Because implementing a site to support Internet-based client involves so many roles, it is critical that you identify early who is responsible for the various roles, and work with them to incorporate their requirements and their processes.

For example, if updating public DNS servers can take a month, initiate this request early enough so that it's completed when you are ready to configure clients for their Internet-based site, rather than leaving it until the day before on the assumption that it will be completed quickly.

A successful ongoing implementation will depend on identifying and adhering to processes that coordinate the various functions between the roles.

Some of the potential consequences of not having and following defined processes when implementing Internet-based client management in a production environment are as follows:

Use a methodology such as ITIL or Microsoft Operations Framework ( to help you implement Internet-based client management within a framework of defined processes. Make sure you document your design, testing procedures, the areas of responsibility, and the processes to follow for configuration and troubleshooting, and then disseminate this information, making sure that it is centrally available and updated.

Review existing company security policies and, if necessary, modify them to include the implementation of Internet-based client management.

See Also