Details of the scenario you tried and the problem that is occurring
Verbose output of Languages property is broken in Test-TargetResource, it returns System.Collections.Specialized.StringCollection instead of list of languages
Verbose logs showing the problem
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Mi
crosoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer SRV1 with user sid S-1-5-21-2574420874-2490326428-1586090461-500.
VERBOSE: [SRV1]: LCM: [ Start Set ]
VERBOSE: [SRV1]: LCM: [ Start Resource ] [[UpdateServicesServer]WSUS]
VERBOSE: [SRV1]: LCM: [ Start Test ] [[UpdateServicesServer]WSUS]
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] Getting WSUS server.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] WSUS server is Present.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] Getting WSUS server configuration.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] Getting WUSS server subscription.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] Getting WSUS SQL server.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] WSUS Server SQL Server is MICROSOFT##WID.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] Getting WSUSServer content directory.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] WSUS Server content directory is E:\.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] Getting WSUSServer update improvement program.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] WSUS Server content update improvement program is False.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] Getting WSUS Server languages.
VERBOSE: [SRV1]: [[UpdateServicesServer]WSUS] WSUS Server languages are System.Collections.Specialized.StringCollection.
Details of the scenario you tried and the problem that is occurring
Verbose output of Languages property is broken in
Test-TargetResource
, it returnsSystem.Collections.Specialized.StringCollection
instead of list of languagesVerbose logs showing the problem
...
Suggested solution to the issue
https://github.com/dsccommunity/UpdateServicesDsc/blob/dd6be4e15d88399dc9152364b0b80ef270f329a0/source/DSCResources/MSFT_UpdateServicesServer/MSFT_UpdateServicesServer.psm1#L117-L127
Adjust line 124 to:
...to transform the string collection into a simple string.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used