• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 
Menu

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.

Show posts Menu

Messages - Liviu (Patch My PC)

#1
And thank you for letting us know we missed this one.

Automation can break at times and cause us to miss an update, we are always grateful of our customers when they let us know!
#2
The latest version is now part of our catalogue.
#3
Hello muja1913,

Thank you for letting us know we missed this release.
Our automation broke for this software and failed to let us know a newer version is available.

It will be added to our catalog with today's release.
#4
Hi Kevin,

Would it be possible to provide more details on what you are looking for?
We only support version 8.0 and the latest, which is 8.3.
We don't support version 8.1.

The applicability rule for version 8.3 (MSI-x64) is configured so it will not upgrade devices that have version 8.0 (x86) installed.
#6
Hey Martin,

If the "failure" exit code - in your case, the user snooze option - is marked as "retry" in the win32 app properties, Intune retries the install every 5 minutes for 3 times, then every 24 hours.
https://patchtuesday.com/blog/tech-blog/win32app-retry-interval/#scenario2

If you'd like us to, collect these log files from the device and email them to our support inbox and we'll have a look.
#7
The latest version of this software is now part of our catalogue.
#8
Thank you for letting us know we missed this. It will be added with today's catalog release.
#9
Providing a quick workaround for those that need to publish one app only, overriding the delay:

1. Go to the ConfigMgr app tab --> Options --> and uncheck the delay option --> OK
2. right-click on the software you want to immediately publish without delay and choose the "Publish this product during the next manual sync" right-click option.
3. Go to the "Sync Schedule" tab --> press the "Run Publishing Service Sync" button. You'll be presented with a prompt confirming that only the software you selected at Step #2 will be published.
4. Wait for the software to be published.
5. Once that software is published, go back to the ConfigMgr apps tab --> Options --> Enable the Delay option again.

Not the perfect workaround, but should be a viable one until we have a better option in place.
#10
The process should be the same then.

Duplicate lines 189-201, modify them to copy your json and your new xml file.
It should work.
Let us know if it won't.
We recommend running a test on a few devices before deploying this to production.
#11
Hello asgeirk,

Are the config files for those additional modules XML files as well?

If that's the case, you can specify those additional xml files in the "Additional files" section, and modify the script we use as an example to copy those additional file to the right destination path.

You can duplicate lines 189-201 and adjust them to account for your new configuration files.
#12
That's definitely a step forward, thank you for the update!

If you run into any other issues, let us know!
#13
Hi EricS,

Thanks for reporting this.
This issue will require further investigation, can you please open a support case with us?

I checked the applicability rules for this update, and they look correct.
I'm curious which VLC update you are deploying - x64/x86 and MSI/EXE.
I'm also curious to look at the VLC version installed on a device which is listed as already compliant.
Can you please run this script on such a device?
https://github.com/PatchMyPCTeam/CustomerTroubleshooting/blob/Release/PowerShell/Export-PMPCInstalledSoftware.ps1

It will export a CSV file with app information.
It will allow us to verify the applicability rules for the VLC update.
#14
hey Madd,

Replying to this while Ben is out of the office.

At the moment, due to limitations in our detection scripts, any software with the same product code for each version cannot be used for updating the software, as it's going to be detected as installed.

We are working on updating the detection script template to account for such software as well, and look beyond the product code and check the DisplayVersion as well.

We are offering such software as an Intune App for customers that would like to install on devices which don't have it installed at all.

If you'd like to use it for updates, you would have to manually edit the detection rule and set it to check the product code AND the version instead of using our script.
This will have to be done manually every time there is a new version, unfortunately.

As I mentioned earlier, we are working on improving our detection scripts. If you'd like to be notified this will be complete, please upvote this idea on our UserVoice.
#15
Hey JoeH,

Unfortunately, that isn't the case.
Intune doesn't collect app architecture information from the devices.
So, if one device has "Google Chrome" installed, the Scan feature will show "1" device to both Google Chrome x64 and x86.

It only works correctly for software which the DisplayName contains the architecture: e.g. Notepad++ (x64).