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

Was this helpful?

  1. Configuring
  2. Easy2Patch 4.0 Settings
  3. Connection Settings

WSUS

Scope: Easy2Patch 4.0

PreviousSCCMNextIntune

Last updated 10 months ago

Was this helpful?

Depending on the license, the SCCM/WSUS/INTUNE button is clicked in the settings page. WSUS settings are made from the WSUS Settings menu as follows:

  1. In the Host address part, the server address of the SUP role is written as FQDN.

  2. If WSUS is running securely, the use SSL option should be selected and the SSL port on which WSUS is running should be entered.

  3. Enter the Secure Port value configured in WSUS in the Port field. By default it is 8531. But it could be 443 or any other port.

  4. Base Url is new in Easy2Patch 4.0. This URL is the address used to contact WSUS. It consists of 2 parts.

    • The first part is the portal address of easy2patch 4.0, and the second part is the fixed ConfigMgr.

    • For example: If the address where Easy2Patch is published is e2p.domain.com, https://e2p.domain.com/ConfigMgr is written in this field.

  5. The connection test is performed by pressing the test button. If the test is successful, a question about saving the record is asked. Yes is clicked.

WSUS Secure Port is the HTTPS port used by the WSUS server. By default, WSUS uses the Secure Port as 8531.

To verify which port the WSUS server is using, you can follow these steps:

  1. On the WSUS server, open IIS Manager.

  2. In the left-hand panel, expand the "Sites" node and click on the "WSUS Administration" site.

  3. On the page that opens, click on "Bindings" in the "Actions" section on the right.

  4. In the window that opens, click the "Edit" button next to the port specified as "https" in the "Type" column.

  5. In the window that opens, in the "Port" field, you can see the WSUS Secure Port number.

By following these steps, you can find out the secure port used by the WSUS server.

Size limit for WSUS Update Publishing

WSUS server has a maximum size limit. Some update packages may exceed the size limit. When you want to deploy updates larger than 384 MB You shouldn't do that in general. Updates can't be published to the WSUS server due to the locally published packages size limit. The WSUS package size limit is 382 MB by default.

You can change the default size limitation in 2 ways.

First method is, you can change the maximum file size from registry. When you run the powershell script, maximum file size for publishing updates in wsus changed to 512 MB. Maximum file size for publishing is 2047 MB.

[reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration")
$wsus = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer()
$size = $wsus.GetConfiguration().LocalPublishingMaxCabSize
Write-host "Current Max Size" $size
$config = $wsus.GetConfiguration()
$config.LocalPublishingMaxCabSize = 512
$config.save()

You can change this value easily in Easy2Patch Console. Change Local Publishing Max Size (MB) value to 512 and then click submit button.