-
Notifications
You must be signed in to change notification settings - Fork 983
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update accounts.md #4538
Merged
Merged
Update accounts.md #4538
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The sentence: "Managing clients in untrusted domains and cross-forest scenarios allows for multiple network access accounts." does not make any sense under section: "The network access account is still required for the following actions (including eHTTP & PKI scenarios):". Because we also state the following: "If you configure the site for HTTPS or Enhanced HTTP, a workgroup or Microsoft Entra joined client can securely access content from distribution points without the need for a network access account. This behavior includes OS deployment scenarios with a task sequence running from boot media, PXE, or the Software Center." Thats why I copied the sentence to an appropriate place.
@jonasatgit : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit e27ae01: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Banreet
approved these changes
May 13, 2024
#sign-off |
prmerger-automator
bot
added
do-not-merge
and removed
ready-to-merge
qualifies-for-auto-merge
labels
Nov 12, 2024
Learn Build status updates of commit e27ae01: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The sentence: "Managing clients in untrusted domains and cross-forest scenarios allows for multiple network access accounts." does not make any sense under section: "The network access account is still required for the following actions (including eHTTP & PKI scenarios):". Because we also state the following: "If you configure the site for HTTPS or Enhanced HTTP, a workgroup or Microsoft Entra joined client can securely access content from distribution points without the need for a network access account. This behavior includes OS deployment scenarios with a task sequence running from boot media, PXE, or the Software Center." Thats why I copied the sentence to an appropriate place.