Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PC fails to wake-up for client backup if suspended with this app #19

Open
siebert opened this issue Mar 26, 2022 · 3 comments
Open

PC fails to wake-up for client backup if suspended with this app #19

siebert opened this issue Mar 26, 2022 · 3 comments

Comments

@siebert
Copy link

siebert commented Mar 26, 2022

My PC is automatically backed up each night with the client backup feature of Windows Server 2012 R2 Essentials.

If the PC is suspended via the Windows toolbar menu, it automatically resumes at the scheduled backup time and the backup job is executed.
If the PC is suspended via the remote-shutdown-pc tool, it doesn't resume and the backup job isn't executed.

Why is the suspend-behavior different, and is there a way to also have the PC resume for the backup when suspended via the tool?

@karpach
Copy link
Owner

karpach commented Jul 26, 2022

It works as expected. I specifically disable wake events in suspend command (third parameter):
Application.SetSuspendState(PowerState.Suspend, true, true);

I guess I can make the third parameter part of the settings.

@siebert
Copy link
Author

siebert commented Jul 26, 2022

I already figured that out and tried to fix it in a local build, but I was unable to compile a fully working binary (I even tried multiple versions of Visual Studio), so I'm currently using a simple Python script I wrote.

But if this issue gets fixed in this app, I'll switch back to it.

I can't imagine why someone would like to ignore wake events, as they were probably scheduled for a reason, so I would expect that just changing the third parameter to "false" should work for everyone, but making it configurable via settings is fine for me as well.

@siebert
Copy link
Author

siebert commented Oct 19, 2022

I see that you released a new version, but didn't address this issue. I would be really great if you could make another release with that fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants