xPSDesiredStateConfiguration | DSC resources for configuring common operating systems | Command Line Interface library

by dsccommunity PowerShell Version: v9.2.0-preview0007 License: MIT

X-Ray Key Features Code Snippets Community Discussions(6)Vulnerabilities Install Support

kandi X-RAY | xPSDesiredStateConfiguration Summary

xPSDesiredStateConfiguration is a PowerShell library typically used in Utilities, Command Line Interface applications. xPSDesiredStateConfiguration has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The xPSDesiredStateConfiguration module is a more recent, experimental version of the PSDesiredStateConfiguration module that ships in Windows as part of PowerShell 4.0. The supported version of this module is available as PSDscResources. This module is automatically tested using PowerShell 5.1 on servers running Windows 2012 R2 and Windows 2016, and is expected to work on other operating systems running PowerShell 5.1. While this module may work with PowerShell versions going back to PowerShell 4, there is no automatic testing performed for these versions, and thus no guarantee that the module will work as expected.

Support

Quality

Security

License

Reuse

Support

xPSDesiredStateConfiguration has a low active ecosystem.

It has 187 star(s) with 131 fork(s). There are 40 watchers for this library.

It had no major release in the last 12 months.

There are 122 open issues and 285 have been closed. On average issues are closed in 228 days. There are 8 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of xPSDesiredStateConfiguration is v9.2.0-preview0007

Quality

xPSDesiredStateConfiguration has no bugs reported.

Security

xPSDesiredStateConfiguration has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

xPSDesiredStateConfiguration is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

xPSDesiredStateConfiguration releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of xPSDesiredStateConfiguration

Get all kandi verified functions for this library.

xPSDesiredStateConfiguration Key Features

No Key Features are available at this moment for xPSDesiredStateConfiguration.

xPSDesiredStateConfiguration Examples and Code Snippets

No Code Snippets are available at this moment for xPSDesiredStateConfiguration.

Community Discussions

Trending Discussions on xPSDesiredStateConfiguration

Error while applying configuration using PowerShell DSC VM extension : "Compilation errors occurred while processing configuration"

Credentials in Desired State Configuration

Azure DSC Extension. HKLM:\SOFTWARE\Microsoft\PowerShell\3\DSC doesn't exist

DSC Pull server unable to register Windows 10 (1709) Client

Powershell DSC - Download MSI file to VM

Desired State Configuration HTTPS Doesn't Work

QUESTION

Error while applying configuration using PowerShell DSC VM extension : "Compilation errors occurred while processing configuration"

Asked 2019-Dec-10 at 22:35

I have a simple configuration that I am trying to apply to an Azure VM using PowerShell DSC extension

...

ANSWER

Answered 2019-Dec-10 at 22:35

The logs inside the target machine showed that the issue is with the execution policy.

In my script I changed "Set-ExecutionPolicy -ExecutionPolicy RemoteSigned" to "Set-ExecutionPolicy -ExecutionPolicy ByPass -Scope CurrentUser -Force" and it worked fine.

Source https://stackoverflow.com/questions/59242940

QUESTION

Credentials in Desired State Configuration

Asked 2018-Sep-04 at 10:58

I have the following Desired State Configuration (DSC)

...

ANSWER

Answered 2017-Mar-28 at 20:37

You need to allow for plaintextcredentials (link)

Source https://stackoverflow.com/questions/43078422

QUESTION

Azure DSC Extension. HKLM:\SOFTWARE\Microsoft\PowerShell\3\DSC doesn't exist

Asked 2017-Nov-16 at 10:08

I'm trying to create an Azure RM Template with SQL Server 2016 AlwaysOn Avaiability Group by using this base template http://4c74356b41.com/post5775 The template I linked is too complex for me. I just need to create 2 VMs and 1 Storage Account and apply proper DSC to the VMs. I'm getting the following error while applying configuration sql-primary and configuration sql-secondary to the both VMs:

...

ANSWER

Answered 2017-Nov-16 at 10:08

Just to sum up a bunch of points here:

domain and sql accounts should be different
sql cluster ip address should be in one of the cluster networks
you need to precreate the dns name record for the load balancer (due to how i'm doing everything in parallel i've decided to put that functionallity into the domain provisioning dsc configurations)
to check deployment you can use always on dashboard

Cannot find path 'HKLM:\SOFTWARE\Microsoft\PowerShell\3\DSC' because it does not exist.

Seems to be a general error being thrown when something goes wrong (at least I could never find a pattern why it appeared), so usually its safe to disregard that error, it will be gone when you fix the real error (in my experiecen, at least).

SQL provisioning fails (sometimes) with weird errors (usually dns\timing related). I'm not sure how this would behave in an environment where domain is precreated in advance. it might be less fragile overall. In my latest commit (at the time of writing) I believe I've addressed some of the stability issues, and I'm quite sure with domain, storage for backups, keyvault precreated those issues shouldn't be present at all.

Source https://stackoverflow.com/questions/47154974

QUESTION

DSC Pull server unable to register Windows 10 (1709) Client

Asked 2017-Oct-25 at 19:16

Issue: Unable to register DSC windows 10 (version 1709) client with pull server.

Background: Below is a detailed list of the environment/configuration that was implemented and working correctly to register the windows 10 client node (version: 1511) before updating the client to version 1709. The pull server and its certificate has been recreated using the below configurations to keep the configurations as simple as possible to prove the issue.

Pull Server system details:

OS: Windows Server 2012 R2

WinVer: Version 6.3 (Build 9600)

PSVersion: 5.1.14409.1012

xPSDesiredStateConfiguration: 7.0.0.0

Pull Server configuration:

The pull server was configured using the microsoft sample script located here under page title: "Setting up a web pull server" (copied below for convenience)

...

ANSWER

Answered 2017-Oct-25 at 19:16

After posting this question on Powershell.org/forums it was quickly answered by Don Jones. It turns out using a self-signed certificate for your pull server to have a "fake" secure test environment is now locked down by windows and no longer supported. This is to prevent developers from accidentally using it in a production environment.

My solution for now is to have a standard unsecured http pull server for our test lab until we need a true certificate for a production environment.

Source https://stackoverflow.com/questions/46939614

QUESTION

Powershell DSC - Download MSI file to VM

Asked 2017-May-19 at 02:08

I've tried the following example to download from Azure blob or Azure file share but never got it to work. Is there a way to download files to VM passing credentials or keys?

...

ANSWER

Answered 2017-May-19 at 02:08

If you download file from Azure File Share, you could refer to this example. Add following script to your script.

Source https://stackoverflow.com/questions/44049688

QUESTION

Desired State Configuration HTTPS Doesn't Work

Asked 2017-Apr-13 at 09:03

I've created a domain certificate for my DSC web pull server (issued by my internal CA) and retrieved the thumbprint.
I exported the certificate from inetmgr and installed it on the pull server (both local machine and user).
I then put the thumbprint in the script in the CertificateThumbprint parameter.

However when I re-run the config script to generate the new MOF and restart the DSC configuration, I can still only get to the site via http and not https.

When I try to navigate to the pull server site with https I get TLS warnings. (I'm on Windows Server 2016, PS version 5.1)

Cheers

EDIT:

Below is the script for generating the MOF with the thumbprint inside.

...

ANSWER

Answered 2017-Apr-13 at 09:03

I managed to resolve this issue by adding a site binding for the PS DSC Pull Server site in IIS with the certificate, FYI.

Source https://stackoverflow.com/questions/43340394

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install xPSDesiredStateConfiguration

This configuration will download a file from a specific URI to DestinationPath. The web request will contain specific headers and will be sent using a specified user agent.