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

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 - lee-mecm-admin

To reiterate, what we're seeing is after the deadline has been surpassed, the mechanism that is supposed to force close the running process is not working.  Confirmed on 2 end user's machines this morning.
Is there a setting I'm missing or do we just count this as a glitch with the ccm client?
I have attached a ss of how all updates are set for conflicting processes.

As I was skimming through, I cannot believe I did not spot the drop-down for Focus Assist...  :o

Now I know what to change for the next round of updates.  However, it still does not explain why I'm getting about a 10% failure rate more than 24 hours past the deadline.  And now, we're more than 72 hours past the deadline and we're down to about 5% failure rate.  Checking through the logs, only a fraction of those failures are on machines where focus assist was listed as I mentioned previously.

I've recently started seeing an uptick in software update failures.  After closing inspection, I noticed that:
User in session 1 [xxxxxx] has exited with command: Notification cancelled (Focus Assist enabled)
User has blocked the update installation process (A conflicting process is still running).
End of Script Runner. Exit code is: 1602

Searching this forum and scowering the interwebs, I'm not finding much in the way of whitelisting SCNotification with Focus Assist/Quiet Hours.

I did come across this command line though:
<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"ÿ/ApplicationID=2e630e69-0b39-4b2b-a6c0-3cc3bf8b551bÿ/KillProcessList=KeePass.exeÿ/ShortcutFileName=KeePassÿ/LoggingSwitch=/LOG={path}ÿ/PrefixInstallLogÿ/LoggingPath=C:\windows\ccm\logs\PatchMyPCInstallLogsÿ/LogRetentionDays=28</CommandLine>

Any help will be greatly appreciated.
I think that's what we need to do!

The interesting thing is why it worked before though, with no change(s) to the certs since we began using this product-- which is great by the way!

I'll get back to you once I have time to look through this in more detail.  Thank you.
We are getting at least 40% error rate on most deployments as of late with the error code and message in the subject line.

There doesn't appear to be any common denominator.  All machines are in the same OUs they have been, same device policies, etc...

This started happening about 2 weeks ago or so, before that very little issue with app deploys and patching.
Primary site: MECM 2111 / Server 2019

I have multiple errors: WebClient reported an error during download: The request was aborted: Could not create SSL/TLS secure channel.

Most of the 3rd party updates and full content downloads are working just fine, however the ones that are failing are providing the same error message.
However, if I navigate to the download URL in Chrome, the download succeeds.  What can I do to resolve the Publisher from failing when attempting to retrieve these updates?