Setting the Authentication Service Using VBScript

When accessing a Windows Management Instrumentation (WMI) server with a script, you can choose between NT LAN Manager (NTLM) or Kerberos authentication protocols. Specifying Kerberos is not required except when using delegation. For more information, see Connecting to a 3rd Computer-Delegation.

Because operating system versions differ in which authentication service they use, it is recommended that you do not specify a value for the authority field when connecting to a remote system. Instead, allow the operating system and distributed version of Component Object Model (DCOM) to select NTLM or Kerberos. If an authentication service is specified, the syntax requires the server principal name, which is the name of the target computer rather than the domain controller.

You can use the authority parameter only with connections to remote WMI servers. The connection attempt fails if you attempt to set authorization levels as part of a moniker or with a call to SWbemLocator.ConnectServer for a local connection.

Perform the following procedure to specify the authentication service that you want to use in the strAuthority parameter of the SWbemLocator.ConnectServer method or the moniker string connection.

Aa393616.wedge(en-us,VS.85).gifTo specify NTLM or Kerberos authentication with the Scripting API for WMI

  1. If the strAuthority parameter begins with the string "kerberos:", WMI assumes the string refers to a Kerberos principal name and Kerberos authentication is used. If the strAuthority parameter begins with the string "ntlmdomain:", WMI uses NTLM authentication instead.
  2. Alternately, You can use the authority part of a moniker to specify the type of authentication used to connect to WMI. To use Kerberos authentication when using a moniker include the string, "authority=kerberos:" followed by the principal name. To use NTLM authentication, include the string, "authority=ntlmdomain:" followed by the NTLM domain name.

    The following example shows you a moniker that requests Kerberos authentication using the principal "mydomain\server".

    winmgmts:{impersonationLevel=delegate, _
            authority=kerberos:mydomain\server} _

    In contrast, the following example shows you a moniker that requests NTLM authentication using the domain "mydomain".

    winmgmts:{impersonationLevel=impersonate, _
            authority=ntlmdomain:mydomain} _