best way to setup a server 2008 domain
Server is running windows server 2008 Ent w/ 8gb of ram
here is the roles I need to deal with, obviously some of them are going to be virtual machines. I am simply looking for a logical topology on how to configure the servers.
Hyper-v obviously runs on the host os
Domain Controller
Virtual Machine Control Center
SQL Server 2008
IIS
DNS
Routing and remote access.
I am looking for a brief explanation on how you would recommend setting up this configuration, considering that I have other computer running on teh same network that are most likely going to be on a workgroup, although I would not be opposed to joining the domain.
How many vm's do I need, who is going to do what?
here is the roles I need to deal with, obviously some of them are going to be virtual machines. I am simply looking for a logical topology on how to configure the servers.
Hyper-v obviously runs on the host os
Domain Controller
Virtual Machine Control Center
SQL Server 2008
IIS
DNS
Routing and remote access.
I am looking for a brief explanation on how you would recommend setting up this configuration, considering that I have other computer running on teh same network that are most likely going to be on a workgroup, although I would not be opposed to joining the domain.
How many vm's do I need, who is going to do what?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Darius Ghassem
To add all of the VMs should be part of the domain.
ASKER
Yes, I do have the latest dns server of my isp, I actually have business grade fios with a static ip address.
ok, here is my only other question.
It it required for the workgroup computers (including my hyper-v server 2008 host os) to use the dns servers of the domain controller in order for proper communications between the workgroup and the domain?
ok, here is my only other question.
It it required for the workgroup computers (including my hyper-v server 2008 host os) to use the dns servers of the domain controller in order for proper communications between the workgroup and the domain?
ASKER
I would prefer to stick with the dns server of my isp to resolve my internet queries for the workgroup computers, but I still may need to connect the the sql server vm on the domain system.
No, your Hyper-v Host 2008 server doesn't have to point to the internal DNS servers but if you want to remote manage and other services then yes you would need to use the internal DNS server. If it is in your local network then you want it to point to your internal DNS server.
You have to think of Hyper-V like this. The host is seperate to any of the VMs just like the VMs are seperate to any of the other VMs.
You have to think of Hyper-V like this. The host is seperate to any of the VMs just like the VMs are seperate to any of the other VMs.
ASKER
Q: So if i wanted to join the domain or use native mmc services i would have to route the dns through the dc?
Q: But from a workgroup pc I would still be able to connect to ip based services like sql server?
Anyway, Believe it or not I have lots of experience with virtualization for years I been working with vmware, vpc, vs2005, and hyper-v. I am an early adopter too.
I am simply trying to get a better insight into running a domain system other than my local workgroup with little hassle or dns dependency of my physical workstations.
I am getting the idea here though that it may be my best bet to leave my workgroup intact and completely virtuilize my domain.
When i have tested this before I had issue resolving the domain from my workgroup. It is possible I may have slipped and not used the domain account or tried the ip address of the domain controller.
I may run this restore on my server, go back and see what happens from there.
Q: But from a workgroup pc I would still be able to connect to ip based services like sql server?
Anyway, Believe it or not I have lots of experience with virtualization for years I been working with vmware, vpc, vs2005, and hyper-v. I am an early adopter too.
I am simply trying to get a better insight into running a domain system other than my local workgroup with little hassle or dns dependency of my physical workstations.
I am getting the idea here though that it may be my best bet to leave my workgroup intact and completely virtuilize my domain.
When i have tested this before I had issue resolving the domain from my workgroup. It is possible I may have slipped and not used the domain account or tried the ip address of the domain controller.
I may run this restore on my server, go back and see what happens from there.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
How is everything going?