Forge Home


Module that will manage IIS for windows server 2008 and above. It will help maintain application pools, sites and virtual applications


9,524 latest version

3.2 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.0.6 (latest)
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2 (deleted)
  • 0.0.1 (deleted)
released May 2nd 2014

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'apaz-iis', '0.0.6'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add apaz-iis
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install apaz-iis --version 0.0.6

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



apaz/iis — version 0.0.6 May 2nd 2014


Module for puppet that can be used to create sites, application pools and virtual applications with IIS 7 and above.

Build Status


This module is only available to Windows Server 2008 and above due to using the WebAdministration module that ships with PowerShell. To use the module, use git clone to a directory in your modules folder on your puppetmaster. Then create a module manifest for the site you wish to maintain configuration for. Then you need to include this new module manifest in your nodes.pp file as follows:

node 'nodename' {
    include 'mywebsite'

Please note, that you need to implement the iis class in your module as in the example below


  class mywebsite {
    iis::manage_app_pool {'my_application_pool':
      enable_32_bit           => true,
      managed_runtime_version => 'v4.0',

    iis::manage_site {'':
      site_path     => 'C:\inetpub\wwwroot\mysite',
      port          => '80',
      ip_address    => '*',
      host_header   => '',
      app_pool      => 'my_application_pool'

    iis::manage_virtual_application {'application1':
      site_name   => '',
      site_path   => 'C:\inetpub\wwwroot\application1',
      app_pool    => 'my_application_pool'
    iis::manage_virtual_application {'application2':
      site_name   => '',
      site_path   => 'C:\inetpub\wwwroot\application2',
      app_pool    => 'my_application_pool'

This will result in an IIS Directory setup as follows:

The module knows that if requesting a virtual application, then it will have to create a site and application pool in the correct order so that it can build the correct model. Further usage would be to include the values as specified in the iis class above from hiera configuration.

Additional Bindings

A default binding is setup using the values passed to the manage_site resource. Additional bindings can be added to a site using the manage_binding resource.

-- iis::manage_binding { '': site_name => '', protocol => 'http', port => '8080', }

Host header and ip address can also be supplied.

-- iis::manage_binding { '': site_name => '', protocol => 'http', port => '8080', ip_address => '', host_header => '', }