Примеры использования Default management point на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
Failed to discover default management point.
The default management point used to download content for the client installation.
Ensure that the client's default management point is operational.
If necessary, the client downloads the configuration data from the site's default management point.
It locates its default management point for the Toronto site.
Helps you determine if you should publish the default management point to DNS.
Make sure that a default management point is configured for the site.
Publish identity data to DNS(corresponds to Publish the default management point in DNS(intranet only)).
The client's default management point provides the client with a list of distribution points from the Sydney site(SYD).
Configure the site system that holds the default management point role with an FQDN.
The client's default management point provides the client with a list of distribution points from the Houston site(HOU).
Until you reconfigure the NLB management point with an FQDN, clients will be unable to contact their default management point and will be unmanaged.
They will locate the site's default management point using DNS publishing.
The default management point in Houston provides the client with a list of distribution points in Sydney(SYD) if the content is hosted there.
A new computer connects to the default management point during operating system deployment.
A client is considered unmanaged when it is installed but not assigned to a site, or is assigned to a site butcannot communicate with that site's default management point.
It continues to communicate with its own default management point in Houston(HOU) for these operations.
If the default management point is configured as an NLB and configured to access the site database directly, it will cause degraded site server performance.
Configuring an FQDN is also recommended if this site system will host the default management point that will publish to Domain Name System(DNS).
Displays the DNS suffix of the default management point, which is required if Configuration Manager is publishing the default management point to DNS.
This data flow displays the process by which Configuration Manager 2007 clients locate their default management point, when their assigned site is operating in mixed mode.
You cannot create more than one default management point for the site, but you can use a computer with RAID, or other fault tolerant features.
However, this can result in other clients also installing this content when they are roaming to another site if they fall back to asking their default management point for content.
A Configuration Manager2007 site can have only one default management point that intranet-based clients will use to communicate with the site server.
By default, if Configuration Manager 2007 finds more than one valid client for this communication,it will not attempt to communicate with its default management point and will be unmanaged.
If the content is not hosted in Sydney, the default management point provides the client with a list of distribution points from the Houston site(HOU).
Updated SPN requirements when configuring the management point component to use a network load balancing(NLB)cluster virtual server as the default management point for a Configuration Manager 2007 site.
The client successfully assigns,finds its default management point in Toronto(TOR), and then reads site settings from Active Directory Domain Services.
If the content is not hosted in Melbourne, the default management point provides the client with a list of distribution points from the Houston site(HOU).
If that attempt fails,the client locates the default management point for the site using WINS and then asks thedefault management point for the list of management points. .