2012/2003 quick questions

Just about to deploy a 2012 server to run alongside an existing 2003 with Exchange  (about 10 users), please correct me if any of these steps shouldn't be there :

Raise forest/domain level to 2003 (IP 192.168.0.100  / SERVER )
Install new 2012 server (IP 192.168.0.101  / SERVER2 )
SERVER2 joining SERVER
Add role (Active Directory Domain Service)
Add domain controller to existing domains
Add DNS
Add GC

The new server seem to have a full set of AD and DNS, so am I ready to go with this 2012 ?
The whole poing of this exercise is to create a second server to offload the workload from the 2003.
There will be a heavy database running on the 2012 (8 cores + 16GB + RAID10 )

What I were looking for is for the 2012 to hold all database stuffs, so users will carry on using the 2003 to logon and access Exchange, but then the database clients will be point to the 2012 to take the strain away from the 2003.

Am I heading the right direction ?
CombemartinAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Lee W, MVPTechnology and Business Process AdvisorCommented:
You don't need to Add DNS - the process of adding the Domain Controller services will do that for you.

BUT, WHY are you making the second server a DC?  Yes, some people here will tell you you must have TWO DCs - I used to be one of them.  But in recent years I heard a very good argument that said if you're NOT an AD expect, multiple DCs can just complicate things for you in the event of a recovery and if you try to recover improperly, you can destroy your whole network... so... UNLESS you understand AD and the process of restoring a domain controller, I would say, DO NOT make it a domain controller.  Put your database on it.

(BTW, You ARE making the server a Hyper-V host and running a VM with the Database on it, right?  2012 gives you TWO installation licenses aside from a hyper-v license - you'll be wasting one that you could use now or later if you don't virtualize, not to mention shooting yourself in the foot with flexibility and recovery options.

And keep in mind 2003 DIES in 4 months... when are you leaving that?  You could migrate completely off the existing server onto 2 VMs on a new server with a single new license.
0

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
CombemartinAuthor Commented:
Hi Lee, thanks for the reply.
I plan to up the 2003 later this year, may be around August Bank holiday when theres enough time.
For now, if I just deploy a 2012 server for the database, I just simply join that to the domain for the software and allow users to access it, do I need any additional CALs for this as its just a 'user' station ?
0
CombemartinAuthor Commented:
Thanks Lee.
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Lost track of the question - yes, you need CALs for every user who is going to access ANY resource on the server.
0
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
Windows Server 2012

From novice to tech pro — start learning today.