WMF5 Bug? Start-DscConfiguration Error: Unrecognized argument: "JobId"

I’m trying to push a configuration to multiple nodes:

Start-DscConfiguration -ComputerName $servers -Path ‘.\SomeDir’ -Wait -Verbose

I get the following error:

The WinRM client cannot process the request. The object contains an unrecognized argument: “JobId”. Verify that the spelling of the argument name is correct.

Searching around, it seems that I’m not alone in seeing this, but I’ve yet to find a solution.

I’m pushing to 2012-R2 Servers that have WMF4 and my authoring / push box is WMF5 Feb.

Any help would be most appreciated!

I think your best bet would be, at this point, to not use WMF5 in any kind of production situation. It’s very very very very beta, and it actually isn’t licensed for use in production.

Therefore, I’ll assume you’re working in a test environment :).

There’s likely some v5-to-v4 communication snafu. Given that WMF5 is very pre-release, it probably isn’t practical to look for a workaround at this stage. Log the bug in Connect, so the team knows about it, but I wouldn’t hold my breath for a solution.

I am using WMF4 and get the Error

The WinRM client cannot process the request. The object contains an unrecognized argument: “Force”. Verify that the
spelling of the argument name is correct.
+ CategoryInfo : MetadataError: (root/Microsoft/…gurationManager:String) [], CimException
+ FullyQualifiedErrorId : HRESULT 0x803381e1
+ PSComputerName : testdsc-54