I tried this many times and never got anywhere with it so we just kept using the install from CD for Windows. Never got around to opening a case since we had always done it through the script anyway.

If you do get an answer please let us know.

As I'm doing a fresh install across our estate I can go either the A02(.74) route but then i'd need to upgrade the servers straight away to the UB5 versions(.100), talking about 800 Windows and 1000 Unix servers whereas the native installs appear to be rev 189 so that would potentially avoid 1800 * 2 upgrades.

I'll get a case raised tomorrow if theres no answer in here.

Hmmm... we'll have to give this a try again.

One other gotcha to watch out for is if you have perl already installed on the server you are performing the agent install on.
We have Symantec foundation suite which has a perl install with it and this sets the environment variable Perl5LIB to the location of the Symantec perl install.
Ecc silent install can't cope with this and whilst it installs the agent, it doesn't update the ini files with the correct values so you have to manually revisit the server.
We tried setting the perl5lib to be blank in the cmd prompt then do the install but as it's an msi installer it takes the default environment variables when it runs.

Shouldn't be a problem in our environment. I believe this is the only thing that uses perl on the Windows hosts. But I'll definitely keep it in mind if we are still having problems.

Thanks for the update.