Skip to content

Conversation

@Mindless999
Copy link

  • Added feature to check if module is installed and otherwise automatically install it if agreed by the user
  • Added feature to check if running as Administrator, because of connection to the SQL server
  • Fixed not able to connect using newer versions of invoke-sqlcmd requiring encrypted connection by default

Invoke-Sqlcmd by default now requires mandatory Encryption. On local WSUS databases by default this is still unencrypted. Allowing for the Encryption to be optional
Checking if SqlServer powershell module is installed, and asks to be installed if not. Stops script if declined
Checking if running as Administrator due to required Administrator privileges when connecting to the database
@Givrix
Copy link

Givrix commented Jul 10, 2023

This script is nice but crippled without editing the Invoke-sqlcmd encryption.
Sad this request is not pulled !

@tunisiano187
Copy link

This should really be merged, as these 3 corrections are improving and required for some people, like me ;-)

@vseven
Copy link

vseven commented Apr 12, 2024

Just wanted to comment since the author hasn't merged these requests. The first one is the main one and it's easy enough to manually edit the script and add the " -Encrypt Optional" to the two lines. The second two items are nice to have but easy to get around. I agree they should be merged but if you are having this issue you can fix it yourself for now.

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

Successfully merging this pull request may close these issues.

4 participants