Allow Parent tickets to pass information to child ticktes in a process (workflow). eg, if creating a new user you would want to pass the user name, dept, phone etc from the partent ticket to other departments involved in the new user creation. Currently these have to be re-typed in each child ticket.

If a machine is reported lost or stolen, KBox should be able to implement a secure wipe function.

Updated Asset Permission to where buttons at buttom of asset can be added or removed based on job requirements, etc.

For example: If employee only make updates to assigned assets but does not have rights to delete make permissions to remove Delete Button in assigned role or make it grayed out.

I would like to have a schema of the K1000 / K2000 databases to facilitate the creation of reports with external tools.

I would like to limit access to report categories and asset types by role or user label. For example, we have a vehicle maintenance queue. We have vehicles as assets and we have reports for those vehicles. My vehicle maintenance guy doesn't need be able to see and modify the IT assets or reports, he just needs to see and modify his vehicle assets. Also, he doesn't need to be able to see the IT reports, just reports for his vehicles.

Asset management needs to display more than 6 columns of data. We currently have need for 9-10 columns to list everything on the screen.

I would love to see the ability to set a more specific deployment schedule for the managed installs. Make it like the patch deployment scheduling where you can pick certain day(s) of the week, specific time of day, specific date & time, etc. We have many machines that can only have software deployed to them at specific times and this would help automate that process.

Under Reports/Alerts, it would be nice if the scheduling were better. As it is now, you can only schedule an alert to run every day or once a week. It would be nice if you could schedule an alert bi-weekly, monthly, yearly, etc.

Online Kscripts - Add 'Run on next connect if Offline'. Many times a system goes offline when a scheduled script was supposed to run. Adding in this feature would insure that machine still ran the script. Currently we are always troubleshooting, "Is scripting broken?", versus "Did konductor NOT assign the machine the script". If we had this feature we could focus on machines that have a broken scripting mechanism.

Make sort order for "Move to Queue" and "New Ticket From Queue" consistent. Currently queues are listed in alphabetical order on the ticket listing page. However, when in the ticket detail page, the "Move to Queue" list is not sorted alphabetically.

Any end-users would like to be empowered to use K1000 software library for installing any software on either Windows or Mac system without required admin privilege. I found that K1000 software library supports only Windows. K1000 software library needs to support Mac, too.

In addition, the auto filter depending on what machine they are running needs to be added to K1000 software library. For example, end-user is logged onto Mac system, then, K1000 software library needs to provide only Mac apps by auto-filtering.

It would be nice if you could choose an option that instead of using the labels to be completely inclusive you can use the labels to be more exclusive. For instance, you could use a label for Windows XP machines and then another label for machines that have Firefox 3.x installed. Instead of having to make a brand new label for windows xp machines with firefox installed you could use both in conjunction to drill down to what you're looking for. This would allow you to create more broad labels that could be used over and over again.

Limit user access to queues without limiting their ability to submit tickets to that queue. We have 3 queues and I do not want the user of the third queue viewing the tickets in the other 2 queues (unless it is a ticket this person submitted). Thanks.