Will SBS 2003 shutdown when there is a different domains in the network

Hi all,

I have a server 2003 small business server with a domain abc.local. I am setting up another domain def.local  with Windows Server 2012 in the same subnet.

This is a temporary setup for maybe a few months to half a year.

Will this actually affect anything on the SBS2003 (abc.local) and server 2012 (def.local), like auto shutdown?

They will not be any trusted relationship between the 2 domains

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:

This will not affect anything as long as you don't set up trust between the domain.

Larry Struckmeyer MVPCommented:
Two comments:  

What will be effected is the DHCP server on the SBS.  When there is a second DHCP server in the LAN, the DHCP server on the SBS will stop.

Second, you cannot establish trusts with SBS.  Not allowed, but more, the functionality has been removed.

So as long as you are OK with having only one DHCP server you should be good to go.
I just started the same journey few weeks ago.

I will agree with  "giveandtake638" nothing major to start with and will have to disagree with fl_flyfishing.

First, SBS will install everything you need to make your network work, 2012 Standard will go out as a file server and you will choose what other roles will it perform or will be installed.

Now, you can have more than one DHCP, DNS and DC on the same domain you just have to make sure their scope and/or functionality doesn't affect the other one.

Just be extra cautious when moving your FSMO roles; if your exchange is 2003 and/or is attached to your 2003 SBS you better transition to exchange 2007 or 2010 before you go ahead.  Ah... keep your old DC in place for a few days after all roles have been transferred and replicated elsewhere in case there is a forgotten machine somewhere in the company that is not been used for a long time as it won't get the changes... GPO, DNS, DHCP etc.

Good Luck

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Larry Struckmeyer MVPCommented:
Not sure what the accepted answer has to do with the question as migration and new Exchange and moving FSMO roles and so on were not mentioned in the question.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.