microsoft / microsoft/CSS-Exchange
[Issue] - Health Checker - Missing detection of legacy sec groups in TXT output.
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.3k
- Forks
- 395
- Avg merge
- 14h 7m
- Merged PRs (30d)
- 5
Description
Provide Version Number
26.07.14.1645
Describe the issue
In regards to the Legacy Exchange Security Groups, as I still had Exchange Domain Servers hanging around, I see the script detects it from the output XML plus see it listed when run in verbose mode but doesn't mention their presence in the associatext TXT output file from the HealthChecker script ? Maybe by design by thought worth mentioning,.
In fact there must be a bug in the script as if all the groups are there, it does show...
But if I only have 1 group , verbose output from the script :
VERBOSE: Calling: Get-ExchangeLegacySecurityGroups
VERBOSE: Found legacy group: CN=Exchange Domain Servers,CN=Users,DC=xxxxx,DC=com
......
VERBOSE: Calling Add-AnalyzedResultInformation:
VERBOSE: No legacy Exchange security groups found.
VERBOSE: Completed: Invoke-AnalyzerOrganizationInformation and took 0.2263122 seconds
Expected behavior
Missing detection of legacy sec groups in TXT output.
Script Output
Missing detection of legacy sec groups in TXT output.
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at Invoke-AnalyzerOrganizationInformation and trace its calls to Get-ExchangeLegacySecurityGroups and Add-AnalyzedResultInformation. Compare the verbose and XML handling with the associated TXT output when exactly one legacy group is found. Done means the TXT output reports that group while preserving the no-groups behavior; verify both cases with the HealthChecker script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100