Since you're running Windows Server, you should double-check to ensure that you've activated your copy of Windows. If you haven't activated it yet, I think you will get some trial period and then it will start regularly shutting itself down.
Power on the VM and check its Windows Event Log (eventvwr.exe) to see if there's a reason given for the OS shutdown. The log you posted shows that the VM is powering off because Windows asked the system to power off, not because of anything that vSphere in particular is doing. For a guest-OS-initiated shutdown, usually the guest OS's event log will explain why.
Cheers,
--
Darius
If the guest OS is Windows check the power options.
Since you're running Windows Server, you should double-check to ensure that you've activated your copy of Windows. If you haven't activated it yet, I think you will get some trial period and then it will start regularly shutting itself down.
Power on the VM and check its Windows Event Log (eventvwr.exe) to see if there's a reason given for the OS shutdown. The log you posted shows that the VM is powering off because Windows asked the system to power off, not because of anything that vSphere in particular is doing. For a guest-OS-initiated shutdown, usually the guest OS's event log will explain why.
Cheers,
--
Darius
A Guest OS initiated halt generates below event within the virtual machine logs
2017-03-21T17:02:40.242Z| vcpu-0| I120: PIIX4: PM Soft Off. Good-bye.
2017-03-21T17:02:40.242Z| vcpu-0| I120: Chipset: Issuing power-off request...
2017-03-21T17:02:40.261Z| vmx| I120: Stopping VCPU threads...
Check the OS logs for details.
Thanks Darius for the insights. Will definitely look into this.
Checking as well the issue on the Window Server event viewer and see if there's anything which can an idea of what's going on.
MDOnsakia are you have any anti virus installed in this VM ?
The server has Kaspersky Anti-virus installed.
However, I don't expect this to be the cause.
As an update, I did activate the Windows and today the server has not restarted. Will keep monitoring to see if this was the root cause.
Thanks guys. I appreciate.
Activating Windows seems to have resolved my issue.
I wish Microsoft can make this more explicitly in their Windows that you need activation otherwise they will keep you stressed by powering in off till manually powered on.