Jump to content

Unable to install new Teams since latest version on Windows 21H2 LTSC


Milan KTG

Recommended Posts

Hello,

Been using New Teams for a few months now. Since he latest version of bootstrapper I am getting the error in the screenshot. 
Anyone know why? I can still use older version of bootstrapper but why?

 

image.thumb.png.79c163bd78383b701260a156210573b9.png

Link to comment
Share on other sites

I just found that as well! It used to be on the supported list for sure. 

There is a workaround to get it installed but how does Microsoft support Win 10 21H2 until 2027 but not support New Teams on it?

 

 

Link to comment
Share on other sites

@Milan KTG, Microsoft provided guidance many years ago to avoid using LTSC versions of Windows for VDI deployments. Later on, Microsoft 365/Office 365 stopped supporting Windows LTSC as well, requiring Office LTSC to be used with LTSC versions of Windows.

Omnissa cannot provide a recommendation on which specific version you should use, as you'll need to do this based off your workload, your requirements, etc. However, they can provide a list of supported operating systems for Horizon that you can choose to use for a supported configuration.

List of Supported versions of Windows with Horizon: Supported Windows 10 and Windows 11 Guest Operating Systems for Horizon Agent and Remote Experience, for Omnissa Horizon 8.x (2006 and Later) (78714)

I'd recommend choosing a version of Windows that supports all your applications, including Office and any LoB applications you're running.

  • Insightful 1

Stephen Wagner (President, Digitally Accurate Inc.)

VMware vExpert (vExpert Pro, vSphere, vSAN Awards), Omnissa Tech Insider, NVIDIA NGCA Advisor, VMUG Leader, and Director (Board of Directors) at World of EUC

Check out my Tech Blog: https://www.StephenWagner.com

Link to comment
Share on other sites

Thank you for the reply @StephenWagner7!

I think somewhere we missed the part that Microsoft does not recommend LTSC versions for VDI.

We have been using Office Semi-Annual release channel for years with it now.

I guess its time to discuss internally what are future steps will be.

I can get latest version of Teams running fine if I use older version of bootstrapper.exe (likely does not block LTSC).

 

Link to comment
Share on other sites

31 minutes ago, Milan KTG said:

Thank you for the reply @StephenWagner7!

I think somewhere we missed the part that Microsoft does not recommend LTSC versions for VDI.

We have been using Office Semi-Annual release channel for years with it now.

I guess its time to discuss internally what are future steps will be.

I can get latest version of Teams running fine if I use older version of bootstrapper.exe (likely does not block LTSC).

 

Keep in mind I'm unfamiliar with your workload, however normally these days you normally see the GAC (General Availability Channel) versions of Windows 10/11 pushed in VDI environments, to make sure they support Office 365, etc...

All deployments I'm doing, we're using either the latest Windows 10 release, or Windows 11 23H2 (24H2 isn't supported yet).

Stephen Wagner (President, Digitally Accurate Inc.)

VMware vExpert (vExpert Pro, vSphere, vSAN Awards), Omnissa Tech Insider, NVIDIA NGCA Advisor, VMUG Leader, and Director (Board of Directors) at World of EUC

Check out my Tech Blog: https://www.StephenWagner.com

Link to comment
Share on other sites

Looks like Windows 

7 minutes ago, StephenWagner7 said:

Keep in mind I'm unfamiliar with your workload, however normally these days you normally see the GAC (General Availability Channel) versions of Windows 10/11 pushed in VDI environments, to make sure they support Office 365, etc...

All deployments I'm doing, we're using either the latest Windows 10 release, or Windows 11 23H2 (24H2 isn't supported yet).

Looks like Windows 10 23H2 has another year of support? At that time we would have to move to Windows 11 anyway?

We could wait for Windows 11 24H2 to be supported and move to that, or if we setup 23H2 is it recommended to do in place upgrade, or build a new gold image with every new version of Windows? Running LTSC for years never really had to worry about feature upgrades, just security patches. 

Finally, my last question is edition of Windows. I am sure we would still go Enterprise (just checking our licensing). I see Enterprise IoT. Is that better suited for VDI environment and longer support?

I've been reading things online, but opinions from experts like you, really help. 

Thank you. 

Link to comment
Share on other sites

1 hour ago, Milan KTG said:

Looks like Windows 

Looks like Windows 10 23H2 has another year of support? At that time we would have to move to Windows 11 anyway?

We could wait for Windows 11 24H2 to be supported and move to that, or if we setup 23H2 is it recommended to do in place upgrade, or build a new gold image with every new version of Windows? Running LTSC for years never really had to worry about feature upgrades, just security patches. 

Finally, my last question is edition of Windows. I am sure we would still go Enterprise (just checking our licensing). I see Enterprise IoT. Is that better suited for VDI environment and longer support?

I've been reading things online, but opinions from experts like you, really help. 

Thank you. 

If you deploy Windows 11 properly (using WinPE and ADK) without a vTPM on your base image for non-persistent VDI VMs, you won't be able to perform upgrades to new feature releases on the image, and will require a new base image on every feature update. With this being said, best practices is to automate this process and be able to build a base image out at the click of a button or keystroke.

If you're running persistent VMs, you could have your VDI VMs upgrade to the next feature release as your approve it and roll it out.

To my knowledge, Enterprise IoT is a version of LTSC. So I would recommend avoiding this version.

Stephen Wagner (President, Digitally Accurate Inc.)

VMware vExpert (vExpert Pro, vSphere, vSAN Awards), Omnissa Tech Insider, NVIDIA NGCA Advisor, VMUG Leader, and Director (Board of Directors) at World of EUC

Check out my Tech Blog: https://www.StephenWagner.com

Link to comment
Share on other sites

  • 3 weeks later...

Hey Milan,

 

it is possible to unzip the MSTeams.MSIX File and Copy Paste it into your program folder of your master Image.
You than also have an .exe file to use for triggering directFlex and configuring a DEM based shortcut.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...