Skip to main content

sms: sql query to display chassis type

here's a query inspired by a post from garth jones for something sherry kissinger whipped up. this sql query basically gives you an output of all of your machines, with the type of chassis.

select  sys.name0 as 'Name', sys.manufacturer0 as 'Manufacturer', sys.model0 as 'Model',
        case enc.chassistypes0
            when 1 then 'Other'
            when 2 then 'Unknown'
            when 3 then 'Desktop'
            when 4 then 'Low Profile Desktop'
            when 5 then 'Pizza Box'
            when 6 then 'Mini Tower'
            when 7 then 'Tower'
            when 8 then 'Portable'
            when 9 then 'Laptop'
            when 10 then 'Notebook'
            when 11 then 'Hand Held'
            when 12 then 'Docking Station'
            when 13 then 'All in One'
            when 14 then 'Sub Notebook'
            when 15 then 'Space-Saving'
            when 16 then 'Lunch Box'
            when 17 then 'Main System Chassis'
            when 18 then 'Expansion Chassis'
            when 19 then 'SubChassis'
            when 20 then 'Bus Expansion Chassis'
            when 21 then 'Peripheral Chassis'
            when 22 then 'Storage Chassis'
            when 23 then 'Rack Mount Chassis'
            when 24 then 'Sealed-Case PC'
            else 'Unknown'
        End As 'Chassis'
from    v_gs_computer_system sys join
        v_gs_system_enclosure enc on sys.resourceid=enc.resourceid
order by 'Chassis'

Comments

  1. I don't get it. I can't paste this into a query. It's not the right syntax. How can I use this?

    ReplyDelete
  2. usually it's because your focus is not set to your sms database name. if it's set to master, you're going to get an error. otherwise, this is microsoft t-sql. what's the error?

    ReplyDelete
  3. I'm in the SMS Administrator Console, in the queries section. I created a new query and copied and pasted this, but got an error.

    ReplyDelete
  4. oh got it. this is a t-sql query whereas the sms admin console only accepts wql queries. i don't believe wql will accept "select case" statements so you'll have to use this in query analyzer or create a web report for it.

    ReplyDelete
  5. Thanks a lot, that was exactly i was looking for.

    ReplyDelete
  6. Hey, thanks for this sql query...I added chassis type 65(tablet) to it...looks great in reporting!

    Wouldn't it have been nice for these chassis types to be better documented? It's not exactly intuitive!

    ReplyDelete
    Replies
    1. they are loosely documented on msdn... :|

      Delete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m