

Consult your licensing professional for guidance on how to downsize processors for a system if necessary. Note: In most situations, using the System Configuration Tool to specify a limited number of processors is not an acceptable licensing workaround for per-processor situations.

The System Configuration Tool will not distinguish between sockets and cores, however you may need to intervene to the server's BIOS to limit cores or hyperthreading. By using the System Configuration Tool, you can quickly step down to a fewer number of processors on the system via a soft configuration. For physical systems, this can save unnecessary handling of the internal parts of the server and sensitive processor components. In a virtualized environment, this is pretty straightforward, as you would provision processors to the virtual machine upward or downward. This is useful for one main reason: determining if lesser performance is acceptable on a system to conserve resources. Here I can step the system down from the current inventory of visible processors (four) to any number less than that.

Figure A shows the system running the System Configuration Tool. In the following example, the server has one physical processor with four cores. By clicking the Advanced Options button, you edit the number of processors that are visible to the operating system on boot. System Configuration (or msconfig.exe) has a Boot tab that allows an interactive edit of the Boot.INI file. I've used this utility to step-down processors on a Windows Server. Might be just my platform but if not it seams that there linked in pairs and not working correct if not both are active or diabled.Īnd for Andrews problem, i would gess it´s due to overload, try run with 2 cores and i bet it will work, or try run 1 core + failsafe start with minimal setting to lower load on core.Most versions of Windows Server have the System Configuration Tool, which shows a number of configuration items for the local system. When i tried disabling inbetween a row i ended up getting unstability during stress tests. Tried running just the game with a set amout of cores but didn´t work, Then i tried a couple of different settings with either windows 10 controlling tru boot settings or directly tru bios, and i found that running an 8 core AMD processor at 1 core made the whole platform unstable and not working due to overload. Tried some dif changes mainly to get an old game called Call of Juarez to work, it has issues with 8 cores but works with 1 to 6 cores.
