Clarify TSS Offline Log Collector run location (rescue VM / Hyper-V host) - #139
Merged
pagienge merged 1 commit intoAug 10, 2026
Conversation
Contributor
|
basic doc updates, merging. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Clarifies where the TSS Offline Log Collector must run, addressing confusion that it might run on the broken VM.
The tool runs on a working machine that has the broken VM's OS disk attached as an offline data disk \u2014 an Azure rescue VM or a Hyper-V host \u2014 not on the broken VM itself.
Changes
[CmdletBinding()]stating the same requirement.Notes
Stacked on
feature/tssofflinelogcollector(base of PR #138). Docs/comment only \u2014 no functional change.