Re: New install into existing subnet

Thanks for your advice.

We have already got a trial installation running on a completely separate
mini-network, and everything _seems_ to be OK!

We've decided through today to go the 'cold turkey' route and switch the
email to exchange from 9:00am tomorrow. The email junkies will have to do
without their hour-by-hour fix until their machine gets connected to the
domain and outlook set up! Tuff.

It will cause howls of protest, but it saves a lot of buggering about in the
long run.

Thanks for your help.

:)

--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Check out the Entourage User's WebLog for hints, tips and troubleshooting
<http://homepage.mac.com/barryw/weblog/weblog.html>


From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Date: Fri, 10 Feb 2006 03:31:53 +1100
Subject: Re: New install into existing subnet

http://seanda.blogspot.com/2004/10/having-trouble-trusting-exchange-from.html

Your existing mail system could stay in place, you could continue to use OE
on the clients but I'd swing them to Outlook.

Though you don't wish to immediately move to Exchange it is the most
integrated SBS application, install it.

AND it sounds like you're new to SBS. Do yourself a favour and do a practice
install or two, get familiar with her. It's popular here for us to suggest
that you get your SBS install right on about the third go, once to run
through a 'bog standard' installation, once to try modifying items during
the installation, and finally the production system.

"Barry Wainwright [MVP]" <barry@xxxxxxxxxxxxxxxx> wrote in message
news:C010CC00.9C389%barry@xxxxxxxxxxxxxxxxxxx
No, there is no existing AD - this is a fresh install into a peer to peer
'network' running a mix of winXPpro & w98 machines.

Our priorities were to get the file sharing working first (limited
resources
(me & one other) stop us changing everything at once), then switch email
over to exchange sometime next week. I was hoping I could leave the
existing
email system in place until then.

--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Check out the Entourage User's WebLog for hints, tips and troubleshooting
<http://homepage.mac.com/barryw/weblog/weblog.html>


From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Date: Thu, 9 Feb 2006 21:11:07 +1100
Subject: Re: New install into existing subnet

Is there an existing AD?
http://support.microsoft.com/default.aspx?scid=kb;en-us;884453
How to install Small Business Server 2003 in an existing Active Directory
domain

there's no reason (AFAICS) for you to implement a new subnet.

If the existing network was SBS you might want to look at
www.sbsmigration.com but I read your post as suggesting no current AD and
no
existing Exchange (though you are using an alternate mail server).

Fine, install SBS default. Join the workgroup workstations to the SBS in
the
standard manner (http://sbs/connectcomputer), import their OE email into
Outlook (and therefore Exchange), live happily ever after.


"Barry Wainwright [MVP]" <barry@xxxxxxxxxxxxxxxx> wrote in message
news:C010B5B8.9C350%barry@xxxxxxxxxxxxxxxxxxx
I'm planning to roll out a new installation of SBS (standard) into a 16
user
existing network this weekend.

The current system is using a network on a 192.168.0.x subnet (with
(mainly)
static IPs). This includes a mail server serving POP mail & smtp to the
clients who are running OE.

We want to introduce SBS into this, but with minimum disruption. It's
our
plan to leave the users on OE collecting mail from the existing server
until
all the desktops and laptops (some of which will not be on-site for a
few
days) have been set up with server '03. Then, at some point next week,
we
will switch them all over to exchange & outlook.

We are planning to leave the existing 192.168.0.x subnet in place, but
add
the SBS server into this network. The server is currently set up to have
one
network card (the external one) use this subnet (because it would need
to
talk to the router currently doing NAT to the outside world). The
internal
network card on the server will be set to a subnet of 192.168.1.x.

As an intermediate step, we were planning to put both these subnets on
the
same wires, by plugging both network cards on the sbs server into the
same
switch. Current clients in their current config will simply not see this
other subnet. As we integrate them into the win 2k03 network we can set
the
subnet mask to 255.255.254.0, so they should be able to see both the
current
mail server and the SBS file server 9these machines will then be
entering
the domain of the sbs server).

When all machines are in the sbs domain, we can switch over to exchange,
push the outlook clients out to the client machines and remove the
192.168.0.x traffic from the internal network

Does this sound reasonable? I know it's hard to describe without the
diagrams on the flip chart for you to look at, but I hope you get the
gist...

--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Check out the Entourage User's WebLog for hints, tips and
troubleshooting
<http://homepage.mac.com/barryw/weblog/weblog.html>


--
Barry Wainwright
Microsoft MVP (see http://mvp.support.microsoft.com for details)
Check out the Entourage User's WebLog for hints, tips and
troubleshooting
<http://homepage.mac.com/barryw/weblog/weblog.html>







.

Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • Re: Opinions on SBS 2003 for a small business
    ... I have to admit I was very impressed with all the abilities of SBS 2003 ... I have been thinking about the 3rd install today to see what things get done ... that's a network admin, and I have tapped him more than once, ... As a server solution for small businesses though, ...
    (microsoft.public.windows.server.sbs)
  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server/Network setup question
    ... Let's keep the P2P network and the ... SBS server's internal NIC to the switch. ... The internal NIC of the SBS server will default to 192.168.16.2 during the ... you change the IP of the rented printer to 192.168.16.8 (or some ...
    (microsoft.public.windows.server.sbs)
Loading