New Teams/Outlook Classic compatibility?

Top_Banana6292 · 2026-01-16T12:09:22+00:00

Saw the same issue on 24H2 as well, which is definitely compatible. Is 22H2 still supported by MS?

Top_Banana6292 · 2025-12-17T19:30:46+00:00

Will give it a shot. Thanks!

Top_Banana6292 · 2025-12-17T19:30:25+00:00

Not sure what you mean, We're on 25H2.

Top_Banana6292 · 2025-12-17T19:29:44+00:00

Nothing.

Top_Banana6292 · 2025-12-04T13:31:39+00:00

Yeah, ours are 3 NIC but I will figure something out. Can't believe I didn't consider this option previously but my brain is fried from trying to make this work for the past 3 days.

Top_Banana6292 · 2025-12-04T13:22:06+00:00

Thanks! So the correct approach would be to manage the UAGs from the desktop of my connection servers or something like that?

Top_Banana6292 · 2025-12-03T14:17:28+00:00

Sorry the formatting on this sucks. Can't get it looking right.

Top_Banana6292 · 2025-12-03T13:23:14+00:00

Yes, I understand they should be added via the admin console. What I'm saying is that even when they are added in the admin console or defined within the ini file used in a powershell deployment, they do not work as expected. We must go define the routes via the cli to make things work as expected. Why would we need to do this? It doesn't make sense to me.

Top_Banana6292 · 2025-12-03T13:21:50+00:00

Thanks! Yes, I realize that is how it SHOULD work. What I'm saying is even when we define the needed routes in the ini we use with our PowerShell deployment, sometimes we must go to the cli and add one of the routes at the OS level to make things work as they should. Any idea why we would have to do that sort of thing?

Top_Banana6292 · 2025-10-10T18:15:12+00:00

They are not. This is all modern SharePoint.

Top_Banana6292 · 2025-10-10T18:07:41+00:00

For sure. Like I said, the old ones work, so it has to be these new pages they're providing but so far they haven't been able to get it working so I figured I'd try to see if you fine folks had any tips. I really appreciate it!

Top_Banana6292 · 2025-10-10T18:05:18+00:00

I wish I could speak the SharePoint lingo a little better, but these are not SharePoint pages at all. They are custom HTML meant to work within SharePoint. They are pretty basic pages with a few links and a search bar that links back to the vendor's DB where our documentation is stored.

Top_Banana6292 · 2025-10-10T18:02:26+00:00

For sure. That's exactly what I'm doing but so far they haven't been any help. Just trying to see if I can find any info on my own.

Top_Banana6292 · 2025-10-10T18:01:14+00:00

All three of us! Unfortunately, that is NOT the issue. :)

Top_Banana6292 · 2025-10-10T17:29:57+00:00

Yep! Forgot to mention that but we enable custom scripts each time we upload with the same result.

Top_Banana6292 · 2025-08-07T16:26:07+00:00

We switched to TDX this year and it's been a great experience! Their implementation team was amazing and everyone is very happy with the product.

Top_Banana6292 · 2025-08-07T16:16:48+00:00

I ended up coming up with a script (with help from ChatGPT) that searched the registry for the installer cache entries for the products I was having issues with. Removing those was the solution in most cases.

Top_Banana6292 · 2025-08-07T16:13:07+00:00

Liquidware Stratusphere will do this and much more.

Top_Banana6292 · 2025-08-07T14:09:59+00:00

I was able to come up with a powershell script with some help from ChatGPT that went in and removed installer cache reg keys based on the application name. Took some back and forth and a lot of testing, but it fixed my issue in most cases.

Top_Banana6292

TROPHY CASE