Re: Server Configuration Help

Hello Wayne,

Start here:
http://support.microsoft.com/kb/555073

And i suggest to post this to:
microsoft.public.windows.server.sbs

Upgrading to normal windows domain is not that simple and you can not use
ADMT for it.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi everyone,
> I'm looking for some advice on setting up and configuring a few
> different servers for a company that has been using Small Business
> Server 2003 Standard for a couple of years and are now considering a
> move to a different configuration.
> Basically they have outgrown their current setup and have asked me to
> explore the possibility of setting up something similar to the
> following:
>
> 3x Servers with the following configurations:
> - Server 1: Windows Server 2003 Enterprise with Domain Controller, DNS
> and DHCP
> - Server 2: Windows Server 2003 Standard with Exchange Server 2003
> - Server 3: Windows Server 2003 Web Server configured with IIS
> They have a single broadband connection with one static IP address and
> I guess really what I'm looking for is some documentation or white
> papers that I can read up on before I move over to setting up a test
> configuration, and ultimately a production environment.
>
> Small Business Server 2003 has been a really good environment for them
> up to this point but they have now outgrown the limitations on this
> setup, and as SBS almost configures everything through a series of
> wizards etc, the new setup will probably involve quite a considerable
> manual configuration to achieve a production environment and I would
> really appreciate any documentation or white papers that you can point
> me to that would give me a fairly good insight into setting up this
> type of environment.
>
> Any help, pointers or suggestions would be very gratefully
> appreciated.
>
> Many thanks in advance
> Wayn

Hi
Thanks for taking the time to reply to my post, its very much appreciated.

Just to clarify, I'm not really looking to upgrade from the SBS
configuration, but ideally to start from scratch with the setup (or similar)
that I mentioned in my original post, and that was why I sent the message to
this group as opposed to the SBS group.

I only mentioned the current SBS configuration to give you an idea of how
things are currently set up and what the intentions were for a brand new
configuration, and also to highlight that the SBS configuration tends to set
everything up through a series of wizards, while a new configuration
incorporating a Windows 2003 Server setup would I suspect involve quite a
lot of manual configuration to achieve a working production environment.

I'm quite happy to leave the SBS alone altogether and let the company
continue with that setup until I have first gone through a test
configuration to give me the opportunity to test my own knowledge when it
comes to setting something like this up from scratch, once I am comfortable
and confident that I know what I'm doing, then I intend to take that a step
further and create the working production environment, and only then will I
shut down the SBS setup and switch everything over to the new clean Server
2003 environment.

This is really why I was looking for some documentation or white papers to
read through first so I can try and be aware of what I need to do before
diving in head first and making a hash of everything.

Thanks
Wayne


"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news: .com...
> Hello Wayne,
>
> Start here:
> http://support.microsoft.com/kb/555073
>
> And i suggest to post this to:
> microsoft.public.windows.server.sbs
>
> Upgrading to normal windows domain is not that simple and you can not use
> ADMT for it.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Hi everyone,
>> I'm looking for some advice on setting up and configuring a few
>> different servers for a company that has been using Small Business
>> Server 2003 Standard for a couple of years and are now considering a
>> move to a different configuration.
>> Basically they have outgrown their current setup and have asked me to
>> explore the possibility of setting up something similar to the
>> following:
>>
>> 3x Servers with the following configurations:
>> - Server 1: Windows Server 2003 Enterprise with Domain Controller, DNS
>> and DHCP
>> - Server 2: Windows Server 2003 Standard with Exchange Server 2003
>> - Server 3: Windows Server 2003 Web Server configured with IIS
>> They have a single broadband connection with one static IP address and
>> I guess really what I'm looking for is some documentation or white
>> papers that I can read up on before I move over to setting up a test
>> configuration, and ultimately a production environment.
>>
>> Small Business Server 2003 has been a really good environment for them
>> up to this point but they have now outgrown the limitations on this
>> setup, and as SBS almost configures everything through a series of
>> wizards etc, the new setup will probably involve quite a considerable
>> manual configuration to achieve a production environment and I would
>> really appreciate any documentation or white papers that you can point
>> me to that would give me a fairly good insight into setting up this
>> type of environment.
>>
>> Any help, pointers or suggestions would be very gratefully
>> appreciated.
>>
>> Many thanks in advance
>> Wayne
>
>

Hello Wayne,

Start here, there are the most roles defined you need:
http://technet.microsoft.com/en-us/l.../cc787486.aspx

Exchange 2003:
http://www.microsoft.com/downloads/d...displaylang=en

IIS:
http://support.microsoft.com/kb/324742

Some additional infos:
- you should have at least 2 DC's in a domain for redundancy and in case
of failure the AD database is still exisiting
- do NOT multihome(2 different ip's on 2 NIC's) domain controllers like you
know it from SBS
- the web or mailserver should NOT be used for DC role, this kind of servers
should always run on member machines
- Domain machines should always use only the domain internal DNS server and
NO externals like the ISP's, this should be configured as a FORWARDER
- you should think about any kind of firewall, either hardware or software(ISA
server), a webserver you should place in a DMZ if you use a firewall that
is capable of that (e.g. CISCO ASA), so that it is separated from the domain
internal network, in case it will be hacked the domain is still secured
- DNS zones i would use AD integrated on both above mentioned DC's, also
for redundancy
- make all DC's Global catalog server, no problem in a sibgle forest domain
-DHCP you can also run redundant on 2 DC's: http://technet.microsoft.com/en-us/l.../cc780311.aspx
doesn't matter if it is 80/20 or 50/50 or 70/30

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi
> Thanks for taking the time to reply to my post, its very much
> appreciated.
> Just to clarify, I'm not really looking to upgrade from the SBS
> configuration, but ideally to start from scratch with the setup (or
> similar) that I mentioned in my original post, and that was why I sent
> the message to this group as opposed to the SBS group.
>
> I only mentioned the current SBS configuration to give you an idea of
> how things are currently set up and what the intentions were for a
> brand new configuration, and also to highlight that the SBS
> configuration tends to set everything up through a series of wizards,
> while a new configuration incorporating a Windows 2003 Server setup
> would I suspect involve quite a lot of manual configuration to achieve
> a working production environment.
>
> I'm quite happy to leave the SBS alone altogether and let the company
> continue with that setup until I have first gone through a test
> configuration to give me the opportunity to test my own knowledge when
> it comes to setting something like this up from scratch, once I am
> comfortable and confident that I know what I'm doing, then I intend to
> take that a step further and create the working production
> environment, and only then will I shut down the SBS setup and switch
> everything over to the new clean Server 2003 environment.
>
> This is really why I was looking for some documentation or white
> papers to read through first so I can try and be aware of what I need
> to do before diving in head first and making a hash of everything.
>
> Thanks
> Wayne
> "Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
> news: .com...
>
>> Hello Wayne,
>>
>> Start here:
>> http://support.microsoft.com/kb/555073
>> And i suggest to post this to:
>> microsoft.public.windows.server.sbs
>> Upgrading to normal windows domain is not that simple and you can not
>> use ADMT for it.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Hi everyone,
>>> I'm looking for some advice on setting up and configuring a few
>>> different servers for a company that has been using Small Business
>>> Server 2003 Standard for a couple of years and are now considering a
>>> move to a different configuration.
>>> Basically they have outgrown their current setup and have asked me
>>> to
>>> explore the possibility of setting up something similar to the
>>> following:
>>> 3x Servers with the following configurations:
>>> - Server 1: Windows Server 2003 Enterprise with Domain Controller,
>>> DNS
>>> and DHCP
>>> - Server 2: Windows Server 2003 Standard with Exchange Server 2003
>>> - Server 3: Windows Server 2003 Web Server configured with IIS
>>> They have a single broadband connection with one static IP address
>>> and
>>> I guess really what I'm looking for is some documentation or white
>>> papers that I can read up on before I move over to setting up a test
>>> configuration, and ultimately a production environment.
>>> Small Business Server 2003 has been a really good environment for
>>> them up to this point but they have now outgrown the limitations on
>>> this setup, and as SBS almost configures everything through a series
>>> of wizards etc, the new setup will probably involve quite a
>>> considerable manual configuration to achieve a production
>>> environment and I would really appreciate any documentation or white
>>> papers that you can point me to that would give me a fairly good
>>> insight into setting up this type of environment.
>>>
>>> Any help, pointers or suggestions would be very gratefully
>>> appreciated.
>>>
>>> Many thanks in advance
>>> Wayne

"Wayne Smith" <> wrote in message
news:948A521E-9893-4AC6-801F-...
>>> - Server 1: Windows Server 2003 Enterprise with Domain Controller, DNS
>>> and DHCP
>>> - Server 2: Windows Server 2003 Standard with Exchange Server 2003
>>> - Server 3: Windows Server 2003 Web Server configured with IIS

Forget the Enterprise Edition,...it is pointless and a waste of money in
your case. Use Standard Edition on all three.

You forgot the Firewall. The Firewall can either be an appliance or a 4th
dedicated Server. MS's ISA Server comes in both a PC and an Appliance
format, if you choose that.
Do not try to build a Firewall out of any of the three Servers you listed.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Hi Phillip,
Thanks for your input, these little nuggets of information are really
invaluable to me and I appreciate you taking the time to post a reply to my
message.

The only reason I originally opted to use the Enterprise edition in the main
server was because I assumed (wrongly it seems) that only the Enterprise
edition of Server 2003 allowed you to setup a DC and DNS, I thought that was
the main difference and advantage of the Enterprise edition and if that's
not the case, then then Standard edition will be more than adequate.

I will take on board what you have said and build it into my plan from the
outset.

Thanks again
Wayne


"Phillip Windell" <> wrote in message
news:OVv6Z$...
> "Wayne Smith" <> wrote in message
> news:948A521E-9893-4AC6-801F-...
>>>> - Server 1: Windows Server 2003 Enterprise with Domain Controller, DNS
>>>> and DHCP
>>>> - Server 2: Windows Server 2003 Standard with Exchange Server 2003
>>>> - Server 3: Windows Server 2003 Web Server configured with IIS
>
> Forget the Enterprise Edition,...it is pointless and a waste of money in
> your case. Use Standard Edition on all three.
>
> You forgot the Firewall. The Firewall can either be an appliance or a 4th
> dedicated Server. MS's ISA Server comes in both a PC and an Appliance
> format, if you choose that.
> Do not try to build a Firewall out of any of the three Servers you listed.
>
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>

"Wayne Smith" <> wrote in message
news:8987A504-A2CF-432A-92DC-...
> Hi Phillip,
> Thanks for your input, these little nuggets of information are really
> invaluable to me and I appreciate you taking the time to post a reply to
> my message.
>
> The only reason I originally opted to use the Enterprise edition in the
> main server was because I assumed (wrongly it seems) that only the
> Enterprise edition of Server 2003 allowed you to setup a DC and DNS, I
> thought that was the main difference and advantage of the Enterprise
> edition

No. The primary differece is the ability to do Server Clustering. There are
other more obscure differences in limits and limitations that I couldn't
list or care to worry about for this thread.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------