2

Im autodeploying an old website which have this binding:

net.tcp 808:*

But when I use WebAdministration to set it like this:

New-WebBinding -Name "site" -Procotol "net.tcp" -Port 808

I get this binding:

net.tcp *:808:

Are they the same?

Christian Mikkelsen
  • 1,661
  • 2
  • 19
  • 44
  • Nevermind, I can use: New-ItemProperty -Path "IIS:\sites\sitename" -Name Bindings -value @{protocol="net.tcp"; bindingInformation="808:*"} to achieve the same. Thx to: http://stackoverflow.com/questions/9424362/why-powershells-new-webbinding-commandlet-creates-incorrect-hostheader – Christian Mikkelsen Nov 15 '13 at 13:01

1 Answers1

5

Nevermind, I can use:

New-ItemProperty -Path "IIS:\sites\sitename" -Name Bindings -value @{protocol="net.tcp"; bindingInformation="808:*"}

to achieve the same.

Thx to: Why Powershell's New-WebBinding commandlet creates incorrect HostHeader?

Community
  • 1
  • 1
Christian Mikkelsen
  • 1,661
  • 2
  • 19
  • 44