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

MultipleInstancesEnum not described #204

Closed
colinangusmackay opened this issue May 16, 2018 — with docs.microsoft.com · 8 comments
Closed

MultipleInstancesEnum not described #204

colinangusmackay opened this issue May 16, 2018 — with docs.microsoft.com · 8 comments
Assignees

Comments

Copy link

There is a parameter called -MultipleInstances the type of which is MultipleInstancesEnum, however this type is not described, nor it is linked to. The upshot of this is that I don't know what are the valid values for the MultipleInstances parameter and what each value means.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@bladeoflight16
Copy link

bladeoflight16 commented Jan 12, 2019

The fully qualified name of the enum is Microsoft.PowerShell.Cmdletization.GeneratedTypes.ScheduledTask.MultipleInstancesEnum. With this name in hand, you can list the values:

PS> [System.Enum]::GetNames([Microsoft.PowerShell.Cmdletization.GeneratedTypes.ScheduledTask.MultipleInstancesEnum])
Parallel
Queue
IgnoreNew

These values are also found in the "Accepted values" row of the table below the parameter.

I believe the meanings are as follows:

Value Meaning Corresponding Value in Task Scheduler Interface
Parallel Run a new instance in parallel Run a new instance in parallel
Queue Wait until the current instance finishes and then execute this one. Queue a new instance
IgnoreNew Do not start a new instance Do not start a new instance
??? Kill the process for the currently running instance Stop the existing instance

"Stop the existing instance" from the Task Scheduler UI conspicuously has no enum value.

This does still need to be documented in the page better. If it's not going to be linked to an actual documentation page, the meanings at least need to be specified.

@o0nj
Copy link
Contributor

o0nj commented Mar 14, 2019

@officedocsbot assign @yogkumgit

get-itips added a commit to get-itips/windows-powershell-docs that referenced this issue Mar 21, 2019
added more detail to MultipleInstances parameter MicrosoftDocs#204
@get-itips
Copy link
Contributor

Hi @colinangusmackay thanks for your feedback.
A PR has been created to improve the article based on your suggestion.
Thank you!

@yogkumgit
Copy link

@kenwith please merge this PR, if you find it suitable

@yogkumgit
Copy link

@get-itips Thank you very much for the contribution and updating the documentation with PR. @colinangusmackay Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@yogkumgit
Copy link

@officedocsbot close

@colinangusmackay
Copy link
Author

Thank you. It is much appreciated.

@o0nj o0nj removed their assignment Aug 5, 2019
@Rob-S
Copy link
Contributor

Rob-S commented May 12, 2020

It was noted above that:

"Stop the existing instance" from the Task Scheduler UI conspicuously has no enum value.

Value in Task Scheduler Interface: Stop the existing instance
Value in Task XML file: StopExisting
Meaning: Kill the process for the currently running instance

That value is missing from the Microsoft.PowerShell.Cmdletization.GeneratedTypes.ScheduledTask.MultipleInstancesEnum but is needed for ComputerManagementDsc Issue#333 ScheduledTask: MultipleInstances Parameter Should Allow For 'StopExisting'

Question: Where do we file the bug issue for that?

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

7 participants