-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Allow -JobName and -HostName parameters in Invoke-Command #11443
Copy link
Copy link
Closed
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugWG-Cmdlets-Corecmdlets in the Microsoft.PowerShell.Core modulecmdlets in the Microsoft.PowerShell.Core moduleWG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer
Description
Summary of the new feature/enhancement
I feel like this leans on the bug category... but I suppose it is a feature...
Today, you can't use -HostName and -JobName together in the same call to Invoke-Command.
PS > Invoke-Command -ScriptBlock { gci } -AsJob -HostName localhost -JobName foo
Invoke-Command: Parameter set cannot be resolved using the specified named parameters. One or more parameters issued cannot be used together or an insufficient number of parameters were provided.
Once I get rid of -JobName it works:
PS > Invoke-Command -ScriptBlock { gci } -AsJob -HostName localhost
Id Name PSJobTypeName State HasMoreData Location Command
-- ---- ------------- ----- ----------- -------- -------
5 Job5 RemoteJob Running True localhost gci
Proposed technical implementation details (optional)
Could this be as easy as allowing JobName parameter with this parameter set?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugWG-Cmdlets-Corecmdlets in the Microsoft.PowerShell.Core modulecmdlets in the Microsoft.PowerShell.Core moduleWG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer