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

Installing Patch Manager without internet access

I'm running an install of Patch Manager on a VM that currently has no internet access. We are running into an issue during the install where it will not continue without internet access. How can this be installed in an environment where there is no internet access and no proxy for internet?

Find more posts tagged with

Accepted answers

All comments

LGarvin

An important question here is during what stage of the installation is this occuring. Patch Manager has several installation prerequisites, and if the target server does not have these prerequisites, some of them are obtained via the Internet automatically. On a target server without Internet access, you'll need to install these prerequisites manually:

In the disconnected network you'll need a WSUS v3.2 server patched with KB2734608, or a WSUS v6.2 server.
On the target Patch Manager server you'll need to pre-install the WSUS Administration Console and KB2734608 if the OS is WS2008R2 or earlier.
On the target Patch Manager server you'll need to pre-install the .NET Framework v3.5 Service Pack 1 (if not already installed) if it's a WS2003/WS2008 server. On WS2008R2 this is an installable feature and the bits are already on the server, and the PatchManager installer will handle this for you without requiring an Internet connection.

Following the installation, you'll also want to disable the regular checks at service startup.

In HKLM\Software\EminentWare\Data Grid Service\Roles\Application change the value "CheckInternetForUpdates" to dword:0x0 (FALSE).

dkeyser

Turns out that we didn't have the visual C nor the .Net framework 4.0 packages that it needed. Once those were downloaded and installed we went through just fine.

LGarvin

The .NET4 would be the key issue there.

The Visual C++ runtime redistributable should be contained within the installer package and not require any separate download or Internet access.