CiTool in Windows Server, improved wording and updated notice #11954
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.
Description
Windows Server 2025 has the inbox CiTool.exe.
Updated wording to be consistent, changed apply to deploy. Apply was only used in 2 places while everywhere else the word "Deploy" was used.
Added a note to the known issue notice.
Why
Windows Server 2025, which is nearly GA, has the inbox CiTool.exe which has the same features as the CiTool.exe in Windows 11 24H2. It can be used to deploy signed and unsigned policies.
Before when this repository allowed opening issues, i had opened an issue where I asked about the known issue between memory integrity and deploying signed policies. One of the persons responsible for the feature commented that the problem is resolving in the next update, that was almost a year ago and in Windows 11 24H2, the problem is no longer reproducible as far as I can tell. So I added a note to make it conditional but if that update is backported or you plan to do so then I suggest removing it entirely.