Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-3202

sqlserver.rb DISM command references undefined $LocalSource variable

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: sqlserver
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      Need to be able to install .NET framework 3.5 from an external package source.

      Assuming manual validation.

      Show
      Need to be able to install .NET framework 3.5 from an external package source. Assuming manual validation.
    • Epic Link:
    • Story Points:
      3
    • Sprint:
      Windows 2016-08-24, Windows 2016-09-07

      Description

      When a system does not already have .net 3.5 installed, the sqlserver module attempts to install it. However, the DISM command that it uses references an undefined $LocalSource variable.

      From sqlserver.rb:

      Install-WindowsFeature  NET-Framework-Core
       
      Write-Host "Installing .Net Framework 3.5, do not close this prompt..."
      DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:$LocalSource | Out-Null
      $Result = Dism /online /Get-featureinfo /featurename:NetFx3
      If($Result -contains "State : Enabled")
      {
          Write-Host "Install .Net Framework 3.5 successfully."
      }
      Else
      {
          Write-Host "Failed to install Install .Net Framework 3.5,please make sure the local source is correct."
      }
      

      Improvement Request

      Define LocalSource variable, and add parameterized version to allow users on offline systems to install the module using custom install path for .net 3.5

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              erick Erick Banks
              Reporter:
              nathanael Nathanael Cole
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support