PowerShell: Load WebAdministration in ps1 script on both IIS 7 and IIS 7.5

Question

I have a PowerShell script that configures web site and web application settings in IIS. So I use the cmdlets in the WebAdministration snap in. But this script needs to run on Windows 2008, Windows 7 and Windows 2008 R2. And I need it to run with minimal fuss from the user.

The problem is that Windows 7 and Windows 2008 R2 use IIS 7.5 which comes with the WebAdministration installed as a module. On Windows 2008 we have installed the IIS 7 PowerShell provider which installs WebAdministration as a snap in.

So including import-module WebAdministration in the script blows up on IIS 7 but works fine on IIS 7.5 and including add-pssnapin WebAdministration blows up on IIS 7.5 but works fine on IIS 7.

So our workaround is to make the administrators load WebAdministration manually with the appropriate command for the environment before running the script. But this isn't optimal as it is easy to forget which command works in which environment. We could create two different scripts, but that creates a maintenance problem for development.

Has anyone solved this problem? Does anyone know how to check the environment and then call the appropriate cmdlet from within the PS script?

--- ANSWER (for my situation) ----

The solution is a combination of code and pre-configured console. The IIS 7 PoSH Provider includes a desktop shortcut that launches a PoSH console with WebAdministration loaded. That combined with the following function make my script run like a charm on all three systems.

Function Load-WebAdmin {
  $webAdminModule = get-module -ListAvailable 
                                        | ? { $_.Name -eq "webadministration" }
  If ($webAdminModule -ne $null) {
    import-module WebAdministration
  }
}

Answer 1

This is probably a bit late to help you, but here is how we do this:

$iisVersion = Get-ItemProperty "HKLM:\software\microsoft\InetStp";
if ($iisVersion.MajorVersion -eq 7)
{
    if ($iisVersion.MinorVersion -ge 5)
    {
        Import-Module WebAdministration;
    }           
    else
    {
        if (-not (Get-PSSnapIn | Where {$_.Name -eq "WebAdministration";})) {
            Add-PSSnapIn WebAdministration;
        }
    }
}

Answer 2

Is it possible to catch the error from one or the other, and do the opposite. Dont have my shell handy but something like:

$succeeded = import-module WebAdministration
if (($succeeded -ne $null) -and ($succeeded.GetType() -eq [System.Exception]) {
  #Could not import, trying to snapin
  add-pssnapin WebAdministration
}

Actually thinking about this a bit more...

$hasSnapin = get-pssnapin | Select { $_.Name.toLower().Trim() = "webadministration" }
if ($hasSnapin -ne $null) {
  add-pssnapin WebAdministration
} else {
  import-module WebAdministration
}

On the first one, I know the error type check will probably need to be modified. As far as the work going on, this can actually be done in C# by looking in the registry for loaded snapins, or the IIS version installed on the machine and then use the appropriate method.

Answer 3

This is great. All I had to do was add an else so it would add the snap-in when run on Windows 2008. This works in scripts for my situation.

Function Load-WebAdmin {
  $webAdminModule = get-module -ListAvailable | ? { $_.Name -eq "webadministration" }
  If ($webAdminModule -ne $null) {
    import-module WebAdministration
  }else{
    Add-pssnapin WebAdministration
   }
}

Answer 4

Another way using Windows version:

if ([System.Version](Get-ItemProperty -path "HKLM:\Software\Microsoft\Windows NT\CurrentVersion").CurrentVersion -ge [System.Version] "6.1")
{ Import-Module WebAdministration }
else
{ Add-PSSnapin WebAdministration }

Answer 5

I ran into this problem today and here is solution I used

Add-PSSnapin WebAdministration -ErrorAction SilentlyContinue

Import-Module WebAdministration -ErrorAction SilentlyContinue

The only situation this does not work in was if the iis powershell snapin is not installed at all.

Answer 6

If you want to create "pre-configured" PowerShell sessions, look into PowerShell console files e.g.:

man Export-Console -full

You can create one for use on Win7 and Server 2008 R2 and another for use on Server08.