Differentiating Vostro 360 AIOs

Posted on

We purchase and use Dell all-in-ones (Vostro line) as the primary desktop in our organization.  The difficulty is that, as consumer hardware, the model can be modified or discontinued at any time without prior notice.  Needless to say it creates headaches from time-to-time.  Recently the Vostro 360 hardware was changed, resulting in the need for new drivers.  Within my SCCM task sequences, I have the install of drivers (within the full OS) limited based upon the name of the model.  The challenge with the Vostro 360 is that they maintained the same exact model name, but had different hardware configurations.  What I found was a main difference between the two types was the Bluetooth hardware ID.  So in addition to querying the model, I added a new query for the Bluetooth hardware.

The point of this post isn’t so much about the Vostro, but more about how I used Win32_PnPEntity to differentiate the two models so that the old config would get one set of drivers and the new config would get the other set of drivers.  In the driver install package step for the task sequence, simply click on the Options tab and add a WMI Query action with the following code:

Select * from Win32_PnPEntity where DeviceID like 'USB\\VID_0CF3&PID_3002%'


2 thoughts on “Differentiating Vostro 360 AIOs

    Robert Saraceno said:
    January 5, 2012 at 12:45 pm

    It’s worth noting that the Win32_PnpEntity class will not contain any USB* devices unless the driver has already been installed (at least in my finding). So you can’t control the installation of the drivers for WWAN drivers, for instance, using this method. I know this isn’t an issue in this particular example, but many like me will attempt to expand upon this, and spend hours figuring out why it works in a case like this, but not in others.

      Nicolas Moseley responded:
      January 5, 2012 at 12:50 pm

      That’s a great extra tip which I failed to include in my post, thank you! It did work in this instance because Windows had a generic device driver for bluetooth, just not the driver to make the device work. I discovered this problem trying to use a different device for which there was no driver. Fortunately using bluetooth works for me on this device :-)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s