Novell Cool Solutions

Q: How does NAL Refresh work?



By:

January 21, 2008 8:46 am

Reads:18,433

Comments:5

Score:4

Print/PDF

Can any one tell me, How NAL Refresh works.
When I click refresh I’d like to know how the Autorun.exe identifies my new launchers and other configurations and works accordingly.

Please anyone help me to know the basic functionality of NAL Refresh.

1 vote, average: 4.00 out of 51 vote, average: 4.00 out of 51 vote, average: 4.00 out of 51 vote, average: 4.00 out of 51 vote, average: 4.00 out of 5 (1 votes, average: 4.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

5

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

5 Comments

  1. By:bkeadle

    You know the Application Explorer icon in your system tray, and when you right click on it and select “Refresh”? That the same thing that the AUTORUN.EXE does. That refresh process is scanning the associated zenworks policies and applications for “new” policy and/or associations. That’s the “basic functionality”. Is that too basic?

    • By:JanaGokul

      Many thanks to you for the reply.

      Can you please explain it a bit more.
      For an example if a new application is added to a user and if NAL Refreshes, how it identifies whether a new objects is included for that user and proceed?
      Where will it find those information ?

      I am very much interested in knowing how this happens ?

      Thanks in Advance!

  2. By:kjhurni

    The NAL Refresh, does not refresh policies.

    It only looks for application objects/changes.

    However, it behaves differently depending upon if the app is user associated or workstation associated. (I believe).

    So, when you launch the NAL the first time, it will find all app objects associated to the user/workstation and then run them based upon how the app object is configured.

    If you add a new application and associate it to the user, and then refresh it manually, it should “run” the app (or if it’s not a forced run app, it’ll show up in the app launcher, desktop, etc.) I think workstation-based apps work the same way.

    It rereads the entire app association again, I believe. So if the user had 5 apps associated, it will see 5 of them. If you add two more, and refresh again, it “re-reads” the app association attributes on the USER object and the workstation object (I think) and now it sees 7 “things”. It then finds those 7 app objects in eDirectory and reads the configuration information.

    But I could be wrong on that part (ie, it may actually read every app object in the tree, but I’m 99% sure it reads the attribute on the user/workstation for app association.).

  3. By:Futia

    correct – I believe NAL only reads the apps associated with the user/workstation on which it is running. The apps are assigned a “version number” if you will, depending on how you
    edit the app object the version number will change or you can change the number yourself to force it to appear as a newly edited version so it will run the next time the user/workstation logs in or the next time NAL is refreshed.
    If your object is set to run always you don’t have to worry about it.

    You can also set an automatic refresh timer for NAL so that it checks for new/edited apps periodically during the day.
    (don’t do it too often though (like every 3 minutes) – it may slow things down)

Comment

RSS