Moved AP's impacting Windows time zone

Last year we closed a location in the Eastern time zone and put the recovered AP's in storage. When a site in the Central time zone had an urgent need, we shipped them 5 AP's from this inventory, and now the site is complaining all their computers are defaulting to the Eastern Time Zone. 

Now the finger pointing is going on between the Windows desktop team and the Networking team. I discovered a portal MS provides where you can request your BSSIDs to not be tracked in their geo database, but it's an input only form that leaves you wondering if anything is really going to happen. It also provides no way to determine if BSSID is what is causing the incorrect time zone detection. 

The FortiGate is set to the correct time zone, has the correct time, and DHCP points clients to the internal NTP servers for centralized time. 

I am curious if anyone else has come across this and have any advice on resolving it?

Denny