The Patch Manager console will automatically integrate with a pre-existing instance of the Configuration Manager 2012 console. When the PM installer runs, it detects the presence of the CM2012 console, and offers an opt-in checkbox in the installer dialog to install the CM2012 console integration. This occurs on both console-only installations, or in the event you are installing a full Patch Manager server to a system containing a CM2012 console instance.
When running the installation of the Patch Manager server, a collection of setup/configuration wizards will automatically launch to walk you through identifying all of the components of the infrastructure (e.g. Site Server, Software Update Point, Domains, etc.) This is documented in the Administrator Guide starting on page 10.
If you have more specific questions about this procedure I'm happy to help.
We currently have a WSUS server integrated with Patch Manager but want to move the WSUS server to System Center. Will we still be able to use Patch Manager with a System Center integrated WSUS deployment?
Yes, you can definitely continue to use Patch Manager with System Center Configuration Manager. There are a few notable differences to be aware of:
- The Patch Manager functionality is fully integrated in the Configuration Manager 2012 console, so you'll generally use the CM2012 console for daily operations, but server and user administration tasks are still performed from the MMC console.
- The Patch Manager software publishing function will work exactly the same way, publishing updates to the Software Update Point.
- The Patch Manager WSUS Inventory and Reporting functionality is not available, by default, in a Configuration Manager environment; however, you can configure the Software Update Point to provide this functionality. See this blog article for more details on how to implement WSUS Inventory and Reporting with Configuration Manager.
- The Patch Manager Update Management and Update Management Wizard deployment tools are not generally used in a Configuration Manager environment, but they can be used in special case scenarios. See this blog article for more details on how/when to use Update Management and Update Management Wizard with Configuration Manager.
- When implemented in a Configuration Manager environment, Patch Manager provides a collection of client management tools that can be helpful in the realm of managing Configuration Manager clients.
The other note I would make here is to strongly recommend installing a *NEW* WSUS Server to be configured as your Software Update Point rather than trying to repurpose an existing WSUS server. There are two reasons for this:
- The existing WSUS server is clogged up with approvals and downloaded content, neither of which are used in the Configuration Manager environment. A NEW WSUS server will present a much cleaner environment for use with Configuration Manager.
- Trying to repurpose your existing WSUS server means that you'll be without a patch management environment until you fully implement the new patch management environment with ConfigMgr. By using a new WSUS server for the SUP, you'll have no time constraints on implementing Configuration Manager Software Updates because your existing WSUS patch management environment will continue to be online.
Finally, take note that your existing Patch Manager server can manage BOTH your existing WSUS environment, as well as your new ConfigMgr environment concurrently.