• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:

Domain Setup with 2 servers - 2003 Std & 2008 Std plus SQL2008

I have 2 servers that need to go on the same network with some software that requires a domain setup.  I have a Windows 2003 Std just setup as a file server in workgroup mode.  I have a new Windows 2008 Std server that needs to run SQL 2008.  I heard you shouldn't make the SQL server a DC?  So, what's the procedure to convert the 2003 server to the DC and then make the 2008 server part of the domain?  I have XP Pro workstations that need to authenticate to both servers.  I originally posted this but just found out that SQL shouldn't be on the DC.  Looking for the easiest procedure to setup as we don't need anything complicated.  Thanks!
1 Solution
Lee W, MVPTechnology and Business Process AdvisorCommented:
If you have NO custom set file permissions in the existing 2003 server, then this should be relatively painless.  Follow the directions here:

Then you join the 2008 and XP systems to the domain - see:
(Don't have a link for joining 2008, but I believe it's still under the System control panel and the procedure is very similar to XP.

BEFORE DOING THIS - do a system state backup on the XP and 2003 servers - see http://www.lwcomputing.com/tips/static/sysstate.asp - on the 2008 server, you'll need to do a complete backup of the C: drive.

I almost always recommend STARTING with a domain and never using a workgroup because, among other thing, migrating to a domain from a workgroup can be problematic if you've customized anything at all in the workgroup.

As for using Active Directory Authentication with SQL, can't help you on that.
randyphillipsAuthor Commented:
Makes perfect sense.  I will consider the "starting with a domain" in the future.  We just thought keeping things simple was best.  Have never had a problem or rarely a need to have a DC other than SBS forcing that.

When doing the DC install on the 2003 server do we have to enable DNS?  No reason to do that as the router does that for us - correct?  Or, should we just let it do DNS?  Confused.
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.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now