1 of 1 people found this helpful
So is there any way to do this for upgrading rscd agents that may be installed in multiple locations? Or so I just need to create a separate deploy job for each possible previous install directory?
Agentctl should be in the path on the target system.
Or you can read in the install path from c:\windows\rsc\HOME
Hmm i don't see a windows\rsc\home. Its not in the path and i didn't see any environment variable with "RSC" or "rsc" in it.
If you type ‘agentctl’ from the cmd line, does it work?
'agentctl' is not recognized as an internal or external command,
operable program or batch file.
Volume in drive C is CDRIVE
Volume Serial Number is 68F3-8A88
Directory of C:\Windows\rsc
11/23/2010 12:41 PM <DIR> .
11/23/2010 12:41 PM <DIR> ..
11/08/2010 05:20 AM 1,746 certificate.pem
04/29/2009 06:21 PM 291 exports
11/18/2010 09:21 AM 107 license.dat
11/23/2010 12:41 PM 2,255 log4crc.txt
11/08/2010 05:20 AM 496 secure
04/29/2009 06:21 PM 157 securecert
11/08/2010 05:20 AM 1,575 users
11/08/2010 05:20 AM 402 users.local
8 File(s) 7,029 bytes
Hmm. Maybe HOME is only created if nsh or the om is installed.
you could cheat a little here – try something like this:
blpackage that contains the agent, and an external command that builds the install command – dump that into c:\temp (or wherever).
Then in the post-install of the job, run the batch file you created.