Re: Preparing for new install - Questions

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



If your home DSL is running through a firewall/router you could set a static
IP on the external SBS NIC in the range the router uses. Since you're not
going to have ISA installed I'd be a bit uncomfortable about doing that.
Hopefully in the office you plan to have a "good" hardware firewall/router
and not a low end one. All my installs are SBS 2003 PE using ISA 2004 so
obviously that's what I prefer.

"Mark Post" <post@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23Js%23mIY7GHA.4804@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Steve.

It is the Standard Edition.

I have DSL at home. I have to check if it is a dynamic or static IP
address I guess.

Are you suggesting I set up the server using my home DSL and then when I
move the server into it's final location and have my business DSL
installed that I run the CEICW again and make the changes for the new DSL?

I do have a backup plan and will have UPS on the server as well as each
workstation and will be using Trend Micro CSM for SMB.

Thanks for your help.

Mark

"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:uck$9pX7GHA.4288@xxxxxxxxxxxxxxxxxxxxxxx
Mark

It sounds like you're doing your homework on SBS. First question for you
is this SBS SE or PE and if the latter are you installing ISA 2004 with
the 2 NICs. You need to plug the NICs (I usually set static IPs on them
that don't necessarily need to be the final IPs you'll use) into a "live"
switch otherwise you'll get an error during setup. What type of Internet
connection do you have at home? Its possible to get the SBS connected
temporarily through a router so you'll also be able to do your security
patches via the new R2 WSUS feature. The most important thing on the to
do list is the CEICW. Don't forget a backup plan, antivirus protection,
and a UPS. Definitely install 3 times and come back here for more advice.
As you've probably seen there are several good SBS books to have for
reference as well.

Good luck with the new SBS and your vet clinic.

Steve

"Mark Post" <post@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OIq5RMX7GHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I'm preparing to set up an SBS Standard R2 install on a new server I
built. This is for a new veterinary clinic my wife and I are starting in
December. This is the first time I've set up a server from start to
finish and I have some questions before I get started.

I've read the suggestions to install three times prior to putting into
production and plan to do so.

Now for the questions -

The Getting Started instructions mention hooking all hardware up prior
to installing. Since I am testing all of this at home and the clinic
won't be finished for a few months I won't have my internet connection
available yet. It will be a static IP DSL once installed. Is it OK
during this testing phase to hook up everything but the router and modem
(it will be a 2 NIC set up) and work through the installation? Also,
the Getting Started guide mentions doing all of the To Do List in order
but once again I won't have internet access at the clinic established at
this time. Can I skip over that and complete the rest of the To Do List
so I can get some practice with the rest of the install? Once I feel
comfortable with the install I would like to get a headstart setting up
the Clinic Practice software so my wife can begin entering codes, etc.
Can anyone see any issue with doing that and then going back and
completing the internet set up for the server once we are at the clinic?
Finally, for now at least, I was thinking of having 4 hard drives (2
pairs of Raid 1) so that I can use 1 hard drive for the OS and another
for Data and the Clinic Practice Manager Software. I would also have a
hot spare. I'm most concerned with redundancy not speed especially since
it's such a small network. Anyone see any issues with that set up?
Initially we are only going to have 4 workstations, all running XP Pro
and all brand new. I can't see us adding more than one or two more
workstations in this location due to size and the fact that all of the
workstations with the exception of mine are shared by all staff.

Thanks so much for your insight. I've been lurking in this forum for
about two months (while waiting for SBS 2003 Standard R2 to be
delivered) trying to absorb everything in the hopes that it will make
for a smooth install. This forum has been very helpful.

Mark







.



Relevant Pages

  • Re: SBS 2003 messed up after sp3 install
    ... I feel this tool is a must for any SBS install. ... You might also want to check the binding order since you have 2 NICs: ... Check Internet access and Exchange mailboxes ...
    (microsoft.public.windows.server.sbs)
  • Re: What would you do differently?
    ... Having the PIX firewall is a good idea as it can handle the VNP stuff directly. ... Be careful not to apply the plain 2003 Server service pack as this has issues with SBS. ... I want to do a full blown SBS install I'm planning on two nics plus ISA behind a Cisco Pix 501. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2004 setup fails on brand new SBS 2003 Premium installatio
    ... And, if you haven't already, please download and run the SBS Best Practices Analyzer. ... The Change Server IP wizard can be at: ... Two Nics, a static IP address, ISA, router ... After you have the network physically set up, install ISA. ...
    (microsoft.public.windows.server.sbs)
  • Re: Two internet connections - One SBS
    ... identical questions in the SBS group. ... DSL line that is near some DSL limit and is extremely slow, ... We also have a Comcast cable connection with excellent speed, ... The SBS has two nics, one for internal and the other for external. ...
    (microsoft.public.windows.server.networking)
  • Re: Multiple domain controllers
    ... NICs + router Network Configuration ... is the loopback connector installed instead of a real NIC? ... uninstall the updates and service pack and try re-running SBS setup again. ... Did you complete the SBS Integrated Setup install before you updated the ...
    (microsoft.public.windows.server.sbs)