menu

Using Windows PowerShell Desired State Configuration in AWS

Go to Lab

542 Reviews

8a2bfad401d8bf70ada94b96100e1dea

Jie Z. · Reviewed about 2 months ago

F2f1866d7a30bb9472b30398ba254aeb

Cheryl M. · Reviewed about 2 months ago

De6f6155d413cde0f3a95ac083e608d8

Not Very good. I would suggest instructions on verifying the configuration has been pushed/pulled on to the node machine.

Jason L. · Reviewed about 2 months ago

387936983c7d86ec3e159f8cf1184b27

missing text for example username and password... unable to complete the lab...

Brian S. · Reviewed 2 months ago

1226ceeec2db17df813d0878e97cd98e

Unable to proceed ~ PS C:\Program Files\WindowsPowerShell\Modules> ./createMOF.ps1 At C:\Program Files\WindowsPowerShell\Modules\CreateMOF.ps1:8 char:64 + Import-DSCResource -ModuleName xPSDesiredStateConfiguration + ~ Unable to load module 'xPSDesiredStateConfiguration': module not found. At C:\Program Files\WindowsPowerShell\Modules\CreateMOF.ps1:2 char:1 + { + ~ Missing closing '}' in statement block. At C:\Program Files\WindowsPowerShell\Modules\CreateMOF.ps1:43 char:1 + } + ~ Unexpected token '}' in expression or statement. + CategoryInfo : ParserError: (:) [], ParseException + FullyQualifiedErrorId : ModuleNotFoundDuringParse

James H. · Reviewed 2 months ago

223eb4bc1e3ceb2bfc72818fedf19364

jaime d. · Reviewed 2 months ago

7c46adf4844e88c7d8c8602eafa4130f

Narendra A. · Reviewed 2 months ago

Bffb38868b6fd4bd33aa0f59b1cde146

Daniel C. · Reviewed 2 months ago

35c2b8d66f7a80810736a36fafb9f8da

RIADH A. · Reviewed 2 months ago

C5089b9d6888b4bedabc8927e47a160d

Senthilvel P. · Reviewed 2 months ago

B2421652b1abf39a33021e1184ca8dd0

Steps 74 and verifying the forcePull config did not run succesfully at all. You can't run internet explorer from an administrator account. Might want to doublecheck that.

Carl m. · Reviewed 2 months ago

Dbcaf13bff5c2bc92dd97e8d57d1b734

Tomáš Ž. · Reviewed 2 months ago

C37d4184de98ec768fd0158f139567d9

Couldn't get back onto RDGW after joining to the domain, password not accepted - maybe something I did, not sure.

Evan K. · Reviewed 2 months ago

90352a49a9a5a513f2b466f74b51ffcf

good

ravi k. · Reviewed 2 months ago

Fa3f839d858e4ab8c29c94ea8c345be6

Kapil S. · Reviewed 3 months ago

939f89810d2b17baec2a5ae552e941a1

John I. · Reviewed 3 months ago

939f89810d2b17baec2a5ae552e941a1

John I. · Reviewed 3 months ago

846ff2b39121bf8e967bacfe5ef9216c

Access is denied when remoting into DSCServer

Kevin Y. · Reviewed 3 months ago

B9c9bace2ddc3d20b8dd6209b72083d0

Ed M. · Reviewed 3 months ago

4c267d866bbc79cf77a93e7d4925deef

It was OK

Bob B. · Reviewed 3 months ago

7ed4bc453ba89ba230ddef51253cbdf5

Martin A. · Reviewed 3 months ago

799d3b362b2b3758a3acc48879513945

could use a bit more explanation of the config files, what they are doing, some example changes, showing those changes happen, etc..

Jeffrey I. · Reviewed 3 months ago

16b4d5694b1ba600b03bc5719232252f

David R. · Reviewed 3 months ago

60f2bff81e859e86e54028f467502321

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.

Robert L. · Reviewed 3 months ago

80006ee379a611c33bc0d5758fb84fbe

Server was not named correctly and the DNS even after renaming the DNS entry refused to ping from DSCserver.

Anthony W. · Reviewed 3 months ago