Messages

I love PSADT and we have it doing lots of fun tricks. That said, rather than sourcing a big workaround here, do it natively or use a different psadt function. I'm typing on a phone so please forgive bad syntax.

To wit:

I'd put the old msi in the SupportFiles folder.

Then, I would make a pre-install step that checked for the existence of the old app, whether by wmi query or just a test path or file version or date or reg path or whatever feels best.

Then either:
Execute-Msi -action "uninstall" -path "$dirSupportFiles/msiname.Msi"

Or just do it with native powershell, something like
Start-process "msiexec.exe" ArgumentList "/x $dirSupportFiles/msiname.exe /qn /l*V c:\logpath\log.log"

Either way reference the old msi in the package contents. Wee bit sloppy but then you don't need to use supersedence or guid's  or worry about cached msi availability or distribution point content of retired apps or any of that mess. 

Thanks Andrew.

I did go ahead and publish the latest version for testing. We never update agents in place so I suppose it won't hurt me to always let it do bleeding edge updates, splunk is just weird. 9 to 9.1 introduced breaking changes, which is probably why you have it as a separate app! Then they iterated 9.1.4 to 9.2 in less than a month.

Appreciate the responses!

Thanks to you both.

Splunk, at least ours, requires a lot of customization. I'm afraid to let it go latest because our infrastructure policies mean we can't go bleeding edge until a burn in period is over unless there's a critical vuln to mitigate—but also, no unnecessary changes for the sake of changes especially with agents.

But...every time a new minor version is a new app, I have to redo the customizations.

I suppose I should let it roll with latest and change how I'm deploying it? Maybe I'm overthinking it.

No. It won't. Not yet, anyway. You need to build an app that searches for the machine wide installer, uninstalls it, then clears out the app folders for all users %appdata%/local/microsoft/teams, then installs new teams. I know you said that you have mostly user installs, the easy way to nuke them is just nuking those folders. I can share some code if you'd like, I used PSADT.

Note that you will need to coincide this with changing your enterprise tenant default to new teams.

You CAN coexist them and then change default and then remove as well, just know that once the new flavor is there all the old flavors will stop updating and sit there vulnerable forever---well, assuming you change your default.

We're configured for 9.1 updates/apps, I recognize that 9.2.1 is a new (minor? major?) version, however 9.2 isn't listed as an option in the list. I'm guessing "Splunk...Latest" is probably what I want to be subscribed to although in a cursory search I also don't see 9.2.1 listed. Please advise

Hmm that's odd. I will investigate why we aren't seeing it then. Thank you and sorry for the faulty request.

Apologies if I'm in the wrong place. Adobe is always a challenge. The official update page for ADE does not list the most recent version, it shows the last version which PMPC just updated a month ago (4.5.11.187303):
https://www.adobe.com/solutions/ebook/digital-editions/download.html

The new version is only here, but addresses critical score CVE's:
https://helpx.adobe.com/digital-editions/kb/security-update-april-2023.html

Any chance we can get this...soonish?