blashmet

It shows what packages were synced, but the important thing to know is if one needs to download any of those newly synced packages (i.e., ones that are published and need to have their new version published instead).

Ok, well this is quite frustrating. I updated the package with the following rules, but it's still not working. It checks for the existence of Trillian.exe (to make sure only machines with it installed get the update), then checks that the file version is less than 5.4.0.16. The XML shows: -<sdp:ApplicabilityRule…

Oh, perhaps I've been specifying the path incorrectly this whole time? Does choosing PROGAM_FILES from the Common Paths dropdown search both Program Files and Program Files (x86)? I haven't been appending Program Files (x86) to the contents in the Path: field.

Leaving Sub-Path blank generates this error: Any ideas?

Lawrence Garvin wrote: One suggestion: Before leaning toward using registry locations in the CurrentVersion node, or the Uninstall node, look for something in HKLM\Software\VendorName\ProductName, e.g. HKLM\Software\Cerulean Studios\Trillian Pro Those don't exist, so I'm resorting to what I can find.

I also found these, which seem like they might be more appropriate: Did I enter that information correctly?

Ah, I see. I'm having the same problem with Trillian. It correctly identifies the machines that need updates. However, once the update is installed, it keeps requesting to install it. I am attempting the registry method, but it is pretty unintuitive. For example, is it checking the value of a registry key or is it using…

It's not obvious to me how one would configure this. The only key I see with the product version is: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\20DCF4E78888CE7489D268FE0343B409\E3C0A25A102ABCF4EA9BFC24991EEC16 which has a String called "ProductVersion" with a value…

Ahhh I see. Yes, I could manually find all the information and generate the report, but I want to have a dashboard type thing where it updates automatically. How are people dealing with having to search for the latest versions of things all the time and making sure the latest version is actually in patch manager?

Any other ideas?

I already removed /qn and /norestart and posted the test results above. I understand where the flags should be included; when I said "command line field", I was referring to the command line field on the package configuration screen. I know this command works from the command line: msiexec /qn /norestart /i backup2.msi…

No system without the product is receiving it since I don't put those in the Altaro WSUS group. They are only reporting it as applicable (which is fine, since we understand why it's happening. i.e., because the version is technically below the condition value). The primary issue is that systems which satisfy the…

Attached is the .xml file.

This looks like what I'm looking for! Can you walk me through the steps on how to set that up?

What about the SOAP interface? Can I access that with Powershell?

I know it shouldn't be included in the command line field, but the command that I tested from the command line is: msiexec /qn /norestart /i backup2.msi ADDLOCAL=Feature_BackupEngine,Feature_BackupServer,Feature_ManagementTools /L*v %TEMP%\AltaroInstall.log So how do I get Patch Manager to yield the same results as running…

Yes, I've tested with these rules. All computers still say not applicable with the rules I posted above. To test, I approve the update for the selected group, and view the status in Patch Manager. It starts off detecting 0 machines, then they start getting sorted into Installed, Not Applicable, etc. They all end up in not…

I chose the static path since I know none of the machines have Trillian installed. I can't really clear the cache that way unless PM has those options. I need to do that on 25+ machines.

Sorry, I posted the install rule incorrectly. I corrected it to how I actually have it configured. Lawrence, I do want to do an upgrade, but rather than making more rules, I have an "Altaro" WSUS group with only the systems I want to install on, so that should accomplish the same thing. Where can I local the .xml of the…

It fails: clientname.corpdom.com0clientname.corpdom.comcheck_client_accessFailedHostname is clientname.corpdom.com1/7/2013 3:32 ttSERVERNAME I can't ping the machine. I think I found the answer though...I think we can't push updates out manually, but the client can pull them from the WSUS server. What settings do we have…

I made that change, but it still shows as not applicable for that system. Any other ideas?

Thanks for the reply. I opened the .exe in 7zip, but I don't see an .msi file. I opened Brosix.exe as well, but I don't see an .msi in it either. However, I still enabled MSI logging on my machine. Would it help to redeploy even though I don't see an MSI file inside the .exe?

That worked great. I was able to use PowerShell to grab the contents of the report and email it in HTML. Thanks!

Yes, but that has the latest releases. I'm looking for something more customized. I want to view only the patches we are deploying. That is, I want to view the current version we have published, and view the latest released version. The idea is to make it easy to see if I need to download/publish any new packages. I get…

Enabling/Disabling monitors is part of a much longer process we go through when updating certain servers. We want to automate each part of this process as much as possible. Rather than opening IE, logging into IPmonitor, and disabling/enabling the monitors, we’d rather have a simple bat file with this functionality.…

How would that work exactly? I wanted script commands because the monitors need to be enabled/disabled after certain steps in software deployments are completed. It won't be the same everytime.

Thanks for the help. I created a new test package and removed the log flag completely: ADDLOCAL=Feature_BackupEngine,Feature_BackupServer,Feature_ManagementTools /L*v However, installing now gives a different error: Code 80070667 I have a feeling it has to do with the msiexec syntax. The /qn /norestart and /i flags should…

These are different from the original one I tested, but I believe they should work as well (these rules are "stronger" in that the patch should be applicable if the operating system is greater than windows version 5). All computers still say not applicable with these rules: Prerequisite: -<sdp:PrerequisiteRule…

The applicability rule I am using checks for the existence of C:\Program Files\Trillian\trillian.exe. If the version is less than 5.3.0.15, then it's supposed to be applicable. Most of the machines don't have Trillian installed. From a previous support ticket, this means the version is automatically less than the one I…

I'm not using the registry to check for the version. The applicability rule I am using checks for the existence of C:\Program Files\Trillian\trillian.exe. If the version is less than 5.3.0.15, then it's supposed to be applicable. Most of the machines don't have Trillian installed. From a previous support ticket, this means…