Installing 2nd SBS2000 server

I currently have one server running Windows 2000 and
SBS2000. For the sake of this message I'll call the domain
mycompany.com. Someone else set up this server, who is
nolonger here, but said that because we already have a
website called mycompany.com we could not see
mycompany.com in our network so He said he tricked the ISA
software to use mc (short for my company) as the displayed
domain. The machine name is sbs2000.

At any rate, I am tring to install another server in the
domain to run as a backup. Actually I am upgrading NT 4.0
& SBS 4.5 TO SBS 2000 onto a NEW server.

The instuctions tell me to install W2k on the new server
but keep as a Workgroup. The machine name is sbs2000-2.
Did that.

Now when I install SBS2K on the screen that asks for
the "Full DNS name for new domain" I put in mycompany.com
and the system says it has detected a duplicate DNS domain
name on the network.

How do I name this to come up and be a member of my
current domain to run as a backup?

Dan
.

Javier
Mon Jul 21 12:46:39 CDT 2003

Dan,

There are several post addressing this issue in this NG... I would probably
do a google search on the topic and Jeff Middleton as the author.

You can have a BDC in a SBS2000 network... but it has to be plain-vanilla
Windows 2000 (or 2003). One of the limitations of SBS is that it has to be
the root of the domain... thus you cannot have two of the same kind in the
same domain. If you have a Win2k BDC and the SBS fails, users can
authenticate... but you might find this is very limited since now you don't
have Exchange, ISA... or anything that is hosted on the SBS box.

I think I read somewhere that on SBS2003 there will some changes on this (as
a backup scenario I mean)... but I really don't know.

Let me see if I can find you one or two articles on this subject...

-Javier

"Dan" <gill_daniel@yahoo.com> wrote in message
news:01e501c34fad$ff420880$a301280a@phx.gbl...
> Javier,
>
> How then do I get a backup incase the first server goes
> down. Need another server to validate logins, correct? I
> was under the impression that this would be a member
> controler and could be promoted to a domain controller if
> the other server goes down?
>
> dan
> >-----Original Message-----
> >> At any rate, I am tring to install another server in the
> >> domain to run as a backup.
> >
> >You cannot have 2 SBS servers in the same domain... so
> you need to rethink
> >your strategy.
> >
> >BTW, you should name your AD domain as mycompany.local
> and don't use your
> >FQDN.
> >
> >-Javier
> >
> >
> >.
> >

danabeckonline
Mon Jul 21 13:18:00 CDT 2003

Hello Dan,

What Javier means in this case is to simply install Windows 2000 server on
the second server. Then run dcpromo manually from Start | Run. This should
allow your second server to become a 2nd domain controller on the SBS 2000
network.

Regards,

Dana Becker
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.




|
| How then do I get a backup incase the first server goes
| down. Need another server to validate logins, correct? I
| was under the impression that this would be a member
| controler and could be promoted to a domain controller if
| the other server goes down?
|
| dan
| >-----Original Message-----
| >> At any rate, I am tring to install another server in the
| >> domain to run as a backup.
| >
| >You cannot have 2 SBS servers in the same domain... so
| you need to rethink
| >your strategy.
| >
| >BTW, you should name your AD domain as mycompany.local
| and don't use your
| >FQDN.
| >
| >-Javier
| >
| >
| >.
| >
|

Susan
Mon Jul 21 14:05:24 CDT 2003

IMHO... I get more bang for the buck if I ensure that the parts of the
server are quality than if I buy 2 servers.....

Let's say we "could" do a redundant SBS2k server setup.....

We'll buy two servers, two OS', two sets of CALs, link the suckers
together, replicate the databases...but in order to "pop" that second
server "exactly" in the place of that first server you would need
instead a Ghosting method to exactly capture the SID on the main server
so that your workstatons wouldn't freak.

Look around your office...there are SO many single points of failure
that your server is only one.....

One phone system
One fax machine?
One telephone company in your area servicing your phone
One DSL line [what no backup on that?]
One power company [PG&E says we're doing a brown out today... not much I
can do as I don't have a generator]

There are many people that post in very worried about the fact that
their single point of failure is the SBS... but quite honestly.. it's
just the most obvious. There are tons more.

Get "good quality server equipment" [RAID 5 etc] and just keep an eye on
the server.... if it's having problems... it will let you know.

Dan wrote:

> I currently have one server running Windows 2000 and
> SBS2000. For the sake of this message I'll call the domain
> mycompany.com. Someone else set up this server, who is
> nolonger here, but said that because we already have a
> website called mycompany.com we could not see
> mycompany.com in our network so He said he tricked the ISA
> software to use mc (short for my company) as the displayed
> domain. The machine name is sbs2000.
>
> At any rate, I am tring to install another server in the
> domain to run as a backup. Actually I am upgrading NT 4.0
> & SBS 4.5 TO SBS 2000 onto a NEW server.
>
> The instuctions tell me to install W2k on the new server
> but keep as a Workgroup. The machine name is sbs2000-2.
> Did that.
>
> Now when I install SBS2K on the screen that asks for
> the "Full DNS name for new domain" I put in mycompany.com
> and the system says it has detected a duplicate DNS domain
> name on the network.
>
> How do I name this to come up and be a member of my
> current domain to run as a backup?
>
> Dan
> .

--
"Don't lose sight of security. Security is a state of being,
not a state of budget. He with the most firewalls still does
not win. Put down that honeypot and keep up to date on your
patches. Demand better security from vendors and hold them
responsible. Use what you have, and make sure you know how
to use it properly and effectively."
~Rain Forest Puppy
http://www.wiretrip.net/rfp/txt/evolution.txt

Dan
Mon Jul 21 14:07:32 CDT 2003

Ok, read Jeff's articles and have a better understanding,
however, making a BDC was for my own sanity. The real
issue is that my Exch2000 is hosed. All of the reading
that I have done tells me to move the individual mail
boxes to another Exch server. Then fix the db and move the
mail back.

So, do I bring up a totally diff domain to put exch 2k?
Will Exch2K or SBS2K allow me to move mailboxes across
domains? I felt that if I am going to spend the time to
bring up another server to fix the mail, why not make a
BDC at the same time. Sounds like that's not going to
happen.

Is this a question for another board?

dan
>-----Original Message-----
>Hi Dan -
>
>First assignment (required reading) - do a Google groups
search on Fault
>Tolerance by Jeff Middleton. :^)
>
>Next - you can add another server (plain Win2k) as a DC
to your SBS domain.
>This will authenticate users if your SBS is down.
However, once your SBS is
>down, you no longer have internet access or email (and
possibly user
>settings, fax functionality, file & printer shares).
Granted, you can have
>the additional DC act as your file / print server to help
distribute the
>load, but you've still got services out of commission
until your SBS comes
>back online. In addition, if you have all Win2k / XP
clients, they will use
>a cached login if no DC is available to authenticate
their request.
>Likewise, any PCs logged on when the server goes down
will still be able to
>access other network resources even without a DC (member
servers, etc.)
>
>But, as Javier has indicated - you can only have one SBS
on your network
>
>--
>Chad A Gross
>
>Lerman's Law of Technology: Any technical problem can be
overcome
>given enough time and money. Corollary: You are never
given enough
>time or money.
>
>
>
>Dan wrote:
>> Javier,
>>
>> How then do I get a backup incase the first server goes
>> down. Need another server to validate logins, correct?
I
>> was under the impression that this would be a member
>> controler and could be promoted to a domain controller
if
>> the other server goes down?
>>
>> dan
>>> -----Original Message-----
>>>> At any rate, I am tring to install another server in
the
>>>> domain to run as a backup.
>>>
>>> You cannot have 2 SBS servers in the same domain... so
you need to
>>> rethink your strategy.
>>>
>>> BTW, you should name your AD domain as mycompany.local
and don't use
>>> your FQDN.
>>>
>>> -Javier
>>>
>>>
>>> .
>
>
>.
>

Frank
Mon Jul 21 15:00:25 CDT 2003

Right on the money Susan.

Frank


"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
wrote in message news:3F1C3974.DC36C1E6@pacbell.net...
> IMHO... I get more bang for the buck if I ensure that the parts of the
> server are quality than if I buy 2 servers.....
>
> Let's say we "could" do a redundant SBS2k server setup.....
>
> We'll buy two servers, two OS', two sets of CALs, link the suckers
> together, replicate the databases...but in order to "pop" that second
> server "exactly" in the place of that first server you would need
> instead a Ghosting method to exactly capture the SID on the main server
> so that your workstatons wouldn't freak.
>
> Look around your office...there are SO many single points of failure
> that your server is only one.....
>
> One phone system
> One fax machine?
> One telephone company in your area servicing your phone
> One DSL line [what no backup on that?]
> One power company [PG&E says we're doing a brown out today... not much I
> can do as I don't have a generator]
>
> There are many people that post in very worried about the fact that
> their single point of failure is the SBS... but quite honestly.. it's
> just the most obvious. There are tons more.
>
> Get "good quality server equipment" [RAID 5 etc] and just keep an eye on
> the server.... if it's having problems... it will let you know.
>
> Dan wrote:
>
> > I currently have one server running Windows 2000 and
> > SBS2000. For the sake of this message I'll call the domain
> > mycompany.com. Someone else set up this server, who is
> > nolonger here, but said that because we already have a
> > website called mycompany.com we could not see
> > mycompany.com in our network so He said he tricked the ISA
> > software to use mc (short for my company) as the displayed
> > domain. The machine name is sbs2000.
> >
> > At any rate, I am tring to install another server in the
> > domain to run as a backup. Actually I am upgrading NT 4.0
> > & SBS 4.5 TO SBS 2000 onto a NEW server.
> >
> > The instuctions tell me to install W2k on the new server
> > but keep as a Workgroup. The machine name is sbs2000-2.
> > Did that.
> >
> > Now when I install SBS2K on the screen that asks for
> > the "Full DNS name for new domain" I put in mycompany.com
> > and the system says it has detected a duplicate DNS domain
> > name on the network.
> >
> > How do I name this to come up and be a member of my
> > current domain to run as a backup?
> >
> > Dan
> > .
>
> --
> "Don't lose sight of security. Security is a state of being,
> not a state of budget. He with the most firewalls still does
> not win. Put down that honeypot and keep up to date on your
> patches. Demand better security from vendors and hold them
> responsible. Use what you have, and make sure you know how
> to use it properly and effectively."
> ~Rain Forest Puppy
> http://www.wiretrip.net/rfp/txt/evolution.txt
>
>

Dirk-Thomas
Mon Jul 21 15:35:51 CDT 2003

Further... If you do decide to check the scenario out... Don't try
installing the plain Windows 2000 Server portion of SBS on the other server.
You need another copy of Windows 2000 Server

Dirk-Thomas

"Frank" <info@microsoft.com> wrote in message
news:e6$qUL8TDHA.2208@TK2MSFTNGP11.phx.gbl...
> Right on the money Susan.
>
> Frank
>
>
> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
> wrote in message news:3F1C3974.DC36C1E6@pacbell.net...
> > IMHO... I get more bang for the buck if I ensure that the parts of the
> > server are quality than if I buy 2 servers.....
> >
> > Let's say we "could" do a redundant SBS2k server setup.....
> >
> > We'll buy two servers, two OS', two sets of CALs, link the suckers
> > together, replicate the databases...but in order to "pop" that second
> > server "exactly" in the place of that first server you would need
> > instead a Ghosting method to exactly capture the SID on the main server
> > so that your workstatons wouldn't freak.
> >
> > Look around your office...there are SO many single points of failure
> > that your server is only one.....
> >
> > One phone system
> > One fax machine?
> > One telephone company in your area servicing your phone
> > One DSL line [what no backup on that?]
> > One power company [PG&E says we're doing a brown out today... not much I
> > can do as I don't have a generator]
> >
> > There are many people that post in very worried about the fact that
> > their single point of failure is the SBS... but quite honestly.. it's
> > just the most obvious. There are tons more.
> >
> > Get "good quality server equipment" [RAID 5 etc] and just keep an eye on
> > the server.... if it's having problems... it will let you know.
> >
> > Dan wrote:
> >
> > > I currently have one server running Windows 2000 and
> > > SBS2000. For the sake of this message I'll call the domain
> > > mycompany.com. Someone else set up this server, who is
> > > nolonger here, but said that because we already have a
> > > website called mycompany.com we could not see
> > > mycompany.com in our network so He said he tricked the ISA
> > > software to use mc (short for my company) as the displayed
> > > domain. The machine name is sbs2000.
> > >
> > > At any rate, I am tring to install another server in the
> > > domain to run as a backup. Actually I am upgrading NT 4.0
> > > & SBS 4.5 TO SBS 2000 onto a NEW server.
> > >
> > > The instuctions tell me to install W2k on the new server
> > > but keep as a Workgroup. The machine name is sbs2000-2.
> > > Did that.
> > >
> > > Now when I install SBS2K on the screen that asks for
> > > the "Full DNS name for new domain" I put in mycompany.com
> > > and the system says it has detected a duplicate DNS domain
> > > name on the network.
> > >
> > > How do I name this to come up and be a member of my
> > > current domain to run as a backup?
> > >
> > > Dan
> > > .
> >
> > --
> > "Don't lose sight of security. Security is a state of being,
> > not a state of budget. He with the most firewalls still does
> > not win. Put down that honeypot and keep up to date on your
> > patches. Demand better security from vendors and hold them
> > responsible. Use what you have, and make sure you know how
> > to use it properly and effectively."
> > ~Rain Forest Puppy
> > http://www.wiretrip.net/rfp/txt/evolution.txt
> >
> >
>
>