The software inventory report contains thousands of records when you consider all the users and workstations in a network. Being able to sort or filter out, by date, just the applications that were installed in the past x days, would be helpful in identifying what has actually been added to the network.
Within Default Settings please add an option for Date Format as we use YYYY-MM-DD as a standard across all our tools and would like the option to modify system wide.
There appears to currently be no way to set a default due date under ticket or queue settings, nor is there a rule field you can use to set a ticket due date. Our agents do not generally manually set due dates when they create tickets so it makes it virtually impossible to get any reliable data from reports based on due dates. While this could be addressed as a training issue, it would save time and make far more sense ...more »
the file manager isn't very good at showing if something is up to date when it only shows the date, but no time.
I then have to switch to the command prompt as a workaround.
When generating invoices for QuickBooks, the dates in the ticket time entries don't follow. That means we need to go back and forth between Service Desk and QuickBooks and manually enter all the time entry dates again in QuickBooks.
This would be a HUGE time-saver!
wen man in der Zusammenfassung das Installationsdatum des PCs sehen kann
Whenever a report is exported to CSV (or excel), the date is formatted in a display format. Converting it to a numeric format would allow me to format the column however I desire, sort based on true chronologcal order, and apply other data transformations without having to do my own conversion for every exported report.
05-JAN-2016 08:00 should be 42374.3345
If a user inadvertently or purposely changes the date/time on a machine, it can cause the agent reporting and other checks to report erroneous results. The agent should include the local time as a part of the reporting to the host which should compare that to the reception time. If there is a significant discrepancy (more than a couple of minutes), it should be flagged as a possible clock error. e.g. changing the date ...more »
When Microsoft re-releases a patch/update, the "Release date" for it needs to be updated to the correct date in the console. A few examples: 1) KB2952664 has been re-released quite a few times now from MS, but the release date in the cloud console still shows as "22-Apr-2014". 2) An August 2014 update, KB2975719, that had to be pulled and re-released in September. The release date is still from the original patch ...more »
I know you can set an expiration date in the cloud management console. We will sign clients up for a year. It be nice to have a Warning sent out when the expiration date is close.
Within the current patch management reports, you can generate a Pending patches report or an Installed report, but not specified by date. I have a customer that has had PM for years, which generates massive reports that nearly crash browsers. I need a way to send them reports that simply cover a date range, so when they request a report of the patches that were installed last week, it would be great to have an option ...more »