Sorry if this was posted already, but I didn’t see it on the first few pages of posts.
Whenever I configure multiple ‘ConfigurationNames’ in the LCM config (metaconfig), I get this error when pulling, such as when running {Update-DSCConfiguration}:
PS C:\Windows\system32> Update-DscConfiguration -Wait -Verbose VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = PerformRequiredConfigurationChecks,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'. VERBOSE: An LCM method call arrived from computer KYLE-IPAM with user sid S-1-5-21-3149736864-2278915772-2866003438-1107. VERBOSE: [KYLE-IPAM]: [] Executing Get-Action with configuration 's checksum: 27CF2908BFD506C5C390EB5BDEE48601BF238F64C3E36384D6C55DAF88AB5184. VERBOSE: [KYLE-IPAM]: [] Executing Get-Action with configuration 's checksum failed. Please check the availability of pull server. A generic exception occurred during the invocation of the Get-DSCAction cmdlet by Download Manager WebDownloadManager. + CategoryInfo : InvalidResult: (root/Microsoft/...gurationManager:String) [], CimException + FullyQualifiedErrorId : GetActionException + PSComputerName : localhost VERBOSE: Operation 'Invoke CimMethod' complete. VERBOSE: Time taken for configuration job to complete is 1.532 seconds
If I configure ConfigurationNames with @(‘test’) or @(‘test2’), it pulls the configuration and works perfectly. If I configure that same setting as @(‘test2’,‘test’) or @(‘test’,‘test2’), I get the above error.
Is this a valid configuration at this point? I also wasn’t sure what order they would be applied in, as I don’t believe DependsOn will work between configs, but I could be wrong. I was trying to test out those concerns when I was stopped by the previously mentioned error.
Just to be clear, all I’m changing is that one setting in the metaconfig.
In the meantime, I’m considering simply creating one large configuration with the whole per-node configuration style using configuration data variables. Running smaller configs would be nice, but have their own issues as well.