Can KACE somehow inspect the Properties of an application shortcut (.lnk)?
Our company is gearing up a project where we need to replace shortcuts in users' start menus, desktops, etc. with new versions of the shortcuts that point to different locations.
Unfortunately, using a custom inventory rule that tries to find the shortcuts in a series of locations isn't really viable because of the sheer number of shortcuts, as well as the way the users have them scattered and even renamed.
Is there a way for KACE to inspect the Properties sheet of a shortcut to find the Target of the shortcut? Those Targets are fairly unique and point to only a couple of locations on a couple of servers in our Enterprise.
Is there possibly another way entirely to use KACE to find and perhaps replace these shortcuts?
Community Chosen Answer
Are you replacing the shortcut, or just the location that it points to? For the former:
It would be more difficult if it's on the user's desktop as the agent doesn't typically have access to it, but if you put it in All Users or Public, you could create a dummy software item to use a custom inventory rule to see if it's there.
If so, something like this might work as a custom inventory rule to get the string: ShellCommandTextReturn(type location-to\shortcut.lnk|find "\"|findstr/b "[a-z]:[\\]")
To target the ones that need to be replaced, create a smart label that only targets the old link and have your script/managed install deploy to those machines.
If it has to be on the user's desktop, you could use a script that runs as logged in user and have it deploy the shortcut.
In my experience, the easiest way to deploy a shortcut is to zip it up and use a script to unzip it into location in All Users or Public. You could add a step to delete the old one.
If you need to change the location that the link points to, perhaps you can use a kscript to call a vb script like this: http://stackoverflow.com/questions/416957/change-a-shortcuts-target-from-command-prompt