mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-06 01:27:21 +00:00
whitespace edits
This commit is contained in:
parent
e328cb2b81
commit
83e7b41be7
@ -61,7 +61,7 @@
|
||||
## [Troubleshoot HoloLens](hololens-troubleshooting.md)
|
||||
## [Known issues](hololens-known-issues.md)
|
||||
## [Frequently asked questions](hololens-faq.md)
|
||||
## [Frequently Asked Security Questions](hololens-faq-security.md)
|
||||
## [Frequently asked security questions](hololens-faq-security.md)
|
||||
## [Hololens services status](hololens-status.md)
|
||||
## [SCEP Whitepaper](scep-whitepaper.md)
|
||||
|
||||
|
@ -231,4 +231,3 @@ If your device isn't performing properly, see [Restart, reset, or recover HoloLe
|
||||
*Coming soon*
|
||||
|
||||
[Back to list](#list)
|
||||
|
||||
|
@ -74,4 +74,3 @@ We then pass that to the device and then the device generates it’s CSR and pas
|
||||
1. Connector checks in with Intune, and will process and any cert revocation transactions (i.e, if the Intune tenant admin issues a remote wipe – full or partial, also If a user unenrolls their device from Intune), reporting on issued certs, renewing the connectors’ SC_Online_Issuing certificate from Intune. Also note: the NDES Intune connector has shared PKCS cert functionality (if you decide to issue PKCS/PFX based certs) so the connector checks to Intune for PKCS cert requests even though there won’t be any requests to process. We are splitting that functionality out, so this connector just handles SCEP, but no ETA yet.
|
||||
|
||||
1. [Here](https://docs.microsoft.com/intune/intune-endpoints#microsoft-intune-certificate-connector) is a reference for Intune NDES connector network communications.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user