Iis – Powershell IIS plugin – cmdlets not working

iispowershell

I'm pretty much a novice at Powershell so bear with my noobness. I'm specifically trying to run the "Get-WebBinding" cmdlet (which I have successfully run on some of my other servers)

Windows Server 2008 R2 Standard:

Get-PsProvider

Shows the WebAdministration module is not loaded

Import-Module WebAdministration

An error occurs. "Cannot be loaded because the execution of scripts is disabled….."

Get-ExecutionPolicy

Output is "restricted"

Set-ExecutionPolicy RemoteSigned

Confirmed with a Yes.

Import-Module WebAdministration

An error occurs. "…skipped because it's already present"

Get-PsProvider

Shows that WebAdministration is now installed

Get-WebBinding (the cmdlet I really want to run)

Another error. "not found"

Any ideas why this cmdlet won't run?

Best Answer

Not sure if you managed to sort it but I do a bunch of stuff in IIS and need to run the following to enable it all:

Import-Module WebAdministration
[System.Reflection.Assembly]::LoadFrom("C:\windows\system32\inetsrv\Microsoft.Web.Administration.dll") | Out-Null

Related Solutions

IIS Administration PowerShell Cmdlets on Windows 2008 R1

You need to load the snapin containing the cmdlets. (A snapin is the PSH1, supported in V2, means of implementing cmdlets. In V2 modules are a better, more flexible, approach.)

There are some details here: http://learn.iis.net/page.aspx/429/installing-the-iis-70-powershell-snap-in/ which details the shortcut installed which is pre-configured with the snapin loaded.

Sql-server – Powershell execution policy within SQL Server

First, run the powershell command "Get-ExecutionPolicy -List" (as mentioned in the error message). This will give you a list of the different execution policy scopes and which setting is defined in which scope.

This list of scopes has an order of precedence (MachinePolicy, UserPolicy, Process, CurrentUser, LocalMachine). Each of these scopes can have a different setting;

Restricted
AllSigned
RemoteSigned
Unrestricted
Bypass
Undefined

Powershell will evaluate these scopes in the order listed and apply the first setting that is set to something other than 'Undefined'.

The error you're getting when running 'Set-ExecutionPolicy' indicates that you have a setting of 'Restricted' defined at a more specific scope than the default of LocalMachine. The Get-ExecutionPolicy -List cmdlet will tell you where.

If the Restricted setting is applied in either the LocalUser or Process scopes then you can change this. Use the Set-ExecutionPolicy cmdlet, but specify the scope using the -scope parameter. For example;

Set-ExecutionPolicy -Scope Process RemoteSigned

If the Restricted setting is defined at either the MachinePolicy or UserPolicy scopes then this indicates your domain administrators have configured a group policy that is overriding your local settings. This is where you would need to go and talk to them and see if you can have a less restrictive setting applied via GPO.

To the best of my knowledge you cannot easily override the GPO settings locally; however if I'm wrong on this then someone please do correct me! :)

Best Answer

Related Solutions

IIS Administration PowerShell Cmdlets on Windows 2008 R1

Sql-server – Powershell execution policy within SQL Server

Related Topic