Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Adam Cook

Pages: [1] 2 3 4 5 6 7
1
May you please share the below logs:

%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Company Portal.
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log

And also the .csv produced from this script: https://github.com/PatchMyPCTeam/CustomerTroubleshooting/blob/Release/PowerShell/Export-PMPCUninstallRegistryHives.ps1

Feel free to upload to patchmypc.com/share.

2
Is this for ConfigMgr/WSUS software updates, or Intune updates?

3
Through the ideas page, please! What's the application?

4
Interesting. Thanks for sharing!

5
Yes, absolutely.

Using the right click option Manage assignments, you can designated AAD groups to be applied to newly uploaded packages and also configure the availability/deadline between each AAD group. This will allow you to create a phased/wave release of updates in a timely fashion.

6
Do you experience the same if you packaged Teams manually and used that in a task sequence? That would be indiciative of whether it's a Teams issue, or perhaps something we're doing at the time of install with the Teams installer.

Here is a link to the installer we use (offered both 32bit and 64bit):

Quote
https://statics.teams.cdn.office.net/production-windows-x64/1.5.00.5967/Teams_windows_x64.msi
https://statics.teams.cdn.office.net/production-windows/1.5.00.5967/Teams_windows.msi

and here are the parameters we also use:

Quote
Reboot=ReallySuppress ALLUSERS=1 /qb

7
I'm sorry, I cannot reproduce your described behaviour.

8
This issue is being caused by Techsmith themselves. There seems to be a node within their CDN that has an unsigned version of the Snagit 21 installer being served, and if you're unlucky enough to hit that node the Publisher will fail to download with that error.

We have a ticket open with Techsmith to make them aware of the issue, but have yet to receive an update, unfortunately.

My apologies for any inconvenience this has caused you

10
Yeah absolutely, if you know the UninstallString you can totally do that. Product codes _generally_ change between versions of software, so if that product code is consistent across all the devices you're targetting, you should be good - otherwise that's why the previously mentioned script is good. It helps you trigger the UninstallString if all you know is the product name, and have a mix of versions of said product.

11
I tried deleting that key. I attached a picture from before I deleted it.

After deleting it I restarted the computer and logged in, but I still only see the teams machine wide installer in my apps and features, so I don't think it's running for my profile. Any other suggestions? I really appreciate your help Adam!

Perhaps you could share %LocalAppData%\SquirrelTemp\SquirrelSetup.log?

12
It looks like when I run the 64 bit Teams install it puts the folder in Program Files (x86), but that Run registry key is pointing to the Program Files folder I attached a screenshot. Is this a mistake by Microsoft?

No, because as far as I know it's in the WOW6432NODE key path of the registry so it will resolve to the Program Files (x86).

I can actually reproduce this. Teams isn't starting for me.

In my %LocalAppData%\SquirrelTemp\SquirrelSetup.log I saw the below whenever I logged on, and when I tried to ran the command line in the Run key manually:

Quote
2022-03-24 10:08:45> RegistryService: RegKeyExists: HKEY_CURRENT_USER\Software\Microsoft\Office\Teams has PreventInstallationFromMsi. Data - 1

I had to delete the registry value PreventInstallationFromMsi under the key the log references in order for Teams to start. Does this work for you too? I was testing on Windows 11 which does come with the new 'home' Teams app - I wonder if that's relevant.

13
You could deploy it as a proactive remediation script in Intune, or package it in a custom Win32 package - both could work. I think the former might be easier.

It's general enough to work with any software that appears in the registry ARP keys and has an UninstallString registry value with data in it. It could do with some improvements, eg accept wildcard for -DisplayName parameter, and perhaps also look for QuietUninstallString registry value, too.

14
Microsoft Teams generally creates a Run reg value for all users to execute Teams for each logon. You can learn more about the Run / RunOnce registry keys here if you're unfamiliar: https://docs.microsoft.com/en-us/windows/win32/setupapi/run-and-runonce-registry-keys

To my understanding, Microsoft Teams creates the following Run registry value (see below image). Do you see this on your devices after installing Teams?


15
It doesn't need to have execution policy set to bypass, only if your devices have an execution policy configured where they can only run PowerShell scripts if they're signed by a trusted certificate. More information here:

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies
https://adamtheautomator.com/how-to-sign-powershell-script/

Pages: [1] 2 3 4 5 6 7