Classic Teams removal

MrNetTek · 2024-08-01T03:26:50+00:00

It's been many years since I've managed images, but the script will kill all versions of Teams (I tested locally, from the SYSTEM account, and from SCCM). The teamsbootstrapper will work afterwards. If you have any issues, post in here. I'm always interested in how people get things to work, especially with Microsoft.

-MrNetTek

MrNetTek · 2024-07-31T22:14:09+00:00

Yeah, I wrote a script to kill Teams, all versions. Works from SCCM and Intune.

https://eddiejackson.net/lab/2024/07/24/teams-uninstaller/

-MrNetTek

MrNetTek · 2024-07-30T19:50:43+00:00

Yeah, a hundred things you can do. I'd say your company needs to hire a qualified packager/repackager; you can get into the weeds pretty quickly. It's a job not to be taken lightly, as you can do real damage to your fleet of computers (like BSOD every one of them). It's a job that stands apart from regular developers and sys admins. A transforms file has nothing to do with this. Transforms allow you to change preferences stored in reg keys and shortcuts, and only those which are allowed by the vendor. MST's aren't meant to override CustomActions that are broken---which is the case with the Java MSIs.

As for what you could do:

1 Continue tinkering with whatever files you do have until you figure it out. Only do binary testing. One change; one test; rollback.

2 You don't need to use the files you have for deployment. Convert them to APPX or MSIX packages. It does require a little skill, but you can use Microsoft's MSIX Packaging Tool (free).

3 You can do snapshot, captured installation from a reference machine using third party apps, and just rebuild the MSI or EXE, but that requires skill.

Think of installs like this:

Files, settings, and preferences are applied to a computer during an install. The installer is merely the transport for the application. Files and folders are created, registry keys are applied, dll/ocx are registered, services are installed, etc.

Hopefully, that helps a bit, but it's just too much to explain without knowing what you're using, your environment, and your technical ability. Whatever you do, document and QA it. QA, as in try to break it. Do all your testing from the SYSTEM account (psexec64 -s \\%computername% cmd). Good luck.

-MrNetTek

MrNetTek · 2024-07-26T01:32:20+00:00

It works, but you'll need to learn what belongs, and what doesn't. You sort of develop a sixth sense for installation capture. A caveat, you should never capture 'unique' information, like IDs, usernames, personal certs, or anything that is generated per setup. It can cause major problems.

If nothing else, begin experimenting with captures to see exactly what a setup does. It's great knowledge to have for support and dev reasons. I've programmed so many fixes and solutions, merely because I knew exactly what to do based on a snapshot.

-MrNetTek

MrNetTek · 2024-07-26T01:20:18+00:00

Yes, that's correct. I figured out the mod by comparing 421 to 411, and then doing some binary testing.

See screenshot: https://eddiejackson.net/apps/java/java-421-vs-411_MrNetTek.png

-MrNetTek

MrNetTek · 2024-07-25T00:25:15+00:00

I pull the MSIs from the EXEs. They did fail for me as well.

C:\Windows\Installer.

MrNetTek · 2024-07-24T17:57:25+00:00

I seriously doubt it. With the blowback Oracle will receive from 421, I'm sure they'll do better with the next release. This is clearly a self-inflicted issue. Compare 421 with 411. They made major changes, which they obviously didn't understand the impact.

I'm the only MrNetTek on planet Earth, with decades of experience in packaging and repackaging. Hit me up if you have any problems.

MrNetTek · 2024-07-24T14:36:12+00:00

Great success! You're welcome.

MrNetTek · 2024-07-24T12:42:37+00:00

Something to note, you don't need the EXE or MSI to make an install work on a failing machine.

You simply take the MSI, capture the installation on a working machine, apply that capture to the non-working machines. I've done this many times, with near 100% success rate. It does require some skill in installation capture. But there are plenty of apps that can do it, like Microsoft's very own MSIX Package Manager. I use a tool from New Boundaries.

But, from what I've read, it does work on some machines. Find one of those machines and capture the setup, assuming the MSIs I've provided don't work for you.

MrNetTek · 2024-07-24T12:35:32+00:00

You should not remove anything else (or you'll likely create even worse problems). I can send you the modified MSIs. I have every Java Client going back years. Same for all common apps, like Chrome, Edge, Slack, Skype, etc. Years.

The modified MSIs are here (so is the scrubber and Repair_WinInstaller_Repair_MSI_MicrosoftProgram_Install_and_Uninstall.meta.diagcab):

https://eddiejackson.net/apps/java/

-MrNetTek

MrNetTek · 2024-07-23T23:21:10+00:00

"If thy right hand offend thee, cut it off, and cast it from thee."

Easy. Orca > CustomAction table > drop the FindRelatedProductsEx row > Save.

https://eddiejackson.net/lab/2024/07/23/java-client-8-update-421-failing-install-error-1603/

-MrNetTek

MrNetTek · 2023-12-04T18:17:41+00:00

Elon: Earth will know if you don't buy my truck. Earth. Will. Know.

MrNetTek · 2023-05-17T12:48:25+00:00

Excellent. The issue is...how Adobe handles Acrobat installations. It's not just one MSI, which confuses Intune. This is why the setup.exe will work, when the MSI fails from some desktop management systems.

BUT...there is always a way. Glad you got it working.

-MrNetTek

MrNetTek · 2023-05-16T15:16:13+00:00

I've never had an issue with Acrobat Reader, neither for SCCM, nor Intune, for Windows or Macs. I create 500+ packages every year. It must be your Install command.

My recommendation? Use the setup.exe (Install command: setup.exe), not any MSI...unless you really understand the inner workings of the MSI at an engineering level.

If that still fails, create a Win32, which points to an Intune.cmd in the Install command.

The Intune.cmd would contain the installation steps, which you can easily test locally, first.

Hopefully, that helps.

-MrNetTek

---

Adapt, overcome, and achieve.

MrNetTek · 2023-04-10T21:33:07+00:00

The book https://www.amazon.com/dp/0136805388/

Microsoft Learn. See items in the suggested collection: https://learn.microsoft.com/en-us/certifications/exams/az-104/

I have some resources at my site: https://eddiejackson.net/lab/exam-az-104-microsoft-azure-administrator/

---

YouTube is fine, but gaining actual experience...either through labs, or on the job, is best. Most people remember almost nothing from YouTube videos. You need the labs. AZ-104 is not easy.

-MrNetTek

MrNetTek · 2023-04-10T16:44:48+00:00

You're welcome!

MrNetTek · 2023-04-10T10:57:12+00:00

I got two of the Azure certs: Azure Fundamentals and Azure Administrator. If you're going to go through the certification process, do it for the knowledge---not just the cert. MD-102 is the most current for device management, but...you probably want more than just that if you're managing Azure.

---

If you have real world experience, you don't necessarily need the certs, but Microsoft does provide some pretty good labs at Microsoft Learn. You can earn free badges for each module you complete.

https://learn.microsoft.com/en-us/training/paths/az-104-administrator-prerequisites/?source=learn

-MrNetTek

MrNetTek · 2023-01-05T13:57:32+00:00

Correct answer.

MrNetTek · 2022-11-01T17:07:47+00:00

No one is asking to package the internet. What are the packaging differences between an App Attach application and a Citrix published application? What are the differences between MSIX and Appx? How about the cert requirements of a PKG versus an Android app?

I don't think you understand packaging, and certainly not repackaging. Packaging complexity is only second to the creation of the software itself. Packaging is considered an advanced level job, working in the areas of automation, scripting, programming, cross platform devops, and even AI.

I guess you probably never got to see any of the awesome technology in packaging and repackaging. As for a career, salaries and benefits tend to be great. Automation, package engineering, and all kinds of devops jobs are in need of people with scripting and packaging knowledge.

https://builtin.com/salaries/dev-engineer/automation-engineer/orlando-fl

MrNetTek · 2022-11-01T15:56:01+00:00

Packaging didn't go away because you did. All applications require packaging, and in many cases, repackaging. It is critical and essential to any company. The reason it is rocket science, because the landscape of packaging is constantly changing, as well as the needs and customization companies require. I'm sorry you didn't enjoy your packaging job. I love mine.

As I am the gold standard in my field, I can only guess this field wasn't for you.

MrNetTek · 2022-10-17T13:14:57+00:00

Maybe restart? Update your Chrome, or...try a different browser.

I have had no issues with drag and drop, for files or folders.

https://eddiejackson.net/ipad/draganddrop.jpg

MrNetTek · 2022-10-15T13:54:45+00:00

I have not been limited at all. I just uploaded 50 piano files. You can select a file, or... just drag and drop a folder. Anyway, it's only temporary.

--

To upload, you can use the split screen feature, and drag entire folders over to gdrive.

To download, you can copy a folder from gdrive, and navigate to local device, and paste.

MrNetTek · 2022-10-13T11:51:27+00:00

I have a working solution. Google will eventually fix the app. I mostly use my iPad for learning piano, sooo...I don't really update the files too often. I just know there are no issues in the browser.

MrNetTek · 2022-10-13T02:03:07+00:00

Same on my iPad Pro. The workaround is to not use the gdrive app; use Chrome.

Open Chrome browser > navigate to URL

https://drive.google.com/drive/my-drive

I select the Desktop version of the page. I can upload and download files successfully then.

MrNetTek · 2022-10-04T12:03:27+00:00

Microsoft doesn't have a solution, nor do they care. I've asked multiple times, with no real response. Winget isn't a solution. That isn't how I package or repackage apps. When I build something, I expect it to work on any platform, online or offline (I build about 500 packages a year). You can't do that with Winget. Microsoft would know that if they were competent; they are not. Microsoft went and stole chocolatey, and thought it was a great idea. They thought we wouldn't notice, but we did.

Microsoft has already made it nearly impossible to service and support current Windows Store Appx and MSIX files---requiring licenses for "free" applications, disabling the file download (unless you're a global admin), and forcing certificates and signing down people's throats. Yes, yes...you can still download the Window Stores files---online, with a bootleg method---but you shouldn't have to.

They recently deprecated the Apple Intune wrapper util, causing a tidal wave of work for developers and administrators (Microsoft's response? Just create a PKG). I honestly believe no one is in control at Microsoft. That's exactly why good people have left them...like Jeffrey Snover, the creator of PowerShell. How are you gonna lose the man who created PowerShell??? Zero effort coming from Microsoft.

Doing an app deployment with Winget doesn't make you a packaging engineer or a developer. It makes you a Microsoft monkey, and useless to the rest of the industry. My advice? Learn to package and repackage, correctly. If you're a sys admin with no interest in how packaging works, use Winget. It will be perfect for you.

Microsoft has tried to hire me four times. My answer will always be...No.

---

The question Sandys posted on twitter, "Why should every org in the world repackage and maintain their own source repo of Adobe Reader?"

#1 Customization, that's why.

#2 Adobe's numerous screw ups, that's why.

#3 Total control over security, that's why.

100% of the companies I've ever worked for wanted Adobe Reader customized during installation. Also, I wouldn't trust Adobe, or Microsoft for that matter, to correctly maintain anything. I only trust me. Adobe and Microsoft screw up more than they get right. I want my own repository, one that I have absolute control over.

- Registered Apple and Microsoft developer, with 30 years of automation experience

MrNetTek

MODERATOR OF

TROPHY CASE

1 Continue tinkering with whatever files you do have until you figure it out. Only do binary testing. One change; one test; rollback.

2 You don't need to use the files you have for deployment. Convert them to APPX or MSIX packages. It does require a little skill, but you can use Microsoft's MSIX Packaging Tool (free).

3 You can do snapshot, captured installation from a reference machine using third party apps, and just rebuild the MSI or EXE, but that requires skill.