Installing Hyper V server around existing SBS2008 DC
Hi, I have started a project to convert our existing setup as follows:
SBS2008: Acting as a DC and Exchange 2007 server.
I have a new server (physically the same as the existing server) that I want to install Server 2008 Enterprise R2 and instlal Hyper V on.
Now this server will ultimately replace the SBS2008 server and will have Virtual machines acting as a DC and an Exchange 2007 server.
BUT, my question is, will the Hyper V Server need to join the existing Domain so I can connect to it vvia Remote desktop and Hyper V manager?
The Hyper V server will use the full version of Server 2008 R2m not core.
The main thing is I need to remotely connect to it. I'm loathe to do a DC promo on this new server (To allow remote access etc), as I want to be able to see it from my PC which is connected to the Domain controlled by the SBS2008 server.
Having another DC that is seen by the SBS2008 server will probably cause problems.
If I install Server 2008 R2 on the new server and have it join the existing domain (DC is SBS2008), will that cuase problems?
SBS2008: Acting as a DC and Exchange 2007 server.
I have a new server (physically the same as the existing server) that I want to install Server 2008 Enterprise R2 and instlal Hyper V on.
Now this server will ultimately replace the SBS2008 server and will have Virtual machines acting as a DC and an Exchange 2007 server.
BUT, my question is, will the Hyper V Server need to join the existing Domain so I can connect to it vvia Remote desktop and Hyper V manager?
The Hyper V server will use the full version of Server 2008 R2m not core.
The main thing is I need to remotely connect to it. I'm loathe to do a DC promo on this new server (To allow remote access etc), as I want to be able to see it from my PC which is connected to the Domain controlled by the SBS2008 server.
Having another DC that is seen by the SBS2008 server will probably cause problems.
If I install Server 2008 R2 on the new server and have it join the existing domain (DC is SBS2008), will that cuase problems?
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, after following up with some more research about permissions etc, it worked perfectly.
The Hyper-V Server only needs to be a member of a domain if you go for the domain option.
If you use the option 2 (i.e. no domain) then you dont even need a domain but you will need to setup some more things; follow the link;
http://technet.microsoft.com/en-us/library/cc794756(WS.10).aspx
Scroll down to the section headed; Configuring the management tools
In this section is discribed the mehord to setup Remote Admin tools without being part of a domain.
"The following procedures describe how to configure the server running Hyper-V. When domain-level trust is not established, perform all the steps. "
If you use the option 2 (i.e. no domain) then you dont even need a domain but you will need to setup some more things; follow the link;
http://technet.microsoft.com/en-us/library/cc794756(WS.10).aspx
Scroll down to the section headed; Configuring the management tools
In this section is discribed the mehord to setup Remote Admin tools without being part of a domain.
"The following procedures describe how to configure the server running Hyper-V. When domain-level trust is not established, perform all the steps. "
ASKER
Yes thanks. After I read over your answer a couple of times I worked it out.. :)
Thanks for the clarification though. :)
Thanks for the clarification though. :)
ASKER
I'd prefer it not to be a DC if I can get away with it. AS I want ultimately a virtual machine to replace the old SBS2008 DC.