Response to your points:
No, in any given backupexec v9 installation we only ever had a license for the basic backupexec, plus extra licenses for Advanced Open File (of dubious value in that version), Exchange Agent, or SQL Server agent.
Maybe I am confusing things, because maybe the situation is confusing, but V9 has a "remote agent" service, even if there is no seperate "remote agent" option installed. This service is the "beremote.exe" process, and "speeds up backup of remote computers". Even though dont want to back up remote computers, nothing works if this service is stopped.
Another problem:
Incidentally, the customer also has an afternoon "go-slow" problem which has been going on for years, but we have never got to the bottom of. Iniitially they had network drive hangup symptoms around 5pm at the local site, while running v9 on the domain server. More recently (around the time v11 demo followed by v12 full version) there was an additional 3pm slowdown which was experienced by remote sites which log into a terminal server.
Somebody else did some investigation and discovered part or all of the problem was due to 100% CPU usage by the BEREMOTE service. This may be a symantec problem, yet microsoft supposedly had a fix for it
(microsoft kb867667). They registered with microsoft to receive the fix in April, but have not received it.
I find it unbelievable that a service offering functionality pertaining to "remote" operations which are not desired, should cause such problems and simultaneously be impossible to disable?
The file selection problem:
As far as the original file selection problem is concerned, we are getting round it for now by copying sqlserver backup files to the domain server, and backing up to tape from there. This is not ideal, since if the single tape drive goes down, backups for both servers go down.
We could maybe try backing up targets on the w2008 server directly from the w2003 server, but we have never tried this. And I'd say in this particular case It is quite likely not to work this way round, since it is not possible for the w2003 server backupexec instance to create a backuptodisk folder on the w2008 server because of authentication problems, so this method may encounter similar problems.
In the meantime, still no call from symantec, who presumably dont want to sell symantec products.