No DEM can't provide this at all, you need something like
which does exactly what your asking for. In general all DEM does is zip things up when you logoff and unzips them when you logon, and for general settings unzips them everytime you login. What you can do with dem is package your scripts and shortcuts so they are deployed on user login so you don't need to deploy them everywhere.You would first package the scripts
making sure they are in before the profile is imported
to deploy your shortcuts.
Thx for the answer!
If I understand you correctly. You need to distribute the shortcut and script and make a shortcut to the script. We have 500+ shortcuts, so that will be very complicated. Isn't it easier to use e.g. a Pre-Import task by default for every application? The Pre-Import task runs a script from the network. I only need to figure out how I can know which application is linked to the Pre-Import task. Can I get an id or process name of the application in the script from the pre imort task?
DEMdev or someone else might have something I can think of but It doesn't work that way. The pre import
is for application archives which is for user settings not shortcuts, you could do something here, but there isn't any feedback so you would be doing the same thing. So you still need have the shortcut and the script there somehow, or have intelligent enough scripts to find the id and set it up correctly.Thats still outside of the products capabilities, again remember outside of a few exceptions all DEM does is export an import your settings, the only intelligence it has is what's available in condition sets and directflex
Take a look at this,
this shows you how to make your own config file and you look at the token available its only file path or registry settings, nothing that can see application ids or something similar.The only thing you can do is if a file exists then run this script.
Although I think DEM does a little bit more than "zip things up when you logoff and unzips them when you logon" , sjesse is correct in his assessment that DEM does not provide any functionality around application tracking.
I'd suggest leveraging standard Windows process auditing:
and querying the Security event log for event ID 4688.
"zip things up when you logoff and unzips them when you logon" just in terms that cars go fast
We found a solution, maybe someone in the future can use this solution.
We can make a config file and use a pre-import task with a script and a parameter (e.g. application or processname). This script writes the .exe, PC, user, time, etc in a database. So we know which .exe was started. We have a tool where we register all our application information, and in this registration tool, we are going to register all .exe files of the application. After this, we map in our database the .exe files with the application, so we know which applications aren't started for the past x time. And we can remove these applications.
But I think we are going to use the solution of DEMdev, read the log of Windows (event 4688), so DEM will be clean and fast. And write all these event information to our database. And use our application registration tool (same as above) to map the application with the process.