Windows Server 2008 Domain Role Assignments with DC in HyperV VM

Our current environment is this:

1. Single domain with three (3) DCs, all GC servers.

2. First DC is running Windows Server 2008 Standard SP2 32-bit. Machine is generic black box with P4 and 4GB of RAM.
3. Second DC is running Windows Server 2008 Standard SP2 32-bit. Machine is IBM System x3250 with dual core Xeon and mirrored 73GB drives.
4. Third DC is running Windows Server 2008 R2 Standard SP1 64-bit as a VM inside HyperV. 4GB allocated to it.

5. First DC is DNS and Print Server. (with GC)
6. Second DC is DNS and DHCP Server. (with GC)
7. Third DC is just DC (with GC) so far.

I have a separate VM that will be the new print server, so I intend to remove that first from the First DC.

Here are the current roles:
First DC - Schema Master, Domain Naming Master, Infrastructure Master
Second DC - PDC, RID Pool Manager

We have just these DCs. All servers in the organization are Windows Server 2008 or 2008 R2. All clients are Windows 7.  We have about 80 users - not a very big environment.

Questions:
1. I intend to retire the First DC.  How should I split roles between Second DC and Third DC (VM) ?
2. I intend to install DNS on Third DC (VM).  Is 4GB and two virtual processors allocated to it sufficient to support DNS with additional roles suggested above ?

Thanks much.
-Stephen
lapavoniAsked:
Who is Participating?
 
NetfloCommented:
Hi Stephen,

In reply to your questions:

1. Just move the roles down, so 2nd DC takes over 1st DC roles. 3rd DC takes over 2nd DC roles.
2. Typically DC comes with DNS, especially on Server 2008. In reply to your question, yes 4GB RAM and 2 virtual processors will be sufficient.

Points to note:

1. Assuming you update your DHCP server to publish the primary DNS as your second DC and secondary DNS as your third DC. Your second DC will take the brunt of all requests. So you will not see much load applied to your VM.

2. You DC VM will have static RAM assigned not dynamic, the NIC card on the VM is synthetic for performance reasons too.

Hope that helps.
0
 
Exchange_GeekCommented:
First DC - Schema Master, Domain Naming Master, Infrastructure Master
Second DC - PDC, RID Pool Manager

Move roles from First DC to second.

Second, convert both DCs (second and third to be GC)

Thirdly, convert DNS to be AD Integrated, introduce the third server as DNS and once the environment looks good, remove the first.

If you have DHCP setup, remove first server as primary DNS Server, promote the second server as primary DNS and third as secondary DNS Server.

Ensure, that you are not in a hurry to demote a DC, there are various issues where if you do not provide adequate time - causes a menace in the environment.

You're RAM is good enough.

Regards,
Exchange_Geek
0
 
kevinhsiehCommented:
I say that 1 GB of RAM and 1 vCPU is sufficient. You can go a little higher on the RAM if you want, but the second vCPU is not needed and will probably have a slightly negative impact on performance. I run DCs under Hyper-V with 1 vCPU for my 600 user environment.
0
 
lapavoniAuthor Commented:
Great suggestions. Exchange_Geek, it sounded like your suggestion is to move all roles to the second DC and leave them there. I'm thinking Netflo's might be better to split roles.
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.