Completing Configuration Prerequisites

This high-level outline lists each procedure that you'll perform when configuring HEAT PatchLink DeskTop for System Center (HEAT PatchLink DeskTop).

Before installing, review the requirements for the HEAT PatchLink DeskTop Server, HEAT PatchLink DeskTop Console Plug-in, and the signing certificate used to publish and deploy 3rd-party software. This review can prevent potential install problems.
If your enterprise uses a proxy server between your network and the Internet, configure it to work with HEAT PatchLink DeskTop.
Tip:
- If you don't have a proxy server, skip this step.
- Consult the user documentation for your proxy server for detailed information on proxy configuration.
- Consult Knowledge Article 26244 at the HEAT Self-Service Portal for an up-to-date list of URLs.
1. Allow the following URLs (and ports) to communicate through your proxy:
  - cloudapi.lumension.com: 443
  - cache.lumension.com: 80
  - lumstorage.blob.core.windows.net: 443
  Also, allow the following URLs (and ports) to download content from vendors relevant to your environment (only open URLs/ports for the vendors you need).
  Note: Some of these URLs may redirect communications to port 443 or other URLs.
  - appIdnId.apple.com: 80
  - ardownload.adobe.com: 80
  - armdl.adobe.com: 80
  - cache-download.real.com: 80
  - ftp.mozilla.org: 80
  - support1.uvnc.com: 80
2. Open port 60065 to allow communication between your HEAT PatchLink DeskTop Server and any standalone HEAT PatchLink DeskTop Console Plug-ins that you install.
Configure your standalone primary site/CAS environment for communication with HEAT PatchLink DeskTop.

Attention: If you're installing HEAT PatchLink DeskTop directly on your primary site server/CAS, don't complete this step. Skip to the next step.
1. Make sure that the target WSUS server has connectivity with the primary site server/CAS.
2. Create a service account that will be used for communication between the HEAT PatchLink DeskTop and the primary site server/CAS. This account has the following requirements:
  - It must be either a domain account or an identical local account on both your WSUS Server and the primary site server/CAS.
  - It must be a member of the SMS Admin local user group on the primary site server/CAS.
  - It must be a member of the WSUS Administrators local user group on the WSUS Server.