Information Technology Reference
In-Depth Information
from a distribution point. After the installation program is complete, the client contacts the
management point to register itself and obtains its site assignment. It then reports the state
of the installation. If the client cannot contact the management point, all the client compo-
nents will show as Installed instead of Enabled or Disabled.
The client software follows several methods to locate the management point and uses the
methods in the following order:
1.
Setup parameters
As part of the installation command, you can specify a manage-
ment point.
2. AD DS The client software will query AD DS for an appropriate management point.
3. Domain Name System (DNS) The client will search for a service (SRV) resource
record type for a management point. To find the right SRV record in DNS, you must
configure clients with their site code.
4. Windows Internet Naming Service (WINS) A management point will update its
WINS record with appropriate information automatically. If a client is a WINS client,
WINS is the last resource the client software uses to locate a management point.
Automatic client assignment is determined using boundaries that are members of a
boundary group, where that boundary group has automatic assignment enabled. In previous
versions of Configuration Manager, automatic site assignment would fail, and Configuration
Manager would not manage clients if they fell outside all boundaries. With System Center
2012 Configuration Manager, you can configure a fallback site for client assignment at the
hierarchy level. If you install a client that is outside any of the configured boundary groups,
the automatic site assignment process will use this site, and the installation process will com-
plete successfully.
Fallback status point
The fallback status point is an optional site system that you can use during the client instal-
lation process. A fallback status point monitors client deployment and identifies unmanaged
clients because unmanaged clients cannot communicate with a management point. The fall-
back status point relies on unauthenticated connections from clients over HTTP. You should
use a dedicated system for the fallback status point so that if a site system is not available,
the client can contact the fallback status point to report the error. You cannot configure the
fallback status point as a highly available role.
The reports that the Configuration Manager client software produces use data sent by
clients through the fallback status point. Mobile devices that are enrolled by Configuration
Manager and mobile devices that are managed by using the Exchange Server connector do
not use a fallback status point.
 
Search WWH ::




Custom Search