Reported on Microsoft Connect HERE.
See the summary below. Go to the above link to view the full details. I added this more as feedback versus adding it as an issue (it isn’t an actual “trouble”).
Please use the above link to vote on the issue if you think this should be resolved by the OpsMgr team.
Get-MaintenanceWindow reports StartTime and ScheduledEndTime property as the UTC time (ignoring the local timezone).
Example below, the current time is approximately:
Monday, October 27, 2008 7:15:14 PM
When the New-MaintenanceWindow cmdlet is used to create a maintenance window starting immediately, using Get-MaintenanceWindow immediately after, the StartTime shows as:
(Monday, October 27, 2008 7:15:14 PM)+6 (Timezone value)-1 (not DST)=10/28/2008 12:14:58 AM
So it appears, the StartTime property follows the above formula to display the value to the console via the Command Shell.
Get-MaintenanceWindow should report Date/time properties while accounting for the local timezone settings.