Cool Solutions

Favourite Support TID?


July 2, 2006 11:52 pm





Do you have a favourite (and yes, I have spelt that correctly!)?

Is there one TID, or a number of them, that you always refer to before an engagement?

Here are a couple of mine:

ZENworks 7 Desktop Management Updates – this is the TID of TIDs for any recent updates to ZDM7.

Enable ZENworks logging – this is invaluable for troubleshooting. It details all the logging options available to ZENworks Server and Desktop Management.

Let me know your favourites – I’ll add them to my list.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. 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.


  1. By:FlingGuy


    Uhhh yeah the ones that worked!

    But seriously.. A favorite? I don’t really think so. My problem has been with TIDS that have conflicting instructions. Now don’t get me wrong, the Novell Knowledge base is pretty much the best one out there and I have used lots of them.

    What we really need is a central, but very fast and very nimble clearing house for TIDS, someone to look at TIDS as they come on line and compair them to TIDS that say different things for the same purpose. Then you get the two engineers who wrote the conflicting TIDS, put them in a room…

    But the TIDS are a GREAT source of knowledge and have saved me lots of time and money. Keep it up!

    I would add one thing though, start sifting through the internal support database and gleaning things from it that should really be in the external knowledgebase.

    – Bill

  2. By:Ron van Herk

    Hi Bill,

    Yes, having conflicting information in the Knowledgebase is something bad. Just be sure we do all we can to avoid having something like that in the system. Unfortunately it sometimes happens where two engineers seem to have found different way’s to resolve something (or maybe one of the solutions is just outdated). Because of this we always had an option to provide feedback on TID’s, unfortunately with the move to the new search system this option seems to be unavailable at the moment but I assume it will be back (I’ll verify that and let you know).

    On the internal knowledgebase articles, the policy is not to create any internal solutions at all. If needed we (the engineers that write these solutions) can add an internal statement to the solution but in general they all get published. If I need to get internal info, it often means I need to get in contact with some of the developers to get info from them.


  3. My favourite TID is 10095935, created by Mike Gord:
    “NAL processes in the User and System scope”

    Rolf Lidvall
    Swedish Radio (Ltd)

  4. By:Grant

    I don’t really have a favorite, but if I did it would be the logging TID and the TID telling how to troubleshooting Middle Tier. And this post deserves more than 2.5 stars.