Validation of Windows user

This topic provides instructions about how to validate a Windows local and domain users. If the validations for the user fail, see Troubleshooting. 

Validation of Windows user for BMC PATROL for Microsoft SQL Server version 9.6.12 and later. Click here to expand.

A Windows user can either be a domain or local user. Windows user must be in FQDN format.

  • For domain user: domain_name\user_name
  • For local user: local_machine_name\user_name

Note

BMC recommends to use domain user for a cluster environment. If a user is defined on all possible nodes of the cluster environment, a local user can serve as a Windows user.

Important

If the MS SQL Server login field is left blank, then the Windows user will serve to connect the MS SQL Server. In this case Windows user must pass all validation steps as described in Validation for integrated user section.

Validation

  1. Open command prompt from <PATROL_HOME>\mssql\x64 directory.
  2. Type the following command:
    SQLCollector.exe -diag check_host_conn 
  3. Enter the hostname or IP of the host you want to check

    image2016-9-8 10:21:51.png
    1. Remote host
      1. Enter Domain\User to use for host connectivity test

      2. Enter password
        Success scenario output

        image2016-9-8 10:29:18.png

        Message displayed

        Scenario

        Pinging host sqlhost...success

        Indicates a successful ping

        Credentials are required for remote host sqlhost

        Indicates that the host is a remote host and PATROL will use WMI technology for connection

        Connecting to host... success

        Indicates the connection has been established successfully

        List of installed Microsoft SQL Server instances:

        Lists all available Microsoft SQL server instances on a host discovered by PATROL after searching the host’s registry

        Failed scenario output

        Successful ping to remote host, but connection failed to the remote host using the provided credentials.

        image2016-9-8 10:43:57.png 

    2. Local host
      The logged in user is used for the testing.
      Success scenario output

      image2016-9-8 10:47:17.png

      Message displayed

      Scenario

      Pinging host vw-aus-bpm-qa11... success

      Indicates a successful ping

      Using user VW-AUS-BPM-QA11\Administrator for localhost

      Indicates that the host is a local host and PATROL will use Windows Login methods to login to the local machine

      Connecting to host vw-aus-bpm-qa11... success

      Indicates the connection has been established successfully

      List of installed Microsoft SQL Server instances:

      Lists all available Microsoft SQL server instances on a host discovered by PATROL after searching the host’s registry

      Failed scenario output
      Successful ping to local host, connection has been established successfully but no Microsoft SQL server instances discovered on host

      image2016-9-8 10:52:43.png


  4. To execute another query enter ‘y’ , enter ‘n’ to continue.
  5. To run another test type ‘y’, type ‘n’ to quit.

Note

To use another user for localhost test, run SQLCollector.exe using the RUNAS command:

Runas /user:<domain_name>\<user_name> "SQLCollector.exe -diag check_host_conn"

image2016-9-8 11:0:29.png

Validation of Windows user for BMC PATROL for Microsoft SQL Server version 9.6.11 and before. Click here to expand.

A Windows user can either be a domain or local user. Windows user must be in FQDN format.

  • For domain user: domain_name\user_name
  • For local user: local_machine_name\user_name

Note

BMC recommends to use domain user for a cluster environment.

If a user is defined on all possible nodes of the cluster environment, a local user can serve as a Windows user.

Important

If the MS SQL Server login field is left blank, then the Windows user will serve to connect the MS SQL Server. In this case Windows user must pass all validation steps as described in Validation for integrated user section.

Validation

  1. Open command prompt from <PATROL_HOME>\mssql\x64 directory.
  2. Type the following command:
    SQLCollector.exe -diag check_host_conn

    12.png 
  3. Enter the properties of the host you want to check
  4. The host connection status and available MS SQL Server instances on host are displayed

    1. Success scenario output for remote host:

      13.png
       

      Message displayed

      Scenario

      Ping to host vw-tlv-ngp-dv13... success

      Indicates a successful ping

      Host vw-tlv-ngp-dv13 is remote host

      Indicates that the host is a remote host and PATROL will use WMI technology for connection

      trying to establish WMI connection... success

      Indicates the connection has been established successfully

      List of installed SQL instances:

      Lists all available MS SQL server instances on host discovered by PATROL after searching the host’s registry

      Check host connection success

      Indicates user approval. The tested user can be used as a Windows user on this host

    2. Success scenario output for local host:

      14.png

      Message displayed

      Scenario

      Host 127.0.0.1 is local host

      Indicates that the host is a local host and PATROL will use Windows Login methods to login into the local machine

      trying to logon locally... success

      Indicates that the login is successful

      Note

      All other messages have the same meaning as for the remote host.

    3. Failed scenario output:

      15.png 

      If the validation of a user fails, the user cannot be used as Windows user on tested host till the issue(s) are resolved and user succeeds the validation

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*