Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get-MessageIDs - '-Output Y' Does not work #134

Open
DoubtfulTurnip opened this issue Feb 4, 2025 · 1 comment
Open

Get-MessageIDs - '-Output Y' Does not work #134

DoubtfulTurnip opened this issue Feb 4, 2025 · 1 comment

Comments

@DoubtfulTurnip
Copy link

When using the following command as per the documentation.

Get-MessageIDs -StartDate {STARTDATE} -EndDate {ENDDATE} -sessions {SESSIONID} -outputdir $env:USERPROFILE\Desktop\
 -output Y

No output is provided in the given directory

Removing '-output Y' (which I understand is the default anyway) ensures that output is written to the desired folder.

Also for Get-MessageIDs and Get-Sessions, the documentation infers (although I'd agree that it might just be ambiguous) that the format for start and end date is dd/mm/yyyy however I seem to find that it is mm/dd/yyyy which does seem to be inconsistent with other commands. This could just be something I am doing wrong but I figured that by including this here I will be able to get some clarification if so.

Write-ErrorMessage : Cannot process argument transformation on parameter 'StartDate'. Cannot convert value "30/12/2024" to type "Microsoft.Exchange.ExchangeSystem.ExDateTime". Error: "String '30/12/2024' was not recognized as a valid DateTime."

@JoeyInvictus
Copy link
Collaborator

JoeyInvictus commented Feb 4, 2025

Hi, it's a switch parameter, meaning you don't have to put "Y" or "N" behind it. If you run it with just -output, it should work. Will update the docs for this as well.

Thanks for pointing out the documentation issue. We will update it to make it more consistent with the rest.
The example currently follows the format we use (The Netherlands): dd/mm/yyyy, which makes it more confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants