There is no way to pre-determine how long a job may take to execute. As there a number of factors (job targets, job content, target server performance, job parallelism, etc).
While testing the patches for deployments, this can help to perhaps develop some general baseline timing which could be used to extrapolate runtime of the job against other targets.
In the task in progress bar. It is showing random values. Sometime, 2/6 in progress and after few minutes. It displays 10/20 in progress.
these are not times so even if you understood what they meant they wouldn't be very useful right ?
Users complaining that there is no way we can see the Installation on Progress.
Item-wise status for a Windows BLPackage Deploy Job - Documentation for BMC Server Automation 8.9 - BMC Documentation you should be able to use the 'item details' while the job is running. and why do they need to see this ? will they take some action based on what they find ? and they are going to do this on hundreds of servers ?
and suggest the stake holders
1) Time taken to patch the Target servers.
this depends on a lot: network between the appserver and target/repeaters, number of patches, impact on the target of installing the patch, reboot times, etc. as newton said you can get an estimate by patching a few test systems that need the same patches.
2) How many Patches are installed from the total missing Patches on the Target server.
why do you want to track this real time ?
Keeping in view of tight Change schedule in our environment.
bsa does have the concept of maintenance windows and the ability to stop a deploy job if the window is crossed. it would complete the current patch, then not deploy any other patches in the blpackage if the window is crossed.
what is the real problem you are trying to solve here? the user wants to make sure the patch deploy process doesn't extend beyond a maintenance window ?
Thanks Bill/ Newton for the inputs. I understand it's a limitation we can't view the real time tracking of the installed vs missing patching in the progress bar. The reason I asked these query, as it has Financial impact in case patch deployment process extended beyond maintenance window.
The reason I asked these query, as it has Financial impact in case patch deployment process extended beyond maintenance window.
this is what the maintenance/exclusion windows are for: Walkthrough: Defining a fixed time period for running deploy jobs or patching a server - Documentation for BMC Server Au…
so instead of having people sit around trying to watch 100s of servers while you patch them, wondering if they will cross the window or not, you can prevent that from happening...
?in theory but patching jobs are going to be different each time. different payload sizes, different install times.