Prerequisites Checklist
Every item below must be in place in your environment before you start installing Easy2Patch 4.0 Web Edition. Mark each item; if a step is not ready yet or you are not sure how to do it, let us know and we will resolve it together before the installation.
Server & Operating System
Windows Server 2019 / 2022 / 2025 Standard or Datacenter is required.
Before the installation, verify that the target server meets the minimum and recommended values listed on this page.
-
On the server, open Server Manager › Local Server. The operating system version, processor and total memory (RAM) are shown on this screen.
-
Check the disk space in File Explorer › This PC; at least 100 GB must be allocated to the operating system disk.
-
Requirements can change between product versions, so always use the latest POC requirements document as the reference.
At least 16 GB of RAM (reserved / fixed) is required.
Before the installation, verify that the target server meets the minimum and recommended values listed on this page.
-
On the server, open Server Manager › Local Server. The operating system version, processor and total memory (RAM) are shown on this screen.
-
Check the disk space in File Explorer › This PC; at least 100 GB must be allocated to the operating system disk.
-
Requirements can change between product versions, so always use the latest POC requirements document as the reference.
At least 2 vCPUs are required; 4 vCPUs are recommended.
Before the installation, verify that the target server meets the minimum and recommended values listed on this page.
-
On the server, open Server Manager › Local Server. The operating system version, processor and total memory (RAM) are shown on this screen.
-
Check the disk space in File Explorer › This PC; at least 100 GB must be allocated to the operating system disk.
-
Requirements can change between product versions, so always use the latest POC requirements document as the reference.
At least 100 GB of OS disk is required.
Before the installation, verify that the target server meets the minimum and recommended values listed on this page.
-
On the server, open Server Manager › Local Server. The operating system version, processor and total memory (RAM) are shown on this screen.
-
Check the disk space in File Explorer › This PC; at least 100 GB must be allocated to the operating system disk.
-
Requirements can change between product versions, so always use the latest POC requirements document as the reference.
The server must be a member of an Active Directory domain.
Easy2Patch requires the server to be a domain member; complete this step before the installation.
-
On the server, open Server Manager › Local Server and check that your organization’s domain name appears in the Domain field. If it says “Workgroup”, the server has not been joined to the domain yet.
-
Verify that the server can communicate with the domain controller. Open PowerShell as Administrator and run the command below; the result must be True:
Test-ComputerSecureChannel
The regional settings of the installation server should be set to United States.
Software Components
You can install the components below from Microsoft’s official download links.
ASP.NET Core Runtime / Hosting Bundle 8.x must be installed.
Easy2Patch 4.0 runs on ASP.NET Core 8 on IIS. This requires the .NET 8 Hosting Bundle to be installed on the server.
-
Download the installer with the Download Hosting Bundle 8.0 button on this item.
-
Right-click the file, choose Run as administrator, accept the license terms and complete the installation.
-
The installed version must match the version the product supports. Installing only the latest .NET release (e.g. .NET 10) on the server is not enough; version 8.x must be present.
Important: Install IIS before the Hosting Bundle. If the Hosting Bundle was installed before IIS, run the installer again and choose Repair.
.NET Framework 4.7.2 or later is required.
.NET Framework 4.7.2 or later usually comes preinstalled on current Windows Server versions. You can check the installed version as follows.
-
Open PowerShell and run this command:
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' | Select-Object Version, Release
-
The Version value must be 4.7.2 or later (a Release value of 461808 or higher).
-
If the version is lower, download and install the package with the Download .NET Framework 4.7.2 button on this item.
Database (SQL Server)
One of the supported versions is required: SQL Server 2019 / 2022 Standard, Enterprise or Express.
SQL Server must be installed before SSMS. The steps below use SQL Server Express; the wizard works the same way for the Standard and Enterprise editions.
1. Prepare the installation media
If the server has no internet access, do this part on another computer that can reach the internet, then copy the resulting setup folder to the server.
-
Download the setup tool with the SQL Server Express download button on this item, right-click it and choose Run as administrator.
-
On the installation type screen, choose Download Media.
-
Select the Express Core package, choose the download location and click Download.
-
When the download is complete, run the SQLEXPR_x64_ENU file in the folder with Run as administrator. If the server has no internet access, copy this file to the server first.
-
Choose the folder the setup files will be extracted to. When the preparation is complete, SQL Server Installation Center opens; if it does not, run the setup file in that folder manually.
2. Complete the installation wizard
-
On the Installation tab, click New SQL Server stand-alone installation or add features to an existing installation.
-
Accept the license terms and continue with Next.
-
On the Microsoft Update screen, continue with Next.
-
Make sure the Install Rules checks have completed. A Windows Firewall warning does not block the installation; continue with Next.
-
Continue with Next without selecting Azure Extension for SQL Server.
-
On the Feature Selection screen, continue with Database Engine Services selected.
-
On the Instance Configuration screen, choose Default instance.
-
On the Server Configuration › Service Accounts tab, you can continue with the default accounts.
-
Switch to the Collation tab. The Database Engine collation must be SQL_Latin1_General_CP1_CI_AS; if it is different, change it with Customize.
-
On the Database Engine Configuration screen, choose the authentication mode and add the SQL administrator account with Add Current User or Add…. Also check the database permissions of the account that will be used for the Easy2Patch installation.
-
On the Data Directories tab, check the data, log and backup folders.
-
Review the settings on the TempDB tab and continue with Next.
-
Review the installation summary and follow the wizard until the process is complete.
-
On the Complete screen, confirm that every component shows Succeeded, then close the wizard with Close.
SQL Server can be on the Configuration Manager database server, or on a separate local / remote server for Easy2Patch.
A 64-bit SQL Server must be used.
The SQL Server collation must be set as follows.
SQL_Latin1_General_CP1_CI_AS
The SQL Server collation for the Easy2Patch database must be SQL_Latin1_General_CP1_CI_AS.
-
New installation: select this value on the Server Configuration › Collation tab of the SQL Server setup wizard.
-
Existing SQL Server: open a new query window in SSMS and run the query below; the result must match this value.
SELECT SERVERPROPERTY('Collation');
The recommended compatibility level for the SQL Server version in use must be set.
SQL Server Management Studio must be available (or installable) for SQL administration and connectivity checks.
SSMS is installed after the SQL Server installation is complete. The installation method depends on whether the server has internet access.
If the server has internet access
Current SSMS versions download their components from the internet during installation.
-
Right-click the downloaded vs_SSMS file and choose Run as administrator.
-
Visual Studio Installer opens. With SSMS Core Components selected, click Install and wait for the required components to be downloaded and installed.
-
When the installation is complete, you can open SSMS with Launch.
If the server has no internet access
For servers without internet access, SSMS 19.x, which can be installed offline, is recommended.
-
Download the SSMS 19.x installation package on a computer with internet access and copy it to the server.
-
Run the SSMS-Setup-ENU file with administrator rights and complete the installation by following the wizard.
IIS (Web Server)
IIS Web Server must be installable to host the Easy2Patch Portal.
The Easy2Patch Portal is hosted on IIS. All required IIS components can be installed with a single PowerShell command.
-
On the installation server, right-click PowerShell and open it with Run as administrator.
-
Paste and run the command below. IIS and the components the product needs are installed automatically:
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Static-Content,Web-Http-Redirect,Web-Health,Web-Http-Logging,Web-Custom-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Performance,Web-Stat-Compression,Web-Security,Web-Filtering,Web-Basic-Auth,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext,Web-Net-Ext45,Web-ASP,Web-Asp-Net,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-WebSockets,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Web-WMI,Web-Scripting-Tools,Web-Mgmt-Service
-
When the installation is complete, open IIS Manager and confirm that the service and the components are active.
The Web Server, Common HTTP Features, HTTP Logging, Request Monitor, Static Compression, Request Filtering, Basic Authentication, Windows Authentication, IIS Management Console and Metabase Compatibility components must be installable.
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Static-Content,Web-Http-Redirect,Web-Health,Web-Http-Logging,Web-Custom-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Performance,Web-Stat-Compression,Web-Security,Web-Filtering,Web-Basic-Auth,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext,Web-Net-Ext45,Web-ASP,Web-Asp-Net,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-WebSockets,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Web-WMI,Web-Scripting-Tools,Web-Mgmt-Service
The Easy2Patch Portal is hosted on IIS. All required IIS components can be installed with a single PowerShell command.
-
On the installation server, right-click PowerShell and open it with Run as administrator.
-
Paste and run the command below. IIS and the components the product needs are installed automatically:
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Static-Content,Web-Http-Redirect,Web-Health,Web-Http-Logging,Web-Custom-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Performance,Web-Stat-Compression,Web-Security,Web-Filtering,Web-Basic-Auth,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext,Web-Net-Ext45,Web-ASP,Web-Asp-Net,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-WebSockets,Web-Mgmt-Tools,Web-Mgmt-Console,Web-Mgmt-Compat,Web-Metabase,Web-WMI,Web-Scripting-Tools,Web-Mgmt-Service
-
When the installation is complete, open IIS Manager and confirm that the service and the components are active.
WSUS & SCCM
WSUS or the WSUS Console is required. If the WSUS Console is not available, RSAT-WSUS must be installable.
Install-WindowsFeature -Name UpdateServices-UI
If SCCM application deployment or Trigger SCCM will be used, the SCCM Admin Console is required.
Network & Port Access
Access in the source → destination direction must be allowed on your firewalls.
TCP 80 / 443 access from client and server systems to the Easy2Patch Portal is required.
TCP 389 / 636 (LDAP / LDAPS) access from the Easy2Patch Server to the domain controllers is required.
TCP 8530 / 8531 or TCP 80 / 443 access from the Easy2Patch Server to the WSUS Server is required.
RPC high ports access from the Easy2Patch Server to the Configuration Manager site server is required.
TCP 80 / 443 access from the Easy2Patch Server to the Intune platform is required.
HTTPS (TCP 443) access to the address below must be allowed on the firewall.
https://picblobstorage.blob.core.windows.net
TCP 443 access to license.arksoft.com.tr is required for online licensing.
Service Account
Depending on your installation scenario, choose one of the Service Account, GMSA or Built-in Account options.
Certificates
An HTTPS Web Server certificate containing the product FQDN is required.
Having the certificate ready before the installation avoids delays caused by waiting for a certificate on installation day. Handle the certificate request according to your organization’s policies.
-
Decide the address (FQDN) Easy2Patch will be published on, e.g. easy2patch.company.local.
-
Request a Web Server certificate covering this address from your internal CA or your certificate provider. The address must appear in the certificate’s CN or SAN / DNS Name field.
-
Export the certificate together with its private key in .pfx format (Certificate › Export › “Yes, export the private key”) and keep the password you set ready to share with the installation team.
A certificate in .pfx format that includes the private key, together with the certificate password, is required.
Having the certificate ready before the installation avoids delays caused by waiting for a certificate on installation day. Handle the certificate request according to your organization’s policies.
-
Decide the address (FQDN) Easy2Patch will be published on, e.g. easy2patch.company.local.
-
Request a Web Server certificate covering this address from your internal CA or your certificate provider. The address must appear in the certificate’s CN or SAN / DNS Name field.
-
Export the certificate together with its private key in .pfx format (Certificate › Export › “Yes, export the private key”) and keep the password you set ready to share with the installation team.
The CN or SAN / DNS Name on the certificate must match the product access address.
Having the certificate ready before the installation avoids delays caused by waiting for a certificate on installation day. Handle the certificate request according to your organization’s policies.
-
Decide the address (FQDN) Easy2Patch will be published on, e.g. easy2patch.company.local.
-
Request a Web Server certificate covering this address from your internal CA or your certificate provider. The address must appear in the certificate’s CN or SAN / DNS Name field.
-
Export the certificate together with its private key in .pfx format (Certificate › Export › “Yes, export the private key”) and keep the password you set ready to share with the installation team.
A code signing certificate should be requested.
Installation Package
The Easy2Patch for Web 4.0.8 package is required.
AAAD82FD121E8D760C073D1618F13F552AFD27F6F78D0126C72F3142C8C11516