
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-08-2016 09:35 AM
Hi,
we have the following problem.
two Servers with the same mainbord typ and CPU Information.
for one server the information about cpu and numer of cores is correct. OS is Windows Server 2008 R2
for the other one the information about number of cores is missing. OS is Windows Server 2003.
Is this a problem of the os?
we have the following problem.
two Servers with the same mainbord typ and CPU Information.
for one server the information about cpu and numer of cores is correct. OS is Windows Server 2008 R2
for the other one the information about number of cores is missing. OS is Windows Server 2003.
Is this a problem of the os?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2016 08:44 PM
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.
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2016 08:44 PM
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.
