Helpdesk and Recurring Incidents
This procedure will outline the steps needed to create a recurring incident. Recurring incidents are helpful for many reasons; however, they can especially help with trying to satisfy audit control requirements.
For instance, you could set up a recurring incident for the network team to view VPN logs on a monthly or quarterly basis.
To begin, go to your Notification Server > Tasks > Helpdesk > Notification Policies. From this point, you can create the policy here or you can create a custom folder to keep things organized.
Once you determine the exact location of your policy, right click on the folder where it will be housed. Click New > Notification Policy.
You will now see the New Notification Policy screen.
Enter a name and description for this notification policy. A sample has been created below. For the source, select query.
Now, click on the create query link. ![]()
At this point, all we need is a SQL statement that will always evaluate as true. For this reason, click on the Edit SQL Directly and enter a simple query.

You can use the query below. Once you have entered the query, click Finish.
You should now be back at the New Notification Policy screen. Now that we have our true query, we are ready to select the schedule. You have the option of creating a custom schedule or using a pre-defined shared schedule. For the purposes of this document, we will use the Monthly schedule that is out of the box.
To create the incident(s), select 'New Incident Automated Action' as the Add action type and click Add.
Now fill in the information for the automated new incident action. The top portion of this screen is for descriptive purposes only.
The title will be the title of the incident.
The comment will be the comment of the incident.
Now scroll down and class the ticket the way it should be categorized. You may modify these at any time.
Should you want specific notify rules, select them here. Next, click OK.
At this time, you are taken back to the new notification policy screen. We are now ready to test the policy. Before you can run a test, you must enable the policy and click apply.
At this point, you can clone this policy to create additional policies or you could add additional incidents to this policy by simply adding another New Incident Automated Action.










The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments
Great article!
Thank you for this great article, it works like a charm
I just have one question, how do i set a contact on the recurring incidents?
Thanks!
Hi HHansen, were you able
Hi HHansen,
were you able to find a solution for your question.
thanks,
mike
This is a very good
This is a very good article--easy to follow. I am having some difficulties testing my notification policy, though. I have enabled both my policy and automated action, which creates a new incident; however, when I click "Test Notification Policy" I do not receive an email nor does a ticket get created.
I suspect it is something I am doing wrong in the Source Query, but I am at a loss for words. My source query is as follows...
SELECT 'dummy'
This returns one column with the word 'dummy' in it. In this particular notification policy I am not concerned with specific results. More or less I am using the policy to send out automated reminders for work to be completed. I got the idea from this article and from https://www-secure.symantec.com/connect/forums/create-automated-incidents-jobs-daily-basis
Any ideas? Thanks.
Would you like to reply?
Login or Register to post your comment.