-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 windows-server-2016-improvements.md #7728
base: main
Are you sure you want to change the base?
Conversation
Through testing, backed up by code review, I've confirmed that GP processing on it's own is not enough to make the w32time service become aware of UtilizeSslTimeData changes, as this value is only ready at service/thread startup. Current wording is a bit misleading, suggests the GP Client will become aware of the change and that alone is enough for changes to take effect, which is not true.
@JoshMoraDSE : Thanks for your contribution! The author(s) have been notified to review your proposed change. @dahavey |
Learn Build status updates of commit c324124: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
#assign: @robinharwood, @Xelu86 @robinharwood @Xelu86 #label:"aq-pr-triaged" |
Learn Build status updates of commit 8c94ec6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
#sign-off |
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @dahavey |
nudge @robinharwood @Xelu86 |
Through testing, backed up by code review, I've confirmed that GP processing on it's own is not enough to make the w32time service become aware of UtilizeSslTimeData changes, as this value is only ready at service/thread startup. Current wording is a bit misleading, suggests the GP Client will become aware of the change and that alone is enough for changes to take effect, which is not true.