Currently, I am working with CA ITCM version 14 and I did a test with a software package.
The package was implemented on the server, but it was not installed. We only saw the installation start message. then the software package was deleted and also the Job.
but the message persists. how do we remove the task for the message that is no longer displayed on the server?
This message is displayed by the OS (not ITCM) and occurs because your software package is trying to display a message on the screen. Because of the way Windows allocates user sessions, it cannot directly interface with the user’s screen because the package installation is running in a different session. This is a normal situation with current Windows releases. The dialog will not go away until you either close it or view the message.
You can prevent this message by ensuring your installation procedure runs in silent mode. This is highly recommended. You should ensure that all dialogs are avoided, and all text output is redirected to $rf if possible, which will be uploaded to the job output tab so you can see the result of your job.
It is likely, based on your description of events, that the installation displayed some error message and exited without performing the installation. However it looks like it returned an exit code 0, which indicates to software delivery that the package was successful.
If you need help creating packages you could either open a support case, or ask more questions on the communities. Also there are a lot of resources already published on the communities which may help. Please look through what is available so you can learn how to create a package successfully.
Steve McCormick, ITIL
Principal Services Consultant
it is clear to me, what they tell me.
but as such the package that was used at that time, it was already removed from the ITCM console, just like the job.
Is there any way to eliminate the task or service that displays the message in the operating system?
No, the only way to prevent this dialog is to create your package such that it does not output to the screen. This should be the normal for software delivery packages anyway, they should run silent, with no dialogs or questions for the user, and write their output to a log file, preferably using the $rf variable as the output file as this file will get uploaded to the job status tab of the job properties.
Tacking onto Steve's reply here. Way back in Windows Vista, Microsoft added Session-0 isolation. Basically system services (background processes) can no longer interact directly with logged on users, as it used to be in Windows XP. Microsoft introduced a concept known as session-0 isolation, so services could no longer be "interactive".
The ITCM agent runs as the SYSTEM account, in side of session 0. As Steve mentions, your setup package must display a message to the user or require some input, hence Microsoft detects this with interactive service detection and displays a message to the user logged into the console.
Please share more details about what you are packaging. Most software will have a silent switch that will suppress all user interaction, and perhaps you are required to specify some installation options using other switches. It's really dependent on the software title.