Hi All,
I was wondering if any of the LANDesk geniuses out there might have some suggestions on how I can approach this problem.
We deploy our packages using the policy method (linked to a AD group with a LDAP query) and this works very well for us (Post SP5). Our uninstall tasks use the push mechanisim. We have noticed that the registry key on the local client (HKLM\SOFTWARE\Intel\LANDesk\LDWM\AppHealing\Agent\AMClient\APM\PolicyCache\{Package-xxx}) to indicate a successful install is left behind. This prevents us from redeploying the application to the client
Is there anyway that we can create a vbscript that can pass in the package number detailed in the registry (in bold above) and delete it. I'm new to VBScripts and have learnt to manipulate registry keys (Add, Delete, Amend) but don't know how to read LANDesk data. We are hoping to use one VBScript for all our packages. Also, is it possible to pass in LANDesk data into VBScripts?
We are currently on 8.7 SP5.
Many thanks
Craig
LANDesk geniuses...isn't that an Oxymoron?
So this issues was reported to LANdesk and I believe addressed in 8.8 where the package ID was used as the reg key. This will only prevent a PSP or required policy from being installed again. So some ideas:
Sure somebody else will have some other ideas, but these should get the old juices flowing.
I'm thinking along the lines of the last point. I've noticed that LANDesk uses the Package.IDN in the registry key. Is there a clever way of extracting this data from the SQL database and input it into a VBS?
So it may be technically feasible to do this in vbscript or other scripting tools using ADO, I'm not sure it would be worth all the extra work when simply creating a new distribution task by copy and paste is much simpler and supportable. Also, I believe this goes away with 8.8. However, if you want to pursue:
http://www.technowledgebase.com/2007/06/12/vbscript-how-to-create-an-ado-connection-and-run-a-query/
It will be difficult to handle this in a multiple core environment.
Thanks ZMan. I'll have a look into the link you attached. We are still going to run 8.7 for at least another year and then hopefully move to version 9 when it's out. If worst comes to worst, we will have to build a script per application with the value hard coded in to nuke this key.
Thanks again for all your help.
Craig
So another thought would be to use the NAME key from the registry so you don't have to use any DB lookups. So use Autoitscript or other language and search the registry for the NAME (this would be a command line argument so you don't have to write a lot of scripts), once you find the name check the TYPE for 1 (I think that is required), then whack the key.
| ||||||
