Video Screencast Help
Search Video Help Close Back
to help

Endpoint Management Community Blog

Showing posts tagged with Helpdesk Solution
Showing posts in English
johnquinn | 23 Jun 2008 | 5 comments

I was trying to set up an e-mail template today with an attachment that was nearly 8MB in size. Upon trying to attach the file, I got an error message: "Maximum request length exceeded."

Details: 
Application_OnError - Unhandled Exception: 
System.Web.HttpException: Maximum request length exceeded. 
at System.Web.HttpRequest.GetEntireRawContent() 
at System.Web.HttpRequest.GetMultipartContent() 
at System.Web.HttpRequest.FillInFormCollection() 
at System.Web.HttpRequest.get_Form() 
at System.Web.UI.Page.GetCollectionBasedOnMethod() 
at System.Web.UI.Page.DeterminePostBackMode() 
at System.Web.UI.Page.ProcessRequestMain()

Upon doing some research, I discovered that the default setting for file attachments in the Helpdesk solution is 4MB.

I also found that you can increase this to meet your needs....

johnquinn | 10 Jun 2008 | 0 comments

I came across an interesting little modification that I thought I would share. Perhaps some might find this useful.

I discovered a way to color code the comments made by Guest users in incidents.

You create an incident rule it would look something like this:

When actually entering the properties for the comment color, it will look like this:

joamreynoso | 30 May 2008 | 1 comment

As everybody knows whenever the HelpDesk user edits an incident based on parameters set on tasks, leaving no comments about the change done, Altiris HelpDesk just place a comment with the changes in the history frame of the incident. For example:

If change the priority or even the status (could be any other value) it will appear in the comments field a message like this: Priority or Status Change from Old Priority/Old Status to New Priority/New Status.

For some customer, this is not acceptable just because you can be changing values that you don't want somebody else to see it. For these cases I found the way to get the previous comment and paste it in the new edit of the incident.

Below are the steps to make this work:

  1. Create an incident rule. Select a name for it.
  2. In...
scott76 | 23 May 2008 | 9 comments

Have you ever created a query for the helpdesk, set an auto refresh on that page, and then wished there was a way you could set the sort order? This will show you how.

  1. First in your Helpdesk Worker Console click on the Incident Queries link located to the left.
  2. Next locate the Query that you would like to set the search order for. Once you have located that Query click on the edit icon.

    ...

scott76 | 12 May 2008 | 2 comments

Many of us would like to see more columns added to the worker grid in helpdesk. Here is a fairly simple process to add those columns.

  1. You must first create a custom folder on your helpdesk server. If you have a default install of helpdesk you can find this at c:/program files/altiris/helpdesk/AexHd. In this directory create the custom folder.
  2. After you have created your custom folder browse to the templates directory. Locate and copy the WorkItemTable.ascx

    ...

SliSir | 16 Apr 2008 | 5 comments

Most of you have probably have read the Altiris KB article 34253 for customizing the Incident Grid.

The one thing they don't mention is what format the coloring they have in there is. Most HTML or Web coding uses HEX coloring, like White is #FFFFFF, however for this you have to Convert HEX to Decimal.

Simply open up your calculator, switch to Scientific mode. Then, click HEX, insert the color you want, like #666666 (Grey) then click Decimal and "BAM!" it converts it to 6710886, which the JAVA Script can then read. Now you are free to use all the pretty colors you want in the helpdesk grid. :)

Tenacious Geo | 03 Apr 2008 | 13 comments

We desired for tickets that are completed by workers to be set to the Resolved status and then if the contact did not respond within 24 hours the ticket will automatically go to Closed status. Here is a simple way to do it that may be useful to Helpdesk beginners.

This can't be done with an Incident Rule within Helpdesk because those rules are evaluated when the ticket is saved. Therefore, an NS notification policy is the best place to do it. The notification policy can be run on a specific schedule to accomplish the task needed.

Here is the query I used for the notification policy called "Set Resolved to Closed after 24 hours".

SELECT  
workitem_number AS 'Ticket_Number'  
FROM  
HD_workitem_current_view  
WHERE  
workitem_status_lookup_id = '400'  
AND  
DateDiff(hh,workitem_modified_on,GetDate())...
MBHarmon | 07 Mar 2008 | 2 comments

Sometimes there are some tasks that just don't fit into the typical boxes we put them in. Maybe they're tasks that should be run by managers or maybe they're tasks that only Altiris Admins should use.

Adding the following "Advanced Condition" you can restrict the view to just a single user:

CURRENT_WORKER(worker_id)
is equal to
x

If it's a task that might be good for an entire team you can instead replace the first line with:

CURRENT_WORKER(worker_queue_id)
is equal to 
x

X will of course be the worker's id or the queue's id as is applicable. You'll also probably want to compare the two values as a number.

dfnkt_ | 24 Jan 2008 | 5 comments

I posted this a few weeks ago over on the Altiris forums and have finally gotten around to submitting it here.

This might be common sense or well known information to a lot of the more well practiced people here. I started in my current position the 1st of November and had zero experience with Altiris, so everything is a learning experience.

I have created some queries using the helpdesk guide and would like to share what I've learned in hopes of others who come after me can learn something or find a quick answer.

First of all, this information can be found in the Altiris helpdesk 6.0 SP5 guide which can be found here: Helpdesk SP5 Guide - Page 222-226

We can start with something very basic:

A query to find all tickets whose status...

Global_Altiris | 20 Aug 2008 | 2 comments

Check out this best practice document from the Business Software Alliance, A.K.A. The people who bust companies for software piracy. It contains some easy and obvious best practices for Software Management.

"Of the $13 million that the Business Software Alliance (BSA) reaped in software violation settlements with North American companies last year, almost 90 percent came from small-medium businesses" -Associated Press 11/26/2007

http://www.bsa.org

Altiris Solutions & Reports backed up by strong corporate policies can help keep you off of their radar!