Easy2Patch v4.0
Easy2Patch v4.0
  • Infrastructure Documents
  • Overview
    • What is Easy2Patch?
    • Request a new 3rd Party Applications
    • FAQs
    • Road Map
    • Release Notes
    • Version Compare
    • Licensing
  • Planning
    • POC Requirements for Easy2Patch 3.1
    • POC Requirements for Easy2Patch 4.0 Web Edition
    • Supported Configurations
    • Windows Operating System Requirements
    • SQL Server Requirements
    • Other Requirements
    • Network Considerations
    • Antivirus Exclusion List for Easy2PatchV3
    • Design
      • Update & Application & Intune (Server Deployment)
      • Standalone WSUS Deployment
      • Standalone Intune Deployment
  • Deployment
    • Installing WSUS Console
    • Installing SCCM Admin Console
    • Installing IIS Component for Easy2Patch 4.0
    • Configuring Intune Application Registration
    • Getting Code-Signing Certificate
    • Installing Easy2Patch 3.1
      • Upgrading to Easy2Patch 3.1.10
      • Licensing Easy2Patch 3.1
    • Installing Easy2Patch 4.0
      • Upgrading Easy2Patch 4.0
      • Easy2Patch Backup & Restore
      • Licensing Easy2Patch 4.0
  • Configuring
    • SSL Configuration in WSUS for 3rd Party Update
    • Configuring ConfigMgr for 3rd Party Updates
    • Easy2Patch 3.1 Settings
      • General
        • Certificate Management
        • Backup Settings
          • Restore Easy2Patch 3.x
        • General Settings
        • Application Deployment
        • Intune Deployment
        • Maintenance
      • Notification
        • E-Mail
        • Telegram
          • Creating a Telegram Bot
          • Telegram Chat ID
      • SCCM / WSUS / INTUNE
        • WSUS Settings
        • SCCM Settings
        • Database Settings
        • Intune Settings
      • Proxy
    • Easy2Patch 4.0 Settings
      • Migrate from Easy2Patch 3.x
      • General Settings
        • General
        • Identity
          • Active Directory
          • EntraID
            • Required Permissions for EntraID
        • Proxy
        • Log
        • Maintenance
        • Login
      • Deployment Settings
        • Process Conflict
        • Update
        • Application Deployment
        • Intune Deployment
        • Defender
      • Connection Settings
        • Database
        • SCCM
        • WSUS
        • Intune
      • Managements
        • Role
        • License
        • Certificate Management
      • Alert Settings
        • Notification
          • E-Mail
          • Telegram
            • Creating a Telegram Bot
            • Telegram Chat ID
            • Telegram Setting
        • Alerts
        • Recipients
  • Managing Easy2Patch
    • Easy2Patch 3.1
      • Update
      • Application Deployment
      • Intune Update
      • Intune Application
      • License Management
    • Easy2Patch 4.0
      • Dashboard
        • WSUS
        • SCCM
        • Intune
      • Update
        • Application Custom Settings
        • WSUS Maintenance
        • Side Menu
      • Application
        • Application Deployment Right Click Menu
        • Application Custom Settings
        • SCCM Maintenance
        • Side Menu
      • Intune Update
        • Intune Update Right Click Menu
        • Application Custom Settings
        • Intune Maintenance
        • Side Menu
      • Intune Application
        • Intune Application Right Click Menu
        • Application Custom Settings
        • Intune Maintenance
        • Side Menu
      • CVE List
      • Schedule
      • Reporting
        • Update Status
  • Troubleshooting
    • Schema files not found!
    • Failed to sign package
    • Fixing 500.19 web.config error
    • Securing Windows Server
Powered by GitBook
On this page
  • Easy2Patch 3.x
  • Easy2Patch 4.x

Was this helpful?

  1. Planning
  2. Design

Update & Application & Intune (Server Deployment)

Scope: Easy2Patch (All Versions)

Easy2Patch 3.x

In this deployment model, the server where SCCM's Software Update Point (SUP) role is installed is used. Before installing Easy2Patch on the server with the SUP role, at least WSUS Console and if it will be used SCCM Admin Console must be installed. It communicates with the SUP role. It performs this operation from TCP 8531 / TCP 443 or the specified any other Secure WSUS Port number.

In the configurations made here, the choice of Standalone WSUS does not affect the requirements and design.

If you want to install Easy2Patch 3.x software other than SUP/WSUS machine, WSUS role must be configured with Secure SSL Access.

Easy2Patch 4.x

In this deployment model, the server where SCCM's Software Update Point (SUP) role is installed is used. Before installing Easy2Patch on the server with the SUP role, at least WSUS Console and if it will be used SCCM Admin Console must be installed. It communicates with the SUP role. It performs this operation from TCP 8531 / TCP 443 or the specified any other Secure WSUS Port number.

Easy2Patch Web version consists of 2 components. If you want to install Easy2Patch WE in a distributed structure, the 1st component, .Net Core, can be installed on another server independent of the SUP/WSUS server. The second part, the ConfigMgr application, must be installed on the SUP/WSUS server.

In the configurations made here, the choice of Standalone WSUS does not affect the requirements and design.

If you want to install Easy2Patch 4.x software ConfigMgr application other than SUP/WSUS machine, WSUS role must be configured with Secure SSL Access.

PreviousDesignNextStandalone WSUS Deployment

Last updated 11 months ago

Was this helpful?