Skip to content
#

dsc

Here are 253 public repositories matching this topic...

typozh
typozh commented Jan 24, 2017

Details of the scenario you try and problem that is occurring:
For a large search topology I'm missing a few things. One is that all the databases are created in the same sql instance. The name cannot be configured individually and there is only one property for the sql server. And I need to create multiple crawl store databases which is not possible with the current version. The multiple cra

johlju
johlju commented Jul 23, 2018

Details of the scenario you tried and the problem that is occurring:
When using Get-DscConfiguration with the resource WaitForNetworkTeam there are no indication of the status of the network team.
I suggest we add a read-only property Status where we can return the current status of the network team ('Up','Down'). Alternative the read-only property could be named IsUp, so it could be

ykuijs
ykuijs commented Nov 5, 2019

Details of the scenario you tried and the problem that is occurring

When you specify an application pool that does not exist in a xWebsite resource, the resource does not check if the specified application pool exists. This results in a broken website with error "Unknown:The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)"

Verbose logs showin

johlju
johlju commented Jul 20, 2018

Details of the scenario you tried and the problem that is occurring:
In the resource CertificateImport there should be no need to have the non-mandatory parameter Ensure in the Get-TargetResource function.

https://github.com/PowerShell/CertificateDsc/blob/6906fc5b31a783a899260c9c9d4ba84a02dd4c14/Modules/CertificateDsc/DSCResources/MSFT_CertificateImport/MSFT_CertificateImport.psm1#L65-

danagarcia
danagarcia commented Oct 3, 2019

Details

Currently the xExchInstall resource doesn't check for prerequisites for Exchange 2013/2016/2019 and install them if necessary. This is pretty much the only thing that limits this DSC resource module from being a 100% end to end solution for deploying, configuring, and maintaining Exchange 2013/2016/2019.

Suggested solution

Add a prerequisite check for prerequisites i.e. .Net

johlju
johlju commented Jul 24, 2018

Details of the scenario you tried and the problem that is occurring:
Suggest we add a read-only parameter to the WaitForVolume resource. That way the Get-TargetResource could call Test-TargetResource and return the result (the actual current state) of the volume in the property Available when calling Get-DscConfiguration.

**The DSC configuration that is using the resource (as detai

Improve this page

Add a description, image, and links to the dsc topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the dsc topic, visit your repo's landing page and select "manage topics."

Learn more