David_Di_Blasio

You can automate most if not all tasks in Patch Manager. I actually have a reoccurring task set up for WSUS cleanup as shown in the following screenshot.

This has actually been implemented as of Patch Manager 1.85.

I believe this is already implemented as you can select a package, or catalog and export them as .cab files with the Export Catalog function. The resulting files can be archived or shared. We actually have a few packages in our content share now.…

It's currently possible to modify the Vendor field when you edit/create a package. Once you refresh the All Packages node the new catalog name will appear based on the value you declared.

RIP L. You will be missed

What's the end goal behind the modifications you are making?

Computer explorer has a function called "Uninstall Software", which can be leveraged against a single or multiple machines. Here's a KB on this functionality. SolarWinds Knowledge Base :: How to Uninstall a Program Using the Patch Manager Computer Explorer

Hi Johnny. Here's a kb article that goes over creating the third party view. SolarWinds Knowledge Base :: How to create a third party updates view in the Patch Manager console

I actually ran into a similar case the other day. Try the following steps: 1. Expand Patch Manager System Configuration node, and then expand the Patch Manager Servers sub node. 2. Select Application Servers and then select your Application Server in the middle pane. 3. Click the Application Server Settings tab, and double…

Hi. I just wanted to check in to see if you got the assistance you needed to resolve this issue through support.

One possibility here is that the installer used with the 11.5.502.135 package template is from a lower version number. This would cause the update to successfully run over and over again as the conditions for "is installed" would never be met. Can you verify the update content your machines are receiving is 11.5.502.135?…

Setting Level and Options to 3 is totally fine, and probably more useful as you'll collect more information.

If I remember correctly the service account user will just need to be sysadmin in the local sql instance. The requirements are similar to what is documented in the following KB article, without the need for the account to be domain admin. SolarWinds Knowledge Base :: What SQL account permissions does Patch Manager require?

Mike, It sounds like you configured your automation server to write to the same database as the Primary Application Server (PAS). I'd recommend to take the local default sql instance for the automation server at this time. I'd be happy to look at this issue via GoToMeeting if you open a support case.

Provided you have fast storage (raid 1+0) on the database server, the specs listed should be adequate. I'd say you might have good cause to open a case with support so one of us can take a look at your diagnostics.

Usually these types of things are available in the release notes, however, I do not see several known issues listed in the current notes. Patch Manager v1.85 Service Release 2 Release Notes

The last 100 or so lines may contain all the info we need. Otherwise pastebin.com may be a good option.

I did a little more research into using msp files. Unfortunately it looks like it isn’t really possible to directly modify them. Here’s a couple of options you have to remedy this situation. * 1) You could create a new msp that has the correct built in guids to allow the patch to know if it’s needed or already installed on…

antwesor wrote: For me it is the DELL and HP catalogs that are FTP based. Adobe Catalogs are http:// and I am pretty sure the Solarwindws Update Catalog is http:// Hopefully no one shut down your ports 20 and 21 on your network. Correct. Here's the specific URLs in question.…

Certainly. The steps would be the following: 1. Grab the report located on http://thwack.solarwinds.com/docs/DOC-167269 2. Import the above report into the Windows Server Updates Services Analytics reporting category. 3. Modify it to look exactly like the report in the screenshot below: 4. Run the report and export the…

I'll just add that we still see this semi frequently in the support dept. Changing the service account to a domain account is the usual fix we suggest. SolarWinds Knowledge Base :: Changing the account or password used for the Patch Manager service

A support ticket is probably the next step as it sounds like there's a few other issues at hand. Here's a link to create a support ticket. Technical Support Ticket Submission Form | SolarWinds

Here's a technet article that details out the switches available for the forefront installer. Installing from a command prompt - specifying parameters

Were these machines already regularly checking into this particular WSUS server, or is WSUS new in the environment?

Without looking directly at the issue I'm out of ideas. Feel free to open a support case so I can take a look via GoToMeeting.

Scratch that idea I tested it and it failed as well.

I think the issue is likely related to the permissions the ewdgs service account has on the SQL server as this is the account that is attempting to create the database.

Regarding your request for creating a registry on a target machine. This could be accomplished via package boot with the following process. Create a REG file with the desired settings. Include the REG file as an Additional File. Configure PackageBoot to use a <postexecution><programs><program> element to execute REG.EXE…

Sure. Here's a write up that contains some more specific information on how to implement this workaround. http://thwack.solarwinds.com/community/solarwinds-community/geek-speak_tht/blog/2013/01/29/managing-wsus-on-windows-server-2012-with-patch-manager-v185

Correct. With SCCM 2012 the actions have moved from the Patch Manager MMC console app to the native SCCM console. This eliminates the need to have 2 things open when patching.