Примеры использования Trusted root key на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
To remove the trusted root key.
Trusted root key management is not required.
Describes how to verify the trusted root key.
Removes the trusted root key for the Configuration Manager 2007 client.
Describes how to remove the trusted root key.
The trusted root key is stored in the client registry and can be set using Group Policy or configured manually.
Describes the procedure to remove the trusted root key.
Describes the procedure to place the trusted root key on the client computer during installation.
If the central site server needs to be recovered,it will generate a new trusted root key.
What should you do if your trusted root key is compromised?
If you reinstall and restore the central site server,you will generate a new trusted root key.
Describes the procedure to view the trusted root key configured in the client computer's WMI repository.
Because a client in another site trusts the management point,it will accept the new trusted root key.
Use the following procedure to remove the trusted root key from a Configuration Manager 2007 client.
At this point,the management point has several keys used in the trusted root key process.
In a single site hierarchy that requires trusted root key authentication, always use a separate management point.
If the clients cannot query Active Directory Domain Services to verify trusted management points,the clients use the trusted root key.
Describes how to preprovision the trusted root key on clients.
The trusted root key provides a mechanism for clients to verify the authenticity of the management point and its certificate if they cannot query Active Directory Domain Services.
If clients cannot query Active Directory, manage the trusted root key provisioning process.
Without the trusted root key, the client has no way to verify that the management point is a trusted management point for the site, allowing a skilled attacker to direct the client to a rogue management point.
If clients can query Active Directory Domain Services,they do not rely on the trusted root key so compromise does not pose serious risk.
If you suspect that your trusted root key is compromised, you should monitor the site audit client status messages for indications of unauthorized site activity such as unrecognized packages running.
If its site server is not the central site, the certificate is passed up through the hierarchy until it arrives at the central site where the trusted root key is kept.
Running in native mode requires a PKI-issued certificate for the management point,so trusted root key compromise is less risky in native mode than in mixed mode.
In the case of a system failure on the site server, a new trusted root key is created during site server recovery and the management point receives a new certificate, either by creating a self-signed certificate for mixed mode or by getting a new PKI-issued certificate for native mode.
If you restructure your site hierarchy so that a child site is promoted to be the new central site,Configuration Manager 2007 creates a new trusted root key for the hierarchy.
The central site server signs the management point's certificate with the private trusted root key and sends it back down through the hierarchy to the management point, along with a copy of the public trusted root key.
This would likely be the action of a sophisticated attacker andcould occur only within a limited time before the client retrieves the trusted root key from a valid management point.
Ensure that the Configuration Manager clients get an authorized copy of the trusted root key upon installationIf you have not extended the ActiveDirectory schema,clients rely on the trusted root key to authenticate valid management points.