?
Solved

any problems running 2000sbs with 2003server, where 2003 is master AD and exchange 2007 server

Posted on 2007-03-27
9
Medium Priority
?
217 Views
Last Modified: 2010-03-17
I have a 2000sbs server, i'm going to add a 2003 server with exchange 2007.
I've been given info on moving the AD and exchange from one to the other.
But my problem is the SBS server has lots of other software on it and i want to keep it running a bit longer, along side the 2003 server.
I've heard that 2000sbs doesn't like other AD servers on the network ?

Can i have the 2000SBS server along side the 2003 server, where the 2003 is the master AD ?
what problems will i get if i choose to do it. with servers and workstations ?
thanks for you advice
0
Comment
Question by:total123
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18806696

> Can i have the 2000SBS server along side the 2003 server, where the 2003 is the master AD ?

Basically, no.

SBS must be the master, it is a requirement of SBS. You would either need to build a new domain and manually move everyone over to it, or purchase the migration / transition pack to upgrade your SBS licenses and remove it's built in restrictions.

However, you can have another DC in an SBS network, it's just SBS must be the boss.

Chris
0
 

Author Comment

by:total123
ID: 18807241
hi chris.
so if i change it to some thing like this, will it work ?

2000sbs as master DC which controls AD
2003server with exchange 07 - make it a DC with AD on it and transfer the exchange info from sbs to 07.
keep the 2000sbs running until its not required any more ?

cheers
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18807646

It should do yes. But remember that you must keep the SBS server running for the lifetime of the domain unless you either make a new domain or upgrade it.

It may be worth considering either upgrading the version of SBS or upgrading to a full-blown domain.

Chris
0
Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

 

Author Comment

by:total123
ID: 18807875
so there's no way we can take out the sbs and upgrade one of our 2003 servers to become the master DC ?
with out keeping the domain intact
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18807920

No... it's a built in restriction I'm afraid (it just breaks if you try it). Just one of those things, they like you to spend money with them.

Chris
0
 

Author Comment

by:total123
ID: 18808167
what about upgrading the sbs2000 to sbs2003, then taking the sbs out of the system ?
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 18808421

Nope. Bear in mind that this is a deliberate restriction of SBS in general, it isn't something that's limited to SBS 2000.

Chris
0
 

Author Comment

by:total123
ID: 18814948
Hi Chris

I do appreciate your help, just one last question for future ref.
all that seems clear, what happens if and when the sbs dies. I assume the 2003 DC will take over, and i also assume i wont be able to add users, etc.
And i'd have to rebuild the domain from scratch ?
or could i stick a replacement sbs in to copy the AD from the 2003 DC ?
thanks again
0
 
LVL 71

Accepted Solution

by:
Chris Dent earned 375 total points
ID: 18814964

You must basically ensure you have a full backup (especially of the System State). MS have produced fairly extensive articles on doing all of this:

2000:
http://www.microsoft.com/technet/prodtechnol/sbs/2000/maintain/bkuprcvr.mspx

2003:
http://download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d62bcc9/BKU_bkuprstr.doc

In the event of failure an additional DC would mean people can still logon (as long as you duplicate the DNS service and make it a Global Catalog).

Chris
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question