Re: Deploy a webserver?



Excellent advice. I would generally advise the same. Correct on all accounts and much less of a headache for your friendly local I.T. director.

I do realize that deploying and administering a web server is not for the faint of heart. Fortunately, I have a quasi masochistic streak and have run my own small (microscopic really) web hosting service for my clients. Still, your advice has merit and I concur with the majority of your assessment.

However, I do have this lovely Dell looking at me as we speak. As it so happens, I have a spare OS & the box that we have currently running our subdomain (long story) will make a splendid ISA Server.

This will be one site, with a sub-domain (mentioned above). I will be going with DNN externally and SP internally. I have multiple IP's and our bandwidth is up to the task. We may consider hosting member portals/sites in the future.

So, there you have it.

I am hearing that you both concur: Run it as a stand alone on it's own network segment, behind an ISA?

What do you think about the SmarterMail > Exchange > Pop3 connector?

--
Best Regards,

Marc Everlove MSCE, MCDBA

http://everlovetech.blogspot.com/

"Every day I get up and look through the Forbes list of the richest people in America. If I'm not there, I go to work."
- Robert Orben

Information conveyed here is intended as advice and is offered without warranty. Use it at your own discretion.

"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message news:%23xWE8LfNIHA.4272@xxxxxxxxxxxxxxxxxxxxxxx
The expense of maintaining a single secure web server is generally much more
than hosting charges where the hosting company amortises cost over many
servers and clients.

You have active maintenance of the server, increased cost of internet
connectivity in order to give web visitors a reasonable browsing experience,
the hardware and software cost of the box itself.

As Claus suggests, if you insist on doing it, do it as an isolated box.

OH, and if you want HTTPS to the box _and_ SBS (RWW, OWA, etc...) you'll
need multiple IP's from your ISP.

"Marc Everlove" <marc@xxxxxxxxxxxxxxx> wrote in message
news:%23Hrqf9eNIHA.5860@xxxxxxxxxxxxxxxxxxxxxxx
There are a number of reasons.

Chief amongst them; our needs will exceeed a shared hosting package and we
would like to avoid the recurring expense of a dedicated or co-located
server.

--
Best Regards,

Marc Everlove MSCE, MCDBA

http://everlovetech.blogspot.com/

"Every day I get up and look through the Forbes list of the richest people
in America. If I'm not there, I go to work."
- Robert Orben

Information conveyed here is intended as advice and is offered without
warranty. Use it at your own discretion.

"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ukTm1weNIHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
'Best practice' is to use a 3rd party hosting service.

What is the purpose of this webserver? Why do you wish to have it
inhouse? (eg. some people believe that because they wish to provide
access to a database used both by internal and external users that
inhouse is desirable. In most cases they are wrong and the inhouse
database and that of the hosted service should interact in some manner.)

"Marc Everlove" <marc@xxxxxxxxxxxxxxx> wrote in message
news:OvMKFXeNIHA.4136@xxxxxxxxxxxxxxxxxxxxxxx
I have an SBS domain. I would like to deploy a new server as a webserver.
I am considering options and designing the topology right now. I would
like to get a "best practice" consensus from the community. I have a few
different scenarios in mind, but wanted to get a broader opinion.

I have considered deploying an ISA server, though my last foray with ISA
was less than encouraging...

I was also considering deploying it as a standalone, though I would like
to use Exchange as a mail server.

Let me know what you think ...

--
Best Regards,

Marc Everlove MSCE, MCDBA

http://realestatetechonline.com

"Every day I get up and look through the Forbes list of the richest
people in America. If I'm not there, I go to work."
- Robert Orben

Information conveyed here is intended as advice and is offered without
warranty. Use it at your own discretion.









Relevant Pages

  • New installation
    ... I am getting ready to setup an ISA Server and I need a lot of advice. ... Is ISA cluster aware so that I can create a failover cluster? ...
    (microsoft.public.isaserver)
  • Is ISA Server sufficient ?
    ... I am going to be hosting a commercial website on a dedicated server ... Is ISA Server sufficient? ...
    (comp.security.misc)
  • ISA Server out of the domain
    ... I have an ISA 2000 server in a AD2000 domain. ... This ISA server is a proxy only. ... Thanks for your advice. ...
    (microsoft.public.isaserver)
  • Re: Basic NT4 to w2k3 migration questions
    ... > The easiest way and the least disruptive is to upgrade your existing PDC ... If you can't do that then use the "advice". ... >> hardware and then upgrading it to w2k3 which sounds a bit idiotic to me. ... This includes a Windows 2003 Exchance server. ...
    (microsoft.public.windows.server.migration)
  • Re: Basic NT4 to w2k3 migration questions
    ... The easiest way and the least disruptive is to upgrade your existing PDC ... If you can't do that then use the "advice". ... > hardware and then upgrading it to w2k3 which sounds a bit idiotic to me. ... This includes a Windows 2003 Exchance server. ...
    (microsoft.public.windows.server.migration)