VMware Horizon Community
tdubb123
Expert
Expert

alway on: vm does not stay powered on

When I shutdown my vm, it shuts down but according to the admin guide. its supposed to stay on or reboot even when shutdown.

any idea?

0 Kudos
6 Replies
Linjo
Leadership
Leadership

What is the OS?

Is there any powersaving setting set on the VM itself?

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
0 Kudos
tdubb123
Expert
Expert

no power saving setting. its set to always on. this is windows xp. this works fro everyone?

0 Kudos
tdubb123
Expert
Expert

this is strange. It seems to be happening to only 1 vm in the pool.

0 Kudos
scottziehr
Enthusiast
Enthusiast

is it an automated pool? can you just remove it and let it get recreated?

0 Kudos
gregb99
Contributor
Contributor

Same problem here. Using View 4.0.1 and Windows XP in the VMs. We have Linked Clone pools with the Always On setting selected. I have found that on the machines that have not been assigned a user yet, the function works. If you shut it down it powers back on. On any machine that is assigned a user the vm will stay powered off. Of course the assigned VMs are the ones we actually care about staying on. With PCoIP users are now able to shutdown the VMs and will experience a delay trying to connect in the morning. Looking into sending Wake on LAN packets at regular intervals as a possible workaround but haven't gotten it to work yet.

0 Kudos
mitrevski
Contributor
Contributor

I hate to resurrect a few months old thread, but we're experiencing the same issue:

VMware View with PCoIP

Manual Persistent Desktop Pool

Set to Always On

OS: Windows XP SP3

If the user initiates a shutdown from Windows, the virtual machine does not get power-on automatically, despite the pool being configured for "Always On".

There are no events in the Vmware View Server log, nor in the Vmware vSphere client that would help me resolve this (nothing gets triggered, no alerts, warning, failures, etc).

To prevent cross-posting, I suggest we post replies here: http://communities.vmware.com/message/1650374 -- the issue seems to be the same.

0 Kudos