Clarify instructions for running Client Analyzer shipped version #498
Clarify instructions for running Client Analyzer shipped version #498albertzhao007 wants to merge 4 commits into
Conversation
…ive response Adjust the format which is clearer for binary version and python version separately.
|
Learn Build status updates of commit 215e60a: ✅ Validation status: passed
For more details, please refer to the build report. |
@microsoft-github-policy-service agree company="Microsoft" |
|
Learn Build status updates of commit 9c8e972: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Could you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
This PR clarifies the Live Response instructions for running the XMDE Client Analyzer version that’s shipped with Microsoft Defender for Linux by separating the binary and Python script guidance and tightening the formatting around the steps.
Changes:
- Splits “shipped version” guidance into distinct binary and Python script creation steps.
- Adds/adjusts markdown code fences so the script contents and execution commands are separated more clearly.
|
Learn Build status updates of commit 6102f74: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 0d85559: ✅ Validation status: passed
For more details, please refer to the build report. |
Clarify instructions for running Client Analyzer shipped version in live response
Adjust the format which is clearer for binary version and python version separately.