Easy2Patch v3.0
  • Infrastructure Documents
  • Overview
    • What is Easy2Patch
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • Supported Configurations
    • Windows Operating System Requirements
    • Other Requirements
    • Network Considerations
    • Design
      • Update & Application & Intune (Server Deployment)
      • Standalone WSUS Deployment
      • Standalone Intune Deployment
  • Deployment
    • Installing WSUS Console
    • Installing SCCM Admin Console
    • Configuring Intune Application Registration
    • Getting Code-Signing Certificate
    • Installing Easy2Patch
    • Licensing
  • Configuring
    • Configuring SSL WSUS for 3rd Party Update
    • Configuring ConfigMgr for 3rd Party Updates
    • Easy2Patch Settings
      • General
        • Certificate Management
        • 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
  • Managing Easy2Patch
    • Update
    • Application Deployment
    • Intune Update
    • Intune Application
    • License Management
  • Troubleshooting
    • Schema files not found!
    • Failed to sign package; error was: 2147954402/2147954429
Powered by GitBook
On this page

Deployment

Scope: Easy2Patch 3.0

After you plan out your Easy2Patch topology, use the information in the following articles:

  • Installing WSUS Console

  • Installing SCCM Admin Console

  • Configuring Intune Application Registration

  • Getting Code-Signing Certificate

  • Installing Easy2Patch

PreviousStandalone Intune DeploymentNextInstalling WSUS Console

Last updated 2 years ago