Server 2016中如何使用新版本的IISAdministration PowerShell模块？

Let’s walk through the most likely fixes for your problem—since you’ve got both the system-built-in and updated user-installed versions of the IISAdministration module, conflicts or version prioritization are probably the root cause. Here’s what to check:

1. Confirm Which Module Version is Actually Loaded #

PowerShell might quietly use the older system module even if you tried importing the new one. Run this to see which version is active:

Get-Module -Name IISAdministration

If the listed version isn’t the updated one you installed from the Gallery, explicitly import the newer version either by specifying its version number:

# Replace 1.1.0.0 with your actual installed version
Import-Module IISAdministration -Version 1.1.0.0

Or point directly to the user-specific module file:

Import-Module "$env:USERPROFILE\Documents\WindowsPowerShell\Modules\IISAdministration\<your-version>\IISAdministration.psd1"

2. Verify the Command Exists in the Loaded Module #

It’s possible the updated module has command name changes or parameter updates. Let’s check if New-IISSiteBinding is available in the loaded module:

Get-Command -Module IISAdministration -Name *IISSiteBinding*

If the command doesn’t show up, run Get-Help New-IISSiteBinding -Full (once the correct module is loaded) to confirm the command name and syntax—sometimes modules tweak command names between versions.

3. Fix Module Version Prioritization #

PowerShell’s auto-loading system often prioritizes system modules over user-installed ones. To force it to use your newer version:

• Use a module specification to target the exact version during import:

  Import-Module -Name @{
      ModuleName='IISAdministration';
      ModuleVersion='<your-updated-version>';
      Scope='CurrentUser'
  }
  

• Or temporarily adjust your PSModulePath to put user modules first (this only applies to the current session):

  $env:PSModulePath = "$env:USERPROFILE\Documents\WindowsPowerShell\Modules;$env:PSModulePath"
  

4. Check Permissions and Execution Policy #

New-IISSiteBinding requires admin rights to modify IIS settings. Make sure you’re running PowerShell as an Administrator. Also, double-check your execution policy isn’t blocking the module:

Get-ExecutionPolicy

If it’s set to Restricted, update it for your user account:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force

5. Reinstall the Module (If Corruption is Suspected) #

Sometimes the module installation can get messed up. Try a clean reinstall:

Uninstall-Module -Name IISAdministration -Scope CurrentUser -Force
Install-Module -Name IISAdministration -Scope CurrentUser -Verbose -Force -SkipPublisherCheck

内容的提问来源于stack exchange，提问作者Newbie