mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 14:27:22 +00:00
Merge pull request #8006 from MicrosoftDocs/repo_sync_working_branch
Resolve syncing conflicts from repo_sync_working_branch to main
This commit is contained in:
commit
0848e2f89c
@ -164,7 +164,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p
|
||||
1. Enable nested virtualization:
|
||||
|
||||
```powershell
|
||||
Set -VMProcessor -VMName "VM name" -ExposeVirtualizationExtensions $true
|
||||
Set-VMProcessor -VMName "VM name" -ExposeVirtualizationExtensions $true
|
||||
```
|
||||
|
||||
1. Enable MAC spoofing:
|
||||
|
@ -238,7 +238,7 @@ sections:
|
||||
- attempting to access on-premises resources secured by Active Directory
|
||||
- question: Can I use RDP/VDI with Windows Hello for Business cloud Kerberos trust?
|
||||
answer: |
|
||||
Windows Hello for Business cloud Kerberos trust can't be used as a supplied credential with RDP/VDI. Similar to key trust, cloud Kerberos trust can be used for RDP with [remote credential guard][/windows/security/identity-protection/remote-credential-guard] or if a [certificate is enrolled into Windows Hello for Business](hello-deployment-rdp-certs.md) for this purpose.
|
||||
Windows Hello for Business cloud Kerberos trust can't be used as a supplied credential with RDP/VDI. Similar to key trust, cloud Kerberos trust can be used for RDP with [Remote Credential Guard](/windows/security/identity-protection/remote-credential-guard) or if a [certificate is enrolled into Windows Hello for Business](hello-deployment-rdp-certs.md) for this purpose.
|
||||
- question: Do all my domain controllers need to be fully patched as per the prerequisites for me to use Windows Hello for Business cloud Kerberos trust?
|
||||
answer: |
|
||||
No, only the number necessary to handle the load from all cloud Kerberos trust devices.
|
||||
|
Loading…
x
Reference in New Issue
Block a user