Firefox patch using Shavlik in SCCM CB 1706 and keep current config

December 10, 2017, 8:05 pm

≫ Next: Installing on Server 2016

≪ Previous: Deploy on Multiple Machines at a Time

$

0

0

Hi,

 

I am new to Shavlik and am having issues with trying to patch Firefox from version 49.0.1 to 57.0.1 and keeping the current configuration we have in place.

If i patch the version then it wipes our config, if i add our config files and batch file script into the "post install" section of the patch and the files to the "custom files" section the update fails with error code 0x87D00668(-2016410008) in software center.

 

The Post Install commands i have are these:

"%PATHTOFIXES%\7z.exe" x "%PATHTOFIXES%\config.zip" -o"%ProgramFiles(x86)%\Mozilla Firefox" -y

if exist "%ProgramFiles(x86)%\Mozilla Firefox\" ren "%ProgramFiles(x86)%\Mozilla Firefox\browser\searchplugins\google.xml" google.tmp

if exist "%ProgramFiles(x86)%\Mozilla Firefox\" del "%ProgramFiles(x86)%\Mozilla Firefox\browser\searchplugins\*.xml"

if exist "%ProgramFiles(x86)%\Mozilla Firefox\" ren "%ProgramFiles(x86)%\Mozilla Firefox\browser\searchplugins\google.tmp" google.xml

if exist "%public%\Desktop\Mozilla Firefox.lnk" del "%public%\Desktop\Mozilla Firefox.lnk"

set errorlevel=0

 

And in the Custom Files section i have 7-Zip files for the configs.

 

I had help with setting this up but still learning the program.

 

Has anyone successfully patched Firefox and kept their current config? I cannot afford to lose the config with the patch.

 

Thanks

---

Installing on Server 2016

December 11, 2017, 1:10 pm

≫ Next: PDFC-023, PDFCreator 3.0.3 not downloading

≪ Previous: Firefox patch using Shavlik in SCCM CB 1706 and keep current config

$

0

0

I'm trying to install the latest Ivanti SCCM Patch plugin on a Server 2016 (version 2.3.974) and it's telling me I'm missing the Visual C++ 2015 (x86 and x64) pre-reqs.   I've installed both of them and rebooted the server, and it still tells me they are Missing -

Does Ivanti work on Server 2016?  Is there something I'm missing?

PDFC-023, PDFCreator 3.0.3 not downloading

December 12, 2017, 12:34 am

≫ Next: Exception Occurred During Publishing: CreateDirectory Failed

≪ Previous: Installing on Server 2016

$

0

0

Maybe some problem with PDFC-023 update. I have tried to download it month ago and it didnt work and still seems to be same problem. Patch tuesday is coming and i wanted to publish this one also at the sametime.

Exception Occurred During Publishing: CreateDirectory Failed

July 15, 2013, 5:34 am

≫ Next: What is the consensus on how to deploy ivanti patch for sccm updates with regard to grouping updates.

≪ Previous: PDFC-023, PDFCreator 3.0.3 not downloading

$

0

0

Purpose

 

The purpose of the document is to review a common error when publishing updates.

 

Symptoms

 

Exception occurred during publishing: CreateDirectory Failed

 

Cause

"System Drive:\WSUS\UpdateServicesPackages" or "System Drive:\WSUS\WsusContent" is not shared for System Center Updates Publisher (SCUP) or System Center Configuration Manager (SCCM)

 

Resolution

 

Ensure "UpdateServicesPackages" exists in your WSUS content directory. By default, this will be whatever you specified during your SCCM installation. If it doesn't exist, create it and then go through the following steps.

 

Microsoft recommends having the WSUSContent on a different drive than the OS. In the following example, the WSUS content is in C:\WSUS, but you can find the location of your content on your WSUS Server at HKLM\Software\Microsoft\Update Services\ServerSetup in the ContentDir key data section:

 

1. Navigate to "C:\WSUS\UpdateServicesPackages"/"C:\WSUS\WsusContent" then Share the directory and set permissions to:

 

• Admin's Group Full access
• Network Service Full access
• Everyone Read access
• WSUS Administrators Group Full access.

 

2. Set NTFS permissions to:

 

• Administrators Group Full access
• Network Service Full access
• System Full access
• Users Group Read/List Folder Read & Execute
• WSUS Admins Group Full access.

 

 

3. The following information is from WSUS: How to change the location where WSUS stores updates locally | SUS Blog :

 

This tool will move ALL your existing and future Microsoft and third party content so make sure that your destination location has enough storage space or you could damage your WSUS.

 

On your WSUS server open a command prompt with “run as admin”, Navigate to %programfiles%\update services\tools and issue the following command:

WSUSUtil.exe movecontent <content path> <log path>

 

NOTE:

<content path> = Drive letter of WSUS folder location (i.e. E:\WSUS\WSUSContent\UpdateServicesPackages)

<log path> = Drive letter of log path with log file specified (i.e. C:\Temp\move.log)

 

If that doesn’t work, try moving the content to a temporary location and then move it back to the desired path.

 

Additional Information

 

To find out more about the content and target directory locations use the link below:

Verifying WSUS Server Settings

 

Affected Product(s)

 

Shavlik Patch for Microsoft System Center (Formerly SCUPdates)

When publishing via:

System Center Update Publisher (SCUP)

Shavlik Patch Plugin 2.x

What is the consensus on how to deploy ivanti patch for sccm updates with regard to grouping updates.

December 18, 2017, 6:33 pm

≫ Next: Publishing Fails With Failed to sign Package: error was: 2147942403

≪ Previous: Exception Occurred During Publishing: CreateDirectory Failed

$

0

0

Hi,

     I'm sorting ivanti patch for SCCM for the first time and am trying to figure out what the consensus / "best" practice is for setting up the deployments.  For windows updates, we essentially just do a deployment of - " if any of the updates required by these products - windows 7, windows 8, office 2010, office 2016, visual studio, silverlight, etc, etc are required, deploy them. "

 

With Ivanti patch, I get the feeling that I should be doing this more like a separate deployment for each Product / major version so that as each product is eliminated from the network ( updated to a later version, replaced by another product), the deployment can be disabled/deleted)

 

Is this how most people deploy using ivanti patch?

 

E.G.

one deployment for Adobe Acrobat XI - "Patch for SCCM - Adobe Acrobat XI updates"

one deployment for Adobe Flash V27 - "Patch for SCCM - Adobe Flash V27 updates"

one deployment for winzip 25 - "Patch for SCCM - winzip 25 updates"

one deployment for winzip 24 - "Patch for SCCM - winzip 24 updates"

one deployment for winzip 23 - "Patch for SCCM - winzip 23 updates"

 

OR do people combine them into

1. all of the products currently in use (similiar to how I described the way I do windows updates) - "Patch for SCCM - all updates")
   1. the disadvantage I see there is the addition of new products/versions on a regular basis and having to recreate the deployment each time to facilitate that.
2. single deployment per product without separating major versions (winzip 23,24 and 25 for example) "Patch for SCCM - Winzip updates"
   1. we do occasionally get this (multiple versions with some of these type of products. 
3. combine vendor products - one deployment for adobe flash products, adobe reader products, adobe acrobat products.   "Patch for SCCM - Adobe updates"

Publishing Fails With Failed to sign Package: error was: 2147942403

August 5, 2016, 12:39 am

≫ Next: Deployemnt Complete (not verified)?

≪ Previous: What is the consensus on how to deploy ivanti patch for sccm updates with regard to grouping updates.

$

0

0

Symptoms

 

Unable to publish updates.

 

Following entry could be found in the AutoPublish.log:

 

Error Publishing 'Adobe Flash Player 22.0.0.210 Internet Explorer' : Failed to sign package; error was: 2147942403

 

When running Configuration Checker under Shavlik Patch settings you are getting the error below:

 

 

Cause

 

• There is a WSUS configuration issue with the UpdateServicePackages shares.
• The problem is described here: https://social.technet.microsoft.com/Forums/en-US/5fdb03a7-2605-488b-80ca-f389499ab0df/scup-failed-to-sign-package-error?forum=configmanagersecurity

 

Resolution

 

You can verify where WSUS believes the folders are by running this at a CMD prompt on the Shavlik Patch server:

 

net share

 

This will show the location of the UpdateServicePackages shares.

You will need to use this command to point WSUS to the correct location of:

 

• \WSUS\WsusContent
• \WSUS\UpdateServicesPackages

 

WSUSUtil.exe movecontent <content path> <log path>

 

To use this command without actually copying your content over, use the following command:

wsusutil.exe movecontent contentpath logfile [-skipcopy]

 

More information:  WSUSUtil.exe

 

Affected Product(s)

 

Shavlik Patch Plugin 2.x

Deployemnt Complete (not verified)?

December 20, 2017, 7:22 am

≫ Next: Unable to publish binaries after publishing Metadata only

≪ Previous: Publishing Fails With Failed to sign Package: error was: 2147942403

$

0

0

Hello,

 

I recently upgraded from Shavlik 9.3 to Ivanti 9.3. Everything is going well however after a patch deployment I received a "Complete (not verified)" status.

The default credential I am using is a service account that has domain admin level access.

 

Could someone point me in the right direction?

 

Thank

Ryan

Unable to publish binaries after publishing Metadata only

December 21, 2017, 5:47 am

≫ Next: Deployed updates to clients, Compliance shows mostly complete, but version hasn't actually updated on Client. Why?

≪ Previous: Deployemnt Complete (not verified)?

$

0

0

Hello,

We currently have a problem with the release of some software which we have published the metadata only.

 

Here is the situation:

A member of our team published the metadata only of some applications to finally realize that he had made a mistake and that he needed the binaries as well.

But unfortunately we are now unable to publish the binaries of these applications

 

What we tried:

 

• We have republished the applications without success. SCCM tells us that we only have Metadata.

• We removed the products and republish with the binaries and SCCM still mentions that we only have the metadata.

 

What we noticed:

 

In the AutoPublish.log file, we noticed that all the applications, including the Metadata, only have been published and that we are trying to recover the binaries (republish), there are always 2 downloads that occur when we try to republish or following the erasure and the 2(download) are successful?

We checked on the WSUS and the CAB files are there, but SCCM tells us that there is only Metadata in Software Update.

 

Configuration information:

 

Ivanti patch for SCCM: version 2.3 update 2

Windows 2012 R2

SCCM Curent Branch 1706

 

Thank you for your help

---

Deployed updates to clients, Compliance shows mostly complete, but version hasn't actually updated on Client. Why?

January 3, 2018, 10:31 am

≫ Next: Horizon Client for Windows

≪ Previous: Unable to publish binaries after publishing Metadata only

$

0

0

I deployed Adobe Reader XI (11.0.23) to my test group of clients that were at (11.0.10) at most.  The deployment appears to be successful because 10 out of 13 reports as compliant.  But when I check the clients Reader has not been updated.  On a couple of the clients the update appeared in the Software Center as available and I was able to update them by clicking on install.  But most didn't even show up in any way.  Is there any log file that shows why they are considered compliant and can I can it be made to correct itself.

Horizon Client for Windows

January 10, 2018, 6:24 am

≫ Next: URL Exception List For Shavlik Patch For Microsoft System Center (01-09-2018)

≪ Previous: Deployed updates to clients, Compliance shows mostly complete, but version hasn't actually updated on Client. Why?

$

0

0

Does Ivanti no longer provide updates for Vmware Horizon client? I haven't seen a new one since 2016. Was hoping for a release to version 4.7 to patch the security vulnerabilities in the previous versions.

URL Exception List For Shavlik Patch For Microsoft System Center (01-09-2018)

February 25, 2014, 7:43 am

≫ Next: SCCM and Shavlik patch and en-gb language

≪ Previous: Horizon Client for Windows

$

0

0

Purpose

 

This article provides a list of web addresses that may be required to download content or patches when using Shavlik Patch for Microsoft System Center.

 

Description

 

Ensure that these web addresses required by Shavlik Patch are accessible and allowed through firewalls, proxies, or web filters.

 

ftp://archive.mozilla.org

ftp://ftp.adobe.com

ftp://ftp.attglobal.net

ftp://ftp.hp.com

ftp://ftp.mozilla.org

http://34e34375d0b7c22eafcf-c0a4be9b34fe09958cbea1670de70e9b.r87.cf1.rackcdn.com

http://aimp.su

http://airdownload.adobe.com

http://apache.cs.utah.edu

http://apache.mesi.com.ar

http://apache.mirrors.ionfish.org

http://apache.mirrors.lucidnetworks.net

http://apache.mirrors.pair.com

http://apache.mirrors.tds.net

http://apache.osuosl.org

http://apache.spinellicreations.com

http://app.oldfoss.com

http://appldnld.apple.com

http://appldnld.apple.com.edgesuite.net

http://archive.apache.org

http://ardownload.adobe.com

http://audacity.googlecode.com

http://bitbucket.org

http://cache.lumension.com

http://cache-download.real.com

http://ccmdl.adobe.com

http://cdn01.foxitsoftware.com

http://cdn02.foxitsoftware.com

http://cdn09.foxitsoftware.com

http://cdn1.evernote.com

http://classicshell.net

http://content.ivanti.com

http://d.7-zip.org

http://dl.google.com

http://dl.notepad-plus-plus.org

http://dl2.xmind.net

http://download.adobe.com

http://download.cdburnerxp.se

http://download.documentfoundation.org

http://download.dymo.com

http://download.filezilla-project.org

http://download.gimp.org

http://download.imgburn.com

http://download.macromedia.com

http://download.microsoft.com

http://download.nullsoft.com

http://download.oldfoss.com

http://download.oldfoss.com:81

http://download.oracle.com

http://download.pdfforge.org

http://download.piriform.com

http://download.royalapplications.com

http://download.services.openoffice.org

http://download.skype.com

http://download.splunk.com

http://download.techsmith.com

http://download.tuxfamily.org

http://download.videolan.org

http://download.virtualbox.org

http://download.windowsupdate.com

http://download.winzip.com

http://download1.operacdn.com

http://download2.operacdn.com

http://download3.operacdn.com

http://download3.vmware.com

http://download3.xnview.com

http://download4.operacdn.com

http://downloadarchive.documentfoundation.org

http://download-installer.cdn.mozilla.net

http://download-origin.cdn.mozilla.net

http://downloads.hpe.com

http://downloads.pdf-xchange.com

http://downloads.sourceforge.net

http://downloadus1.teamviewer.com

http://downloadus2.teamviewer.com

http://en.community.dell.com

http://files2.zimbra.com

http://fpdownload.macromedia.com

http://ftp.adobe.com

http://ftp.df.lth.se

http://ftp.hp.com

http://ftp.mozilla.org

http://ftp.opera.com

http://ftp.osuosl.org

http://ftp.ussg.indiana.edu

http://ftp.utexas.edu

http://get.geo.opera.com

http://get.geo.opera.com.global.prod.fastly.net

http://gigenet.dl.osdn.jp

http://heanet.dl.sourceforge.net

http://hivelocity.dl.sourceforge.net

http://install.nitropdf.com

http://iweb.dl.sourceforge.net

http://jaist.dl.sourceforge.net

http://javadl.oracle.com

http://javadl.sun.com

http://jsimlo.sk

http://majorgeeks.mirror.internode.on.net

http://master.dl.sourceforge.net

http://mirror.cc.columbia.edu

http://mirror.nexcess.net

http://mirror.reverse.net

http://mirror2.layerjet.com

http://mirror6.layerjet.com

http://mirrors.advancedhosters.com

http://mirrors.gigenet.com

http://mirrors.ibiblio.org

http://mirrors.syringanetworks.net

http://mozy.com

http://notepad-plus-plus.org

http://olive.download.pdfforge.org

http://operasoftware.pc.cdn.bitgravity.com

http://orange.download.pdfforge.org

http://osdn.dl.osdn.jp

http://packages.vmware.com

http://pilotfiber.dl.sourceforge.net

http://pnotepad.googlecode.com

http://psg.mtu.edu

http://pspad.poradna.net

http://pumath.dl.osdn.jp

http://purple.download.pdfforge.org

http://realvnc.com

http://releases.mozilla.org

http://skylineservers.dl.sourceforge.net

http://softlayer-dal.dl.sourceforge.net

http://software-dl.real.com

http://sourceforge.net

http://superb-dca2.dl.sourceforge.net

http://superb-dca3.dl.sourceforge.net

http://superb-sea2.dl.sourceforge.net

http://supergsego.com

http://support.citrix.com

http://support.citrixonline.com

http://support1.uvnc.com

http://supportdownload.apple.com

http://tchspt.com

http://tdf.mirror.rafal.ca

http://teal.download.pdfforge.org

http://tenet.dl.sourceforge.net

http://ufpr.dl.sourceforge.net

http://upgrade.skype.com

http://videolan-mirror.vpsserver.com

http://videolan-nyc.defaultroute.com

http://vorboss.dl.sourceforge.net

http://wireshark.askapache.com

http://wiresharkdownloads.riverbed.com

http://www.7-zip.org

http://www.apache.org

http://www.carfab.com

http://www.coreftp.com

http://www.cutepdf.com

http://www.fosshub.com

http://www.goodsync.com

http://www.gtlib.gatech.edu

http://www.jam-software.com

http://www.mirrorservice.org

http://www.namesdir.com

http://www.oldfoss.com

http://www.peazip.org

http://www.piriform.com

http://www.rarlab.com

http://www.realvnc.com

http://www.tightvnc.com

http://www.uvnc.com

http://www.uvnc.eu

http://www.wireshark.org

http://www-us.apache.org

http://xh.yimg.com

http://xml.shavlik.com

https://1.na.dl.wireshark.org

https://2.na.dl.wireshark.org

https://airdownload.adobe.com

https://allwaysync.com

https://atlassian.jfrog.io

https://bitbucket.org

https://cdn.gomlab.com

https://cdn1.evernote.com

https://clientupdates.dropboxstatic.com

https://content.ivanti.com

https://cytranet.dl.sourceforge.net

https://d1ilhw0800yew8.cloudfront.net

https://data-cdn.mbamupdates.com

https://desktopassets.prezi.com

https://dl.bandicam.com

https://dl.google.com

https://dl.tvcdn.de

https://dl3.xmind.net

https://download.cdburnerxp.se

https://download.gimp.org

https://download.microsoft.com

https://download.royalapplications.com

https://download.skype.com

https://download.splunk.com

https://download.sublimetext.com

https://download.teamviewer.com

https://download.techsmith.com

https://download.tortoisegit.org

https://download3.vmware.com

https://download3.xnview.com

https://downloadplugins.citrix.com

https://downloads.hpe.com

https://downloads.plex.tv

https://downloads.sourceforge.net

https://downloadus2.teamviewer.com

https://downloadus4.teamviewer.com

https://e3.boxcdn.net

https://endpoint920510.azureedge.net

https://fpdownload.macromedia.com

https://ftp.mozilla.org

https://get.geo.opera.com

https://gigenet.dl.sourceforge.net

https://github.com

https://hipchat-ops.s3.amazonaws.com

https://iweb.dl.sourceforge.net

https://knowledge.autodesk.com

https://launch.getgo.com

https://managedway.dl.sourceforge.net

https://master.dl.sourceforge.net

https://media.inkscape.org

https://meetings.webex.com

https://neevia.com

https://nmap.org

https://nodejs.org

https://notepad-plus-plus.org

https://packages.vmware.com

https://phoenixnap.dl.sourceforge.net

https://pilotfiber.dl.sourceforge.net

https://s3.amazonaws.com

https://secure.logmein.com

https://secure.mozy.com

https://secure-appldnld.apple.com

https://slack-ssb-updates.global.ssl.fastly.net

https://superb-dca2.dl.sourceforge.net

https://superb-sea2.dl.sourceforge.net

https://svwh.dl.sourceforge.net

https://swdl.bluejeans.com

https://telerik-fiddler.s3.amazonaws.com

https://the.earth.li

https://versaweb.dl.sourceforge.net

https://web.mit.edu

https://www.fosshub.com

https://www.goodsync.com

https://www.hipchat.com

https://www.jam-software.com

https://www.mozypro.com

https://www.piriform.com

https://www.realvnc.com

https://www.scootersoftware.com

https://www.uvnc.eu

https://www.wireshark.org

 

Additional Information

 

If using the Shavlik Patch pluginwith SCCM, you may also want to review Certificate verification sites to allow for Shavlik Patch

If you require the IP addresses to create exceptions you can find the IP addresses used for xml.shavlik.com or content.ivanti.com here. To obtain the IP for vendor sites you can ping the site for the current IP address or contact the vendor to obtain this information.

 

If you want to create an exception for an entire domain rather than entering all specific URLs, you can usually do so by entering the exception in this format:

*.domain.com

Example: *.Shavlik.com

 

Affected Product(s)

 

Ivanti Patch for SCCM

Shavlik Patch for Microsoft System Center

(Shavlik SCUPdates)

SCCM and Shavlik patch and en-gb language

January 12, 2018, 5:28 am

≫ Next: Shavlik file KB4072698U.exe to remediate Meltdown/Spectre changes the registry keys?

≪ Previous: URL Exception List For Shavlik Patch For Microsoft System Center (01-09-2018)

$

0

0

I am trying to patch our systems 3rd party products with sccm and shavlik.

I have downloaded the latest firefox and deployed the installs successfully on any device that has installed the en-us version but anyone who has the en- gb version this will not install.

It shows as not required on these devices. When I look at language settings in shavlik I can only see en which is the American version.

Shavlik file KB4072698U.exe to remediate Meltdown/Spectre changes the registry keys?

January 12, 2018, 11:55 am

≫ Next: Update to Patching Citrix Receiver

≪ Previous: SCCM and Shavlik patch and en-gb language

$

0

0

We patched a hand ful of machines on Jan 7 with Shavlik/Ivanti and everything went well when we applied the Meltdown/Spectre patch. We pushed the reg key before hand so all that Shavlik did was run the executable. When we did the same thing in the rest of our dev environment now it is not working. We noticed 2 executables signed by Shavlik that what they look like they are doing is changing registry keys to a value of 3 which based on Microsoft's article is turning the patch OFF.

 

The 2 file names are KB4072698U.exe and KB4072698.exe

 

 

these 2 files are messing up the patch deployment, Shavlik seems to always execute KB4072698U and changing the registry key to 3

Update to Patching Citrix Receiver

January 15, 2018, 9:47 am

≫ Next: sccm 1710 support

≪ Previous: Shavlik file KB4072698U.exe to remediate Meltdown/Spectre changes the registry keys?

$

0

0

Overview

 

We are changing how we handle patching for Citrix Receiver to better match up with Citrix's lifecycle process. The changes we are making are:

 

Versions less than 4.9: Systems running versions of Citrix Receiver prior to version 4.9 will detect as previously, with the newest patch being offered updating the software to version 4.9 which is the Long Term Service Release (LTSR) of Citrix Receiver.

 

Version 4.9: As this is the LTSR release it will have any Cumulative Updates marked as applicable for it, but it will not have the update to version 4.10 marked as applicable. If you want to upgrade off of the LTSR version, you will need to install the desired version on your Endpoints. We are currently working on an upgrade package, and will update this article regarding it.

Due to the fact that Citrix only provides links for token based downloads of previous versions of Citrix Receiver we are unable to automatically download the files for the LTSR updates. The patches will need to be manually downloaded and placed in the Local Source Folder, which must be enabled as detailed in the Product Help here: https://help.ivanti.com/sh/help/en_US/PAT/23/Topics/Offline_Options_Tab.htm

 

For Citrix Receiver 4.9, the latest version can be found here: https://www.citrix.com/downloads/citrix-receiver/windows-ltsr/receiver-for-windows-ltsr_4_9_1000.html

Version 4.10: As this is the current release, and the start of a new branch, it will have updates marked as applicable as they are released up to the point of the next LTSR release of Citrix Receiver. At this point a new branch will be created, with versions between 4.10 and the next LTSR being offered updates to the LTSR version.

 

Additional Information

 

• Lifecycle Milestones for Citrix Receiver - Citrix
  
• Citrix Receiver for Windows 4.9 LTSR

 

Affected Product(s)

 

Shavlik Patch for SCCM 2.3.x

Ivanti Patch for SCCM 2.3.x

sccm 1710 support

January 17, 2018, 2:15 am

≫ Next: Discrepancy in amount of categories

≪ Previous: Update to Patching Citrix Receiver

$

0

0

Hello

 

It's Ivanti Patch supported  for SCCM 1710 ?

 

Regards

 

Wojtek

---

Discrepancy in amount of categories

January 17, 2018, 1:51 pm

≫ Next: How To: Re-Sign 3rd party updates previously published to WSUS

≪ Previous: sccm 1710 support

$

0

0

Hello,

 

I have Ivanti Patch for SCCM installed on 2 separate sites (test and production). I noticed there is a difference in the amount of categories available:

 

One site shows:

The other site shows:

 

Questions:

 

1. What is causing the difference in amount of categories available? or better yet, how can I bring the low (184) one match the big one (208)?
2. I keep trying to apply the checkmark on empty check boxes so my catalogs include all available categories, I hit "Apply changes", when prompted for sync I answer "Yes", then I close the "Manage Products" window. A few minutes later, I opened it again and it's as if I did nothing: the categories I marked continue to be unchecked. Any recommendations?

 

 

Sincerely,

Jose

How To: Re-Sign 3rd party updates previously published to WSUS

September 12, 2014, 10:44 am

≫ Next: Steps to Upgrade from Shavlik Patch 2.2.568.0 to Ivanti Patch for SCCM 2.3

≪ Previous: Discrepancy in amount of categories

$

0

0

Purpose

 

This document is meant to provide some basic information about how to re-sign updates that have been previously published to WSUS, but may need a new digital signature due to changing certificates.

 

Description

 

If you change the certificate used for WSUS, the client systems will now accept any updates that are signed with the new digital certificates, but you may have older updates already published which are still signed with the previous digital signature.  In this scenario, the updates will fail to deploy on the client systems as the client does not recognize the digital certificate.

 

The Shavlik Patch plugin currently does not have a feature to re-sign updates when publishing, however, this can be done via System Center Update Publisher (SCUP).

 

Here's how to do it:

 

1) In SCUP, ensure you have the latest .cabs from Shavlik imported. You can manually download the .cabs by logging into https://protectcloud.shavlik.com/.

2) Select any updates you need to re-sign, then choose to Publish.

3) On the 'Publish Options' make sure to select 'Full Content', and make sure to check the box for 'Sign all software updates with a new publishing certificate when published software updates have not changed but their certificate has changed.'

4) Finish through the steps of publishing to complete the process.

 

Additional Information

 

• Microsoft has a video on how to re-sign updates, here.
  
• SCUP 2011 can be downloaded here.
  

 

Affected Product(s)

 

Shavlik Patch for Microsoft System Center

(Formerly SCUPdates)

Steps to Upgrade from Shavlik Patch 2.2.568.0 to Ivanti Patch for SCCM 2.3

January 19, 2018, 12:48 pm

≫ Next: Vendors catalog for Ivanti patch for SCCM

≪ Previous: How To: Re-Sign 3rd party updates previously published to WSUS

$

0

0

Hello. I am receiving a message about the EOL for the current version of Shavlik Patch that I am using. I am looking for the latest upgrade steps to Ivanti Patch for SCCM 2.3. Below is the latest upgrade documentation that I have been able to find. Is there a newer version? Thank you for the assistance.

 

Updating from Shavlik Patch 2.2 to 2.3

Vendors catalog for Ivanti patch for SCCM

January 22, 2018, 7:33 am

≫ Next: Patch for SCCM add-in

≪ Previous: Steps to Upgrade from Shavlik Patch 2.2.568.0 to Ivanti Patch for SCCM 2.3

$

0

0

Is there a list of the vendors that provide catalog we can add to Patch for SCCM? Is HP part of them?

 

Thanks

 

David

Patch for SCCM add-in

January 22, 2018, 11:26 am

≫ Next: The wsus server could not be contacted when install on remote console.

≪ Previous: Vendors catalog for Ivanti patch for SCCM

$

0

0

Hello, I'm trying to install the add-in on my local computer where I'm normally using my SCCM console. During installation it is saying that MS Visual C++ 2015 is missing and if I hit Install it failed. I tried to manually re-install it but it is still saying it is missing. I also tried to remove it completely but it is still failing.