It appears this is **not possible**.

According to [Andrew Barber's comment on "Get windows user login name from sql server"][1]:

> If they are logged in as a SQL Server user, they are *not* logged in as a Windows user; no Windows credentials are passed at all; so you simply can't get that information directly

[1]: https://stackoverflow.com/q/25629000/#comment40043473_25629000

We are using a SQL Login as a vehicle for issuing permissions, but once authenticated through SQL, we'd still like to know the Active Directory name of the connected user?

We've tried:

```sql
SELECT SUSER_NAME()
SELECT SUSER_SNAME()
SELECT SUSER_SID()
SELECT USER_NAME()
SELECT USER_ID()
SELECT SYSTEM_USER
SELECT SESSION_USER
SELECT ORIGINAL_LOGIN()
```

Is that information still available somewhere?

**Note**: This is different from how to [get windows user login name from sql server][1] since we're using *SQL Login*, not a *Windows Login* to connect to SQL Server


[1]: https://stackoverflow.com/q/25629000/1366033

Get current user while using SQL Authentication

This has been entered as a bug since 2013.   According to the workarounds listed in [Auto-completed parameter values, with spaces, do not have quotes around them][2], you can update the `TabExpansion2` function that Powershell uses for autocompletion.  To do so, just run the following code:


    function TabExpansion2
    {
        [CmdletBinding(DefaultParameterSetName = 'ScriptInputSet')]
        Param(
            [Parameter(ParameterSetName = 'ScriptInputSet', Mandatory = $true, Position = 0)]
            [string] $inputScript,
        
            [Parameter(ParameterSetName = 'ScriptInputSet', Mandatory = $true, Position = 1)]
            [int] $cursorColumn,
    
            [Parameter(ParameterSetName = 'AstInputSet', Mandatory = $true, Position = 0)]
            [System.Management.Automation.Language.Ast] $ast,
    
            [Parameter(ParameterSetName = 'AstInputSet', Mandatory = $true, Position = 1)]
            [System.Management.Automation.Language.Token[]] $tokens,
    
            [Parameter(ParameterSetName = 'AstInputSet', Mandatory = $true, Position = 2)]
            [System.Management.Automation.Language.IScriptPosition] $positionOfCursor,
        
            [Parameter(ParameterSetName = 'ScriptInputSet', Position = 2)]
            [Parameter(ParameterSetName = 'AstInputSet', Position = 3)]
            [Hashtable] $options = $null
        )
    
        End
        {
            if ($psCmdlet.ParameterSetName -eq 'ScriptInputSet')
            {
                $completion = [System.Management.Automation.CommandCompletion]::CompleteInput(
                    $inputScript,
                    $cursorColumn,
                    $options)
            }
            else
            {
                $completion = [System.Management.Automation.CommandCompletion]::CompleteInput(
                    $ast,
                    $tokens,
                    $positionOfCursor,
                    $options)
            }
    
            $count = $completion.CompletionMatches.Count
            for ($i = 0; $i -lt $count; $i++)
            {
                $result = $completion.CompletionMatches[$i]
    
                if ($result.CompletionText -match '\s')
                {
                    $completion.CompletionMatches[$i] = New-Object System.Management.Automation.CompletionResult(
                        "'$($result.CompletionText)'",
                        $result.ListItemText,
                        $result.ResultType,
                        $result.ToolTip
                    )
                }
            }
    
            return $completion
        }
    }

---

It's worth noting that string insertion works properly for native cmdlets like `Get-EventLog -LogName` which will properly encase `'Internet Explorer'`.  Although if you [look at the source][3] for `Get-EventLog`, you'll see that `$LogName` doesn't actually use `ValidateSet` so it's intellisense must be provided through another mechanism.

---

**Other Instances**:

* [ValidateSet and tab completion does not work on strings with spaces][1]

[1]: https://social.technet.microsoft.com/Forums/windowsserver/en-US/91d85311-f1a6-4c21-ad9d-f909c468bea2/
[2]: https://connect.microsoft.com/PowerShell/feedback/details/812233/
[3]: https://stackoverflow.com/a/20484505/1366033

First, I do apologize for posting another question concerning PowerShell and tab completion.  The StackOverflow system identified several excellent questions with answers concerning this very topic, but they all seemed too cumbersome to implement into this simple `New-ADComputer` script.

The params are going into a `Splat` to keep the script readable.  The following code correctly tab completes in the ISE, but must be wrapped in double quotes.

Is there any native method in PowerShell to allow for tab completion of Parameter Sets that include spaces?



    Param(
      [Parameter(Mandatory=$true)]
      [string]$Server,
      [Parameter(Mandatory=$true)]
      [ValidateSet('Env1','Env 2','Env 3')]
      [string]$Environment,
      [Parameter(Mandatory=$true)]
      [ValidateSet('Application','Database','File and Print','Web Server')]
      [string]$Type
    )
    $NewADitems = @{
      Name        = $server
      Path        = "OU=$Type,OU=$Environment,OU=Smaller DN string"
      Location    ='MySite'
      Description = "Test Description"
      ManagedBy   = "Huge Distingushed Name string"
      WhatIf      = $true
    }
    Write-Host @NewADitems



Command used and error received:

    PS C:\Scripts> .\ADComputer-ParamTest.ps1 -Server ThisTest -Environment Env 3 -Type File and Print
    C:\Scripts\ADComputer-ParamTest.ps1 : Cannot validate argument on parameter
    'Environment'. The argument "Env" does not belong to the set "Env1,Env 2,Env3"
    specified by the ValidateSet attribute. Supply an argument that is in the
    set and then try the command again.At line:1 char:58
    + .\ADComputer-ParamTest.ps1 -Server ThisTest -Environment Env 3 -Type File and Pr ...
    +                                                          ~~~

**Edit:** More information.  If you leave off the single/double quotes in my example script for the parameter `Environment`, tab completion will not work for the final parameter `Type`.  Enclosing the 2nd set in quotes will correct this but it's a way to keep watch for this behavior.

PowerShell Param ValidateSet values with Spaces and Tab completion

Echoing mjolinor's comment, but feel free to append with extra info.

Installing the AD tools won't help. `Get-DistributionGroup` is an Exchange cmdlet.

You'll need to either: 

* install the Exchange Management Tools
* or connect to a management session on an Exchange server

The `Get-DistributionGroup` command is supposed to list distribution groups in a domain but I can't get it to run on my server.

After some Googling I found that `Import-Module ActiveDirectory` needs to be run first, but what I get when I run that is:
    
> Import-Module : The specified module 'ActiveDirectory' was not loaded because no valid module file was found in any module directory.

My questions are 

1. How do I install this module into my PowerShell module directory? I thought it was supposed to do this automatically
1. Once I have it installed, do I just run `Import-Module ActiveDirectory` and then I can run `Get-DistributionGroup` to list my dist groups?