After that you'll have to wait 90 days till you can move you licenses again. I'm not so sure if this is allowed be Microsoft, so perhaps a Licensing Specialist could confirm that. We are only just moving from Exchange , and the only reason we are looking at Software Assurance is due to the mobility rights not that we are thinking about updating, this will most probably be in place until Exchange goes out of support.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. I have been told by a reseller that i don't HAVE to but should. Thanks in Advance. Best Answer.
Simon Matthews This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. View this "Best Answer" in the replies below ».
Bottom line is that it is most likely cheaper to purchase and assign a Datacenter license to each host in the cluster. The Datacenter license grants you the right to run an unlimited number of Windows Server virtual images.
I suggest you talk with a trained Microsoft licensing specialist. Your lawyers would appreciate it, and your company will appreciate it if you are audited. Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft.
Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Usually, you want virtual machines on that failed host to be powered back on to other functioning hosts within the same cluster. Sometimes a host can become isolated from others in the cluster. When this happens, VMware calls this a host isolation event.
If a host becomes isolated, it could be a simple issue with the management network. We must decide if we want virtual machines to be gracefully powered off and back onto other hosts in the cluster or forcefully powered off and back on again. The main difference here is the graceful power off of the virtual machines. If they hang while powering off, then they might not be brought back online on other hosts. However, forcefully shutting down a virtual machine could corrupt its data.
Instead of defining an action, you can keep the default option to do nothing when a host isolation event occurs. In that case, you can manually reboot virtual machines should this become an issue in your environment. In the context of datastores, this means that the host can no longer communicate with the datastore and considers it unrecoverable. A PDL state occurs after multiple datastore connection attempts fail. When an APD event occurs, every path to a given datastore is offline.
While paths could come back online, vSphere HA lets us set what to do under this condition. You can do nothing which would result in your virtual machines remaining in a failed state. You can also choose to power off and restart affected virtual machines on other hosts, providing those other hosts still have access to the datastore. Aside from hosts and datastore failure responses, vSphere HA also has an interesting way to monitor and respond to virtual machine failure.
If vSphere does not receive a heartbeat during the configured time, it determines that the virtual machine has failed and reboots it. As always, determine the risk-reward and configure appropriately for the virtual machines in the cluster.
To help prevent false positives, you can use the sensitivity options and the maximum number of resets within a time window option. All hosts in an HA-enabled cluster report their status to each other during an election process.
This process occurs during initial HA configuration or when the last elected primary host fails. The primary host is responsible for updating your vCenter server with its status and the status of other hosts within the cluster.
Should one of the non-primary hosts fail, the cluster can react and reboot VMs on other hosts. If the primary host fails, the cluster elects a new one, and the failover process commences. The most common misunderstanding about vSphere HA is that it uses vMotion to move virtual machines from one host to another.
0コメント