Hyper-V server sometimes down
hi,
i installed a windows server 2012 R2.
configured AD on the server.
installed Server Essentials for easy administering.
installed hyper-v server
instaled on hyper-v again a second windows 2012 R2
added this server to the AD domain.
installed on the virtual server exchange 2016
rolled out 8 client computers, connected to the AD and configured a mailbox for each client.
everything seems to work but several times a day the client disconnects from the exchange. then outlook says. "disconnected"
any idea's? i installed the server with 1 NIC. i use this nic for the general server and for the hyper-v server.
i installed a windows server 2012 R2.
configured AD on the server.
installed Server Essentials for easy administering.
installed hyper-v server
instaled on hyper-v again a second windows 2012 R2
added this server to the AD domain.
installed on the virtual server exchange 2016
rolled out 8 client computers, connected to the AD and configured a mailbox for each client.
everything seems to work but several times a day the client disconnects from the exchange. then outlook says. "disconnected"
any idea's? i installed the server with 1 NIC. i use this nic for the general server and for the hyper-v server.
Philip Elder
Is this one physical box with several VMs?
ASKER
1 box running the AD
1 vm running exchange
1 vm running sql
1 vm running exchange
1 vm running sql
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Indeed. Hyper-V makes all sorts of changes in the network stack.
Install another VM and DCPromo it in. FSMO transfer to the VM DC. Then do a DCPromo on the host to remove ADDS and its services.
With the way the reboots work on the host the host/guest communication may not function thus not allowing the host to properly remove itself as a DC.
You can forcefully remove the remnants from AD and DNS. Then, make sure the ADDS Roles are completely removed from the host. I suggest disabling auto-startup on the guests during this process to allow for the possible multiple reboots.
Install another VM and DCPromo it in. FSMO transfer to the VM DC. Then do a DCPromo on the host to remove ADDS and its services.
With the way the reboots work on the host the host/guest communication may not function thus not allowing the host to properly remove itself as a DC.
You can forcefully remove the remnants from AD and DNS. Then, make sure the ADDS Roles are completely removed from the host. I suggest disabling auto-startup on the guests during this process to allow for the possible multiple reboots.
ASKER
i understand, but i have no problem with AD. the problem is on the exchange server. how can moving the AD solve this problem?
AD and Exchange are HEAVILY INTEGRATED. And since no professional would recommend this kind of setup, we cannot rule out a problem because of it. You need to set this up PROPERLY before you can start troubleshooting - if it's setup properly to begin with you may not experience these issues!
It's really very important to get PROFESSIONAL assistance when setting up a network if you have little to no experience with the products in question. It's just as important knowing what NOT to do as it is knowing what you SHOULD do. It's already very clear that you've done things that are not recommended or in some cases even supported - which can result in problems - possibly the one your currently experiencing!
It's really very important to get PROFESSIONAL assistance when setting up a network if you have little to no experience with the products in question. It's just as important knowing what NOT to do as it is knowing what you SHOULD do. It's already very clear that you've done things that are not recommended or in some cases even supported - which can result in problems - possibly the one your currently experiencing!