Skip to content

← All integrations

Windows · Web server

Installs and binds certificates on IIS websites and FTP sites.

The service agent on the server fetches the task from the appliance over outbound HTTPS on port 443 and installs the certificate locally on the server. The appliance never connects to the server.

What happens

  1. The service agent on the server fetches the task from the appliance over outbound HTTPS, port 443.
  2. The Windows basics first import the certificate into the Windows certificate store (LocalMachine\My).
  3. HTTPS and FTP bindings that carried the previous certificate switch to the new one. The first time, or when the rule does not follow the previous certificate, only the rule's own bindings change. If it fails: If the change does not read back correctly, the installation reverses it itself, and the result says whether that worked. If it fails before that, nothing is written.
  4. Verification: the package reads the bindings back from IIS. There is no separate verify action.

Technical details

Connection
The package runs through the service agent on the server. The agent connects over outbound HTTPS to the appliance, port 443 by default. You open no port into the server.
Service ports
443
You need
The service agent installed on the server.
Platform
IIS 8.0 and later, Windows Server 2012 and later
Actions
Discovery, Installation, Removal; no rollback action
Packages
iis8pluswindows-iis
Note
  • Discovery finds sites, HTTPS and FTP bindings and application pools.

Get started