|Author||Chrissy LeMaire (@cl), netnerds.net|
|Availability||Windows, Linux, macOS|
Want to see the source code for this command? Check out Enable-DbaForceNetworkEncryption on GitHub.
Want to see the Bill Of Health for this command? Check out Enable-DbaForceNetworkEncryption.
Enables Force Encryption for a SQL Server instance.
Enables Force Encryption for a SQL Server instance. Note that this requires access to the Windows Server, not the SQL instance itself.
This setting is found in Configuration Manager.
Enable-DbaForceNetworkEncryption [[-SqlInstance] <DbaInstanceParameter>] [[-Credential] <PSCredential>] [-EnableException] [-WhatIf] [-Confirm] [<CommonParameters>]
PS C:\> Enable-DbaForceNetworkEncryption
Enables Force Encryption on the default (MSSQLSERVER) instance on localhost. Requires (and checks for) RunAs admin.
PS C:\> Enable-DbaForceNetworkEncryption -SqlInstance sql01\SQL2008R2SP2
Enables Force Network Encryption for the SQL2008R2SP2 on sql01. Uses Windows Credentials to both connect and modify the registry.
PS C:\> Enable-DbaForceNetworkEncryption -SqlInstance sql01\SQL2008R2SP2 -WhatIf
Shows what would happen if the command were executed.
The target SQL Server instance or instances.
Allows you to login to the computer (not SQL Server instance) using alternative Windows credentials
By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.
If this switch is enabled, no actions are performed but informational messages will be displayed that explain what would happen if the command were to run.
If this switch is enabled, you will be prompted for confirmation before executing any operations that change state.