Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues during using this DSCResource #7

Closed
jens-mueller opened this issue Jul 5, 2015 · 0 comments
Closed

Issues during using this DSCResource #7

jens-mueller opened this issue Jul 5, 2015 · 0 comments

Comments

@jens-mueller
Copy link

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…’.

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.

@jens-mueller jens-mueller changed the title Issues during using this modle Issues during using this DSCResource Jul 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant