IIS 7 Setting LoadBalancerCapabilities

In IIS6 you had to set LoadBalancerCapabilities=1 when using windows NLB so
it would terminate the ip connection (when the app pool had an issue - which
is what I want it to do) and not return 503 error.

Now I'm using IIS 7 is the same still true (i.e. IIS assumes layer 7 load
balancing by default)? If so how do I change it to layer 3/4 so it
terminates the ip and does not return 503? To do this in IIS 6.0 I used the
following script but it doesn't work with IIS 7.

Set oIISPrv = GetObject("winmgmts:/root/MicrosoftIISv2")
Set oAppPoolSettings =
oIISPrv.Get("IIsApplicationPoolSetting='W3SVC/AppPools/DefaultAppPool'")
oAppPoolSettings.LoadBalancerCapabilities=1
oAppPoolSettings.Put_()

This fails with a 8004100e scripting error - I assume the WMI changes have
caused this but cannot find the alternative.

Cheer
s

Found the solution! its now a property of the application pool iteself (go
to advanced properties) and change "service unavailable respose type" from
HTTPLevel to TCPLevel :-)
s

"siman" <myname @ nospam.com> wrote in message
news:4968df46$0$20308$(E-Mail Removed)...
> In IIS6 you had to set LoadBalancerCapabilities=1 when using windows NLB
> so it would terminate the ip connection (when the app pool had an issue -
> which is what I want it to do) and not return 503 error.
>
> Now I'm using IIS 7 is the same still true (i.e. IIS assumes layer 7 load
> balancing by default)? If so how do I change it to layer 3/4 so it
> terminates the ip and does not return 503? To do this in IIS 6.0 I used
> the following script but it doesn't work with IIS 7.
>
> Set oIISPrv = GetObject("winmgmts:/root/MicrosoftIISv2")
> Set oAppPoolSettings =
> oIISPrv.Get("IIsApplicationPoolSetting='W3SVC/AppPools/DefaultAppPool'")
> oAppPoolSettings.LoadBalancerCapabilities=1
> oAppPoolSettings.Put_()
>
> This fails with a 8004100e scripting error - I assume the WMI changes have
> caused this but cannot find the alternative.
>
> Cheer
> s
>

Great. Sharing the solution with the commmunity, even better.

Cheers

--

augusto alvarez | it professional
MCP - MCTS - MCITP DBA
http://blog.augustoalvarez.com.ar/


"siman" <myname @ nospam.com> escribió en el mensaje de
noticias:4969ca0a$0$18159$(E-Mail Removed). ..
> Found the solution! its now a property of the application pool iteself (go
> to advanced properties) and change "service unavailable respose type" from
> HTTPLevel to TCPLevel :-)
> s
>
> "siman" <myname @ nospam.com> wrote in message
> news:4968df46$0$20308$(E-Mail Removed)...
>> In IIS6 you had to set LoadBalancerCapabilities=1 when using windows NLB
>> so it would terminate the ip connection (when the app pool had an issue -
>> which is what I want it to do) and not return 503 error.
>>
>> Now I'm using IIS 7 is the same still true (i.e. IIS assumes layer 7 load
>> balancing by default)? If so how do I change it to layer 3/4 so it
>> terminates the ip and does not return 503? To do this in IIS 6.0 I used
>> the following script but it doesn't work with IIS 7.
>>
>> Set oIISPrv = GetObject("winmgmts:/root/MicrosoftIISv2")
>> Set oAppPoolSettings =
>> oIISPrv.Get("IIsApplicationPoolSetting='W3SVC/AppPools/DefaultAppPool'")
>> oAppPoolSettings.LoadBalancerCapabilities=1
>> oAppPoolSettings.Put_()
>>
>> This fails with a 8004100e scripting error - I assume the WMI changes
>> have caused this but cannot find the alternative.
>>
>> Cheer
>> s
>>
>
>