jbaits

I have some packages that have multiple uninstall actions before an install. You would have to change failureaction to continue and the package would report success no matter what happens if there's no actual install happening. It works but you'd have to use a seperate metadata package to track where Air is actually still…

I wouldn't think having two would cause a conflict but I don't actually know. You could try republishing your update package and select the "Re-sign existing selected packages" option just to make sure it is signed with your 2048-bit cert. Beyond that I'm not sure what direction to send you in.

This XML Andrew posted should work. I didn't check through the actual execution line and notice packageboot.exe in there since that is created during the package creation process.

One reason I could see not sending a blanket uninstall command would be that you do not want the uninstall to occur if the Java 8 install has not yet happened. The mass uninstall command does not have any way to determine if that is the case and you may not want to wait for Java 8 to have 100% deployment before removing…

You should be looking for a registry value that contains the install path without the exe (ex. C:\Program Files\Altaro\Altaro Hyper-V Backup\). You can usually find this in HKLM\SOFTWARE\AppName or HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AppName. Once you find that you fill in the path and value entries…

The dummy exe is just a couple second wait command in AutoIT that is compiled to an exe. I had the command in the preexecution but the same line should work either way. Good luck. If you still have a problem post your full XML and I'll take a look..

That error is caused by a certificate failure. Have you pushed your publishing certificate to your clients? If it is not in the Trusted Root Certificate Authorities and Trusted Publishers your 3rd party updates will fail without ever trying to install. You could also be having an issue if you haven't upgraded your…

Here's the log including data from when the updates were approved. http://pastebin.com/vYq8MhRp

No problem. Half the fight with creating custom packages is crafting the unattended install command line. The other half is your detection rules for prerequisites, applicability, and installed status. The first step when creating a package is to make sure you can successfully install the msi or exe completely unattended…

Aside from the best practice changes Lawrence and I have already recommended, the package looks sound as long as your paths and version numbers are correct. I have seen some clients detection work improperly until the Windows Update cache was cleared.

When I make an uninstall package I give patch manager a dummy exe that doesn't do anything and it will create the apply package string. As far as the uninstall commands not working, I'd turn up logging for package boot and sift through that. It's helped me find syntax errors and other issues before. On the machine you're…

Glad to help.

This is fine for a pure uninstall package if you know exactly which version is installed on every system and are sure that there are not multiple installs on each machine. The original question in this thread was how to create a package that will install Java 8 AND uninstall Java 7. Yes they can be installed side by side…

If you use client side targeting in WSUS you can dictate the target group via a registry key on the client. If you join the domain using the default task sequence order you should be able to push this via policy since the machine would be on the domain before running updates. If you delay or do not join a domain you can…

It would be an additional applicability rule.

If you added your unattend.ini as an additional file and it is configured correctly it should work. Below is the exact contents of my "Command Line" field. /INI=C:\Windows\SoftwareDistribution\Download\Install\config.ini My ini has a different name but it should work the same.

The path specifies where the executable is located. In this case the executable is cmd.exe and is located in %windir%\system32. You run the bat by calling /c %MODULEPATH%\HostIP.bat. /c tells cmd.exe to exit once the command is complete. %MODULEPATH%\HostIP.bat expands to…

I haven't used Forefront so I can't give any concrete answers, but I would think you should almost always have some prerequisite rules. They should include things like minimum OS version, OS architecture if there is separate x86 and x64 packages, minimum IE version, etc. For applicability I usually use a combination of…

You can clear the cache using patch manager if you have it setup with the proper credentials. You would select the machines you need to clear the cache on and click the "Windows Update Agent Maintenance" option in the action pane on the right of the screen. This will give you several options including deleting the…

I've uploaded my package and it can be found here http://thwack.solarwinds.com/docs/DOC-171653

I've scrubbed the log for an affected machine from the time I approved the updates to today. It is about 3500 lines and I don't see an option to attach it within the post.

The problem with that approach is that it will not blanket uninstall any version of Java 7. The product codes for each update version would need to be included. A well crafted WMI call will eliminate all installed versions in one command.

To be clear, you do not need to specify anything in the package to achieve the standard install command of "msiexec.exe /i myapp.msi /qn /norestart". You also cannot remove those switches. I would test the install outside of patch manager in the command line and get that working before you proceed. Use that command as a…

You can select the package and click 'Export Catalog'. You will get a cab that contains the xml.

I would check the security log on the endpoint and see specifically what rights are being denied to that account. Depending on your configuration there could be rights that are available to the Administrators group by default that have been removed. I am pretty sure you only get the Access Denied message when you are…

I'm glad you found a solution that works for you. I'm not sure where you were having issues adding commands within package boot but I create custom packages for random tasks all the time. I've found that for some commands I need to call cmd.exe and then as a parameter use /c then the actual command I need to run. It's very…

The fact that your compiled exe is not signed is not actually a problem. Patch Manager will throw a warning but will use unsigned executables without issue. Why are you including the OS requirement as as a prereq, applicability, and installed rule? It should only be present as a prereq. For the OS rules, do you have two…

Some executables extract an msi for install but that might not be apparent by directly extracting the exe. A good example of this would be java. I would suggest running procmon from the sysinternals suite and launching the installer normally but not proceed through the install. You can filter the results down to just…

After looking at the script I'd be willing to bet it is an issue with the working directory. The script does not find the referenced files and fails. Add "cd /d %dp0" (don't include the quotes) to the top of your script to set the working directory to the location the script is running from and it may work for you.

There's a section called "Creating Software Packages" in the admin guide that goes over those functions of the software. There's also another thread on these forums about adobe updates that has a lot of information here . If you have any specific questions while trying to create a package there are several users that help…