Confirm-ExchangeShell function improved to work on management server with SerializedDataSigning turned on#1512
Merged
lusassl-msft merged 1 commit intoFeb 28, 2023
Conversation
lusassl-msft
force-pushed
the
lusassl-ConfirmExchangeShellSerializedDataSigningFix
branch
from
540e858 to
60e0e26
Compare
bill-long
previously approved these changes
Feb 28, 2023
lusassl-msft
force-pushed
the
lusassl-ConfirmExchangeShellSerializedDataSigningFix
branch
from
3bd591c to
12c2d21
Compare
dpaulson45
approved these changes
Feb 28, 2023
lusassl-msft
deleted the
lusassl-ConfirmExchangeShellSerializedDataSigningFix
branch
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
3 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.
Issue:
It was reported that
Confirm-ExchangeShelldoesn't work well in specific scenarios. After some research we were able to pin it down to the Serialized Data Signing feature which causes this behavior if turned on and if the script was executed on a management server (no Exchange roles installed).Resolve #1507
Reason:
The type will change to
PSObjectif Serialized Data Signing was enabled and EMS on a management server is used.We have an internal work item regarding this behavior as several customers reported it.
Fix:
Check for the
SerializationDataproperty ifGetType().Nameproperty is notEventCategoryObject. TheSerializationDataproperty is available in EMS, it is not available if Exchange servers was connected by using remote PowerShell.Validation:
Lab