rodri

Comments

  • Thanks frgpugs. The Support team has given me the guidelines to install the external Adobe Reader DC catalog, and it was pretty good in getting missing updates for Adober Reader in PM. I have also manually tested the remaining Adobe packages and they seem to respect the customizations like "disable auto-updates". I will…
  • Thanks for that! Actually the app owner asked my that question and have been able to answer it!!
  • Excluding particularly older versions would make sense. However, others like adobe AIR still use the uninstall key in the registry when installing latest versions. Perhaps the Shockwave doesnt use it for a particular reason...
  • Does it mean I need to configure external cats not just for Adobe Reader, but for every Adobe software that I have? Full packages worries me as long as the customizations can be lost, isnt it?
  • I doubt it, as long as the patch doesn't even uninstall from the endpoint. Windows marks it as uninstallable and msiexec complains about it or UI option is not available. On the other hand, I have PM integrated to SCCM. I believe update management is only applicable when PM server has direct connection to the endpoint.…
  • charlesnm​, why would you use (upgrade only)? Is it to prevent installing a vanilla version without any customizations you might have in your environment?
  • The administration guide says that Patch Manager is configured as a publishing server. The reality is that the publishing server is the upstream WSUS in the environment, not PM. So there are some definitions that make you feel stuck especially when it is most needed. A guide to migrate Publishing certificate, including how…
  • I get that, no different to what I thought. Interestingly enough, it seems that shockwave doesn't create this Reg Keynormally present for other apps: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Shockwave Player so that a NOT rule will always be true when the application is found to be…
  • That's clear. Just wondering if that is the case, then why the solarwinds one stopped updating on July 2016? At least for Adobe Acrobat Reader DC, not for Flash Player or any other Adobe Product?
  • Hi Dang, thanks. On Thursday the support guys help me introduce a manual "External" catalog from Adobe. Is this how it is supposed to work? The out of the box catalog was doing fine until August, and then stopped updating. Is there something wrong with the default catalog? thanks.
  • Follow kellytice advice. That should take you to the end. Check sccm logs to make sure the sync between sup and sccm is working and then you will see your update reflected in the software updates menu of sccm console.
  • Hi zDavid, how did you manage to solve the problem? How did you overcome the SCCM issue with the download step within the SCCM console?
  • fevinsetter, Did you get a way around it? I have seen in other forums a suggestion to push a dummy package and as a pre-requisite run a cmd from the cmd line, that will run a silent uninstall of Spotify. If you look for "spotify uninstall silent" in Google you might find the following: Uninstall spotify – Support When…
  • I have a reason to discuss with the packagers in SCCM how not to break standard registry modification when doing customisation, so that Solarwinds becomes standard in this environment... Thanks kellytice.
  • kellytice I understand and agree with you. However, I was trying to manipulate the actual msp, with no luck. I actually modified the uninstallable regkey and I was able to uninstall adobe reader DC. Which is like forcing something without knowning the consequences. I read the msi+msp in orca.exe and it seems that the msp…
  • Start in PAS by doing this: Patch Manager Diagnostics (Full) - SolarWinds Worldwide, LLC. Help and Support Then in WSUS or SUP: Log Files for Software Updates
  • For the most part the admin guide structure is difficult to follow. I would change it all to reflect the needs of each customer: standalone wsus sccm. At times sccm and wsus gets mixed. Also, though is not part of the product there are steps in SCCM that are not documented and are required to get a patch finally pushed to…
  • finally, the application settings didn't have the sender (email and name) configured. It is now all ok.
  • If I check the WSUS folder in the certficates snapin within the WSUS server I noticed the new certificate has a private key available, whereas the old one doesn't. I wonder if the rollover just deleted the old private key and this process is not reversible?
  • So far my test indicates google msi for enterprise standalone packages respects the auto-update previously setup. Anyone has had any similar experiences? Thanks.
  • Has anyone noticed that when downloading an older package of Chrome (54.0.2480.71 is still available in PM console as containing not only metadata but also media as well), Google actually makes you download the latest version of the installer?
  • Thanks Dang. Coincidentally I have received it in last night sync, I don't know if related to the case I opened with Solarwinds.