Geeks 4 Data

I'm working on a DSC configuration for SQL Server Reporting Services and it is quite a simple configuration with very few required resources. However, one of the resources (xSQLServerRSConfig) does something rather odd in it's Set-TargetResource function - it uses Invoke-Command to loop back to the same server and specifies the -Authentication parameter as CredSSP. Now up until the other day I had no idea what CredSSP was and the exception that was raised by the LCM was rather new to me: After spending ages trying to learn what the CredSSP protocol is and why someone would use it (see  https://4sysops.com/archives/using-credssp-for-second-hop-powershell-remoting/  and  https://technet.microsoft.com/en-us/library/hh849872.aspx  ) I decided to check for a DSC resource to enable it...and there is one, xCredSSP . Happy days! Then came the joy and agony of seeing DSC in action. Joy because the resource is so simple to configure: xCredSSP Client { E...

When you want to know the current configuration of a DSC node you use the very aptly named Get-DscConfiguration cmdlet like so: PS C:\>Get-DscConfiguration -CimSession $target_node This cmdlet will execute the Get-TargetResource function for every configured resource on the node and return details on its current state like so: And life is good until you add a new resource to your configuration, push it to the target node and run the cmdlet again, only to be faced with an ugly exception like this: I know what you're thinking, "say whaaaat!!". You just want to see what the current config is and because of one dodgy resource you can't see anything - that sucks. However, the solution is quite simple. The words that stand out are key is not a valid property in the corresponding DSC resource schema file . The preceding word (AvailabilityGroupNameDatabase in this case) is the property that the resource Get-TargetResource function is ...