The following table provides information about the compatibility between Windows proxy types and versions, and the operating systems that the Windows proxy runs on for BMC Atrium Discovery version 9.0.
Windows Proxy Type |
Earliest Windows Proxy Version Supported |
Windows Proxy Available for Supported Operating System |
---|---|---|
Credential Windows proxy |
8.1 |
Windows 2003 SP2 (x86 and x86_64) IPv4 discovery only |
Active Directory Windows proxy |
8.1 |
Windows 2003 SP2 (x86 and x86_64) IPv4 discovery only |
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.
The Workgroup Windows proxy has not been supplied since BMC Atrium Discovery version 8.1.x. 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 |
8.1 |
Windows Server 2008 (x86 - 32bit) |
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.
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.
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.