xSQLServer - PowerShell Desired State Configuration Resource Kit

The xSQLServer PowerShell DSC module contains resources for System Center-compliant setup of SQL Server, SQL Server Reporting Services secure connection level, and configuration of firewall rules.

1,244 times
Add to favorites
System Center
E-mail Twitter del.icio.us Digg Facebook
  • Problem with Updates folder
    4 Posts | Last post January 07, 2016
    • Hello!
      IN SQL deployment resource you hardcoded a function which looks for folder "Updates" in folder with SQL media and tries to install updates from it. If no such folder exists your DSC resource fails. Could you please make this update function optional? There are a lot of cases where you don't need to install updates for SQL from media and you are find with default media, but script is failing still as folder has to be there even if its empty
    • Use the UpdateEnabled = "False" flag
    • Installation still fails for me if folder does not exists with same error as before. I set UpdateEnabled = "False" in my DSC Config
    • I found resolution. You have to set:
      UpdateEnabled = $false
      UpdateSource = "MU"
  • Sorry maybe the wrong place for my Informations ?
    2 Posts | Last post June 30, 2015
    • I could only commit 2000 characters, maybe this is the wrong place for my information. Here are the end of my message.
      There are maybe others issues in the feature detection, but that must I test. 
      I hope this information helps, maybe you already know this all ;-), but I spend a lot of time and I thought it would be a good idea to share this information
      best regards jens m.
      PS: If I use the wrong place, then told me the correct one and i put the message there and you can delete my Information here.
    • @jensMuell
      Thank you for the feedback.  Development for this module has moved to GitHub (https://github.com/PowerShell/xSQLServer).  I recommend you report your issues on that site.
      John Slack
      Program Manager
      PowerShell Team
  • Severall Issues in xSQLServerSetup
    1 Posts | Last post June 27, 2015
    • Hi have use the xSQLServer Resource to install SQLExpress Adv (DEU) on Server Core here are my Experience, maybe that helps the developer :
      1. If i started with the Resource on a german language Server, there is a Issue with LocalizedData in the xPDT.psm1. I copy en-Us folder to a de-DE and the Issues are gone. So it would be better to check this, so the others in world could use the resource
      2. My Installation-Resource (setup.exe) is on the UNC-Path in the network, the Resource script called the function GetSQLVersion, but there is no net_use command first to make a secure Connection to the UNC-Source. So the function call failed and the resource execution failed.
      3. If you use netuse from the xPDT.psm1 and the Setup Credential has a complex Password (maybe double Quote inside), the netuse command failed and the connection couldn’t be established.  Maybe it is better to use with pinvoke the WNetAddConnection2 or NetUseAdd methods. I use the implementation from http://stackoverflow.com/questions/1477328/calling-wnetaddconnection2-from-powershell and it worked fine.
      4. The second problem with complex password is in the execution of the setup.exe. If you defined a complex SQLService-Account-Password, then the Installation failed (maybe double Quote inside) with wrong password. So it would be better to escaped the arguments. A good starting point for this is http://blogs.msdn.com/b/twistylittlepassagesallalike/archive/2011/04/23/everyone-quotes-arguments-the-wrong-way.aspx. If I use the rules in the blog the complex password is correct committed to the setup.exe
      5. If you check the features, then the check is CASEsensitiv, so if you not take the correct CASE in the Resource-Property then the installed Feature is not recognized correct. So maybe it is better to make a IGNORE-CASE compare. But this issue is addressed on https://github.com/PowerShell/xSQLServer/commits/dev ‘Resolved problem with $Features due to Contains method being case sen…’.
  • The setting UpdateEnabled is not supported by sql 2008 R2
    1 Posts | Last post June 03, 2015
    • This resource always specified the UpdateEnabled even if it is set to false. This causes the sql server 2008 R2 to fail with the following error
      Overall summary:
        Final result:                  Failed: see details below
        Exit code (Decimal):           -2068578301
        Exit facility code:            1204
        Exit error code:               3
        Exit message:                  The setting 'UPDATEENABLED' specified is not recognized.
        Start time:                    2015-06-03 10:25:52
        End time:                      2015-06-03 10:26:04
        Requested action:              RunRules
      i've made a hot fix on our version but it should be great if there was a way to disable this argument
  • SourcePath cannot be URL
    2 Posts | Last post March 04, 2015
    • Hi, 
      The SourcePath always need to be a folder. How do I specify the Url of my BLOB if I have stored the ISO in the Azure Storage ?
    • Hello!
      you cannot do that. You need to download iso, unpack it and put to sourcepath.
      You can do it like this:
      import-module "C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\Azure.psd1"
      $StorageAccountName = "mystorageaccount"
      $StorageAccountKey = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=="
      $destination = "c:\temp"
      $context = New-AzureStorageContext -StorageAccountName $StorageAccountName -StorageAccountKey $StorageAccountKey
      Get-AzureStorageContainer -Name "sql" -Context $context | Get-AzureStorageBlob | Get-AzureStorageBlobContent -Destination $destination 
      $imagePath = "C:\temp\SQL2012.ISO"
      Mount-DiskImage $imagePath -PassThru
      $diskimage = Get-DiskImage $imagePath
      $volume = Get-Volume -DiskImage $diskimage
      copy-item "$($volume.driveletter):\" -Destination "c:\media\sql2012" -Recurse
      Dismount-DiskImage $ImagePath
  • Variable containing path to source
    2 Posts | Last post February 05, 2015
    • Hello! In your DSC resource you hardcoded path to SQL source files, it has to be named "SQLServer2012.en" if I store SQL media in folder with another name your DSC resource simply fails. Its very bad practice to hardcode paths in scripts. Could you please allow to store any sharing name in source variable?
    • Specify the SourceFolder flag.
      My sql setup.exe lives in c:\vagrant\dscresources\SQL2014"
      My config looks like this
                  SourcePath = "C:\vagrant\DSCResources"
                  SourceFolder = "SQL2014"