RHall
Member
- Joined
- September 11, 2019
- Messages
- 13
- Reaction score
- 1
- City, State
- Blue Bell, PA
- Year, Model & Trim Level
- 19 Explorer Sport 4WD
I had to chat with the online Ford team yesterday too to get my account straightened out, and finally it showed up as well for me a few minutes ago.
I can confirm at least for my 2019 Explorer Sport, that I received the same build and info as Silverkorn above in his post - same URL, same info.
I also confirmed on a couple other forums, specifically on f150forum.com that this is essentially the same as some of the other sources for the 19205 build that have been passed around.
A shame others have had a bad experience with the support team - what I Iearned from the chat yesterday I went though was that they do have access to check based on a VIN if there is an update present - but they don't have access to the build #'s nor can they be certain with any certainty that its not the previous update or one that may/may not already have been applied. Ford should fix that for sure.
I am chalking up this rollout discrepancy to a few things (speculation, but informed speculation):
1. They are in the middle of a migration to a new site wide SSO (Single Sign-on) auth mechanism that is exposed through ibmcloud web services, and its not 100% integrated yet without bugs/issues - there are tons of unnecessary re-directs and other workarounds just to shoehorn this in - its is far from ideal.
2. They have to be enforcing some form of staged rollout based on some internal criteria (zip/geoIP, VIN sequences, account status, etc.) or some combo - they also know if you are happy/satisfied/mad, etc. - they track this - its right in the data that the site exposes - and squeaky wheels are likely allowing you to get bumped into the current queued group of people who can get results and access to the downloads. I base this on the previous urls and services they used to deploy assets, and the new links which are now hosted on Microsofts AzureEdge - they charge for the outgoing bandwidth (rates here: Pricing - Content Delivery Network (CDN) | Microsoft Azure ), and if they opened the gates to everyone at once, its possible they would incur bursting charges or additional charges to handle the sudden influx of requests, and the scale up to handle that overall capacity. I would be willing to be thats the real cause/case - could be totally wrong, but don't think I am. The fact that none of the OTA updates work either is likely a cost issue as to opposed to any real technical challenges. Especially if Ford is on the hook for any bandwidth charges where the updates for Sync might come over the included trial hotspots or Fordpass network)...
It's just a shame Ford isn't more transparent on this, wether it is something along the lines of my speculation, or some other issue, most people just want to be informed, and not have to wonder what is going on.
Anyway, my two cents. Going to apply the update this afternoon and check to see what's fixed and what's not.
I can confirm at least for my 2019 Explorer Sport, that I received the same build and info as Silverkorn above in his post - same URL, same info.
I also confirmed on a couple other forums, specifically on f150forum.com that this is essentially the same as some of the other sources for the 19205 build that have been passed around.
A shame others have had a bad experience with the support team - what I Iearned from the chat yesterday I went though was that they do have access to check based on a VIN if there is an update present - but they don't have access to the build #'s nor can they be certain with any certainty that its not the previous update or one that may/may not already have been applied. Ford should fix that for sure.
I am chalking up this rollout discrepancy to a few things (speculation, but informed speculation):
1. They are in the middle of a migration to a new site wide SSO (Single Sign-on) auth mechanism that is exposed through ibmcloud web services, and its not 100% integrated yet without bugs/issues - there are tons of unnecessary re-directs and other workarounds just to shoehorn this in - its is far from ideal.
2. They have to be enforcing some form of staged rollout based on some internal criteria (zip/geoIP, VIN sequences, account status, etc.) or some combo - they also know if you are happy/satisfied/mad, etc. - they track this - its right in the data that the site exposes - and squeaky wheels are likely allowing you to get bumped into the current queued group of people who can get results and access to the downloads. I base this on the previous urls and services they used to deploy assets, and the new links which are now hosted on Microsofts AzureEdge - they charge for the outgoing bandwidth (rates here: Pricing - Content Delivery Network (CDN) | Microsoft Azure ), and if they opened the gates to everyone at once, its possible they would incur bursting charges or additional charges to handle the sudden influx of requests, and the scale up to handle that overall capacity. I would be willing to be thats the real cause/case - could be totally wrong, but don't think I am. The fact that none of the OTA updates work either is likely a cost issue as to opposed to any real technical challenges. Especially if Ford is on the hook for any bandwidth charges where the updates for Sync might come over the included trial hotspots or Fordpass network)...
It's just a shame Ford isn't more transparent on this, wether it is something along the lines of my speculation, or some other issue, most people just want to be informed, and not have to wonder what is going on.
Anyway, my two cents. Going to apply the update this afternoon and check to see what's fixed and what's not.
