Using Windows PowerShell Desired State Configuration in AWSGo to Lab
Access is denied when remoting into DSCServer
It was OK
could use a bit more explanation of the config files, what they are doing, some example changes, showing those changes happen, etc..
got this error at the end, no one could figure it out, so I just completed the lab. Pull failed but push was successful... VERBOSE: Performing the operation "Start-DscConfiguration: SendMetaConfigurationApply" on target "MSFT_DSCLocalConfigurationManager". VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendMetaConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'. WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer rdgw.qlstudentdomain.local. Verify that the computer exists on the network and that the name provided is spelled correctly. + CategoryInfo : NotSpecified: (root/Microsoft/...gurationManager:String) , CimException + FullyQualifiedErrorId : HRESULT 0x80070035 + PSComputerName : rdgw.qlstudentdomain.local VERBOSE: Operation 'Invoke CimMethod' complete. VERBOSE: Set-DscLocalConfigurationManager finished in 0.078 seconds.
Server was not named correctly and the DNS even after renaming the DNS entry refused to ping from DSCserver.
I could use more explanation, not just implementation plan
DC instance has't passed instance check on start.
I don't see how this is any different from configuring DSC in any other environment. I was hoping to focus less on the initial build out of DSC and more on configuring DSC to interact more with AWS services. This felt more like busy work of copying commands and not focused on some of the great integrations with DSC and AWS.
I felt I was going through the motions without fully understanding the why