Wednesday, June 1, 2016

OSD Details ,Part 2 of my OSD Dashboard Report

As promised, here is part 2 for my OS Deployment Dashboard.

It's designed to be a drill trough report from my OSD Dashboard,but you can also run it stand alone.
The query has been  completely rewritten from my last report so it should be a lot more reliable than the last version.


To upload the report ,download the zipfile and extract to a folder. you can upload the rdl files the old fashion way or you can test drive the new version on my upload script.

To run the script you only need to specify the url to the reporting server(normally the site server)
The script will create a new folder called "Larsen Reports"(can be set with parameter), upload the reports and change the datasource to your configmgr server. 

& '.\Upload Reports v3.ps1' -webServiceUrl http://your-report-server 



Staring with the controls ,the "Deployments" field lists all task sequences and deployments in a readable format. Next the "Computer" will filter to only show computers that have run that deployment.

Lastly for the "Start Date" and "End Date" you just need to make sure the computers OS Deployment are between these dates. (These two parameters are mostly used by the Dashboard to select the correct deployment when there are several attempts for a single machine.) 

The top of the report shows some basic info about the machine, name ,DN and hardware model if they are available.



The part your most likely interested in is the step by step status for the OS Deployment.
It'll show you a nicely formatted (if i may say so myself:-) ) list  with the details for each step. in the task sequence and how long time each step took.



The list is quite minimalist ,but a lot of info is available as tooltips. Execution status on the Group And Action Name and Exit Code and Action Output on the Step number.
If a group or action is skipped the text is over lined to illustrate that. If an action has an exit code other than 0 (Success) the line is colored red so any errors should be easy to spot.



If you have any trouble displaying the graphics in the report ,try restarting the SSRS Service.

As always, hope you like the report. Post comments and questions below.
If you think others might find this usefull ,feel free to share a link on twitter ,facebook and forums. (this blog is tiny so not many people have seen this yet) 





9 comments:

  1. Is the drill thru from the OSD Overview report working? We have both imported but I don't see the OSD Overview report drilling thru to the OSD Detail report.

    ReplyDelete
  2. should be working ,double checked the rdl files just to make sure and the action links are there. As long as both reports are in the same folder it should work
    Should be able to click on the computername in the table on page 2 of the OSD - Dashboard to bring up the details for that computers OS Deployment.

    ReplyDelete
  3. Thomas the reports are both in the same folder: OSD Overview 2.0 and OS - OSD Details but the click through isn't working. Hmmm...

    These OSD reports are awesome and extremely valuable. Any additional help is greatly appreciated.

    ReplyDelete
  4. Thomas sorry to keep bothering you. Can Time outs be either classified as failures or shown as a different classified on the OSD Overview report? We are trying to track Status = "Timed Out" but currently we have to look through the detailed report.

    Again great work and super valuable report!

    ReplyDelete
  5. the status overview chart on the frontpage can be modified to include time-out. i just filtered it out to remove clutter.

    Also. you can doublecheck the Action filter by right-clicking on the computer object and select text box properties.
    Should look like the screenshot.

    http://imgur.com/a/w8UOG

    ReplyDelete
  6. Thomas, thanks for the information. Our SCCM SSRS admin found the issue with the click through. "The version 2 of the OSD Overview 2.0 report I downloaded, did not have the link information configured on the computer name field. I used the version 1 of the report to find the correct values and recreated the link in version 2."

    ReplyDelete
  7. Hi Thomas,

    Your reports are really good!
    Thank you for sharing !!

    Gregory B

    ReplyDelete
  8. Thanks for another great report Thomas!

    ReplyDelete
  9. Hi Thomas,
    Thanks for the reports but it think the "details" one requires optimization: it tooks more than 5 min to show up .
    Fault is on the "Advertisements" dataset. this query looks weird…
    you can try to change this by the Following one:

    select distinct adv.AdvertisementID,col.Name as Collection,pkg.Name as Name,pkg.Name + ' to ' + col.Name as AdvertismentName
    from v_Package pkg
    inner join v_Advertisement adv on pkg.PackageID = adv.PackageID
    join v_Collection col on adv.CollectionID = col.CollectionID
    join (select distinct AdvertisementID from v_TaskExecutionStatus) tes on adv.AdvertisementID=tes.AdvertisementID

    Should be much more quicker.
    Regards.
    Bruno

    ReplyDelete