insentia/windows_sql — pull request #4 by StefanSchoof (2014-11-13 11:11:35+00:00)
Title: Fix sqlpath install

The exec command does not need a leading slash. Otherwise I get
```
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: \setup.exe : The term '\setup.exe' is not recognized as the name of a cmdlet,
==> default:
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: function, script file, or operable program. Check the spelling of the name, or
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: if a path was included, verify that the path is correct and try again.
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: At line:1 char:1
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: + \setup.exe /CONFIGURATIONFILE='C:\\configurationfile.ini';
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: + ~~~~~~~~~~
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: + CategoryInfo : ObjectNotFound: (\setup.exe:String) [], CommandN
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: otFoundException
==> default: Notice: /Stage[main]/Windows_sql::Install/Exec[Install SQL]/returns: + FullyQualifiedErrorId : CommandNotFoundException
```