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

ScheduledTask: Using ScheduledTask resource to create task that recurs once every month on the 1st? #173

Closed
grpowershell opened this issue Jul 26, 2018 · 4 comments
Labels
stale The issue or pull request was marked as stale because there hasn't been activity from the community.

Comments

@grpowershell
Copy link

grpowershell commented Jul 26, 2018

So I want to have DSC create a scheduled task on a target computer where the task recurs every month on a certain date (in my case, the 1st of the month) but it doesn't appear possible to specify a date for a task to start.

Any feedback/insight would be appreciated.

@grpowershell grpowershell changed the title Using ScheduledTask resource to create task that recurs once every month on the 1st? ScheduledTask: Using ScheduledTask resource to create task that recurs once every month on the 1st? Jul 26, 2018
@grpowershell
Copy link
Author

Now obviously a way around this is to create a schedule task that runs every day that runs a script that works out if it's the 1st of the month and then executes whatever you want it to execute. Perfectly possible but I would have thought given that a standard Windows scheduled task has monthly functionality that it should be incorporated in to this DSC resource.

@johlju
Copy link
Member

johlju commented Jul 30, 2018

If you can create what you looking for with New-ScheduledTaskTrigger cmdlet then we could match that with the parameters available, and see if there are any functionality that is missing.

@johlju johlju added the question The issue is a question. label Jul 30, 2018
@stale
Copy link

stale bot commented Aug 29, 2018

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

@stale stale bot added the stale The issue or pull request was marked as stale because there hasn't been activity from the community. label Aug 29, 2018
@stale
Copy link

stale bot commented Oct 8, 2018

This issue has been automatically closed because it is has not had activity from the community in the last 40 days.

@stale stale bot closed this as completed Oct 8, 2018
@johlju johlju removed the question The issue is a question. label Oct 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The issue or pull request was marked as stale because there hasn't been activity from the community.
Projects
None yet
Development

No branches or pull requests

2 participants