Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

2 upstream server

alex13

Hi everyone,

I'm really newbie in solarwinds patch manager and need advice.

so here the story, i just deploy our first solarwinds patch manager to manage our office (HO) & Data Centre.

we have 2 site :

1. Data Centre (manage windows servers updates).

2. Our HO (manage windows servers & workstation updates).

we deployed our first PM in data centre, it will be manage 2 WSUS (WSUS at data centre and WSUS at our HO).

our scenario is windows server in Data Centre will get updates from WSUS data centre and windows servers & workstation will get updates from WSUS HO,

We use solarwinds agent to manage all client and we already deploy agent to all client.

My question is the PM can be manage 2 WSUS upstream server?

i just deployed both WSUS act as upstream server but when i try to publish 3rd party packages to our WSUS HO it can't be publish because there are no cert for WSUS HO.

i already tried to create cert from PM but it failed.

No issue if i publish to WSUS Data Centre.

solarwinds patch manager installed with WSUS Data Centre is in one server (windows server 2016) and WSUS HO is windows server 2008.

Need your advice.

Thank You

Find more posts tagged with

Accepted answers

jrouviere

With a 2016 Patch Manager Server and a 2012 WSUS server you will need to have an automation server in place:

API Mismatch error in Patch Manager - SolarWinds Worldwide, LLC. Help and Support

This will be necessary for interactions with the WSUS server due to the API mismatch and you will usually run into it as you have with publishing the update.

You may run into issues if you try to approve or manage Windows Updates from Patch Manager on the 2012 server. If you were to set up tasks for Update Management to your client machines I believe those should still work as the task is giving the instructions to the nodes to download the updates.

Any case where you run into the API mismatch error, the answer is going to be to install the Automation Server.

All comments

jrouviere

Yes, Patch Manager can manage two upstream servers.

The primary difference is how the WSUS server gets Updates from upstream (is it Microsoft or another WSUS server, that's the main thing for Primary vs Secondary WSUS servers) so that doesn't change much for Patch Manager.

What is the error that you're getting with the certificate? That's likely what you'll need to focus on, so let's focus on that server. What's the OS (2012/2016?) does it have the latest updates?

You may also want to review this:

How to create a self-signed WSUS certificate when the Server Publishing Setup Wizard fails - SolarWinds Worldwide, LLC. …

alex13

Hi Jrouviere,

Thanks for the respons.

I just create self signed certificate and it works.

but now when i publish 3rd party software to the HO WSUS it failed the error says

"Failed to publish <name_update_software>. Publishing operation failed because the console and remote server versions
do not match."

we use Windows Server 2016 for Patch Manager & DC WSUS and Windows Server 2012 for HO WSUS.

if i install automation server on HO WSUS server it need be to reconfigure our current patch manager configuration?beside adding role automation server to PM.

Is automation server function is just to publish 3rd party software to different WSUS version from the WSUS PM in other words i still can be push microsoft updates from WSUS HO to client via PM?

Thank You

jrouviere

With a 2016 Patch Manager Server and a 2012 WSUS server you will need to have an automation server in place:

API Mismatch error in Patch Manager - SolarWinds Worldwide, LLC. Help and Support

This will be necessary for interactions with the WSUS server due to the API mismatch and you will usually run into it as you have with publishing the update.

Any case where you run into the API mismatch error, the answer is going to be to install the Automation Server.