DS Reporting in NS (6-Pack of Reports)

DS Reporting in NS (6-Pack of Reports)

As we all know, there is a fairly large lack of reporting related to DS, so I took some time and created a few NS reports that show me some useful DS information. I figured that they may be useful to others as well, so I am posting them here to share. Using these reports, I was able to see a much clearer picture of things.

Have you ever wondered how many computers still had pending jobs?

Have you ever wanted to email someone a list of computers that haven't run a job yet, but hate excessive amounts of typing for no reason?

Anyone ever ask you for a list of computers that successfully ran Job X, not just a count of them?

Now you can answer these without any effort, just simply run the report and email them the results, or better yet, tell them where the report is so that they don't have to annoy you next time.

I noticed the script that dallasr posted on Juice recently and took some SQL from there when I started this.

Reports:

  1. Shows a listing of all DS jobs that are currently (actively) deploying.
  2. Count of all computers with pending DS jobs. Right-click option will list the jobs pending for the selected computer.
  3. List of scheduled DS jobs that have been scheduled for more than X amount of days, with 30 as the default.
  4. List of all scheduled DS jobs, but you have the option of entering full/partial computer name and DS Job name to filter your results. The default is a full list of all scheduled DS jobs for all computers.
  5. Like report #2, but this is for Completed jobs, rather than pending.
  6. Like report #4, but this is for Completed Jobs, rather than pending.

It would also be very simple to tie in the Primary User from NS into these reports. These are straight exports from NS, so just import them and run them.

Thanks,

Jason

License: AJSL
By clicking the download link below, you agree to the terms and conditions in the Altiris Juice Software License
Support: User-contributed tools on the Juice are not supported by Altiris Technical Support. If you have questions about a tool, please communicate directly with the author by visiting their profile page and clicking the 'contact' tab.
4.206895
Average: 4.2 (29 votes)
AttachmentSize
7_pack_of_ds_reports_for_ns.zip12.51 KB

Hey I voted for you

jjesse's picture

Even though you called me lazy... Great reports, great job on these

Jonathan Jesse
Director of Training
ITS Partners

Thanks Jonathan. Obviously

Thanks Jonathan. Obviously you don't hold a grudge for very long.

ds reporting in ns (6-pack of reports)

Jonathan,

To use these ds reports is deployment server solution needs to be installed on the Notification Server?

No, these solutions do not

No, these solutions do not need to installed on the same server. All of our solution databases exist on the same database server.

Have access to these

jjesse's picture

You just have to make sure you have access to the DS database, both security wise and network connection wise.

Jonathan Jesse
Director of Training
ITS Partners

Updated reports

I found a flaw in a join in these reports, so I fixed that and added an additional report. These work much better now.

Please be aware...

SK's picture

That these reports will ONLY work if your eXpress database is located on the SAME SQL Server instance as your NS database.

If it resides on a different instance or different SQL Server, then a "Linked Server" will have to be created, and the "OPEN QUERY" method will need to be implemented into the reports SQL.

Used Open Query...

And when I click on the Run button to test the query, all results come back. However, when I enter a particular name in the report, no results are returned. I think it has something to do with the variables not being recognized. Can anyone clarify why this would be happening?

Thanks.

Never mind...

figured it out. Thanks.

linked_server and openquery

BenS, I have my DS database on another system (server\instance). Do you think you can give me example or sample on how to use linked_server and openquery statement using these queries.