Test-ADServiceAccount is accessible with the help of addsadministration module. To install addsadministration on your system please refer to this link.


Tests a managed service account from a computer.


The Test-ADServiceAccount cmdlet tests a managed service account (MSA) from a local computer.

The Identity parameter specifies the Active Directory MSA account to test. You can identify a MSA by its distinguished name (DN), GUID, security identifier (SID), or Security Accounts Manager (SAM) account name. You can also set the parameter to a MSA object variable, such as $ or pass a MSA object through the pipeline to the Identity parameter. For example, you can use the Get-ADServiceAccount to get a MSA object and then pass that object through the pipeline to the Test-ADServiceAccount cmdlet.


         Specifies the authentication method to use. Possible values for this parameter include:

    Required?                    false
    Position?                    named
    Default value                Microsoft.ActiveDirectory.Management.AuthType.Negotiate
    Accept pipeline input?       false
    Accept wildcard characters?  false

-Identity <ADServiceAccount>
    Specifies an Active Directory managed service account object by providing one of the following property values. The identifier in parentheses is the LDAP display name for the attribute.

    Required?                    true
    Position?                    1
    Default value                
    Accept pipeline input?       True (ByValue)
    Accept wildcard characters?  false


Test-ADServiceAccount [-AuthType <ADAuthType>] [-Identity] <ADServiceAccount> [<CommonParameters>]

————————– EXAMPLE 1 ————————–
C:\PS>Test-ADServiceAccount -Identity MSA1
Tests that the specified service account (“MSA1”) is ready for use (it is able be authenticated and access the domain using its currently configured credentials) from the local computer.

————————– EXAMPLE 2 ————————–
C:\PS>Test-ADServiceAccount -Identity MSA1
WARNING: Test failed for Managed Service Account MSA. If standalone Managed Service Account, the account is linked to another computer object in the Active Directory. If group Managed Service Account, either this computer does not have permission to use the group MSA or this computer does not support all the Kerberos encryption types required for the gMSA. See the MSA operational log for more information.
Test results returned if MsaInfoCannotInstall

————————– EXAMPLE 3 ————————–
C:\PS>Test-ADServiceAccount -Identity MSA1
WARNING: The Managed Service Account MSA is not linked with any computer object in the directory.
Test returns MsaInfoCanInstall

You can check the Version, CommandType and Source of this cmdlet by giving below command.

Get-Command Test-ADServiceAccount

Get-Command Test-ADServiceAccount powershell script command cmdlet

To know more PowerShell cmdlets(Commands) on addsadministration (Active Directory) click here

Click on this Link for an Single place where you get all the PowerShell cmdlet sorted based on the modules.

You can also refer other blogs on PowerShell at link

You can also refer other blogs on Microsoft at link

And also if you required any technology you want to learn, let us know below we will publish them in our site http://tossolution.com/

Like our page in Facebook and follow us for New technical information.

References are taken from Microsoft

Leave a Reply

Your email address will not be published. Required fields are marked *