Windows proxy deployment

For detailed discovery of the Windows part of the target environment, BMC Atrium Discovery uses a Windows proxy, a discovery proxy that can be installed on any suitable Windows computer in the target environment.

There are three Windows proxy types available, depending on whether credential, workgroup, or active directory security is used. The preferred approach is to use the active directory proxy, installed as a service that is set to run as the discovery user. In this manner, a Windows administrator can set the user name and password, and it never has to be known or entered by a BMC Atrium Discovery administrator. In the case of the credential Windows proxy, user names and passwords for discovery are entered directly into the appliance UI.

The Windows proxy can be a physical or virtual server, and it can use an existing infrastructure server.

The following table provides information on compatibility between Windows proxy types and versions, and the operating systems that the Windows proxy runs on for BMC Atrium Discovery version 8.3.

Windows Proxy Type

Earliest Windows Proxy Version Supported

Windows Proxy Available for Supported Operating System

Credential Windows proxy

7.3
See getServices note below this table.

Windows 2003 SP2 (x86 and x86_64)
Windows 2008 - Service Pack 2 (x86 and x86_64)
Windows 2008 R2

Active Directory Windows proxy

7.3
See getServices note below this table.

Windows 2003 SP2 (x86 and x86_64)
Windows 2008 - Service Pack 2 (x86 and x86_64)
Windows 2008 R2

getServices

The getServices discovery method was introduced with BMC Atrium Discovery version 8.1. Windows proxies before version 8.1 do not support this method although are supported in all other respects.

getFileSystems

The getFileSystems discovery method was introduced with BMC Atrium Discovery version 8.2. Windows proxies before version 8.2 do not support this method although are supported in all other respects.

Workgroup Windows proxy deprecated

The Workgroup Windows proxy has not been supplied since before BMC Atrium Discovery version 8.2. All of its functionality has been moved into the Active Directory Windows proxy.

Windows Proxy type

Earliest Windows Proxy Version Supported

Windows Proxy Available for Supported Operating System

Workgroup Windows proxy
Not available with version
8.3.

7.3
See getServices note above this table.

Windows Server 2008 (x86 - 32bit)
Windows XP - Service Pack 2 (x86 - 32bit)
Windows 2003 - Service Pack 2 (x86 - 32bit)
Refers to 8.1 version.

Minimum host specification

The following are the minimum recommended specifications for the Windows proxy host:

Component

Specification

Operating System

As stated in tables above

CPU

2GHz Intel Pentium® 4 CPU 512k Cache (or equivalent from other manufacturer)

Memory

2GB

Hard disk

60GB

To avoid any impact during resource-intensive periods of discovery, it is strongly recommended not to install the Windows proxy on any host supporting other business services. This is true even if the minimum Windows proxy specification is exceeded, since the Windows proxy will attempt to use what resources are available, in order to optimize scan throughput.

Windows discovery communications

You should also consider the ports that will need to be opened in any firewall between the appliance and the proxy or proxies, and the proxies and target hosts.

Windows discovery metadata

Discovery metadata covers Windows as well as UNIX. This provides information about why sessions failed to be established and why scripts failed to run, including information about what credential or Windows proxy was used.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. John Proudlove

    Not sure how to edit the "Windows proxy compatibility matrix" (it's not listed as an attachment to the page), but the three references in table cells to getServices should also refer to getFileSystems (cf the information boxes between the two tables).

    Feb 20, 2012 03:10