I'm having a hard time doing something that I think should be simple. I can't seem to find the exact version number that Windows XP Embedded has so that I can create a query for a collection. Has anyone else done this before?

I have never done it but I would imagine that you can go into the Resource Explorer and see some of the OS data/Architechture and compare it to a normal machine. It should be listed at Windows XP as "Windows XP Embedded SP2" and so forth.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

I've used this in the past (custom mof extension) [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WindowsEmbedded\\RunTimeID|RunTimeSKUCode"),Dynamic, Provider("RegPropProv")] XPeClient;There's more to it than the above, but it's part of what went in configuration.mof. But I was sure someone told me a different spot that was a key identifier to determine xp embedded But of course I can't find that note right now.Standardize. Simplify. Automate.

So you will depending upon a discovery record, not client data. There are several discovery methods, I don't know if any of them will provide the data you need. Heartbeat is usually the most verbose of all of them, and even that one may not have the data you want (and besides, Heartbeat DDR implies the client is already installed). So you're left with System Discovery--which you may or may not have on, and Network Discovery--which you may or may not have on.And I don't know if either one of those would offer a definitive piece of information to specifically tag it as "XP Embedded". Possibly your best chance would be if you (hopefully?) name your XP Embedded devices differently, and uniquely, from other devices. If so, then a quick'n'dirty where name like 'XPE%', if all xpe devices started with xpe.Standardize. Simplify. Automate.

Thanks for the quick reply, Sherry. I've checked the properties of a DDR that I know is an XP embedded device and I can't see any information in there that would allow me to differentiate between that and a standard XP Pro machine. I'm running all of the discoveries. I thought I had it for a second there because I was thinking I could specify a custom AD attribute but I now have to see if XPe puts anything different in AD than a standard XP Pro machine. So far, it doesn't look to be that way. They both are coming back for the OS version as 5.1 (2600). :(

I thought I would update this to let you know that it looks like WSUS can differentiate between XPe devices somehow but I can't figure out how.

Not that this will help you much, but if it's WES2009, heartbeat ddr will now report the Operating System Name and version as "Microsoft Windows NT Workstation 5.1 (Embedded)"Standardize. Simplify. Automate.