When the Configuration Manager 2007 hierarchy contains sites that are configured for different site modes, roaming between these sites is supported with the following behavior.
A client from a mixed-mode site roams into a site configured for native mode:
- The client continues to communicate with its
default management point over HTTP, and will not communicate with
the resident management point.
- The client will not download content from
distribution points in the native mode site, but it will download
content from its own site using HTTP.
A client from a native mode site roams into a site configured for mixed mode:
- The client continues to communicate with its
default management point over HTTPS.
- If the native mode client is not enabled for
HTTP communication for roaming and site assignment, the client will
not communicate with the mixed-mode resident management point or
download content from distribution points in the mixed-mode site.
Instead, it will communicate only with its assigned management
point and download content from its own site using HTTPS. This is a
more secure solution, but it might result in content retrieval over
a remote link.
- If the client's site is enabled for HTTP
communication for roaming and site assignment, the client will
communicate with the mixed-mode resident management point and
download available content from distribution points in the
mixed-mode site, using HTTP. This is a less secure solution, but it
minimizes data being sent over a remote link.