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

Task execution path unchanged #1188

Closed
Booster2ooo opened this issue Aug 6, 2019 · 2 comments
Closed

Task execution path unchanged #1188

Booster2ooo opened this issue Aug 6, 2019 · 2 comments
Milestone

Comments

@Booster2ooo
Copy link

Disaclaimer

This issue affects an old version of wacs, I didn't try it with the latest version. It may have been fixed already, if so, sorry for bothering.

Issue description

Let's say you downloaded the great tool win-acme is and used it for the first time in your download folder. The program will create a new scheduled task with an action pointing to something like %userprofile%\Downloads\wacs.exe.

Now, you'd like to "properly" install the program so you move it to C:\bin\ and set your ‘%Path%’ (env variable) accordingly so you can call wacs.exe from anywhere. You run the program, revoke the previous certificate, cancel its renewal and recreate a new certificate for your site (with a new renewal). Everything goes nice and smooth.

But, there is a problem you didn't notice, the scheduled task action is still pointing to %userprofile%\Downloads\wacs.exe and so, next month, when you certificate needs to be renewed, it will fail (because the exe moved).

The solution is to delete the scheduled task and recreate it (or edit the action).

Steps to reproduce

Software version: 1911.1.6713.13067 (RELEASE)

  • Run wacs from a path
  • Move wacs somewhere else
  • Run wacs again
  • Check your scheduled task configuration

Desired behavior

I'd like wacs to check the schedule task action configuration and compare the execution path with the current running instance.

@WouterTinus WouterTinus added this to the 2.0.10 milestone Aug 6, 2019
@WouterTinus
Copy link
Member

It's a good idea in my opinion, I'll add some checks.

WouterTinus added a commit that referenced this issue Aug 12, 2019
@WouterTinus
Copy link
Member

Released in 2.0.10

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

No branches or pull requests

2 participants