Maintenance window start date regression in 1606 - year 1970
We have a 5-minute, non-recurring maintenance window starting 1/1/1970 1:00 AM configured on several critical device collections to prevent reboots due to accidentally-configured deployments - and this worked as of SCCM 1511. In 1606 though, when I try to edit that maintenance window, I receive an un-handled ArgumentOutOfRangeException (Value should be between 'MinDate' and 'MaxDate').
Creating a new maintenance window starting 1/1/1971 1:00 AM (the UI won't even allow you to set 1970, it'll just flip it back to the previous value) and deleting the older one works, but this is certainly a bug. I don't know yet if other DateTime pickers in SCCM 1606 are affected too.
This is an issue with windows code that deals with time. 1/1/1970 will cause crashes when doing timezone adjustements (because it can become 12/31/1969) (even when simply converting to UTC)
Best to never use 1/1/1970.