UPDATE
We successfully integrated in the QAS toolset and will be shipping SSO for Active Directory as part of the 5.5 release this summer.

We have identified a technology that will allow us to deliver SSO. The Quest acquisition has provided Dell with a new technology called QAS (Quest Authentication Services). The QAS team is in the process of extending their capabilities to work with FreeBSD, the K1000’s operating system. It’s early, but we are encouraged and are hopeful to have a solution implemented sometime this summer.

I'd like to see a more powerful WYSIWYG editor for the knowledgebase articles, maybe supporting Rich Text Format (RTF) and/or full HTML. I know Markup is already supported, but it's not ideal when you're trying to paste already formatted info into the knowledgebase or creating articles from scratch. There are nice WYSIWYG editors available that could probably be used, versus creating one from scratch.

Being able to forward the knowledgebase articles via email and retain the formatting would be nice too. Even the Markup formatted articles seem to be stripped when emailing them.

Have the K1000 send the WOL request to an Agent (on a PC that is already awake of course) on the same VLAN as the PC that you want to wake up. I need to be able to send WOL packets through VPN Tunnels and across VLANs. This would be a life saver!

Once comments are saved in a ticket/request, they can no longer be edited by users or administartors. Could we create a way for the comments to be edited by ticket owners only after the comment has been saved in a ticket? Could we set this type of field as a Read-Only or Change Permission?

Currently the kbox handles out of office reply's and non delivery reports as normal e-mail.

this causes the following issues.
- closed tickets are reopened
- mail loops are created.

I think the kbox should inspect the Return-Path: header of an e-mail on arrival.

If the return-path is empty or like
Return-Path: < >

Then it is an auto-reply message..

if the message can not be attached to an existing ticket, log and drop it... no reply message.

if the message can be attached to an existing ticket it can be done for debugging reasons.. but it should not trigger any workflow. ticket should stay closed if it was closed, and no mail should follow.

Currently the kbox handles out of office reply's and non delivery reports as normal e-mail.

this causes the following issues.
- closed tickets are reopened
- mail loops are created.

I think the kbox should inspect the Return-Path: header of an e-mail on arrival.

If the return-path is empty or like
Return-Path: < >

Then it is an auto-reply message..

if the message can not be attached to an existing ticket, log and drop it... no reply message.

if the message can be attached to an existing ticket it can be done for debugging reasons.. but it should not trigger…

Currently the only way to provide view access to all tickets is to make the user a ticket owner. Otherwise they can only view their own submitted tickets. We'd like to be able to provide view-only access to all tickets in the admin portal WITHOUT having the person be ticket owner. Also would like to have the option to provide ticket modify access without being owner. This would be for supervisory positions who need to check in on ticket details but we do not want anyone assigning them tickets.

The current design of the ticketing system allows for multiple users to modify a ticket at the same time. The problem is the first person may change the status, for example, then save. Then the second person with the ticket open can save after doing something else like making a comment. This will then switch the status back to the original.

I know this may be complicated, but the web interface needs to lock tickets using some sort of keepalive while someone has a ticket open. Active content updating would be even better (i.e. changing the status or any other field would dynamically update the same field in the ticket for any other user who may have the same ticket open in their browser).

The current design of the ticketing system allows for multiple users to modify a ticket at the same time. The problem is the first person may change the status, for example, then save. Then the second person with the ticket open can save after doing something else like making a comment. This will then switch the status back to the original.

I know this may be complicated, but the web interface needs to lock tickets using some sort of keepalive while someone has a ticket open. Active content updating would be even better (i.e. changing the status or any other…

Currently, to attach a screenshot of an issue, you have to take a screenshot (or multiple) open an additional document (like word) and paste the screenshot(s) into word. then you can take that word document and search for the document on your computer and attach it via the upload function in the ticket.

Other web-based ticketing systems are allowing you to simply click a 'paste' button that allows you to import (Via java in JIRA's case) the contents of your clipboard into a window.

this would really improve the information users provide to techs in the tickets, as well as improving tech response time to resolution.

Currently, to attach a screenshot of an issue, you have to take a screenshot (or multiple) open an additional document (like word) and paste the screenshot(s) into word. then you can take that word document and search for the document on your computer and attach it via the upload function in the ticket.

Other web-based ticketing systems are allowing you to simply click a 'paste' button that allows you to import (Via java in JIRA's case) the contents of your clipboard into a window.

this would really improve the information users provide to techs in the tickets, as well as…

6.0 will introduce the first phase of integrating Quest’s Management Extensions (QMX). Features include automated and recurring discovery of network devices and agentless inventory of most non-Windows network devices. Join us at UserKon to find out more.

When scheduling deployments on patching, it would be nice to set up a schedule to run on the first Thursday of each month, second Saturday, etc.
This way you could schedule a patch job to run the second Wednesday of the month after Patch Tuesday instead of changing the schedule date manually each month.

Allow for a role that has access only to certain machines and the ability only to create and modify their SW distributions, but have access to shared distributions. An alternative would be allowing more than one organization to share software distributions and other resources

It would be wonderful it a WOL option would be added the K1000: Computer Inventory listing. If I see that a machine is offline I can't just click on it and send a WOL. If that was a button next to the "Force Inventory Update" or even under the "Choose Action" maybe "Choose Action --> Machine Options --> "Send WOL" That would allow the user to select multiple machines. It would save the user time from having to go to the K2000 --> Systems --> K1000 Inventory --> Labels --> Find the machine you want. Thanks.

In Service Desk under Tickets tab, I'd like the ability as an admin to set the default view so ALL technicians' active tickets are on my screen and not just the requests assigned to me. Currently, I have to weed through the active and closed tickets or view each status separately.

Each user should have the ability to define which columns appear in each section of the KBOX (Inventory, Help Desk, etc.) based on columns available in the table in the database. Also, each user should be able to define column width for each column - preferably in an easy manner such as dragging the edges of the column label.