Messages

Perfect!
Thank you and have a nice weekend!

Great news, thank you Andrew!
I guess it will be stated in the notification emails right?

Hi Andrew,

I checked on Microsoft's SharePoint resources for the VC++ requirements and it seems that we can go with 2015-2022 for the versions of SharePoint 2016 and onwards.
Also checked our servers and discussed this with our SharePoint Admins and we reached to the conclusion of using that one and replacing the 2015-2019 were it is installed.
Did you do any research from your side?

Yeah, we originally added DDM 2.x to the catalogue where it would uninstall 1.x. However we found supporting documentation that Dell suggests DDM v1 and v2 are independent and v2 isn't always the best option for some monitors. Therefore we added it as a separate product and fence of detection/applicability between the major versions.

That makes a lot of sense, the .Net 5 requirement is also a blocking issue as many of us don't include it in the standard list of software/runtimes.

Word of mouth suggests Dell are releasing an update for DDM 2.x next month to include a newer version of .NET.

Nice to know Adam! Thanks for sharing that info.

Our plan is to remove the VC++ 2015-2019 and move to 2015-2022. Microsoft no longer provides updates for 2015-2019, and 2015-2022 should cover 2015-2019 when it is installed (this is why it does not let you install 2015-2019 when 2015-2022 is already installed, they are actually the same app and 2015-2022 is just a newer version).

We'll need to adjust the applicability rules for 2015-2022 to allow it to upgrade 2015-2019, then remove 2015-2019 from our catalog. I expect this to be completed by the end of March 2023.

Thanks for the reminder on this!

I had a discussion with a SharePoint Admin colleague because I noticed that the installer installs the 2015-2019 redistributable, so AFAI understand, it will not be easy to get rid of it (I would love to have a clean environment with less versions to maintain).
Could you check with the SP PG if this is a hard requirement and if it can be covered by the 2015-2022 redistributable please?

Clock is ticking for MMS-MOA

Thank you very much Andrew!
If you're going to MMS-MOA in May, it would be great to meet there and talk about the product.

Dear moderators,

I was checking the options to change my profile's avatar and in the list there is an option named [custom], while I was browsing through I realised that those are the uploaded avatars of the forum's members.
I would like to request you to hide this option because it is exposing personal data to other users without consent.

Thank you

Hi Andrew,

Just checking if there is any development on this request.

Thank you!

Hi TimothyG, it seems this version is not a straight forward upgrade to 2.0.0.135 from 1.56.2110 and requires more testing.

First thing it's x64 only now I think.

Secondly the installer now is 62MB with a new Logo and new vendor. The previous installer was ~900KB.

Thirdly, it doesn't remove the previous version, and it seems the silent installs witch has changed.

I will update you as soon as I can.

4th The new version works much better than version 1.5 

I was about to request the detection of <2.0 versions and their removal before installing version 2.x on x64 devices, glad I found this thread!
However, I would like to ask for this to be extended to the updates section also, is this feasible Adam, Ben?

Hello PMPC Team,

As always, thank you for your great product and support.

I have both runtimes selected (for both architectures) in the ConfigMgr apps list, their updates are also served, the issue I'm facing is that when Visual Visual C++ 2015-2022 runtime is installed and subsequently Visual C++ 2015-2019 update tries to install, it fails because the 2015-2022 version is newer and supersedes it.
I would like to propose the following:
1) The detection rules of 2015-2019 should detect the newer version(s) and skip the installation for a full app or an update.
2) In the PMPC GUI, there must be a blocking function that grays out and deselects (if selected) the older version if a newer is superseding it (for the 2015-xxxx ones). Also a message to remove the old application would be nice.

Do these proposals make sense to you?
Are the above feasible?

With regards,
George Simos

Please check the Application Event log, in two cases of mine, the following events are logged:

1) Event ID 10005, Source: MsiInstaller, Level: Error, User: System, Product: Adobe Acrobat Reader DC -- Error 2753.The File 'acrosup64.dll' is not marked for installation.

2) Event ID 1024, Source: MsiInstaller, Level: Errors, User: System, Product: Adobe Acrobat DC (64-bit) - Update 'Adobe Acrobat Reader DC
(22.001.20117)' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127

3) Event ID 1036, Source: MsiInstaller, Level: Information, User: System,Windows Installer installed an update. Product Name: Adobe Acrobat DC (64-bit). Product Version: 22.001.20117. Product Language: 1033. Manufacturer: Adobe. Update Name: Adobe Acrobat Reader DC
(22.001.20117). Installation success or error status: 1603.

You can enable logging by adding the registry keys detailed here: https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuous.html?highlight=asian#creating-msi-logs-on-windows.
Also a possible solution is to run the Acrobat cleaner (AcroClean) tool, I will test that and come back, the tool can be found here https://www.adobe.com/devnet-docs/acrobatetk/tools/Labs/cleaner.html.

Coming back for this, the best way to get the Model Name for a deployment type (for one or multiple applications) is by using the SCCM powershell cmdlets.
Example:

Code Select Expand

Get-CMDeploymentType -ApplicationName "KeePass*" | Select-Object -Property LocalizedDisplayName, CI_UniqueID, ModelName | Out-Gridview
You can omit the CI_UniqueID but it is a good thing to have and compare with ModelName.

Thank you again Jake!

Very nice, thank you!

Hi Jake,

Thank you for the quick response, I will check the Deployment Type ID if it matches and will revert if needed.

Hello,

I'm in the process of replacing multiple versions of KeePass (1.x and 2.x, MSI and EXE Setups) with the latest one that is based on MSI installer.
However, I don't have all the previous versions covered by PatchMyPC due to quite old installations, manual ones and the application retention I have set in the publisher.
Because I have either on hand or have located and downloaded all the installers needed, I have created respective applications to be superseded by the latest one but also provide the uninstall command to remove the old ones.
I wanted to use the ability of the "Interactive user notifications" feature in PatchMyPC and use the binaries and modified Package.XML and Detection Scripts as the base of these applications (something that I have done a couple of times succesfuly so far and it is really cool).
However, setting the notification settings and republishing the content for the latest application's version, I noticed in Package.XML the following (sample application based on the Setup.exe installer):

Code Select Expand

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Package>
  <VendorName>Dominik Reichl</VendorName>
  <ProductName>KeePass v1 - EXE Install</ProductName>
  <AppNameFilter>KeePass Password Safe%</AppNameFilter>
  <AppVersionFilter>1.40</AppVersionFilter>
  <SilentUninstallArg>/verysilent</SilentUninstallArg>
  <CommandLine>/MainFile=KeePass-1.40-Setup.exeÿ"/MainArg=/VERYSILENT /NOCLOSEAPPLICATIONS /NORESTARTAPPLICATIONS /NORESTART /SP- /SUPPRESSMSGBOXES"ÿ/BlockingProcessPolicy=Notifyÿ/UserNotificationTimeout=120ÿ/PreventConflictingProcessRestartÿ/NotificationPolicy=AutoCloseÿ/FocusAssistPolicy=DiscardNotificationÿ"/ApplicationName=KeePass v1 - EXE Install"ÿ/[b]ApplicationID=2e630e69-0b39-4b2b-a6c0-3cc3bf8b551b[/b]ÿ/KillProcessList=KeePass.exeÿ/ShortcutFileName=KeePassÿ/LoggingSwitch=/LOG={path}ÿ/PrefixInstallLogÿ/LoggingPath=C:\windows\ccm\logs\PatchMyPCInstallLogsÿ/LogRetentionDays=28</CommandLine>
  <InstallationBehavior>System</InstallationBehavior>
  <PackageID>TST123AB</PackageID>
</Package>

So the ApplicationID is something I haven't noticed before (as it isn't present if you don't use the user notifications feature), I wanted to ask the following:
1) Is this GUID generated arbitrary or not
2) If not, is it related to any files accompanying the applications such as the .exe, .msi, .dll ones?
3) Last but not least, if it isn't related, can I create one by myself to add it in the applications created by me, in order to leverage your solution's functionality?

Thank you.