windows apci shutdown

[ion-ral]

I do not know if you ever, but if you use windows server (2003 for example) as the guest, when you try to send a signal to shutdown the system goes out only if there are no users logged on (eg terminal services)
anyone knows how to remedy this small (but big) problem?

 

[tom]

I do not know if you ever, but if you use windows server (2003 for example) as the guest, when you try to send a signal to shutdown the system goes out only if there are no users logged on (eg terminal services)
anyone knows how to remedy this small (but big) problem?

use the search function of the forum, discussed several times (group policy settings, allow anonymous shutdown).

 

[ion-ral]

sorry Tom, I did another search but I do not think the anonymous is the solution to the problem that I noticed ... you could help me understand if I'm understanding wrong?

 

[tom]

sorry Tom, I did another search but I do not think the anonymous is the solution to the problem that I noticed ... you could help me understand if I'm understanding wrong?

its a windows issue, nothing to configure on the Proxmox VE side. for sure.

 

[ion-ral]

tom waits, do not misunderstand, I never said and certainly do not want to say it is a problem of proxmox, but I hope that you too might have happened and maybe you know how to fix it ...

 

[tom]

tom waits, do not misunderstand, I never said and certainly do not want to say it is a problem of proxmox, but I hope that you too might have happened and maybe you know how to fix it ...

I know that its a windows policy issue - no idea why you do not believe me.

 

[ion-ral]

I know that its a windows policy issue - no idea why you do not believe me.

Tom I believe you that it is a problem of windows! hoping only that some of you already had the same problem and maybe had solved ...

 

[ion-ral]

In short it seems that none of us here has already clashed with this particular problem ... nobody has posted a viable solution ...
sin, surely only those who use Linux virtual machines has to worry about but who uses Windows ...

 

[tom]

In short it seems that none of us here has already clashed with this particular problem ... nobody has posted a viable solution ...
sin, surely only those who use Linux virtual machines has to worry about but who uses Windows ...

This a the support forum for Proxmox VE. And I know that the problem is on the Microsoft side (policies) and I also fixed this on several systems.

If you need support for Microsoft, go for Microsoft support - we do not support this here in full, out of scope.

 

[ion-ral]

tom sorry but I'm not here to highlight this issue just for me ... if anyone knows how I can go around to please everyone ...
then if we want to make the tax here and say what you said then this forum can not give any responses that correlate with proxmox, since the functionality of a Windows operating system is correlated with the same proxmox ...
given what you said however I will avoid to ask again about these problems ...

 

[fluke]

Are you able to shut down windows without logging on? Before logging on, when you press ctrl-alt-del, are you able to press the shutdown button?

Another suggestion:

Go to qemu monitor and issue the command 'system_powerdown' and then go to the vnc console of the server and check if there are any prompts like there are other users logged on.

 

[ion-ral]

Are you able to shut down windows without logging on? Before logging on, when you press ctrl-alt-del, are you able to press the shutdown button?

already solved

Another suggestion:

Go to qemu monitor and issue the command 'system_powerdown' and then go to the vnc console of the server and check if there are any prompts like there are other users logged on.

accurate, tells me that there are other users logged on
can you tell me how to force

 

[fluke]

accurate, tells me that there are other users logged on
can you tell me how to force

If you use terminal services and have logged on users, I would rather suggest that you log them off on a time schedule (for example with tslogoff).

Otherwise you can try this suggestion

Go to Local Computer Policy->Computer Configuration->Administrative Templates->System Select Display Shutdown Event Tracker and disable it.

 

[ion-ral]

does not work either tracker...
the problem is that I can't limit the time of parliamentary sessions terminal services, I only need that if the proxmox must be extinguished even the guest turn off without prompting ...

 

[vlad]

You can try solution here, I have similar problem with Win2k machines and feature MS built-in. The "qm shutdown" causes Win2k machines to shutdown without allowing other programs to close gracefully. I think VMWare solved the issue with their guest Tools, definitely need something like that for KVM.

 

[vlad]

Found poweroff solution that works properly and solved my problem, God bless guy who wrote it. It just saved me a bunch of time trying to setup CYGWIN on every server.

 

[JustaGuy]

I have a machine right now that won't stop no matter what I do. Even that app mentioned above isn't doing anything.
Is there a way to pull it's power cord at the command line?
I just reboot PVE, but need another way if it happens again.

 

[tom]

I have a machine right now that won't stop no matter what I do. Even that app mentioned above isn't doing anything.
Is there a way to pull it's power cord at the command line?
I just reboot PVE, but need another way if it happens again.

list the VM´s with 'qm list'.

the last column shows the PID (process ID). kill this process.

kill PID

 

[dietmar]

Normally you can simply press 'stop' using the web interface - you already tried that?

 

[JustaGuy]

Yes, I noticed in the past "Stop" usually works in instances where "Reset" doesn't.

In this case "Stop", "Shutdown", "Reset" buttons & the "Reboot" link had no effect.