Skip to content
fDeploy Documentation

Installation prerequisites

Operating system

fDeploy should be hosted on Windows Server 2019 or higher but you may be able to get it to run even on earlier versions of Windows Server.

.NET runtimes for fDeploy Server

fDeploy Server is built to target .NET 10 and requires either .NET 10 SDK or the following runtimes installed on the machine where fDeploy Server is to be installed. You can download the required runtimes from Microsoft at the following page: https://dotnet.microsoft.com/en-us/download/dotnet/10.0

  1. .NET 10 runtime
  2. .NET 10 desktop runtime
  3. ASP.NET Core 10 runtime

Download the x64 installers that match your target platform from the .NET 10 download page linked above.

.NET runtimes for fDeploy Agent

fDeploy Agent is built to target .NET 10 and requires either .NET 10 SDK or the following runtimes installed on each deployment target machine. You can download the required runtimes from Microsoft at the following page: https://dotnet.microsoft.com/en-us/download/dotnet/10.0

  1. .NET 10 runtime
  2. ASP.NET Core 10 runtime

IIS modules for the Deploy to IIS step

If your package contains a web.config that references the URL Rewrite module — common for SPA fallback rules that route every request to index.html — install URL Rewrite on every target machine the site lands on before the first deployment.

Without the module, IIS treats the <rewrite> section as unrecognized configuration and rejects the entire site config. The failure surfaces as IIS deployment failed during phase: configure_authentication (or any other phase that touches site config) with the underlying COM error 0x8007000D — there is no hint that the real problem is a missing module.

The same applies to any other web.config section provided by an optional IIS feature (Basic Authentication, Windows Authentication, etc.) — install the corresponding feature on the target before deploying a web.config that references it.