Messages

Currently with the Cloud deployments there is not a way.

Below is our docs on how the Sync Schedule affects the required delayed between rings and why.
https://docs.patchmypc.com/installation-guides/patch-my-pc-cloud/deployments/update-rings/how-the-sync-schedule-affects-update-rings

We do have an 'IDEA' on Feature Request page to allow the configurability of the Availability and Deadlines of Assignments similar to our On-Prem Publisher. I would suggest voting on the Idea so you're notified when it becomes available.
https://ideas.patchmypc.com/ideas/PATCHMYPC-I-4453

There is also an option available if use the 'Unified Installer' of Acrobat x64 to allow 'Reduced Mode'.

[HKLM\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown] bIsSCReducedModeEnforcedEx = 1 (dword)

https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/singleinstaller.html#registry-setting-to-enable-reduced-mode

If you deploy the Adobe Acrobat Reader x64, if your users has a CC license for Pro, they should be able to just select 'Sign In' and the installation will upgrade it self to 'Pro'

Hey Jay, confirming I can see your post.

I was able to repo this in the lab. Issue is that the Adobe installer is creating the icon after we initially delete it during our processes.

But, if you add 'DISABLEDESKTOPSHORTCUT=1' to the command line, the shortcut will not be created by the installer.

You can do this by utilizing the 'Modify Command line' feature.

I can confirm that there are no desktop shortcuts present until AFTER the 64-bit Acrobat is installed.

Do you mean "there are desktop shortcuts present"? Apologies if I'm misunderstanding this.

I'm testing this in the lab right now to see if the Shortcut is not deleted

Hi CODRyan,

Is the issue that during the Replacement of the 32-bit Acrobat to 64-bit Acrobat, the 'C:\Users\Public\Desktop' Icon that is for the 32-bit Acrobat, is left behind?

Hi MParker,

Yes, it is possible that the cleanup tasks don't run because of a reboot, or some other scenario that kills the scriptrunner process prematurely.

Were there any other updates that ran that required a restart?

A scenario that can happen if you use the Restart grace period, and update runs that needs a reboot, the user will get the prompt about the restart, the user chooses to reboot now, but another update already started running and gets cut off early.
Intune's Restart Grace Period Simplified - Patch My PC

Hi AyoubAnouar,

The team has added updated the 32-bit x86 version of Zotero and also added the 64-bit x64 version to our catalog as of yesterday 8/20/2024
https://patchmypc.com/patch-my-pc-catalog-update-08-20-24

You should now see the latest version in the catalog as 7.0.2

Hi AyoubAnouar,

Since this is a new Major release from Zotero, version 7 will get added as a new 'Product' within the PatchMyPC Catalog. This new version had a lot of changes and needed a bit longer to get into the catalog.

Plan is to have it available some time this week!

Hi PS_Alex,

That is something that has been mentioned before. There is an idea on our Idea's page for an option just as you described. I highly suggest that you head over there and give it an upvote as our Dev team does use this to Prioritize what they work on.
https://ideas.patchmypc.com/ideas/PATCHMYPC-I-4019

Currently what you can do is pass the 'ReturnCode' from the main installer to your script and act accordingly. Below is a link on you can do that and also an example of a script taking in that return code and doing something with it.
Pass Variables into Pre and Post Scripts - Patch My PC

You could have your script do this and do a check at the beginning to only run the main part of the script if you get a successful ReturnCode from the Main script.

He @djwatson2,

If you want to open up a support case, you can use the below link:

https://patchmypc.com/technical-support

I'm also wondering if you are running into a detection issue as well.

Hi @djwatson2,

I did some testing with this.

Code Select Expand

& "$PSScriptRoot\teamsbootstrapper.exe" -u
This command does run fine, but I think the problem might be with the exit code it generates. I don't have a client with 'Old' teams to test with, but when running it on a client without 'old' team I get an exit code of '-2147024809' because it can't find any 'old' teams installs.

You may want to modify the script to something like below

Code Select Expand

Start-Process -FilePath "teamsbootstrapper.exe" -WorkingDirectory "$PSScriptRoot" -ArgumentList "-u" -Wait
Exit 0
So that no matter what, the exit code from the script is always 0, and there is also no output displayed.

[psexec.exe -i -s powershell.exe]

Hi @djwatson2,

The error code from the Post Script can be found in the PatchMyPC-ScriptRunner.log

Depending on how you are deploying the application it can be located in a few different places:

When troubleshooting Intune application installation errors on a client:

• %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
• This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Company Portal.

When troubleshooting ConfigMgr application installation errors on a client:

• %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
• This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.

Hopefully can have some additional information to help troubleshoot.

The other way to troubleshoot this is to try and run your powershell script as SYSTEM by utilizing 'psexec'

• psexec.exe -i -s powershell.exe

& "$PSScriptRoot\teamsbootstrapper.exe" -u

I'll look into if this is the best way to call the exe from within your script.