Examples of using Same active directory forest in English and their translations into Russian
{-}
-
Official
-
Colloquial
Clients belong to the same Active Directory forest.
Specifies that the site server andSystem Health Validator points for this site are not in the same Active Directory forest.
The site system is in the same Active Directory forest as the site server.
Explains the special configurations required if all your site servers andSystem Health Validators do not reside in the same Active Directory forest.
Clients must be from the same Active Directory forest as the site server's forest. .
Cannot support workgroup computers,computers from another Active Directory forest, or computers from the same Active Directory forest but using a noncontiguous namespace.
Clients do not belong to same Active Directory forest as the site server's forest. .
Supported on workgroup computers, computers from another Active Directory forest, and computers in the same Active Directory forest but using a noncontiguous namespace.
If your test lab uses the same Active Directory forest as your production network, then do not use the same site codes in your test lab as you do in production.
The site must be publishing to Active Directory Domain Services, and clients are in the same Active Directory forest as the site server's forest.
If the client belongs to the same Active Directory forest as the site server's forest, the site's fallback status point will be automatically assigned during client installation.
Lists four different scenarios for when all the System Health Validator points do not reside in the same Active Directory forest as the site servers, with configuration steps for each scenario.
Additionally, clients that are not in the same Active Directory forest as the site servers(such as workgroup clients or clients from a different Active Directory forest) are not be able to locate the site information they require from Active Directory Domain Services.
If you do not specify a health state reference publishing account, the site server computer account is used,which is appropriate if the site server resides in the same Active Directory forest as the health state reference.
So if your site servers andSystem Health Validator points are not in the same Active Directory forest, you must designate the Active Directory forest and domain that will store the health state references.
If you have extended the Active Directory schema for SMS2003 but not for Configuration Manager 2007,clients can automatically find a server locator point through Active Directory publishing if they are in the same Active Directory forest as the site server.
When the site server andSystem Health Validators are not in the same Active Directory forest, you must designate which Active Directory forest and which domain will be used to store and retrieve the NAP health state reference.
Helps you decide which Active Directory forest will publish the health state references required by the System Health Validator point when your System Health Validator points are not in the same Active Directory forest as your site servers.
When the Configuration Manager2007 site server and System Health Validator points reside in the same Active Directory forest, the Configuration Manager NAP health state reference is located in the same Active Directory forest and the default settings can be used.
If your Microsoft System Center Configuration Manager 2007 site servers andSystem Health Validator points are not in the same Active Directory forest, you must designate the Active Directory forest and domain that will store the health state references, and you must specify an account to use when publishing the health state references to Active Directory Domain Services.
If your site servers andMicrosoft System Center Configuration Manager 2007 System Health Validator points are not in the same Active Directory forest, you must designate the Active Directory forest and domain that will store the health state references, and you must specify an account to use when publishing the health state references to Active Directory Domain Services.
If you do not specify a health state reference querying account, the computer account of the System Health Validator is used,which is appropriate if the System Health Validator point resides in the same Active Directory forest as the health state reference location, or if you are using a designated Active Directory forest and a trust exists between the domains that contain the System Health Validator points and the domain that contains the health state references.
When you have more than one Active Directory forest, and your Configuration Manager site servers and System Health Validator points are not in the same forest, you must designate which forest and domain will store the health state references.
If your Microsoft System Center Configuration Manager 2007 site servers andSystem Health Validator points are not in the same Active Directory Domain Services forest, you must designate the Active Directory forest and domain that will store the health state references, and you must specify an account to use when System Health Validator points read health state references from Active Directory Domain Services.
If an SCP already occurs in the Active Directory forest for which you are installing AD RMS, make sure that the cluster URL in the SCP is the same as the cluster URL for the new installation.
This requires that the Active Directory schema is extendedfor Configuration Manager 2007, that all sites are publishing to Active Directory Domain Services, and the client belongs to the same forest.
If you have extended Active Directory Domain Services and enabled publishing for Configuration Manager, clients in the same forest as the site server can retrieve the public copy of the trusted root key by querying the Global Catalog server.
AD RMS also requires a database, such as Microsoft SQL Server, which can be run either on the same server as AD RMS or on a remote server, and an Active Directory Domain Services forest.
You can also use the same setof logon credentials and the same instance of Active Directory Administrative Center to view or manage Active Directory objects in any other domain(that belongs or does not belong to the same forest as the local domain) as long as it has an established trust with the local domain.
Regional roaming capability refers to the roaming behavior of clients when global roaming is not possible because the Active Directory schema has not been extended for Configuration Manager 2007, or it has been extended but not all sites are publishing to Active Directory Domain Services, or the client doesn't belong to the same forest(for example, is a workgroup client).