Novell Cool Solutions: Trench
By Nicolai Jensen
Digg This -
Posted: 23 Feb 2000
This program might be able to associate applications with Users, Groups and/or Containers relative to the applications context.
When I say 'might' it is because Novell has not (at this time, to my knowledge) released an API for associating NAL objects, so I had to figure stuff out. I've tested the program with NAL 2.01 and the NAL that comes with ZENworks, and it seems to funtion. But I cannot be sure that this always will be the case, so use the program with care, and at your own risk. I will not be held responsible for any damage or harm it may cause in any way.
The motivation for writing this program is that I'm part of a team which manages fairly large networks, and the process of associating NAL objects in a lot of containers can take considerable time in our setup (WAN lines, NAL containers lying in every container etc., etc.) and every time something was changed, we had to fix the batch files as well, whoa nightmare.
A short description of the different buttons and listboxes and stuff follows here:
- Left Side of the window contains two Listboxes, which together form a tree navigator. Pretty straightforward.
- Bottom of the window contains a result box, where results of the operations will be listed.
- Right side of the window:
- App Name box: The name of the application you wish to associate, use only the applications typeless common name, eg 'APP_WAPPASS' not 'CN=APP_WAPPASS' or 'APP_WAPPASS.ENG.NYC.CORP.ACME'
- Relative Context: The context relative to the application, in which you want to associate objects. Note that this only works upwards or at the same level (leave blank). I might change this in the future so that WAppAss can traverse the tree in both diretions, but I have no real use for that myself.
- Object name mask: Wildcard name of object you want to associate with eg '*' for all or USR* for all objects beginning with beginning with 'USR' Note: If left blank and relative context is '.' (dot) and object type is 'Organisational Unit' then the container of the app will be the associee. If two dots, then the parent will be associee.
- Object Type: Type of object to associate with.
- Force run, app launcher etc. Application flags, you should know what they mean, or you are forbidden to use this application at all.
- Simulate only, when checked you can see which objects will be associated with the apps. A number appears after the associee name, the numbers should be interpreted like this.
These values are OR'ed together to form a number (eg 5 means StartMenu AND App Launcher).
- Start Button, when pressed, the association or simulation starts. There is no way of stopping it before it has finished (short of termination the application with ctrl-alt-del, or booting the computer). I might change that sometime.
If you use this program, remember it is a quick hack, and I cannot guarantee it is bugfree, or even works.
The program is e-mail-ware, if you use it, write me. I might even be open for suggestions, if they are not too silly.
Tools used for developing this:
- Delphi 5
- NWLib by devont software (http://www.devont.com)
- Novell's SDK.
- Novell delphi example files, and the exellent delphi_u unit.
- Novell Icons taken from NWICONS.EXE and NWAdmin.
I can be contacted at firstname.lastname@example.org
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com