How to find Windows 7 Computers in your organization? – Applying Filters in “Microsoft Management Console”


 

With the increasing sales of Windows 7, most of the companies have now more than 1 Operating Systems in their systems. Like Windows XP, Windows Vista and Windows 7. With all this mix of operating systems, sometimes, it can be hard to find something very easy. I recently had to find out all our Windows 7 computers in our organization to change all the MAK activated Windows 7's to KMS licensing server. Usually, to find out all the computers with some specific configuration, I would use a program like "Spiceworks" or "Windows System Center Essentials". But let's assume that we don't have anything else other than our famous Windows Administration Toolkit. So, to make a good .CSV report with all the Windows 7 clients inside of your organization follow the following instructions;

  1. Fire up your "Microsoft Management Console" with the "Active Directory" snap-in!
  2. Explore to the "Organizational Unit" of your client computers in Active Directory
  3. From the "Menu Bar", click on "View" tab and "Filter Options"
  4. From the "Filter Options" window, choose to "Create a Personalized Filter" and click on "Personalize" button!
  5. Now click on "Field" button, "Computer" and choose "Operating System".
  6. In the "Condition" field, choose the "Exactly Equal" option.
  7. "Value" field must be the name of your operating system. In my case it's "Windows 7 Professional"
  8. Click on "OK" button in the 2 windows that are open!


 

Now, you can explore again to your client computers "Organizational Unit" in Active Directory and you will only see the "Windows 7 Professional" computers. This is because of the "Filter" that we just applied. To delete this filter and see everything in an "Organizational Unit", follow these instructions;

  1. In the "View" menu, choose "Filter Options"
  2. Choose "View all type of Objects" and click "OK"


 

You must be able to see every object in every "Organizational Unit" like before.


 


 


 

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more