D
DWright PSM
Hi,
Our software team have developed several pieces of code that use the client elements of the Windows Message Queuing Services HTTP support feature. When I enable this feature in both Windows Server and Windows Client, a large chunk of IIS also gets enabled.
However, I don't really want IIS enabled as the application doesn't need it (the applications run fine with both the Default Website (with the MSMQ Virtual Directory) shutdown and/or the IIS Admin shutdown and/or the WWW Publishing Service shutdown) and leaving un-necessary roles enabled goes against the general guidance of managing systems...
Hence, I am trying to find out if the MSMQ with HTTP "client" feature can be enabled with also enabling IIS?
If this is not possible, what is the accepted best way of minimising the system attack vectors that this enables, whilst ensuring that it causes minimal issues (eg. Windows Updates failing because the IIS Admin service is disabled).
Thanks for any pointers!
Continue reading...
Our software team have developed several pieces of code that use the client elements of the Windows Message Queuing Services HTTP support feature. When I enable this feature in both Windows Server and Windows Client, a large chunk of IIS also gets enabled.
However, I don't really want IIS enabled as the application doesn't need it (the applications run fine with both the Default Website (with the MSMQ Virtual Directory) shutdown and/or the IIS Admin shutdown and/or the WWW Publishing Service shutdown) and leaving un-necessary roles enabled goes against the general guidance of managing systems...
Hence, I am trying to find out if the MSMQ with HTTP "client" feature can be enabled with also enabling IIS?
If this is not possible, what is the accepted best way of minimising the system attack vectors that this enables, whilst ensuring that it causes minimal issues (eg. Windows Updates failing because the IIS Admin service is disabled).
Thanks for any pointers!
Continue reading...