I mean no disrepsect, but please accept this: Windows does not alter date stamps on files during DST changes (or when you adjust timezone for that matter), it doesn't work like that. It uses GMT and simply calculates the value to display based on timezone and DST settings. Timestamps are not altered.
No problem - none taken or implied.
I am simply trying to understand what it is that is going on here. Here's what I understand now - if Windows Server is operating using GMT and "displays" it's time stamps according to a new DST setting
AND MC apparently does the same (according to Matt) then we should have no problems whatsoever. However that is not the case.
My screencap that started this thread clearly shows that a specific file shows one modified time on the server and a different modified time within the MC library (At that moment). Therefore - Matt's statement that:
"File dates are stored as GMT. Daylights savings and time zones are not relevant."
Is not exactly accurate. If MC was completely "DST Aware" in real time and DST was not an issue - I should have been able to open that Fine Frenzy record on the morning of Nov 3 and see that the library modified date display was exactly the same as the server. Therefore I believe the issue is not with MC storing file dates as GMT - but with storing GMT file date info in a static fashion.
I think it's now fair to assume that MC's GMT time stamp display is not a "live" thing but stored in the library fileset somewhere and NEEDS an update before it's timestamps - match the GMT/DST settings of the files on the server. So - is this really what is happening during a manual Auto Import (following a DST time change):
1. File enumeration begins in MC as it looks to the server for changes
2. MC determines that the server now has a new GMT setting based on the DST change and...
3. Does something? Consults the library? Perhaps looking for files that have had timestamp changes since the last DST change? (Total speculation here)
4. It then locate all files it finds based on Step 3 and updates something in it's library (or even the file itself - modified date or perhaps more?)
5. Auto Update completes - telling me that 7650 files needed updates.
Guys - I am totally fine with the updates if it makes things groovy between library and server and I am fine with how MC should uses GMT and
should react favorably to DST changes.
What I am not fine with is:
1. Not knowing what changed
2. What exactly is MC looking for and why?
3. Getting a blunt notice that 7650 files are about to be updated - for reasons unknown
This last one is the one that makes me the most nervous. If MC is suddenly going to update 7650 files - I think I deserve to know what it's going to do and why.
I am hoping we can get a clear understanding or logic flow from Matt as to what MC is doing post-DST change to cause it to report so many changes need to occur.
VP