Is it a non-silent install.
One of the reasons could be that the user on the workstation is not giving any input to the installer and thus the installer does not provide a return code of 0, hence post-install (aborted).
it is a silent MSI and the installation is also successfull when you check the logs.
only viewing the tuner administrator your will find the aborted status.
check the MSI logs for the return code and map it to installed in App Packager.
What version of BBCA are you using? If you were to watch the properties.txt and application.txt file of the channel workspace while the channel was 'running', the .txt files do not say 'running'. They are marked as 'Install - Aborted'. My assumption is that the channel is marked this way in the event of a catastrophic termination of the channel or tuner. The channel manager would come back and report 'Aborted'. Are you stating the Tuner Admin is reporting 'Aborted' while the channel is actually 'Running' on the endpoint? Verify, what the channel is doing, via timestamps, at the moment that you are witnessing the 'Aborted' status. Is the channel waiting for input? You mentioned it was silent, but there may be something else happening. I have also come to the practice of NOT being connected to a remote tuner while installing an application. One thing that usually plagues me when I do that, is VERY SLOW downloads of the channel.
I would find the error code and use the tab that allow you put the errors so, it ingore them. Do you where that is in applicaiton pacakger? The error code would be in the WIndows installer logs. They are usually located on c:\windows\temp or %temp% on the run prompt.