My organization is implementing Altiris HelpDesk Solution in July, 2010, so I am very new to the product.  I have read the product guide and the articles you mentioned above.  I am going to training in two weeks to absorb anything and everything I can about the product.

What I am looking for is a document that has samples of the different rules people have implemented in their organizations where I can say..."hmmm, I can use this in my organization."

We are going to use winuser as well as email to create incidents.

For email - when a user replies to the email, how can I prevent another incident created for the same ticket?  If the email address is part of the cc:, how can I prevent a new incident created?

For winuser - I want to route an incident to a specific queue based on IP address.  The manual says to enter 10.10.10 (this is the example given on the manual).  I substitute that with our own subnets, but it is not working.  If I enter the exact IP address of the device, then the routing rule works.  What logic or setting am I missing?

Preventing duplicate incident creations
If you use Altiris Helpdesk's ability to monitor inboxes, it will detect the incident number in the subject and add it to that incident.  By default it detects in the format #<number>, e.g. #64484 in the subject line will add the details to incident 64484 as a new comment.

I'll test you suggestion about the email address.

For the routing rule based on IP, that's exactly how I have my routing rule but it is not working for me.  How do I associate an asset?

Yes, that makes sense.  Have you tried to search an asset based on IP?  Can you search an asset by subnet - for example, I want all of my computers on 10.10.10?  I do not get any result when I search using that parameter.  However, if I search by IP address - 10.10.10.100 - I get a result of the asset with that specific IP address.

Here's what I'm trying to do - I want a routing rule which says - When any of these is true:

managed_object_IP_address contains 10.10.10
managed_object_IP_address contains 10.10.12
managed_object_IP_address contains 10.10.13
and so forth

Any incident that meets these criteria, to route to a queue called ABCD.  The above rule does not work for me.  The incident does not route to the queue I specify.

I guess I can route based on asset name (which works by the way).  However, it is just making me "upset" I cannot get this to work based on IP address.

When I look for an asset and I type the asset name, click on Find, should it display the IP address of that asset?  Right now, all it gives me is the serial number of the asset.

Can you provide a screenshot?  I'm not sure what you're looking at.

I think what you're looking for can be added by clicking the "Format Table" button located on the solid grey bar above your results. 
Simply add the field for Asset_ip_address and place it in the order you're looking for.

I did format the table to include the Asset IP address field, Asset Name, and the other default fields.  The Asset Name appears but the Asset IP address of that Asset Name does not appear.

Does the address appear when you view the asset in Helpdesk solution?
Can you modify the asset from within helpdesk or is it imported from NS inventory?

Was there any resolution to this issue?  I also have machines where the information in the Resource Summary is only showing (static) in the IP address: field and nothing else.  There is no other information in that section.  When I check the Inventory Tab, there is no AeX AC TCPIP information listed in the Tree pane.

I have to create a validation rule or an incident rule that serves so that if the employee is not assigned or dont belonging to that employee especific queue  could not alter the ticket, summarizing that only queue members or the employee thath is currently assigned can to modify their tickets, I welcome your comments.