Client Deploy Tool vs the deprecated java based deployment tool

Usage and Config Platform
1

I was curious what other folks thought about these two tools? Previously, I had always used the java tool. Recently, we updated to 9.5.5 and noticed the latest agent wasn’t in the java tool, and that the client deploy tool had replaced it.

I went to use the newer tool for the first time today and felt like it was a little lacking - there’s no visibility as to what happened without going to the log file to review it, and there doesn’t appear to be logic for what to do if an agent is already installed. upgrade, reinstall, replace masthead? these were things I had done with the java tool before but can’t do with the new tool.

there are a handful of macs in our environment that are not taking the client update fixlet to the latest version, the java tool used to be a method to get an installation deployed in this situation. the new tool just says “hey, the clients already installed, we’re good here” - without an option to upgrade the existing client. I’ll troubleshoot why the update fixlet isn’t working on these devices in the interim, I was just curious if others felt like the replacement tool could use enhancements and if it was worth submitting an RFE for.

2

I’d be interested in hearing any feedback that you or others have about this. I’ve pointed the devs that worked on the new feature at this posting so it would be helpful to hear any pros or cons on the new feature.

1 Like
3

Thanks for the feedback. The idea here is to gradually
integrate the Java tool functionalities into the Bigfix Platform Client
Deploy Tool, with the ultimate goal to improve the user experience in
the overall scenario through an officially supported tool because the
Java tool is officially unsupported.
We will
continue to publish the catalog for the java tool until the transition
is complete so the updated catalog will be published as soon as
possible.

1 Like
4

thanks - sounds good, it’ll be nice to have the option to fall back to the old method until the newer one is developed further.

I will say as a large pro, I look forward to using the deployment method from the console in this manner. sharing the configuration setup for the java tool was clunky at best - keeping it centralized to within BigFix itself is much preferred.