Skip to main content

Application Compatibility and OS Version

One of the issues that you may have when performing your application compatibility testing for your legacy applications to be moved to Windows 7 is the OS version.  Applications may query the OS version to determine how, or if to install.  Below is a chart provided by Microsoft on the different OS versions.

Operating System Version Number
Windows 7 6.1
Windows Server 2008 R2 6.1
Windows Server 2008 6.0
Windows Vista 6.0
Windows Server 2003 R2 5.2
Windows Server 2003 5.2
Windows XP 64-Bit Edition 5.2
Windows XP 5.1
Windows 2000 5.0

This may not be all that the application looks at.  Take a look at this data returned from the following PowerShell query.

Get-WMIObject Win32_OperatingSystem | Format-List *

The above PowerShell command will gather all the Operating System information on my Windows 7 client.  It then displays everything in a formatted list.  I highlighted the version number in the output below.

Status                                    : OK
Name                                      : Microsoft Windows 7 Ultimate |C:\windows|
FreePhysicalMemory                        : 1225908
FreeSpaceInPagingFiles                    : 3266376
FreeVirtualMemory                         : 4724380
__GENUS                                   : 2
__CLASS                                   : Win32_OperatingSystem
__SUPERCLASS                              : CIM_OperatingSystem
__DYNASTY                                 : CIM_ManagedSystemElement
__RELPATH                                 : Win32_OperatingSystem=@
__PROPERTY_COUNT                          : 63
__DERIVATION                              : {CIM_OperatingSystem, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER                                  : JASON-PC
__NAMESPACE                               : root\cimv2
__PATH                                    : \\JASON-PC\root\cimv2:Win32_OperatingSystem=@
BootDevice                                : \Device\HarddiskVolume2
BuildNumber                               : 7600
BuildType                                 : Multiprocessor Free
Caption                                   : Microsoft Windows 7 Ultimate
CodeSet                                   : 1252
CountryCode                               : 1
CreationClassName                         : Win32_OperatingSystem
CSCreationClassName                       : Win32_ComputerSystem
CSDVersion                                :
CSName                                    : JASON-PC
CurrentTimeZone                           : -300
DataExecutionPrevention_32BitApplications : True
DataExecutionPrevention_Available         : True
DataExecutionPrevention_Drivers           : True
DataExecutionPrevention_SupportPolicy     : 2
Debug                                     : False
Description                               :
Distributed                               : False
EncryptionLevel                           : 256
ForegroundApplicationBoost                : 2
InstallDate                               : 20100824184042.000000-240
LargeSystemCache                          :
LastBootUpTime                            : 20110115075916.782644-300
LocalDateTime                             : 20110116141146.331000-300
Locale                                    : 0409
Manufacturer                              : Microsoft Corporation
MaxNumberOfProcesses                      : 4294967295
MaxProcessMemorySize                      : 8589934464
MUILanguages                              : {en-US}
NumberOfLicensedUsers                     : 0
NumberOfProcesses                         : 107
NumberOfUsers                             : 2
OperatingSystemSKU                        : 1
Organization                              :
OSArchitecture                            : 64-bit
OSLanguage                                : 1033
OSProductSuite                            : 256
OSType                                    : 18
OtherTypeDescription                      :
PAEEnabled                                :
PlusProductID                             :
PlusVersionNumber                         :
Primary                                   : True
ProductType                               : 1
RegisteredUser                            : Jason
SerialNumber                              : 00426-068-1063837-86057
ServicePackMajorVersion                   : 0
ServicePackMinorVersion                   : 0
SizeStoredInPagingFiles                   : 3985976
SuiteMask                                 : 272
SystemDevice                              : \Device\HarddiskVolume3
SystemDirectory                           : C:\windows\system32
SystemDrive                               : C:
TotalSwapSpaceSize                        :
TotalVirtualMemorySize                    : 7970052
TotalVisibleMemorySize                    : 3985976
Version                                   : 6.1.7600
WindowsDirectory                          : C:\windows
Scope                                     : System.Management.ManagementScope
Path                                      : \\JASON-PC\root\cimv2:Win32_OperatingSystem=@
Options                                   : System.Management.ObjectGetOptions
ClassPath                                 : \\JASON-PC\root\cimv2:Win32_OperatingSystem
Properties                                : {BootDevice, BuildNumber, BuildType, Caption...}
SystemProperties                          : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers                                : {dynamic, Locale, provider, Singleton...}
Site                                      :
Container                                 :

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...