Nicholas Rayner
pointed out (via Twitter linking back to his blog) a new article available for download on Microsoft.com looking at 5 misunderstood features in Windows Vista today.
Download: 5 Misunderstood Features in Windows Vista (Link down but will be back up shortly)
Those 5 misunderstood features include:
- User Account Control (UAC)
- Image Management
- Display Driver Model
- Windows Search
- 64-bit architecture
The article looks to clear up some confusion IT Pros might have with these features. This article is part of the Springboard Series on TechNet offering a collection of resources, tools, and monthly articles to address your questions on Windows Vista based on community feedback and feedback from early adopters.
We blogged about a Springboard Series Live Roundtable event in February in which Technical Fellow Mark Russinovich took part of addressing Windows Vista Deployment and Adoption. You can watch the recording of the session here.
Thanks Nick (a.k.a "aussienick") for pointing this out!
Written by Brandon LeBlanc on May 15th, 2008 with no comments.
Read more articles on 1426 and 1429 and 1673 and 169 and 2065 and 2157 and 401 and Contributors and Featured News and IT Professionals and Springboard Series and UAC and Windows Vista and technet.
Welcome to "The Quest for the Holy Desktop WMI Filter”, this is a global search for what you could call "The Perfect Desktop WMI Filter". A WMI filter which, by using WMI Query Language (WQL), should be able to spot DESKTOP computers only. It should be a general query - meaning it should be possible to use the filter in most Active Directory environments around the globe for Group Policy filtering.
So, what is a desktop really? Well, actually in this case we’ll say it’s the opposite of a laptop. Hmm, then what is a laptop? Easy enough: a computer with a battery! We’ve got the WMI filter for finding laptops already:
Select * from Win32_Battery - don’t you just love the simplicity in this query?
This filter will make a computer with a battery respond back with "TRUE" (because the WMI class instance is present), meaning a GPO with this filter will apply to computers with batteries. Simple right? And you might think it’s easy to just "turn it around" to find desktops, like:
Select * From Win32_Battery Where Availability != 2
or
Select * From Win32_Battery Where Availability IS NOT NULL
or
“Where Not X Like Y” or whatever
Maybe it is, maybe it’s not… I think it’s pretty damn hard! For spotting laptops we could have tested the classes Win32_PortableBattery, Win32_PCMCIAController, Win32_POTSModem as well - but somehow I think most people will agree, that the "essential ting", which makes a laptop a laptop, is in fact the battery presence!
But, our tests for spotting DESKTOPS only (machines without a battery - yes, I know this will include servers as they a "stationary" too) have not been a success yet! We probably just need the correct syntax? And this is where you get into the picture!
Are you able to crack open this nut? There’s a cool price!
This all started on a mailing list for Group Policy guys and girls - called GPTalk - created and maintained by Group Policy guru and MVP Darren Mar-Elia - the guy behind GPOguy.com and SDM Software. You can join the list RIGHT HERE and participate in this contest to WIN a free copy of the:
BUT you have to be the first person to crack this thing, there’ll be only ONE WINNER - that could be you!
I’ll be evaluating incoming answers - FIFO: "First In First Out" method is used. Hopefully we’ll see the most simple solution first - simplicity works, right? Actually I wouldn’t know in this case would I…
One important thing! We will ask you kindly to TEST any WMI query submissions before sending them to everybody on the list. During your testing, you should use a tool to verify the WMI filter against a minimum of 2 desktops and 2 laptops. You can use the free WMI Filter Validation Tool to test you WMI filters in your environment. Personally I’m also using Scriptomatic version 2 and WBEMTEST for finding the available classes, items, queries etc.
Please have a look at the "rules" further down!
Why do this? Well, because it’s fun - and useful at the same time… When looking at it generally, the purpose of this filter is to say: "I want these user settings to apply, but only when the user logs on to stationary machines". This can be used for a lot of security related setting, eg. in the case where Automatically cached Offline Files/Folders are unwanted on stationary machines for certain users etc. The job of most WMI filters placed on User policies is to limit which machines the policy setting(s) should apply to (even though WMI filters could check for user specific things too). Besides from that it’s a nice challenge, we can pretty easily "spot" laptops, as they have batteries – and desktops don’t, but that’s not good enough for Mr. WQL, is it?!
Stuff we have tried - and the rules
We’ve been around solutions looking for Win32_SystemEnclosure > ChassisType before - which basically doesn’t work in a WMI filter because that’s an Array (and yes, I’ve also seen lots of posts on forums out there claiming that particular class is the solution – but for WMI/WQL queries it’s not). If would work in a script (because you can add additional logic to scripts), but we are searching for a WMI Filter - not workarounds of any kind!
As mentioned we tried with the Win32_Battery WMI class. However, as desktops don’t know this class at all, they’ll return FALSE no matter what. Basically a desktop computer is gonna say “Heck, I don’t know anything about that class *Panic* I’m out!” – or just “False”… Bummer!
We have also tried PowerSupplyState, Win32_DesktopMonitor, Win32_DisplayConfiguration, Win32_SystemSlot, Win32_Fan and other classes – just haven’t found the perfect “this is definitely a desktop WMI item value or class”…
We’re basically looking for something like:
A) Select * from Win32_SomeClassOnlyDesktopsHave
Or
B )Select * from Win32_SomeClass.SomeItem = “SomeValueOnlyDesktopsHave”
Or
C) Some way of saying “if you don’t know the class (eg. Win32_Battery), then apply the GPO anyway”
Again, the “quest” is to find the perfect, *universal*, way of spotting “Non-laptops” or Desktops – it can of course be done by looking for some special computer Manufacturer/Model, BIOS version, specific hardware driver or whatever – but that stuff it most likely gonna be different from environment to environment. Also, if we all just used computer names like “DESKxxx” for desktops and “LAPTxxx” for laptops, we could have used WMI filters for computer name – but unfortunately that’s not the case - or at least I won’t consider that a valid solution 
The thing is, that normally it’s the LAPTOPS that have special hardware – like Batteries and built-in Modems, PCMCIA slots etc. – so they are pretty easy to find. With desktop computers it’s another story – hope you can help us out here!
Please, again, we know lot’s of “workarounds”, but what we need is a *WMI filter* and it has to return *TRUE* for *DESKTOPS* (or let’s call the NON-LAPTOPS or NON-PORTABLES, it doesn’t really matter).
Remember, simplicity works - maybe the answer/solution is pretty straight forward? Feel free to post any additional questions to the mailing list!
Another example of what has been tried
We could maybe try to go for presence of PCI (and not Mini-PCI) or AGP slots, as we expect most desktops to have PCI slots (and laptops to have Mini-PCI, but that would depend on the form factor) – or maybe AGP (but does onboard VGA count as AGP? Any PCI VGA cards left out there? Yeah, probably…). If not we could maybe go for something like this:
A) Select * From Win32_SystemSlot Where SlotDesignation = “PCI%”
Or
B) Select * From Win32_SystemSlot Where SlotDesignation = “AGP”
However, this is not accepted as a solution as we cannot say that all desktop computers have AGP slots. But - maybe you can convince us otherwise?
Other cool Group Policy information:
You’ll find additional Group Policy information at these sites:
www.gpanswers.com - The home of Group Policy guru and MVP Jeremy Moskowitz, check out the community there too!
TechNet Group Policy Forum - A brand new Group Policy forum on Microsoft TechNet
The Group Policy Team - The home of the Microsoft Group Policy Team
Jakob H. Heidelberg blog - My own blog, mostly about Group Policy and Security
www.heidelbergit.dk - My website with blog RSS, certifications, LinkedIn info etc.
Hope to hear from you soon - O’ Yee Knight of the Microsoft Group Policy Table!
Written by Jakob H. Heidelberg on February 13th, 2008 with comments disabled.
Read more articles on Darren Mar-Elia and Jeremy Moskowitz and MVP and gpanswers.com and gpoguy.com and group policy and microsoft and technet.
Microsoft has recently published an "Events and Errors Message Center" on TechNet. It is a bit like
EventId.net, but you can search on more fields than Event ID and Source (note that non-Microsoft products aren't included in the Microsoft offering).
The
basic search allows for selection of a Microsoft product, and a search string. The
advanced search adds a
Version field for the selected product, an
Event ID field, an
Event Source field, a
File name, and
Language. The product list isn't yet all that comprehensive with only 18 entries (and some duplicates or products that could be further filtered by version), but I hope to see it grow to encompass more products and more versions (Vista is not listed yet, for example). It would also be cool if the capability to annotate specific events was made available to users, much like can be done at EventId.net. Another idea that would be nice to see is that as products are developed / maintained / updated, part of the process would involve documenting the events and their meaning, in the same database that the Events and Errors Message Center interfaces with. Perhaps QA and other groups could even add their own annotations to specific events - what caused the problem, how the problem was resolved, etc.
Hopefully, the Events and Errors Message Center keeps improving. Along similar lines, it would be nice to see the
DLL Help Database get some attention - several times I have hoped to see Vista files appear but have been disappointed.
»
Written by «/\/\Ø|ö±ò\/»®© on August 14th, 2007 with comments disabled.
Read more articles on Events and error codes and errors and technet.