Patching Server 2012 using Solarwinds Patch Manager Posted on August 1, 2012 by jeff **UPDATE: Microsoft released KB 2734608 on August 24th, 2012 that describes a patch for WSUS 3.0 SP2 to support Windows 8 and Server 2012 which makes this procedure unnecessary unless you want to take advantage of new features supported in WSUS on Server 2012. Post patch reboot config. With System Server source to throttle patch deployment. Offices on slow links so the download from system server option is a great.
Now to specifics. There are some patch managers that CAN be configured to handle each of those versions separately and install what patches are available in the default repositories for that version. It is not pretty.
I have, in the past, built my own solutions rather than put up with the flaws in all of the existing packages I was able to discover. Something may have evolved to improve the situation since then, my last testing and rollout was a couple of years ago now.
PS. This gets REALLY easy if all of your nodes are the same version of the same distribution. For that there are multiple tools for patch management, and several good configuration management tools. Your problem is the range of distributions you run makes the problem 'interesting'.
To patch managed Linux and UNIX machines, you must install a Red Hat Linux 6, 64-bit machine as the patching repository, configure the communication protocols, and download and configure the Software Content Repository (SCR) Tool.
Caution To ensure security in a geographically distributed Linux and UNIX patching environment, the credentials that you use to transfer patches from the patching repository to the alternate location must be different from the credentials that you use to copy patches from the alternate location to the target managed machines. The credentials used to transfer patch files to the alternate location must have read and write privileges. Use read-only credentials to stage patches from an alternate location to a managed machine.
If you already configured the Red Hat Linux patching repository machine for manual patching with VCM, you can skip this procedure.
Prerequisites
Patching Server With Config Manager Throttle Patch Download Windows 10
- Verify that the Red Hat Linux patching repository machine can access the Internet.
- When you set up a patching repository machine and alternate location machines, you must ensure that users have proper permissions and protocols configured to read patches from the patching repository machine and write patches to the alternate location machines. See Configuring Protocols to Stage and Deploy Linux and UNIX Patches.
- Decide which protocol to use to copy patches from the patching repository machine to the optional alternate location machines. To configure the protocol, see http://kb.vmware.com/kb/2051632 and the Red Hat Linux information online.
Sql Server Config Manager
Procedure
- Download and install the latest version of Java and the Oracle Java Cryptography Extension (JCE), which is used for Software Content Repository (SCR) Tool password encryption.
- Install the latest VCM Linux Agent on the patching repository machine. See the VCM online help.
- Install and configure the service that supports the desired communication method used by the managed machines.
- Configure the communication protocol.
What to do next
- Download the Software Content Repository (SCR) Tool 5.1. See Download the Software Content Repository Tool.
- Configure the SCR Tool. See Configure the SCR Tool.
See Also |
|---|
| Configuring the Alternate Location Patch Repository Machines |
| Configuring VCM to Work with the Patching Repository and Alternate Locations |
| Deploying Patches to Managed Machines without User Intervention |
Help us improve this topic. Send feedback to . | Technical Support | © 2006–2015 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.