Update of MSI download

jdseymour1978  Wow, that's a bit harsh.

I can only assume it wasn't meant that way when it was originally written and has translated poorly to text or you were super frustrated at the time.

Whilst I can appreciate your frustration at getting potentially unhelpful information. There is no reason to belittle someone based on their title. Remember that MVP's are admins, just like you. We don't work for Microsoft, we don't have a special "magic book" with everything in it next to us and we spend our free time helping individuals such as yourself for free in our own time.

I can't speak for Eric, but for myself, it was to give back to the community that helped me when I was a wee young sysadmin running exchange 2003.

---

Anyway, back on topic.

I understand the frustration of working with VDI servers and clients myself having been dealing with it since Lync 2013.

My understanding is one of the main reasons the placeholder is on a specific version is because of the Office365 rollout strategy. With that version being the "safest" version to deploy regardless of tenant status and VDI plugin build.

Your Teams client will update itself depending on many things, including the ring you are on, your tenancies environment/region, the rollout stage on your tenancy/ your office update channel (Preview/Targeted/Current) status etc. None of which can be determined by a simple URL redirect.

(interesting fact, you can kinda get Teams to do weird things by jumping from a TAP tenant to a normal tenant using the same build. Despite flags being set to remove features some weirdness still occurs)

I assume you're already across it, but if your running Teams in a VDI environment you are running the VDI plugin/registry changes as well?

https://docs.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd
https://support.citrix.com/article/CTX253754

Hope this helps.