New Server & Old Server

I have a new server (SERVER10; running Windows 2008SBS) which i am making the new domain controller on my network and will map all my PC's to.

The old server (SERVER02, running Windows 2000 server) is to be kept to keep some files (mainly SQL database stuff).

I want the old server (SERVER02) to continue to be part of my network, however it will obviously no longer be the domain controller, that job will go the new server (SERVER10).

Couple of questions:

1. how do i stop SERVER02 being the domain controller? Is it just case of pressing a button?
2. do i need to do anything on SERVER02 to allow it continue to be part of our network?
3. is there anything else i might need to consider in all this?
The domain name will remain unchanged when we move from one server to another.
VSFLYERAsked:
Who is Participating?
 
Paul JacksonConnect With a Mentor Software EngineerCommented:
Yes running dcpromo on server02 will turn it into a member server of the domain.
0
 
danny1875Commented:
Is the Windows 2000 server the SBS version? What your looking at doing here is a migration. You won't be able to have two SBS servers sitting on the same domain it will cause you ENDLESS problems!!
0
 
Paul JacksonSoftware EngineerCommented:
run dcpromo on server02 that will turn into a member server on the domain
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Paul JacksonSoftware EngineerCommented:
Only other you might need to consider is if the server02 owns any fsmo roles these will need to be transferred to the new dc before running dcpromo
0
 
VSFLYERAuthor Commented:
no, SERVER02 is not SBS. Will only have one SBS server (2008).
0
 
VSFLYERAuthor Commented:
server02 has no FSMO roles as far as i am aware.

so just to confirm - all i need to do is run dcpromo on SERVER02?
0
 
danny1875Commented:
If im honest, it may be easier for you to create a new domain on the SBS2008 server and migrate your data across. You'll need to re-join your clients to the new domain but it saves the hassle of migrating and replicating exchange and active directory. you can then dcpromo your existing server (demote as a DC) and join it to your new domain as a member server.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
The first DC in every domain always has the FSMO roles unless someone moves them off.  If you only have ONE DC (the 2000 server) then it DOES have ALL the FSMO roles or you have series problems with AD.

Before you do ANYTHING, MAKE A FULL BACKUP of the 2000 server.  Depending on how SQL is configured, you could have serious problems with it if you demote the server and effectively get rid of the old domain.

Sorry, I don't have any instructions (never done it) to migrate an existing non-SBS domain into an SBS domain.  HOWEVER, SBS MVP Jeff Middleton DOES offer tools to do this at a very low price and many people recommend using his kit - www.sbsmigration.com
0
 
Paul JacksonSoftware EngineerCommented:
I take it server02 does not have exchange on ?
0
 
danny1875Commented:
what jacko is saying is correct, but if you dont replicate active directory you will loose your computer and user accounts and ultimately any ties into exchange. Personally i'd set up a new domain, migrate your data, exmerge your exchange mailboxes to .pst's (if you have any) and demote your existing server to be added as a member. Its just a clean and pretty easy way of doing it. if you dcpromo your server before you setup your sbs box you'll be re-creating accounts anyway
0
 
danny1875Commented:
and to replicate AD you will need to do the swing migration as leew points out. Its not easy if your doing it for the first time though. Save yourself the time and setup your domain from scratch.
0
 
VSFLYERAuthor Commented:
need to clarify a few points:

- first of all the old server (SERVER02) does not have exchange on it
- secondly, i am setting up all users, groups, permissions etc from scratch on the new server (SERVER10), so in effect starting again
- thirdly, any data i am transferring will be manually be copied from one server to the other.

i think the main concern i have is that on the old server (SERVER02) i am keeping a few programs that run on SQL databases, so users have to be able to access them.  I dont want to do anything to SERVER02 that might affect my SQL databases.

I just want SERVER02 to be another PC on the domain and allow people to continue to access the SQL programs until a time i migrate them accross to the new server.


0
 
Paul JacksonSoftware EngineerCommented:
Yeah there you go, just dcpromo it then.
0
 
VSFLYERAuthor Commented:

can you just clarify what the 'dcpromo' actually is and actually does?
0
 
Paul JacksonSoftware EngineerCommented:
It either installs or removes active directory ds

see here : http://technet.microsoft.com/en-us/library/cc732887(WS.10).aspx
0
 
Paul JacksonSoftware EngineerCommented:
If you just run it from start -> run it will take you through the process.
0
 
danny1875Commented:
In that case a simple dcpromo would be the the right way to go. Then once your sbs box is setup join it to the domain as a member server (the same way you would a client) You'll need to re-join your clients to your new domain whether you keep the same domain name or not so in effect your starting from scratch anyway.

hope it goes well for you
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
> Yeah there you go, just dcpromo it then.
and if SQL uses integrated authentication or the machine has any services running under a domain admin account, you'll break them...
0
 
VSFLYERAuthor Commented:

regarding the SQL what should i be checking here before i proceed with dcpromo
0
 
Paul JacksonSoftware EngineerCommented:
Are you using a domain account for the sql server service or is it using a local account.
What are your databases used for?
What applications use them ?
Do these applications use integrated authentication to access the databases?

Which ever way you do this because you are in effect starting again you will break the access to the database because you are setting up all accounts and groups from scratch. The only way this will not happen is if you are using sql authentication only.

Have a look at the security for the databases see what accounts have permissions for them, see if they are domain accounts or sql accounts only.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.