jbaits

This only gets tricky since there is no identifier for 32-bit installs in the product name. In my environment I have three Java packages; one for x86, one for x64, and one for x86 installs on x64 machines. The x86 package only applies to 32 bit machines and therefore the line I previously provided would work fine. For the…

To my knowledge, patch manager will will tell you the IP a machine had the last time it checked in with the server but it does not use that data to try and connect to machines. It needs to be able to resolve the hostname through DNS to connect and run tasks. Perhaps one of the support reps can tell you how to change this…

Unfortunately since Patch Manager does not actually anonymize when exporting packages I cannot share the package directly but I will gladly answer any questions or provide info on the rules I have set up.

I have done exactly the same thing with Java and left the info in this thread. Remove old versions of Java 8

That is an option but we opted to include definitions just in case a machine downloaded the update but was off our network during the install.

As far as I know it's still being developed but there hasn't been any major changes in a very long time. The sourceforge page is still active and has a couple builds newer than what is on the 7-zip website but I consider them betas until they are officially posted to the site.

What version of patch manager are you using? With the new GUI editor for package boot in 1.8 it should be fairly straight forward. If you have 1.7 or below you need to add a line similar to this within the programs section of pre or post execution. <program…

We use a exe we compiled from a do nothing autoIT script. I think it waits one second then returns success. You could really use any exe that does pretty much nothing and returns a success.

That should be all you need to configure in MDT. If 3rd party updates are trying to install and your publishing certificate is not trusted by the client it will throw errors and not install updates. Make sure the machine has joined the domain and has the certificate pushed via policy or you have installed the cert as a…

I don't know that there is a maintained list of all the GUIDs for the various Java versions. As an alternative you can use the solution I posted above which can remove all versions of Java before installing the latest.

If Firefox is not installed your applicability rule will evaluate to true since not existing is less than the specified version. You will need to add a rule checking for an existing install to prevent the package from applying to machines without Firefox installed. I typically will use a "Reg key exists" rule looking at…

%MODULEPATH% is a packageboot specific variable that translates to the location where packageboot is running, typically "C:\Windows\SoftwareDistribution\Download\Install" during patch installation. Any files you include with the package will be located in %MODULEPATH%.

The install directory is created during package install and contains the extracted contents of the package. You do not need to know the package ID. Any included files, including the zip you generated containing your config files, will also be in that directory. I would suggest watching that directory during an update to…

That looks like it should work for that specific version.

I have not had to deploy any languages other than US English. Since Mozilla offers different packages for each language, I think you could duplicate the package you're using, replace the executable, and change the language selection.

You can clear the update cache from the machine to see if it makes a difference. You will need to turn off the update service, delete C:\Windows\SoftwareDistribution, start the update service, and preform a check for updates. If the package still shows as not applicable then there is a rule preventing install. Personally I…

In my experience it is usually a few days lead time between availability and release to the package catalog. Sometimes when there is a major version switch or a significant change that requires developing new prereq, applicability or installed detection rules it can be longer. I am sure that they either have alerts or a…

I've used File Exists rules as an installed rule for several packages but I was always checking version numbers not modified date. I would guess that the problem lies somewhere with the date and time check.

For my Office 2010 package I made an exe package and added setup.exe. I then uploaded all the additional files that are required in the setup directory including a customized config.xml. The only modifications made to the installer were in that config.xml. I had much better results with the package installing once I…

No these are all new packages that have only been published since the new 2048-bit certificate was in place.

When patch manager calls an msi without any additional parameters specified it is actually running "msiexec.exe /i myapp.msi /qn /norestart". Anything you put in the install parameters field will be added to the end. If you add /S it will run "msiexec.exe /i myapp.msi /qn /norestart /S". You need to find the proper…

As part of the update management the machine will first check applicability for updates. It does not need to show as needed before running to install the update.

This will work but you will not get accurate reports of successful or failed updates since the script should always have a return code of 0. Managing multiple architecture packages really isn't a large hassle and having accurate reporting data is far more valuable than only having to approve one package versus two.

KMSigma's response will get you most of the way there. You can provide patch manager a dummy application which does nothing, include the msu as an additional file, and put the required install commands in package boot as a pre-install task. You can also package the msu into a self extracting zip which you feed patch…

This is due to a change in how the Java installer handles upgrades. This has been discussed in this thread Remove old versions of Java 8.

If a value being checked does not exist it is considered less than the value being checked for and would evaluate as true. The way the package is built it will show as applicable to machines with no Firefox install or ones with an older version. To make an upgrade package you first check that something (registry key, file,…

You are correct in assuming that if a file does not exist that it reports as less than the specified version. To create an upgrade package you would need to do the version check as well as a "file exists" check. Your installed rule should only be "C:\Program Files\Altaro\Altaro Hyper-V Backup\Altaro Hyper-V Backup.exe…

I have encountered the same issue with Java and a few other patches. You could do this using WSUS groups but for my environment I found it easier to manage using an AD group. Computers that are members of the group get a registry key created (ex. DWORD "PreventJavaUpdate" 1). I then built a rule into the update package…

Is the CORP\svc_swndspm user admin of the endpoint you are trying to update? It is failing to access WMI and the EminentWare Provider on the remote system because it is denied access. Those items require admin privileges.

I've made quite a few packages that don't have installers. You don't want to deploy cmd.exe. What I have done is use a filler, do nothing exe as the provided executable (for instance sleep.exe or a compiled auto-it script that only has a wait command) and do any actual actions via Package Boot.