Invoke-DscResource weirdness

[potatoqualitee]

solution is earlier in the script not to test for the existence of the module but for import-dscresource to actually load and if it doesnt then copy to program files and explicitly import from there

[potatoqualitee]

https://stackoverflow.com/questions/7052765/powershell-changing-the-culture-of-current-session

this seems to be a localization issue

[potatoqualitee]

PSDscResources or xPSDesiredStateConfiguration

so when you call Invoke-DscResource, you can specify the ModuleName parameter - you should always do this (and tbh, specify the minimum or precise version you need) and especially to avoid using the resources that shipped in DSC v1.1

[potatoqualitee]

@jpomfret i feel decently confident this will address your issues. please feel free to reopen if you run into it again.