This is true - a primitive agent should help to solve your problem.
The downloads section (http://www.bladelogic.com/support/downloads.jsp) presently has all of the agents back to 5.2.1.
Try installing the 5.3.2 agent, though I believe 6.1 should work.
I've tried 6.1 and that was giving me the same problems.
The version stipluated in the installation documentation which will work (but has less fucntionality) is version 5.1.2 but can't find this on the website....
The version you've tried is 6.1.1.
I don't know if this makes a difference, but you could try 6.1.
To work without AD client, 6.1 will not work either, you have to backrev to either 5.3.x or 5.2.x, not sure which.
The last version we support for NT 4 is 6.1.2, no new agents will be coming out that support NT 4.
To work without AD, you'll actually need to backtrack to at least the 5.1 agent. The 5.2 agent was the first version where we introduced the AD warning as part of the installer.
The following is from the 5.2 release notes.
IR9464: To use 5.2 on NT 4.0 systems, you must install the AD Client Extension (http://support.microsoft.com/default.aspx?scid=kb;en-us;288358). If you do not want to install the AD Client, you can use the 5.1.2 agent in the 5.2 environment with the following known limitations:
1) Processing snapshots/audits on target agents ("at edge") instead of on the app server is not supported
2) Registry ACLs are not supported
The 6.1.X agent is the last version of the agent that we support if you actually install the AD client extension on NT.
Note: The warnings listed above about using a 5.1 agent relate to using it in a 5.2 environment. Using a 5.1 agent in a 6.1/6.2 environment will have even less available functionality. At the very least, I know that deploys will not work.
hi, thanks for the replies.
This is the situation so far. Our client has many NT4 servers. They are only going to allow the installation of the BL agent and nothing else and they don't use the AD client on NT4. Therefore I will need to roleout the older version of the client.
I've downloaded all versions of the agent available from this site and none of them function on NT4 without popping up the message (previously posted). I've since discovered that Internet explorer conflicts with the agent and generated the error displayed on the screen.
What functionality we loose by using a 6.1.1 (last version supporting NT?) agent and a 6.3.2 appserver ?
Message was edited by: