Closed jose-camacaro closed 4 years ago
Thanks @josesonic for the feedback. I'll check on whether there are any Windows feature prerequisites that we don't explicitly document.
I’m sorry that you’re having problems, and I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:
Thanks again for the feedback. We recently moved this content to a new GitHub repository, so this issue is no longer tracked with the original article. As part of that process, we reviewed our backlog of feedback, and made some tough decisions on items that we don't think we'll realistically ever address. If you're passionate about this specific feedback, please refile it on the current article, now under docs.microsoft.com/mem/configmgr.
Reference: https://social.technet.microsoft.com/Forums/en-US/518aea48-fbd8-4cff-a3e9-344788a4a5b9/windows-defender-application-guard-does-hyper-v-needs-to-be-enabled-on-every-machine-in-enterprise?forum=winservermanager
It appears the expectation is that a WDAG policy deployment via ConfigMgr automatically enables both "Hyper-V" and "Windows Defender Application Guard" features. As you can see on that technet thread, I am not seeing that.
Any help is highly appreciated.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.