Mike: worst case, you can always uninstall the agents with a File Deploy or NSH Script Job.
Mike - are the servers that you are trying to upgrade still managed by a BSA instance ?
If so you could upgrade the agent with BSA, al though you might want to test first what happens if you install the new MSI interactively on a system with the 7.4.1 agent already running, just to make sure that will do an upgrade
Must read post more fully.
Ignore MSI bit, but the same question if the servers are still managed with BSA use that to upgrade the agent to 8.1.2
1 of 1 people found this helpful
Hi Mike Brennan,
Not sure about this specific version, but there used to be a NSHLoction property in bulk installer properties
, it will do a simple agentinfo on the target server to find if RSCD Is running or not and get the install path.
Also, under windows/rsc/home -is another place where it can check
why are you using the bulk installer at all? the normal method to do the agent upgrade would be to use a file deploy job as sean mentions.
I've got a long list of servers. Some don't have an agent at all and some are old versions. So using the bulk installer seemed like a nice easy "capture all" solution.
Thank you all for the suggestions. I did end up using a file deploy method for the upgrades and then the bulk installer for the fresh installs. It took a lot longer than it should and I'm still interested in the answer to why the bulk installer does not work correctly.
Rohit - Thanks for your post. The setting you mentioned does exist but did not fix the problem.