• 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
#1
Can PatchMyPC automatically set dependencies on imported ConfigMgr apps?  For example, Devolutions Remote Desktop Manager now requires .NET Desktop Runtime 8 and the install fails with an ambiguous error code if it's missing.

If I set the dependency myself in the ConfigMgr console, will PatchMyPC overwrite it when a new version of the Remote Desktop Manager is released?  If so, is there a way we can have the PatchMyPC Publishing Service add that dependency?
#2
Can we get the names for the .NET Desktop Runtime fixed in the ConfigMgr Apps tab?

There is a .NET Core Runtime and a .NET Desktop Runtime and they're not the same thing, but you've got it listed as .NET Core Desktop Runtime, which doesn't exist.  I had to import it and then go into the file system to see what .exe it actually downloaded to confirm that it really was the .NET Desktop Runtime before deploying it out.

I suppose it doesn't matter to me anymore now that I've confirmed it, but it could save some other overly cautious people like me some confusion.
#3
I'm not sure exactly when this started but the PatchMyPC log is full of this message repeated for every application I have checked:

An error occurred while querying the SMSProvider for applications using source path [<path>]: The RPC server is unavailable.  [System.Runtime.InteropServices.COMException]
An error occurred while processing an Installable Application: The RPC server is unavailable.  [System.Runtime.InteropServices.COMException]


Software Updates seem to be publishing fine, though.