"Susan Bradley" <sbradcpa@newsgroup> wrote in message
> Your users can't type in an "s"? Really they can't be taught that little
> thing? I may be jaded admin but if they can't be taught that, should they
> have remote access in the first place?
> The reason why I keep the 80 closed is that it keeps me a little bit less
> paranoid. It's one less port for me to keep watch on.
> Is it safe? Depends. What's the complexity of the passwords?
I've setup all my non-SBS customers with a redirect for OWA using redirect
command in an asp page. For SBS customers, I have the SBS Welcome page
redirected, and removed Anonymous, so they must log in. Once in, I even
altered the welcome page to add an SSL VPN link to the Cisco ASA to direclty
download the SSL VPN client, as well as added a link to the OWA site.
Believe me, after I did that a few years ago, the phone calls regarding that
the OWA site won't work, went down to zero, of course unless the link or
Exchange was down. You can tell them until you're blue in the face, and
there's always that one or two that have selective listening skills that
will be calling. And if you're late responding (this happened witha specific
140 seat customer where I was just a consultant for their network admin),
they go complaining to the owner, who'll call me directly. I simply explain
that it's in the one page document how-to that I created and emailed
everyone, which is available in a public folder, as well as thumbtacked on
the bulletin board in the lunch room. The boss winds up laughing, which is
cool, but I got tired of it and just setup a redirect.
The easier you make it for them, the less phone calls. :-)