Win2003 for multiple internet domains? How-to?

Hi!
I could buy a nice server from my company, becuase they are doing
hardware upgrades. It is a HP Proliant DL360, with 2x146GB HDs, 2x
DualCore XEONs, 4GB RAM. Also a left-over Win2003SBS (incl SQL and
Exchange) is coming with it.
I want to place it in a datacenter and host my own domain on it,
together with some domains of friends and organisations. The Power and
data volume should be more than enough.

But I am still in doubt what OS I should use. I can install a
classical LAMP (Linux, Apache, MySQL, PHP) on it, and use POP3 Mails.
There are even OpenSource Exchange-clones, so I could offer something
like OWA. On the other hand, I could do an install of Win2003 and
Exchange. PHP will also run on Windows, so that won't be the problem.

But: how do I configure a Windows 2003 system for multiple domains?
I'd like to host abc.com, def.com and ghi.org, each with their own
websites and independant mail-systems. With LAMP this is rather
simple, vhost.conf for Apache and it's working. How can I do this on
Windows?

Any tips and/or links to some how-to's?

Thanx in advance!

"Ardjan" <ardjan (at) besse (dot) at> wrote:
>
> But: how do I configure a Windows 2003 system for multiple domains?
> I'd like to host abc.com, def.com and ghi.org, each with their own
> websites and independant mail-systems.

Hi,

IIS can host websites for different domains, even with a single public IP
address through host headers. You will need separate public IPs only if you
want to use SSL.

Exchange can also host e-mail for multiple domains, not sure about the SBS
version though, it could be limited in its functions.

ThePro

Ardjan,
You can host multiple sites in IIS. With http you can use host headers to
run multiple sites on one IP address. With https you need distinct IP
addresses and certificates.
Exchange can host multiple domains. Everyone will need to be a user in your
single AD domain, but they can have different aliases and internet domains.
Obviously any global settings are going to apply to all customers.
However every user will require both a Windows client license and an
Exchange client license.
Otherwise, depending on your objectives, you can run non-Windows mail, or
non-Windows OS with non-Windows mail, but here may not be the best place to
get advice about how to do that.
Anthony,
http://www.airdesk.com


"Ardjan" <ardjan (at) besse (dot) at> wrote in message
news:...
> Hi!
> I could buy a nice server from my company, becuase they are doing
> hardware upgrades. It is a HP Proliant DL360, with 2x146GB HDs, 2x
> DualCore XEONs, 4GB RAM. Also a left-over Win2003SBS (incl SQL and
> Exchange) is coming with it.
> I want to place it in a datacenter and host my own domain on it,
> together with some domains of friends and organisations. The Power and
> data volume should be more than enough.
>
> But I am still in doubt what OS I should use. I can install a
> classical LAMP (Linux, Apache, MySQL, PHP) on it, and use POP3 Mails.
> There are even OpenSource Exchange-clones, so I could offer something
> like OWA. On the other hand, I could do an install of Win2003 and
> Exchange. PHP will also run on Windows, so that won't be the problem.
>
> But: how do I configure a Windows 2003 system for multiple domains?
> I'd like to host abc.com, def.com and ghi.org, each with their own
> websites and independant mail-systems. With LAMP this is rather
> simple, vhost.conf for Apache and it's working. How can I do this on
> Windows?
>
> Any tips and/or links to some how-to's?
>
> Thanx in advance!

wrote:
> On 12 jan, 03:54, "Bill Kearney" <wkearne...@hotmail.com> wrote:
>> Not a particularly compelling setup. Dirt cheap on fleabay these
>> days.
>> That and since it uses SCSI drives it'll be expensive to upgrade. No
>> thanks.
> Thanks for this information, but since I have already bought this
> server for EUR 20,- (~ US$ 25,-), I have to live with it. Sorry that I
> couldn't buy the new servers for almost nothing... :-)
>
>> Sure about those licenses?
> Yes. This was a server from before the time the company switched to
> Volume Licenses. It has a normal Windows 2003 SBS Premium license.

What about CALs? Note that SBS isn't really suitable for hosting websites.
You shouldn't host public websites on an Exchange server, either - the risk
of an exploit is too great.
>
>> Before you pay for rack space look into either better hardware or
>> just use a hosted solution.
> No thanks. I have the server already, and want to go through this. The
> organisations which will switch to my server will pay me (instead of
> the hosting they have at this moment), so the co-locating costs will
> be rather low for me, if I will pay anything at all.
>
> Thank you for your help, but it didn't answer my questions at all...
>
> Ardjan