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:
- Upgrade to 8.8 - sorry had to list this
- Rather than scripting etc, you could just copy and paste the distribution package, and give it a new name. This will create a new IDN and will allow you to push again.
- Create an optional policy for the users to reinstall. May or may not be an option depending on your requirements.
- The other stuff is scripting. You could create a small autoitscript, batch file using REG, or vbscript to whack the key. The prereq would be the uninstall and the main package would be the key whacker.
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?
1 of 1 people found this helpful
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:
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.
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.