Hello,
I am evaluating your pre-packaged version 0.6.0.0 (the newer package is still broken). I am working getting my Windows 10 LCM talking with the Tug Server. Registration seems to go OK. But The GetDscAction action is failing due to strict input filter checking.

Is there any guidance on how I should proceed here? I can't seem to find an application setting that would turn strict checking off. Since it is the Windows 10 LCM talking to Tug is this a bug in how Tug is supposed to work?

Thank you for your assistance. I haven't seen much activity on here lately so I'm beginning to fear this project has hit the end of the road -- I do hope that is not the case.

Regards,
Brian

> 2017年09月15日 15:05:19.1498|0|WARN|Tug.Server.Filters.StrictInputFilter|Re-serialized representation does not match actual input
> 2017年09月15日 15:05:19.1498|0|TRACE|Tug.Server.Filters.StrictInputFilter|Expected: {"ClientStatus":[{"ConfigurationName":"BaseWindows","Checksum":"","ChecksumAlgorithm":"SHA-256"}]}
> 2017年09月15日 15:05:19.1498|0|TRACE|Tug.Server.Filters.StrictInputFilter|Actual: {"ClientStatus":[{"Checksum":"","ConfigurationName":"BaseWindows","ChecksumAlgorithm":"SHA-256"}]}