Lansweeper pulls processor information from the Win32_Processor WMI (Windows Management Instrumentation) class on the client machine itself. If WMI doesn't return the core information, which is likely the problem, there is nothing we can do about this unfortunately. There are some known issues with and fixes for WMI returning incorrect processor information for Windows Server 2003, which we've documented here and here as well, but I'm not sure these fixes apply to your situation as well.
Lansweeper pulls processor information from the Win32_Processor WMI (Windows Management Instrumentation) class on the client machine itself. If WMI doesn't return the core information, which is likely the problem, there is nothing we can do about this unfortunately. There are some known issues with and fixes for WMI returning incorrect processor information for Windows Server 2003, which we've documented here and here as well, but I'm not sure these fixes apply to your situation as well.