mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 18:33:43 +00:00
fix broken links from 6/19 RUN ID 92f59a3d-bdfc-483c-9281-d7f370b7d945
This commit is contained in:
@ -129,7 +129,7 @@ For information about EAP settings, see <https://technet.microsoft.com/library/h
|
|||||||
|
|
||||||
For information about generating an EAP XML, see the EAP configuration article.
|
For information about generating an EAP XML, see the EAP configuration article.
|
||||||
|
|
||||||
For more information about extended key usage (EKU), see <http://tools.ietf.org/html/rfc5280#section-4.2.1.12>.
|
For more information about extended key usage (EKU), see <https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.12>.
|
||||||
|
|
||||||
For information about adding EKU to a certificate, see <https://technet.microsoft.com/library/cc731792.aspx>.
|
For information about adding EKU to a certificate, see <https://technet.microsoft.com/library/cc731792.aspx>.
|
||||||
|
|
||||||
|
@ -834,9 +834,8 @@ When the MDM-Server receives the above data, it must:
|
|||||||
|
|
||||||
- Forward (HTTP Post) the XML data struct (including the nonce that was appended in the previous step) to the assigned DHA-Service that runs on:
|
- Forward (HTTP Post) the XML data struct (including the nonce that was appended in the previous step) to the assigned DHA-Service that runs on:
|
||||||
|
|
||||||
- DHA-Cloud (Microsoft owned and operated DHA-Service) scenario: [https://has.spserv.microsoft.com/DeviceHealthAttestation/ValidateHealthCertificate/v3](https://has.spserv.microsoft.com/DeviceHealthAttestation/ValidateHealthCertificate/v3)
|
- DHA-Cloud (Microsoft owned and operated DHA-Service) scenario: `https://has.spserv.microsoft.com/DeviceHealthAttestation/ValidateHealthCertificate/v3`
|
||||||
- DHA-OnPrem or DHA-EMC: [https://FullyQualifiedDomainName-FDQN/DeviceHealthAttestation/ValidateHealthCertificate/v3](https://FullyQualifiedDomainName-FDQN/DeviceHealthAttestation/ValidateHealthCertificate/v3)
|
- DHA-OnPrem or DHA-EMC: `https://FullyQualifiedDomainName-FDQN/DeviceHealthAttestation/ValidateHealthCertificate/v3`
|
||||||
|
|
||||||
### <a href="" id="receive-has-response"></a>Step 7: Receive response from the DHA-service
|
### <a href="" id="receive-has-response"></a>Step 7: Receive response from the DHA-service
|
||||||
|
|
||||||
When the Microsoft Device Health Attestation Service receives a request for verification, it performs the following steps:
|
When the Microsoft Device Health Attestation Service receives a request for verification, it performs the following steps:
|
||||||
|
@ -88,7 +88,7 @@ For information about EAP Settings, see <https://technet.microsoft.com/library/h
|
|||||||
|
|
||||||
For information about generating an EAP XML, see [EAP configuration](eap-configuration.md).
|
For information about generating an EAP XML, see [EAP configuration](eap-configuration.md).
|
||||||
|
|
||||||
For more information about extended key usage, see <http://tools.ietf.org/html/rfc5280#section-4.2.1.12>.
|
For more information about extended key usage, see <https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.12>.
|
||||||
|
|
||||||
For information about adding extended key usage (EKU) to a certificate, see <https://technet.microsoft.com/library/cc731792.aspx>.
|
For information about adding extended key usage (EKU) to a certificate, see <https://technet.microsoft.com/library/cc731792.aspx>.
|
||||||
|
|
||||||
|
@ -225,7 +225,7 @@ If the physical computer is still running in a frozen state, follow these steps
|
|||||||
|
|
||||||
Pool Monitor shows you the number of allocations and outstanding bytes of allocation by type of pool and the tag that is passed into calls of ExAllocatePoolWithTag.
|
Pool Monitor shows you the number of allocations and outstanding bytes of allocation by type of pool and the tag that is passed into calls of ExAllocatePoolWithTag.
|
||||||
|
|
||||||
For more information, see [How to use Memory Pool Monitor to troubleshoot kernel mode memory leaks](https://support.microsoft.com/topic/4f4a05c2-ef8a-fca4-3ae0-670b940af398).
|
For more information, see [Using PoolMon to Find a Kernel-Mode Memory Leak](/windows-hardware/drivers/debugger/using-poolmon-to-find-a-kernel-mode-memory-leak) and [PoolMon Examples](/windows-hardware/drivers/devtest/poolmon-examples).
|
||||||
|
|
||||||
### Use memory dump to collect data for the virtual machine that's running in a frozen state
|
### Use memory dump to collect data for the virtual machine that's running in a frozen state
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user