right - the agent installer objects don't support upgrading yet.
Thanks for your reply and I would like to know How to upgrade RSCD agent with deploy?
Because in the environment have to many old version agent.
The instructions in the documentation can be followed.
Please state what specific problem you have so that further advice can be provided.
The simple answer is create a BLPackage to deploy the source files to a known location on the managed servers then run the installation part as a post deploy job with agentctl
Some examples of the post command are:
"agentctl.exe -b exec msiexec /i \temp\stage\rscd\rscd.msi /qn /l* \temp\stage\rscd\rscd_install.log /norestart"
"agentctl -b exec/var/tmp/rscd/rscd.sh -silent"
Would be so much better if this was built into BSA, right click on a server or smartgroup and choose upgrade agent(s)
Well, ideally the UAI jobs will handle this in the future…
You shouldn’t need to do the agentctl anymore w/ the msi. And I’ve never had to do it w/ the unix installer.
Bill thanks, I haven't tried the MSI without agentctl I think I just used it based on previous experience of the installshield version
I checked some of our RedHat jobs and they are configured without agentctl as well so was a case of typing reply without checking - although I don't think it matters if you use agentctl just to make sure
Agentctl is not always in the path which can cause problems for the job ☺
thank you for your idea , i will to try on morning and i will show for result.
many thank for any reply...
thank mike jones
i try by step
1. copy asset /tmp/ton/RSCD83-SP2-AIX32.sh and script file on same path.
2. execute full path install_rscd_usr.sh
/usr/bmc/B*/*/NSH/sbin/agentctl -b exec /tmp/ton/RSCD83-SP2-AIX32.sh -silent
echo "* rw, user=root" > /usr/lib/rsc/exports
Is that working ?
As Bill said and I checked he hasn't ever had to use agentctl for Unix before so you could probably just have
"/tmp/ton/RSCD83-SP2-AIX32.sh -silent" on the top line