We recently had a request that seemed to make way too much sense for us to have not done it already.
A helpdesk worker wanted to be able to view everything associated to an asset (monitors, incidents, people, software licenses) quickly and easily.
By creating a task we were able to make that happen right away.
Like many organizations we have a mixed environment and we have to live with the decisions from the past. One of those was the choice of Forefront for our antivirus/antimalware solution. Until today we've been restricted in forcing scans from the Forefront console. Thanks to Deployment Server our helpdesk staff now have the ability to force those scans themselves.
In some environments, or for some ticket types, there always needs to be an Asset. After all it doesn't make much sense to have an install software request without a computer seleted.
In some environments, or for some ticket types, there always needs to be a contact. For those options you can create a validation rule that will require this option.
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.
Sometimes, when it comes time to manage computers, IT and Accounting don't always see things eye-to-eye. A department based collection -- while may be important for Asset Management -- may not meet the needs you have for delivering software.
Ever have those workers who just sit on the worker report screen and never refresh it to see if new tickets have been added to their queue? We ran into that and quickly found a way to end their excuses.
In our organization we have some very security sensitive managers, one of whom was wholeheartedly for Local Security Solution (LSS). However, he quickly became concerned that passwords, after being disclosed, were opening security holes.
