Two Domains...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello!

Thank you in advanced for reading this and take your time to give advice!

We have 2 SBS servers (2000) each one with it's own domain. I have been here
for 3 months now. I believe it will simplify things a lot if we have one
"Master" and just child domains. However, management is concerned and they
want to keep things "separate" because it's actually two companies (Sister
Companies, so to speak)

There are users on both sides that need access to resources on the other
side. Also, it is know now that the 2000 version will not be supported any
longer in the near future and we will have to upgrade. So far we have been
getting away with all of this by adding users to both sides (Domain1 and
Domain2) with the same credentials. But I believe this is not safe and could
cause more problems than it actually is solving.

We do not have anything fancy really. ERP system (on both sides).
Operational Exchange (on both sides). Folders, etc, etc.

The networks are separated by a router, so each one has it's own IP schema.

My goal, personally is to centralize security and management, without
affecting Exchange, the separation of the ERP system and the overall
performance.

Any ideas? Suggestions?

I am kind of "too" technical and the pitch to management is kind of tricky.
So I need to be very sure and convinced of the aproach.

I believe that using the 2003 upgrade or New install as a Parent domain and
place the other 2 as childs should be the solution. But if something goes
south?

Again, thanks for looking!

Best Regards!
 
I'm not entirely sure that SBS will support this kind of configuration. I'd
suggest consulting with the folks in the SBS forums to be sure.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
Probably not. But, would you consider going W2003 Enterprise and setup this
way?

Can you see the perks vs. the hassle? I mean, perks being more.

Thanks! Have a good one!

Richard G. Harper said:
I'm not entirely sure that SBS will support this kind of configuration. I'd
suggest consulting with the folks in the SBS forums to be sure.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


Mario Manzano said:
Hello!

Thank you in advanced for reading this and take your time to give advice!

We have 2 SBS servers (2000) each one with it's own domain. I have been
here
for 3 months now. I believe it will simplify things a lot if we have one
"Master" and just child domains. However, management is concerned and they
want to keep things "separate" because it's actually two companies (Sister
Companies, so to speak)

There are users on both sides that need access to resources on the other
side. Also, it is know now that the 2000 version will not be supported any
longer in the near future and we will have to upgrade. So far we have been
getting away with all of this by adding users to both sides (Domain1 and
Domain2) with the same credentials. But I believe this is not safe and
could
cause more problems than it actually is solving.

We do not have anything fancy really. ERP system (on both sides).
Operational Exchange (on both sides). Folders, etc, etc.

The networks are separated by a router, so each one has it's own IP
schema.

My goal, personally is to centralize security and management, without
affecting Exchange, the separation of the ERP system and the overall
performance.

Any ideas? Suggestions?

I am kind of "too" technical and the pitch to management is kind of
tricky.
So I need to be very sure and convinced of the aproach.

I believe that using the 2003 upgrade or New install as a Parent domain
and
place the other 2 as childs should be the solution. But if something goes
south?

Again, thanks for looking!

Best Regards!
Click to expand...
Click to expand...
 
I would certainly consider using either Server 2000 or Server 2003 (not SBS,
the straight server package) in this kind of configuration. A master forest
domain over two trees within the forest is definitely a good way for one
admin to administer two domains that must remain separate from each other.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


Mario Manzano said:
Probably not. But, would you consider going W2003 Enterprise and setup
this
way?

Can you see the perks vs. the hassle? I mean, perks being more.

Thanks! Have a good one!

Richard G. Harper said:
I'm not entirely sure that SBS will support this kind of configuration.
I'd
suggest consulting with the folks in the SBS forums to be sure.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


Mario Manzano said:
Hello!

Thank you in advanced for reading this and take your time to give
advice!

We have 2 SBS servers (2000) each one with it's own domain. I have been
here
for 3 months now. I believe it will simplify things a lot if we have
one
"Master" and just child domains. However, management is concerned and
they
want to keep things "separate" because it's actually two companies
(Sister
Companies, so to speak)

There are users on both sides that need access to resources on the
other
side. Also, it is know now that the 2000 version will not be supported
any
longer in the near future and we will have to upgrade. So far we have
been
getting away with all of this by adding users to both sides (Domain1
and
Domain2) with the same credentials. But I believe this is not safe and
could
cause more problems than it actually is solving.

We do not have anything fancy really. ERP system (on both sides).
Operational Exchange (on both sides). Folders, etc, etc.

The networks are separated by a router, so each one has it's own IP
schema.

My goal, personally is to centralize security and management, without
affecting Exchange, the separation of the ERP system and the overall
performance.

Any ideas? Suggestions?

I am kind of "too" technical and the pitch to management is kind of
tricky.
So I need to be very sure and convinced of the aproach.

I believe that using the 2003 upgrade or New install as a Parent domain
and
place the other 2 as childs should be the solution. But if something
goes
south?

Again, thanks for looking!

Best Regards!
Click to expand...
Click to expand...
Click to expand...
 
Back
Top