Hyper-V
Current domain environment: 1 - 2003 Domain Controller w/Exchange
Question is we are adding another server which is currently setup w/Hyper-V:
Parent is only running Hyper-V role (workgroup)
Guest OS's is Windows 2008 enterprise and Windows 7
Want to add the Windows 2008 VM as another DC, do we just go through the normal process of running adprep on the 2003 DC and then dcpromo the 2K8 VM?
What about networking and is there any gottcha's?
Thanks
Question is we are adding another server which is currently setup w/Hyper-V:
Parent is only running Hyper-V role (workgroup)
Guest OS's is Windows 2008 enterprise and Windows 7
Want to add the Windows 2008 VM as another DC, do we just go through the normal process of running adprep on the 2003 DC and then dcpromo the 2K8 VM?
What about networking and is there any gottcha's?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
HornAlum
hardware wise, I'd recommend a dedicated NIC for your VM's, one that will not share an IP with the parent O/S.
ASKER
Configured the VM for External network with it's own IP. You mean actually configure one of the other physical NIC's and actually plug a seperate cable into that NIC? If so, how do you configure that?
pretty simple. Go into Hyper-V, then Virtual Network Manager. Choose External, and hit "Add". Choose one of your spare NICs. uncheck the "allow management operating system to share this network adapter".Give it a particular network name that you can identify it as. Then you're good to go. after that, you just plug in the cable into that particular NIC port.
in the VM properties, assign the new Virtual Network Name to the NIC and you're done.
be careful, that with many multiple nic cards, you are choosing the corrent one. they'll be named the same but will have a # at the end. you'll have to identify which one is which. i usually do that by plugging a cable into each one, and seeing which one lights up in windows as connecting. I then tend to rename them so it's easier to identify.
in the VM properties, assign the new Virtual Network Name to the NIC and you're done.
be careful, that with many multiple nic cards, you are choosing the corrent one. they'll be named the same but will have a # at the end. you'll have to identify which one is which. i usually do that by plugging a cable into each one, and seeing which one lights up in windows as connecting. I then tend to rename them so it's easier to identify.
ASKER
No other problems I should watch out for, sounds very straight-forward? Will transfer FSMO roles and eventually will upgrade or replace the 2003 server. Want to get Exchange off a DC. Probably will setup another server w/Hyper-V and create 2 VM's one for a DC and the other just as a member server running Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Guys!!