WebAdministration Module - Change "Home" Level Properties

[glenn2223]

Steps to reproduce

None, more of a feature request.

Expected behavior

To be able to change properties at "Home" (server) level in IIS

Actual behavior

This option is not available

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.14393.4583
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.4583
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Summary

I have asked about changing a specific property on stack overflow and this feature doesn't seem to be available (maybe it's not even possible).

I have one public IP address and, in IIS, 3 websites and 2 FTP sites. Not a problem, thanks to named bindings. However, IIS is a little broken when it comes to "correctly" choosing the path/certificate on said named bindings. I can't remember the link I used but you must specify the FTP SSL certificate at "Home" level AND at site level in order to establish a secure FTP connection.

I use Certify to manage my certificates and need to have a PowerShell command to transfer the certificate it creates to the other FTP site and to the top server level (or Home) in IIS.

Below is the PowerShell script I have and, as you can see, I have already tried setting it for the "Default Web Site".

Import-Module WebAdministration
$configItem = 'ftpServer.security.ssl.serverCertHash'
$thumb = Get-ItemProperty "IIS:\Sites\FTP 1" -Name ftpServer.security.ssl.serverCertHash.Value
Set-ItemProperty "IIS:\Sites\Default Web Site" -Name $configItem -Value $thumb
Set-ItemProperty "IIS:\Sites\FTP 2" -Name $configItem -Value $thumb

---

Side-bar: is there somewhere I can report the main problem (with IIS itself)

Though this is needed because of an issue with IIS; personally, I still think that setting top-level properties could still be required 😁