Updated List of OS Version Queries for WMI Filters

More likely than not, if you’re using Group Policy to push out software installation or registry entries to client machines or servers on the domain, the policy may be different depending on the OS version or architecture.
Examples, Group Policy Objects may need to be filtered by:

• Desktop / Server
• Domain Controller / Non-Domain Controller
• 32-bit / 64-bit

If you haven’t used WMI filters before, they show up in Group Policy Management at the bottom, between Group Policy Objects and Starter GPOs.

The WMI filters use a query to scope down the application of the Group Policy Object applicability. Here’s what a typical WMI OS filter looks like:


WMI Win32_OperatingSystem ProductType Tips:

ProductType 1 = Desktop OS
ProductType 2 = Server OS – Domain Controller
ProductType 3 = Server OS – Not a Domain Controller

WMI Win32_OperatingSystem Version Number Tips:

5.1 – Windows XP
5.2 – Windows Server 2003
5.2.3 – Windows Server 2003 R2
6.0 – Windows Vista & Windows Server 2008
6.1 – Windows 7 & Windows Server 2008 R2
6.2 – Windows 8 & Windows Server 2012
6.3 – Windows 8.1 & Windows Server 2012 R2

To create your own WMI filters, here is an updated list of WMI filter queries from Window XP – Windows 8.1 and from Server 2003 to Server 2012 R2.

IMPORTANT DISCLAIMER:
Always test your Group Policies and WMI filters before deploying.

DESKTOPS

ANY WINDOWS DESKTOP OS

• Any Windows Desktop OS – Version 1
  select * from Win32_OperatingSystem WHERE ProductType = "1"
• Any Windows Desktop OS – Version 2 (better for Win7 sometimes)
  select * from Win32_OperatingSystem WHERE (ProductType <> "2") AND (ProductType <> "3")
• Any Windows Desktop OS – 32-bit
  select * from Win32_OperatingSystem WHERE ProductType = "1" AND NOT OSArchitecture = "64-bit"
• Any Windows Desktop OS – 64-bit select * from Win32_OperatingSystem WHERE ProductType = "1" AND OSArchitecture = "64-bit"

WINDOWS XP

• Windows XP
  select * from Win32_OperatingSystem WHERE (Version like "5.1%" or Version like "5.2%") AND ProductType="1"
• Windows XP – 32-bit
  select * from Win32_OperatingSystem WHERE (Version like "5.1%" or Version like "5.2%") AND ProductType="1" AND NOT OSArchitecture = "64-bit"
• Windows XP – 64-bit
  select * from Win32_OperatingSystem WHERE (Version like "5.1%" or Version like "5.2%") AND ProductType="1" AND OSArchitecture = "64-bit"

WINDOWS VISTA

• Windows Vista
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="1"
• Windows Vista – 32-bit
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="1" AND NOT OSArchitecture = "64-bit"
• Windows Vista – 64-bit
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="1" AND OSArchitecture = "64-bit"

WINDOWS 7

• Windows 7
  select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="1"
• Windows 7 – 32-bit
  select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="1" AND NOT OSArchitecture = "64-bit"
• Windows 7 – 64-bit
  select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="1" AND OSArchitecture = "64-bit"

WINDOWS 8

• Windows 8 select * from Win32_OperatingSystem WHERE Version like "6.2%" AND ProductType="1"
• Windows 8 – 32-bit
  select * from Win32_OperatingSystem WHERE Version like "6.2%" AND ProductType="1" AND NOT OSArchitecture = "64-bit"
• Windows 8 – 64-bit
  select * from Win32_OperatingSystem WHERE Version like "6.2%" AND ProductType="1" AND OSArchitecture = "64-bit"

WINDOWS 8.1

• Windows 8.1
  select * from Win32_OperatingSystem WHERE Version like "6.3%" AND ProductType="1"
• Windows 8.1 – 32-bit select * from Win32_OperatingSystem WHERE Version like "6.3%" AND ProductType="1" AND NOT OSArchitecture = "64-bit"
• Windows 8.1 – 64-bit
  select * from Win32_OperatingSystem WHERE Version like "6.3%" AND ProductType="1" AND OSArchitecture = "64-bit"

SERVERS

ANY WINDOWS SERVER OS

• Any Windows Server OS
  select * from Win32_OperatingSystem where (ProductType = "2") OR (ProductType = "3")
• Any Windows Server OS – 32-bit
  select * from Win32_OperatingSystem where (ProductType = "2") OR (ProductType = "3") AND NOT OSArchitecture = "64-bit"
• Any Windows Server OS – 64-bit
  select * from Win32_OperatingSystem where (ProductType = "2") OR (ProductType = "3") AND OSArchitecture = "64-bit"
• Any Windows Server – Domain Controller
  select * from Win32_OperatingSystem where (ProductType = "2")
• Any Windows Server – Domain Controller – 32-bit
  select * from Win32_OperatingSystem where (ProductType = "2") AND NOT OSArchitecture = "64-bit"
• Any Windows Server – Domain Controller – 64-bit
  select * from Win32_OperatingSystem where (ProductType = "2") AND OSArchitecture = "64-bit"
• Any Windows Server – Non-Domain Controller
  select * from Win32_OperatingSystem where (ProductType = "3")
• Any Windows Server – Non- Domain Controller – 32-bit
  select * from Win32_OperatingSystem where (ProductType = "3") AND NOT OSArchitecture = "64-bit"
• Any Windows Server – Non-Domain Controller – 64-bit
  select * from Win32_OperatingSystem where (ProductType = "3") AND OSArchitecture = "64-bit"

WINDOWS SERVER 2003

• Windows Server 2003 – DC
  select * from Win32_OperatingSystem WHERE Version like "5.2%" AND ProductType="2"
• Windows Server 2003 – non-DC
  select * from Win32_OperatingSystem WHERE Version like "5.2%" AND ProductType="3"
• Windows Server 2003 – 32-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "5.2%" AND ProductType="2" AND NOT OSArchitecture = "64-bit"
• Windows Server 2003 – 32-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "5.2%" AND ProductType="3" AND NOT OSArchitecture = "64-bit"
• Windows Server 2003 – 64-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "5.2%" AND ProductType="2" AND OSArchitecture = "64-bit"
• Windows Server 2003 – 64-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "5.2%" AND ProductType="3" AND OSArchitecture = "64-bit"

WINDOWS SERVER 2003 R2

• Windows Server 2003 R2 – DC
  select * from Win32_OperatingSystem WHERE Version like "5.2.3%" AND ProductType="2"
• Windows Server 2003 R2 – non-DC
  select * from Win32_OperatingSystem WHERE Version like "5.2.3%" AND ProductType="3"
• Windows Server 2003 R2 – 32-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "5.2.3%" AND ProductType="2" AND NOT OSArchitecture = "64-bit"
• Windows Server 2003 R2 – 32-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "5.2.3%" AND ProductType="3" AND NOT OSArchitecture = "64-bit"
• Windows Server 2003 R2 – 64-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "5.2.3%" AND ProductType="2" AND OSArchitecture = "64-bit"
• Windows Server 2003 R2 – 64-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "5.2.3%" AND ProductType="3" AND OSArchitecture = "64-bit"

WINDOWS SERVER 2008

• Windows Server 2008 – DC
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="2"
• Windows Server 2008 – non-DC
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="3"
• Windows Server 2008 – 32-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="2" AND NOT OSArchitecture = "64-bit"
• Windows Server 2008 – 32-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="3" AND NOT OSArchitecture = "64-bit"
• Windows Server 2008 – 64-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="2" AND OSArchitecture = "64-bit"
• Windows Server 2008 – 64-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "6.0%" AND ProductType="3" AND OSArchitecture = "64-bit"

WINDOWS SERVER 2008 R2

• Windows Server 2008 R2 – 64-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="2"
• Windows Server 2008 R2 – 64-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="3"

WINDOWS SERVER 2012

• Windows Server 2012 – 64-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "6.2%" AND ProductType="2"
• Windows Server 2012 – 64-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "6.2%" AND ProductType="3"

WINDOWS SERVER 2012 R2

• Windows Server 2012 R2 – 64-bit – DC
  select * from Win32_OperatingSystem WHERE Version like "6.3%" AND ProductType="2"
• Windows Server 2012 R2 – 64-bit – non-DC
  select * from Win32_OperatingSystem WHERE Version like "6.3%" AND ProductType="3"

How do I print a listing of files in a directory?

1. Get to the MS-DOS prompt or the Windows command line.
2. Navigate to the directory containing the content you'd like a list to print. If you're new to the command line, familiarize yourself with the cd command and the dir command.
3. Once in the directory you want to print the contents of, type one of the below commands.

dir > print.txt

The above command takes a list of all the files and all of the information about the files, including size, modified date, etc., and sends that output to the print.txt file in the current directory.

dir /b > print.txt

The above command would print only the file names and not the file information of the files in the current directory.

dir /s /b > print.txt

The above command would print only the file names of the files in the current directory and any other files in the sub-directories within the current directory.

4. After executing any of the above commands, the print.txt file is created. Open this file in any text editor (e.g. Notepad) and print the file. You can also print from the command prompt by typing notepad print.txt.

How to change the listening port for Remote Desktop

How to change the listening port for Remote Desktop

Let me fix it myself

To change the port that Remote Desktop listens on, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

1. Start Registry Editor.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
3. On the Edit menu, click Modify, and then click Decimal.
4. Type the new port number, and then click OK.
5. Quit Registry Editor.
6. Restart the computer.

Note When you try to connect to this computer by using the Remote Desktop connection, you must type the new port. Maybe you have to set the firewall to allow the new port number before you connect to this computer by using the Remote Desktop connection.

How to hack or crack IDM manually.

Step 1: Download the IDM trial or If you already have IDM installed Update it by going to Help---}} then to check for Updates. If you don&...

 

 

Step 1: Download the IDM trial or If you already have IDM installed Update it by going to Help---}} then to check for Updates. If you don't wanna update your version, Just click on Registration.

Step2: When you click on registration, Now a new dialog appears that is asking for Name, Last Name, Email Address and Serial Key.

Step3: Now Enter you name, last name, email address and in field of Serial Key enter any of the following Keys:

RLDGN-OV9WU-5W589-6VZH1
HUDWE-UO689-6D27B-YM28M
UK3DV-E0MNW-MLQYX-GENA1
398ND-QNAGY-CMMZU-ZPI39
GZLJY-X50S3-0S20D-NFRF9
W3J5U-8U66N-D0B9M-54SLM
EC0Q6-QN7UH-5S3JB-YZMEK
UVQW0-X54FE-QW35Q-SNZF5
FJJTJ-J0FLF-QCVBK-A287M And click on ok to register.

Step4: Now after you click ok, it will show an error message that you have registered IDM using fake serial key and IDM will exit. Now here the hack starts.

Step5: Now Go to START --}} Then go to RUN and type the following text and click enter:
notepad %windir%\system32\drivers\etc\hosts
For Windows 7 users, due to security reasons you will not be able to save hosts file.
First of all go to C:/ drive then go to Windows Folder and then go to System32 folder and then go to Drivers folder and then go to Etc Folder, in the Etc folder you will see the hosts file. Now right click on hosts file and go to its properties, then go to security tab and then select your admin account, just below u will see an edit button (in front of change permissions), Now give the user full control and write and read rights and then click on apply and then click on Ok, now u will be able to edit the hosts file and save changes in it.

Step6: Now a notepad file appears something

Now copy the below lines of code and add to hosts file as shown above:

127.0.0.1 tonec.com
127.0.0.1 www.tonec.com
127.0.0.1 registeridm.com
127.0.0.1 www.registeridm.com
127.0.0.1 secure.registeridm.com
127.0.0.1 internetdownloadmanager.com
127.0.0.1 www.internetdownloadmanager.com
127.0.0.1 secure.internetdownloadmanager.com
127.0.0.1 mirror.internetdownloadmanager.com
127.0.0.1 mirror2.internetdownloadmanager.com

After adding these piece of code, save the notepad file. And exit from there. Now start your Internet download manager, and now you IDM has been converted to full version and specially when you update next time, your registration will not expire. That means it will remain full version for life time and you can update it without any problem.

There is no disk in the drive. Please insert a disk into Drive\Device\Harddisk1\DR1

i suppose these simple steps might help you;
start you computer
go to start button
run
type regedit (this will open the registry Editor )
go to HKEY_ LOCAL _MACHINE
SYSTEM
CurrentControlSet
control
windows( this will open  a list on the right side of the window)
go to error mode
this will open edit DWORD Value window
change the value data from 0 to 2
then change base to Decima then press ok button
then on the registry editor window, go to view tab and press refresh
close the window and restart your computer.
THE ERROR WILL BE SUPPRESSED.
THE PROBLEM OCCURS DUE TO AN INFECTION BY A VIRUS IN YOUR COMPUTER.
I HOPE THIS WILL SOLVE YOUR PROBLEM

Verifying License… AutoCAD not responding… Crash!

Posted on July 1, 2014 by simonbooth

Windows 10, Windows 7, Windows 8 and Windows 8.1 users (32bit and 64bit) – If you are encountering Autodesk licensing issues such as blank Authorization code (authcode) screens or even crashing on startup with messages like “Verifying license…” then “AutoCAD has stopped responding” when launching AutoCAD, it could be caused by:

1. The July 2014 Windows Security Update KB2962872
   1. these KB’s may also affect your system too – KB2943357, KB2977629 and KB2976627
2. You are using a version of Microsoft Internet Explorer which is not compatible with your version of AutoCAD

NOTE: If you are primarily seeing script errors, then first check out how to enable scripting support in IE 11
Here is a list of AutoCAD versions (and other similarly labeled Autodesk products too) that most likely will be affected…

• AutoCAD 2005
• AutoCAD 2006
• AutoCAD 2007
• AutoCAD 2008
• AutoCAD 2009
• AutoCAD 2010
• AutoCAD 2011
• AutoCAD 2012
• AutoCAD 2013
• AutoCAD 2014

Windows Security Update KB2962872
This update can causes all Autodesk products to crash on licensing verification specifically when using these newer versions of Microsoft Internet Explorer

• Internet Explorer 10
• Internet Explorer 11

You can very easily uninstall KB2962872 using these short steps:

1. Open your Windows Control Panel
2. Navigate to Programs
3. Click View Updates
4. Now search for KB2962872, if KB2962872 is listed there, simply select it in the listbox and then click uninstall
5. Let your machine take a while to think, now reboot.
6. Now try your Autodesk product again.

If the KB2962872 doesn’t solve the problem, these KB’s may also affect your system – KB2943357, KB2977629 and KB2976627
Another reason is that because you have Microsoft Internet Explorer 11 installed on your system. The solution is to rollback to Microsoft Internet Explorer 10, or maybe back as far as Internet Explorer 8
Failing that, I did find this link on the Autodesk website regarding ‘Script Errors in AutoCAD activation‘ – perhaps it helps  somehow.

PRI vs SIP Trunking – Main Differences

What are the Major Differences?

 PRI

• PRI (Primary Rate Interface) is a physical connection to the PSTN over a dedicated line that only serves voice transmission.
• PRI uses a circuit switched model for making voice connections between people
• PRI has a guaranteed Quality of Service (QoS)

SIP Trunking

• SIP (Session Initiating Protocol) Trunking is a virtual connection to the PSTN over a physical line that is often shared over your existing data connection.
• SIP Trunking uses a packet switched model for making voice connections between people
• SIP Trunking is typically Best Effort

Let’s Talk – PRI

A PRI is a single line (typically a T1 connection in North America) with 23 voice channels (and a single data/control channel), that allows your business to hold 23 calls simultaneously.  This is not always equivalent to the number of phone numbers a business has.  Your business may have 100 phone numbers that are directed to come across a single PRI, however, you will only be allowed to hold 23 phone conversations at once.

 

 

Let’s Talk – SIP 

In short, SIP Trunking is a method of sending your voice connection over an existing data line, and therefore is commonly referred to as VoIP (Voice over Internet Protocol).  

Your call goes out over the SIP Trunk, is treated exactly like every other piece of data on that connection and is not given priority over webpages, emails, or instant messages. 

 

  Once it arrives at your carriers network over the SIP Trunk, your provider’s equipment knows where to direct that call; this may either switch it over to the PSTN (so that someone with a regular phone can receive the call) or perhaps send it to a PBX at another location. A single SIP Trunk is typically limited only by the amount of bandwidth on your data connection, or in some cases, limited by the number of “call paths” you are purchasing from your SIP Trunk provider.