Skip to content

Windows Server Datacenter 2-core compliance (System)

OctoSAM system query

This query is an integral part of the OctoSAM application. OctoSAM starts the query to display tabular data within the application. The query can only be started from within the intended application system context.

Windows Server Datacenter 2-Core compliance.

Metric scope and calculation logic

This query calculates license requirements for Windows Server Datacenter under the per core licensing model using 2‑core license packs for Windows machines that have the corresponding Software Item assigned.

For physical servers, it evaluates the licensing core count as the greater of the actual physical cores and 16 cores per server with a minimum of 8 cores per processor (socket), and for virtual machines it applies a minimum of 8 virtual cores per VM regardless of the configured vCore count.

It then determines the number of required 2‑core licenses per machine by dividing the licensing core count by two and rounding up, and consolidates these results together with the associated one‑time and recurring costs for the assigned Windows Server Datacenter 2‑core license.

Key rules for WindowsServer Datacenter licensing

Core-Based Licensing: Licenses are sold in packs of 2, 4, or 16.

Minimum Requirements: Even if a server has fewer than 16 cores, a minimum of 16 core licenses must be purchased per physical server. If a server has more than 1 processor, each processor must have at least 8 cores licensed.

Unlimited Virtualization: Licensing all physical cores entitles you to run the Datacenter edition on the physical server, plus an unlimited number of VMs/containers.

CAL Requirements: Client Access Licenses (CALs) are required for every user or device accessing the server.

Reassignment: Licenses can be reassigned to other servers, but generally not within 90 days of the last assignment. Alternative (Virtual Core): As of late 2022, you can choose to license individual VMs based on virtual cores rather than all physical cores on the host, requiring at least 8 cores per VM.

Datacenter edition is best for high-density virtualization, while Standard Edition is generally limited to two virtual machines.

Fields

Name Type Visible Description
Software Item ID numeric false OctoSAM internal ID of this SoftwareItem entity
Software Item Guid guid false OctoSAM internal Guid of this SoftwareItem entity
Software Item string false Name of the software item
Units numeric false
Initial Cost numeric false
Recurring Cost numeric false
Organization ID numeric false Internal ID that references the Organization entity (Foreign Key)
Organization Guid guid false Internal unique identifier for this organization that can be used for links from external systems
Organization string true Name of the organization
Organization Description string false Description
Environment ID numeric false Internal ID that references the Environment entity (Foreign Key)
Environment string false Name of the Environment
Organization Custom Field1 string false Available for custom data, not used by OctoSAM Inventory
Organization Custom Field2 string false Available for custom data, not used by OctoSAM Inventory
Organization Custom Field3 string false Available for custom data, not used by OctoSAM Inventory
Organization Custom Field4 string false Available for custom data, not used by OctoSAM Inventory
Object State ID numeric false Internal ID that references the ObjectState entity (Foreign Key)
Object State string false Object state name
Object State Octopus Id string false OctoSAM internal name for programmatic access to the object state (e.g. in queries)
Machine Guid guid false A unique ID that can be used to link to this machine object by external applications
Machine ID numeric false Internal ID for the Machine entity (Primary Key)
Machine Name string false Machine name (computer name)
Machine string true Use this name in reports for consistency and to avoid having to build the printable name from its parts
Alternate Name string false Contains the computer name for systems that may have different host and computer names, such as macOS
Fully Qualified Domain Name string false Fully qualified domain name as seen by the scanner through reverse lookup of the network address
Machine Description string false Description attribute of the directory service or manually entered during offline scan
Alternate Description string false Alternate description field specific to the scanned machine type. For example locally entered description in macOS.
Domain Name string false Windows NETBIOS Domain Name
Sid string false Computer SID
Last Scan Guid guid false GUID of the last imported .scan file for this entity.
First Scan date false Date/Time of first scan of this machine
Manufacturer ID numeric false Internal ID that references the Manufacturer entity (Foreign Key)
Manufacturer string false Normalized hardware manufacturer name
Raw Manufacturer string false Manufacturer of the machine as defined in WMI
Model string true Model of the Machine as defined in WMI
Bios Serial Number string false BIOS Serial Number as reported by WMI
Processor string false Processor Name as reported by WMI
Processor Speed numeric false Max speed of the processor in MHz
Number Of Processors numeric true Number of processors as reported by WMI
Number Of Cores numeric true Number of cores as reported by WMI
Number Of Logical Processors numeric false Number of logical processors as reported by WMI
Oracle Core Factor object false Oracle Core Factor to use for Oracle pricing. Queries should always use this field.
Physical Memory numeric false Amount of physical memory in the system as reported by WMI
Chassis Types string false ChassisTypes as reported in WMI in cleartext
Directory Last Logon Last Scan Diff numeric false
Custom Field1 string false Available for custom data for this machine, not used by OctoSAM Inventory
Custom Field2 string false Available for custom data for this machine, not used by OctoSAM Inventory
Custom Field3 string false Available for custom data for this Machine, not used by OctoSAM Inventory
Custom Field4 string false Available for custom data for this Machine, not used by OctoSAM Inventory
Virtual Machine bool true True if this is a virtual machine
Virtualization Host bool false True if this machine hosts virtual machines
Last Scan date true Date/Time of the last imported scan for this machine as reported by the machine (may be out of sync)
Cores For Licensing numeric false
Consumed Units numeric true
Machine Initial Cost numeric true
Machine Recurring Cost numeric true
Current Date Time date false Date and time the query was run. For reference if you use and save query results.

Query information

Property Value Description
Query Guid 0d2e6605-5b01-4926-b749-71881d536eee The internal id of the query. Must be unique
SupportsDesktop true If true, the query can be started from the OctoSAM Windows GUI
SupportsWeb true If true, the query can be started from the OctoSAM Web UI
LastUpdate 2026-04-07 18:06:51 Last change to this document
Build 1.12.4.25 OctoSAM build that last changed this document