The latest SARA tool has updated its registry key from 339020b8684503… #1949
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
…72 to 85d933e50fd6cac2
|
@microsoft-github-policy-service agree |
@microsoft-github-policy-service agree |
…eated in the new versions of installs
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.
…72 to 85d933e50fd6cac2
This updates the Sara Detection rule to look for 85d933e50fd6cac2 instead of 339020b868450372. I am not sure when this has changed but when I followed this document "https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/installation/install-sara-from-intune?source=docs#more-information" it failed for all of my users however I did notice that the software is installed, its just the detection rule was looking for a key that no longer exist.