Description:
Based on the reference to this page in issue ticket #6784
(Scripts documentation missing), I noticed that 2 of 3 links pointing
to the Microsoft Security Baselines blog still used the old and
archived technet blog pages instead of the new and improved
Tech Community pages, in addition to using the outdated name
"Microsoft Security Guidance blog" instead of the new name
"Microsoft Security Baselines blog".
To make this PR easier to review, I have restricted myself to making
only 2 types of change here: URL updates (2) and link text updates (3).
Changes proposed:
- Replace the outdated technet blog links with Tech Community links
- Update the link text names to "Microsoft Security Baselines blog".
Ticket closure or reference:
Ref. #6784
Description:
As reported in issue ticket #6766 (Dead link), the current link to
"Configure certificate infrastructure for SCEP" returns a 404 error
because the page has been moved to a new directory structure in commit
4ae71ed25d10 on February 28, 2020. 1702 files and folders have been
moved and/or renamed in this process, making it a game of chance to
correct more than one 404 link discovery at a time. (I hope some links
were corrected back then, but I have not researched the details.)
Thanks to rossmpersonal for reporting this 404 issue.
Changes proposed:
- Update the link URL to its current location
(docs.microsoft.com/mem/intune/protect/certificates-scep-configure)
- Remove redundant end-of-line whitespace (blanks) throughout the page
Ticket closure or reference:
Closes#6766
Updated the "Using Windows in a FIPS 140-2 approved mode of operation" to be up to date with current Microsoft recommendations and added in additional question to the FAQ to give clarity on the compliance status of SMB3 in Windows. Also re-added the fips@microsoft contact information because it was dropped off in a previous update to this page.
Created a new article based on information provided by FTE Yong Rhee. Article contains instructions to create an .xml file to use with launchd to schedule a quick or full scan in a specific time frame. Request originally had a section to use crontab, but this was removed at the request of the submitter.
Edited the TOC to include the new article.
Description:
As recommended by Tina McNaboe in issue ticket #7021 (Doubt), I suggest
encapsulating all OS strings and keywords in MarkDown back ticks to
avoid automatic translation of text that should never be translated, as
well as keeping the strings as coherent and unmodified as possible.
To paraphrase:
While the engineers are working on a fix to avoid overlocalization like
this on machine translated articles, it may be a few months before
it's fixed. In the meantime, it would be helpful to encapsulate the
non-localizable strings in the English article.
It is also a common problem that Machine Translation adds spacing where
it should not be, even if the surrounding text is kept untranslated.
This type of issue tends to be less easy to discover for non-English
readers who rely more on the translated pages than on the /en-us/ pages.
This PR aims to reduce these issues, at least for this page, to keep it
as correct as possible, even when filtered through Machine Translation.
Changes proposed:
- Encapsulate listed strings, filenames and extensions in MD back ticks
- Make sure that the encapsulated strings don't keep extra backslashes
Additional corrections, since we are already editing this page:
- Replace TechNet URLs with their permanent docs.microsoft.com redirects
- Replace MSDN URLs with their permanent docs.microsoft.com redirects
- Reduce a docs.microsoft.com link to internal tag link (same page)
- Adjust "Currentcontrolset" to CurrentControlSet (3 occurrences)
Ticket closure or reference:
Ref. #7021 (keep open until changes migrate to localized pages)
