Monday, September 12, 2016

Windows 10 - Editions and Versions Report (in lack of a better name)


Hi

May 02: Quick Update ,seems to be a small "bug" with how Windows 10 1703 (Creators Update) registers in Configmgr DB. For some reason the "branch" field is a empty string, not 0 as expected (or at least NULL instead of empty string).
have created a new version of the report (Download it here) as a work around for this issue.


Created this report a few months ago, but didn't release it because I  wasn't sure my reverse engineering was correct until Windows 1607 was released.
But now Windows 10 1607 is released and everything seems to line up.

This report needs Configmgr 1602 to run (maybe it'll work on 1507 ,but haven't tested it)

The report is a details report for Windows 10 ,It can shed some light on Editions,Versions ,update rings and "state". As with most of my reports you can run it against a specific collection to limit the result and contrary to the console, it gives you a detailed list of witch computer is running what.

 & '.\Upload Reports v3.ps1' -webServiceUrl http://yourreportserver.fqdn

(Read more about the script and additional parameters here)

Added some parameters to the report to enable you to show ex. only computers on "Current Branch" or only computers that have reached "End of life".



If you found it useful ,feel free to spread the word:-)

Let me know what you think in the comments below or on Twitter. 



29 comments:

  1. This report is not working for me. Get this error when trying to open it:
    The report server cannot process the report or shared dataset. The shared data source 'Configmgr' for the report server or SharePoint site is not valid. Browse to the server or site and select a shared data source. (rsInvalidDataSourceReference)

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. I get an error as well:
    An error has occurred during report processing. (rsProcessingAborted)
    Query execution failed for dataset 'Windows10'. (rsErrorExecutingCommand)
    The SELECT permission was denied on the object 'vSMS_WindowsServicingLocalizedNames', database 'CM_XXX', schema 'dbo'.

    Happy to help troubleshoot if you'd like.

    ReplyDelete
    Replies
    1. I figured out my issue, in my case I was running it on my CAS, and needed to run the report on a site server. Seems to be working so thanks!

      Delete
    2. Same here, Access denied on 'vSMS_WindowsServicingLocalizedNames' with db owner rights. There are only one primary site in place. So your suggested solution don't work for me.

      Delete
  4. It appears with the Creator's Edition that A.OSBanch01 in the part of the query Select A.Name0,A.User_Name0,A.Client_Version0,D.Caption0,A.Build01,A.OSBranch01... is now null - resulting in the 1703 clients not showing up in our reports :(

    We are using SCCM v1610

    ReplyDelete
    Replies
    1. Hi ,thanks for the heads up.
      Looks like a small "bug" in the DB. Looks like Windows 10 1703 have a empty string in the OSBranch01 column that messes with the join of the query.

      Have hacked the report to work with Creators Update, here's a link to the updated report. https://goo.gl/i2TTH0

      Delete
    2. Thanks! Only problem is that the link is authentication blocked. I get a 403 trying to get the new report.

      Delete
    3. oops ,try this: https://goo.gl/ZNJ8ld

      Delete
    4. Bingo - a few small cosmetic oddities, but it will work fine until MS fixes that little bug.

      Delete
  5. Back again! Looks like 1709 doesn't show up in the report now. (Wonder if MS is doing something different yet again)

    Currently, in the top graphic, I get 3 different totals.
    Current/Current Business/LTSB = 217
    Ent/Ent N/Pro/Pro N = 229
    Release Ready/Business Ready/Near End of Life/End of Life = 237
    Versions circle = 237

    ReplyDelete
  6. I have the some problem of Brian i don't see the 1709 version,how can i fix it?
    Thanks in advance
    Cristian

    ReplyDelete
  7. Hi Thomas,

    Your report has been working great but recently the report has started to show "#Error" for all the entries in the "update" column and far right graph whereas before it showed the version number (ex. version 1709). Any thoughts?

    Thanks,
    Mark

    ReplyDelete
    Replies
    1. We also have this problem. Don't know when it started though, perhaps after upgrading to SCCM 1710?
      /Anders

      Delete
    2. This comment has been removed by the author.

      Delete
  8. Just change the column Update value from an expression to the value "[Version]". Then edit your donut with #Error in it and change that expression to =" Version " & Fields!Value.Value & vbcrlf & "#VALY" That's how I fixed mine.

    ReplyDelete
  9. I was getting the same #Error in the update column. Since that's the field I really wanted and led me here I thought I would post how I repaired. First Similar to what was posted above I simply replaced the expression in the Update Field with [Value] instead of [Version] which then started filling in the field with 1511,1703,1709 ect.. So I got what I wanted there. I then simple deleted the pie chart since I was not able to repair that one and replaced it with a series that included Value from the Version dataset and the values field of [Count(Value)] and a tooltip #Valy. That at least gave me what I was looking for with no errors.

    ReplyDelete
  10. This report is very helpful. Just one question, how do I modify it to report on build 1809?

    ReplyDelete
    Replies
    1. This comment has been removed by the author.

      Delete
    2. Try this, i updated it a bit https://1drv.ms/u/s!AjWJfSOoWmkYur8ZKVUoEYAFwu5tkQ

      Delete
  11. Sorry im not good in this, I open the rdl file in notepad.

    Which line do i change? and what is to replace?

    ReplyDelete

  12. If you are stuck with your Law assignment then in this case you can opt for our Law Assignment Help. we provide the bestLaw assignment writing UK.We also provideLaw Assignment and Essay Writing Help UK for students across the globe. for more information contact us +16692714848.

    ReplyDelete
  13. Great post; I think you can get every information about LogisticGuru.PVT the best Car Transport In Pune. They have a vast and robust network of more than 70 destinations nationwide. All branches in all over India are entirely computerized and linked through. Their unmatched and reliable car transport service makes LogisticGuru.PVT the unbeatable car shipping company in India.

    ReplyDelete
  14. I was trying to download your report. I am getting access denied. Can you please give me access

    ReplyDelete
  15. Not able to download the report, 404. That’s an error.

    The requested URL was not found on this server. That’s all we know.

    Could you please help me with the download link

    ReplyDelete
  16. Hello, thank you for your wonderful reports. Could you please share the updated link so we can download this report? It would be greatly appreciated. Thank you.

    ReplyDelete