Could anyone tell me whether it's possible to entirely disable IIS and
not impact other Exchange 2003 operations please? I'm considering
disabling the 'WWW Publishing' and 'IIS Admin' services so that the
server is no longer listening on port 80.
I'm running Cisco Unity Voicemail, with a single Exchange 2003 SP2
server, so there's no need to offer OWA as users themselves never
login to a mailbox.
Many thanks
James.
I would leave it be. What's the harm? It's very useful for testing.
You can block access to it from the internert entirely (and you'd never want
to have port 80 open to your Exchange server anyway). You can also disable
OWA access per mailbox.
I wouldn't mess around with IIS.
"James.Brown" <james.m...@googlemail.com> wrote in message
news:cd6b4da1-bd55-4722...@k8g2000yqn.googlegroups.com...
ActiveSync and OMA will stop working, but if you don't want to use OWA, you
probably won't care about that. You won't be able to use Exchange
Management Console to administer your Public Folder, since EMC uses WebDAV
to retrieve information about them, and WebDAV is an extension of HTTP. If
you are prepared to use Outlook for PF admin (which is probably actually
better), then you can live without IIS. Oh, Entourage clients might not
work, either. They want to use WebDAV to communicate with the server, and
I'm not sure how they'll react if it's not available. Probably not work,
unless they can fall back on RPC.
Lee.
--
______________________________________
Outlook Web Access For PDA , OWA For WAP
www.leederbyshire.com
lee a.t leederbyshire d.o.t c.o.m
______________________________________
"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in
message news:#S4YLlx#JHA....@TK2MSFTNGP04.phx.gbl...
Thank you very much for your responses. I think I will go ahead and
disable IISAdmin and associated services. This exchange server exists
for one purpose alone - to allow the Cisco Unity Message Store account
to file away and retrieve voicemails using MAPI. It's outside our
normal domain, so any services I can cut down on are a good thing, as
our normal security policies and patching doesn't reach here. I just
wanted to check that there's no internal Exchange processes that rely
on port 80 to achieve their tasks.
Regards
James.
On 2 July, 15:55, "Martin Blackstone [MVP]" <mart...@myrealbox.com>
wrote:
> Crap. I forgot about the WM devices
>
> "Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in
> messagenews:#S4YLlx#JHA....@TK2MSFTNGP04.phx.gbl...
>
> > "James.Brown" <james.m.h.br...@googlemail.com> wrote in message