1 of 1 people found this helpful
In theory ... "sort of".
Managed Scripts can call things - batch-files, AutoIT and so on - but they can't really be programmed to do anything themselves.
In theory you could code up a VB-script that generates the relevant form you want, and then have that be run via managed script (or regular software if you want) ...
I'm not entirely sure what exactly you're after by the term "custom data form" (I'm cautious as we have our own CDF's and I doubt you mean one of those?).
But in theory there's nothing speaking against you scripting your own batch/VB-script or whatever that in turn generates a file from a template.
- Paul Hoffmann
LANDesk EMEA Technical Lead
I actually was referring to the LANDesk custom data forms. Is there a way that the LANDesk Management Console can be set to also set off a trigger to send a CDF to the target machine either at the beginning or the end of the job.
My intention is for this question revolves around a legal backup process that we use. I would like to be able to have a form that pops up that records several key pieces of information and either places it in a text file in a location with the backup or at least takes the information from the form to have a record of it in LANDesk.
Ahh - right.
Yes - that's easy enough - that's just a case of using REMCOPY to copy the relevant CDF over. I wouldn't use a script for that, though, to be honest - I'd prefer using a BAT or VB-based distribution package (and just add the CDF as an "additional file" that would then get moved to the right location).
Potentially rather than messing around with CDF's you *COULD* somewhat play around with hacking straight into the LDCUSTOM.DAT
Here's something useful things for you to look through potentially on doing "funky stuff" with custom data (/ forms):
This includes a bit of a longer explanation of how the down & dirty functions, including the relevant files.
You could - potentially - get away without any CDF, and just slapping the relevant information straight into the LDCUSTOM.DAT file really.
Ultimately, the data from custom data forms just gets slapped into an inventory scan as "custom data" at the end.
Give it a try - create a custom data form, deploy it to a client and fill it out. Once you've filled it out, open up the LDCUSTOM.DAT in notepad ... the structure is pretty self-explanatory.
Except potentially for the "Data Entry Date" - that's done in CTIME.
But the rest is pretty simple . So you could - potentially - skip the custom data form all together, and just whack in the data you're after.
- Paul Hoffmann
LANDesk EMEA Technical lead