David_Di_Blasio

There's some diagnostics that could be analyzed, however I think we should start off a little simpler. What are the specs of the Orion/SQL server, and what software is currently running on this box.

This is a fairly straight forward issue that will occur whenever the WSUS console version does not match the version installed on the WSUS server. You'll want to manually apply the hotfix from http://support.microsoft.com/kb/2720211 against your Patch Manager server. Let us know if that doesn't resolve the issue.

Same steps apply for both Windows and Linux nodes.

Based on this information I believe the first thing you'll want to look at is ports. Here's a list of the ports required for WMI to work. Port 135 TCP - RPC Endpoint Mapper The SolarWinds Patch Manager server uses this port to establish WMI connections to remote computers. It also uses this port to connect to the Service…

The registry on the machine you're testing this against looks exactly like this screenshot right?

I'd recommend removing the old certificates from the policy, and then just import the new ones. They should be located within the policy applied to the affected computers under Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies. Once in this section you'll find the WSUS…

It may be useful for us to get a look at your windowsupdate.log from a problematic machine. Can you provide a scrubbed version of this log so we can see exactly what is happening when these computers are checking in?

What happens if you export the package from Patch Manager, and publish it using SCUP?

Might I ask what exact package you are deploying?

0x80070643 is actually a generic MSI installer failure, so the first place to check would be MSI logs. Here's a KB article we have on troubleshooting this error. http://knowledgebase.solarwinds.com/kb/questions/4081

I was able to accomplish a similar report by utilizing the "Computer Update Status With Details" datasource, which can be found in WSUS Reports > Windows Server Update Services Analytics. I just used a "contains" filter as they are easier for me to work with, but you may choose to be more specific. Here's a screenshot of…

I would say this is normal, and the reason a domain admin account is required for this type of installation. Per the following KB article SolarWinds Knowledge Base :: What SQL account permissions does Patch Manager require? * If you choose to use a remote SQL server, the service account must be a domain account with access…

There's not currently a method to automate the aggregation of this specific data that I am aware of, but it wouldn't be too difficult to combine the results from a Patch Manager report with the table of third party patches spreadsheet. To pull the currently published third party updates I started off with this report, and…

We've actually run into a few issues in regards to localization like this. Typically your best bet would be to start off by duplicating this package, and then remove the English pre-req. From here you'd need to test against some clients to ensure the update is working correctly.

Try running the following tool on one of the problematic machines and see if you get any errors. http://www.solarwinds.com/products/freetools/diagnostic-tool-for-wsus-agent.aspx

I'd suggest to open a case with support to take a look at this issue if you are in maintenance. The original error indicates there's an issue with connecting to this machine using the defined credentials, however, the "NotFound" error is one I am not familiar with.

Hi Bill, Although I have not tested it you may try using &quot instead of " as this is the proper xml declaration.

The agent uses the Console-to-Server Communication port (4092) to connect back to an automation server in your environment so you'll only need to have that one port open vs all ephemeral ports. 

When you've selected any node under Software Publishing there will be a button called "New Package" in the actions pane on the right.

Hi ak00, I duplicated your report in my test environment and am getting the expected results. I think the next thing to look at is when/if wsus inventory was last run. Try running one now and then see if you get any results from the report. Here's a kb on how to run wsus inventory. SolarWinds Knowledge Base :: How to…

This error indicates an update has likely been applied to the server hosting WSUS, but not the server hosting Patch Manager. Here's a KB that has provides some steps to take to resolve this issue. http://knowledgebase.solarwinds.com/kb/questions/4328/

From what I understand the error "has no local extended metadata. Not returning it" likely indicates some sort of corruption in the datastore on the machines affected with this issue. Provided your idea on expiring and duplicating the package doesn't work out, it is possible for you to create a task within Patch Manager to…

The most recent task history entry for your WSUS Inventory Task does not show any error correct? If not can you confirm you've configured WSUS to sync updates, and have computers reporting to this WSUS server?

Patch Manager will only open up to 32 or so concurrent connections per automation server (by default). You can affect this number by modifying the Maximum Worker Processes and the Maximum Thread Pool Size Per Worker Process. These settings can be located with the following steps: * Select Patch Manager Servers under the…

Indeed this can be done withing Patch Manager, however I like to start off with the least invasive procedure first. If something odd happens, or this isn't the issue you can always roll back this change. With the Windows Update Maintenance function within Patch Manager there's no going back as it's a delete command.

Honestly I think what's probably happening is there's a scheduled task set up to run against some scope (like your entire domain) that is picking up and targeting computers that might not be relevant anymore. Try checking through your scheduled tasks in Administration and Reporting > Scheduled Tasks and see if anything is…

This is certainly possible in both the Patch Manager console, and the WSUS console as this is a function provided by WSUS itself. In Patch Manager you would just need to select the group you want to create a sub group under, and then click the "Add Computer Group" button in the actions pane.

I believe this is related to the following KB. SolarWinds Knowledge Base :: WSUS patch causes Access Denied errors in Patch Manager

The information returned from any report in Patch Manager is only as accurate up to the last successful inventory of the datasources. Have you executed a recent WSUS inventory? Here's a KB on how to do this. http://knowledgebase.solarwinds.com/kb/questions/3679

What OS is this new server you added?