• Loading...
This documentation relates to the latest released version of BMC Atrium Discovery (other versions).

Configuring Windows discovery

Skip to end of metadata
Go to start of metadata
Space Search

Searching ADDM 8.3

Table of Contents

Windows discovery requires a Windows proxy host because the methods that are used to access Windows hosts are only available from Windows systems. Windows discovery is handled in one of the following ways:

  • Credential Windows proxy: A BMC Atrium Discovery application that runs on a customer-provided Windows host and uses credentials supplied by the BMC Atrium Discovery appliance to perform Windows discovery.
  • Active Directory Windows proxy: A BMC Atrium Discovery application that runs on a customer-provided Windows host that is part of an Active Directory domain. The user that the Windows proxy service runs as is configured when it is installed. Where that user is configured on hosts in the domain, the Windows proxy can log in and run discovery commands. The Active Directory Windows proxy does not use any credentials entered using the BMC Atrium Discovery user interface.
    Starting with BMC Atrium Discovery, version 8.2, the Workgroup Windows proxy is no longer supplied with the appliance. All of its functionality has been moved into the Active Directory Windows proxy.

Windows proxies are grouped into Windows proxy pools. This enables the appliance to distribute discovery requests in order to balance the load of the proxies. Each proxy pool can only hold one type of Windows proxy (for example, a credential proxy pool can hold only credential proxies).

All proxies in a pool must have identical access to Windows hosts, as only one proxy per pool is tested for access. Unless proxy pools are restricted by IP address, a typical configuration consists of one proxy pool per Active Directory domain containing one or more Active Directory proxies, and a proxy pool containing one or more Credential proxies.

The Windows proxy pools are displayed in the order (from top to bottom) in which you have added them to the appliance. You can change their order. For discovery tasks, the proxies in a Windows proxy pool are selected depending on their loading.

Before you can use a Windows proxy to discover your Windows IT infrastructure, you must perform the following tasks:

  1. Install and run the Windows proxy software.
    For more information, see Installing Windows proxies.
  2. Add Windows proxy pools to the appliance.
    For more information, see Adding Windows proxies and proxy pools.
  3. Add the Windows proxies to the proxy pools.
    For more information, see Adding Windows proxies and proxy pools.
Potential user lock out
By default, AD accounts have a limited number of login attempts, for example three attempts in fifteen minutes. Access Denied errors from WMI, DCOM, and local commands such as systeminfo are counted as unsuccessful login attempts. Where target hosts are incorrectly configured, this limit can be exceeded and the account locked out.

To avoid this, configure the Discovery account to accept unlimited login attempts.

Windows discovery utilities no longer shipped in BMC Atrium Discovery

From version 8.1 the following utilities are no longer shipped with BMC Atrium Discovery. You can download them freely and install them where required.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Dec 15, 2011

    From architecture perspective, can you please add some guidelines for Windows proxy. For eg. One windows proxy is good to discover upto 500 windows machines, if you go above 500 you need to add another proxy. Basically, how should we decide on what number of windows proxies do we need to scan 3000 windows hosts.

    (Given that each proxy has minimum host specification as follows:

    Operating System :- Windows server 2008
    CPU:- 2GHz Intel Pentium® 4 CPU 512k Cache
    Memory:- 2GB
    Hard disk:- 60GB )

    1. Dec 19, 2011

      Hi Shilpa,

      Unfortunately it's not as simple as that. The number of target hosts that a proxy can discover depends on a lot of variables, including size of target, amount of information returned, network speed, load on the target, and so on. Charles has been formulating a best practice for deploying proxies, and one of his suggestions is deploy two proxies where you would have previously have deployed one, and put them both in a proxy pool. This enables you to take advantage of the load balancing capabilities of proxy pools that were introduced in BMC Atrium Discovery 8.3. This requires you to select the "Overload Notification flag (Managing Windows proxies) on the proxies in the pool.

      We're going to take another look at the proxy and proxy pool documentation to take this new information into account.

      I hope that helps,

      Duncan.

      1. Dec 19, 2011

        Thanks Duncan.