microsoft / PowerStig

STIG Automation
https://www.powershellgallery.com/packages/PowerSTIG
Other
548 stars 115 forks source link

DotNetFramework Resource Does Not Generate MOF #329

Closed rtabit closed 5 years ago

rtabit commented 5 years ago

Describe the bug Config with DotNetFramework does not generate MOF.

To Reproduce

  1. Create config

    function New-OrgSettingXmlFile
    {
    @"
    <?xml version="1.0"?>
    <!--
    The organizational settings file is used to define the local organizations
    preferred setting within an allowed range of the STIG.
    
    Each setting in this file is linked by STIG ID and the valid range is in an
    associated comment.
    -->
    <OrganizationalSettings version="1.4" />
    "@ | Out-File -FilePath "$PSScriptRoot\orgsettings.xml"
    }
    Configuration DotNetFw_config
    {
    param
    (
        [string[]]$ComputerName='localhost'
    )
    Import-DscResource -ModuleName PowerStig  
    
    Node $ComputerName
    {
        DotNetFramework DotNetFwConfiguration
        {
            FrameworkVersion = 'DotNet4'
            StigVersion = 1.4
            OrgSettings = "$PSScriptRoot\orgsettings.xml"
        }
    }
    }
    New-OrgSettingXmlFile
    DotNetFw_config -OutputPath 'c:\'
  2. Execute to generate mof
  3. Completes with no errors. Also can't find any related logs. Not sure if bug or if I'm missing something.

Expected behavior MOF gets generated.

chasewilson commented 5 years ago

Hi @rtabit , Thank you for contributing to PowerStig! Your feedback is greatly appreciated. If you look at the latest version of the DotNet STIG, there aren't any rules to automate. It is currently only made up of Manual and Document rules. We are looking at possibilities of automating some of these rules in the future. I'm sorry about the confusion and if you have any more questions, feel free to reach out.

rtabit commented 5 years ago

OK, sounds good thanks.