This is most commonly caused when the agent server has CPUs with Hyperthreading or dual cores. Windows tracks each core (including the hyperthread) as a single CPU so it will appear as 2 CPUs within up.time.
|
Installing the up.time agent on Windows | Rating | Views | |
---|---|---|---|
![]() |
By: uptime Support | Date Created: 6-12-2006 | Last Modified: 7-25-2011 | Index: 079 |
![]() ![]() ![]() ![]() ![]() |
6935 |
Enabling Debugging in the Windows Agent | Rating | Views | |
---|---|---|---|
![]() |
By: uptime Support | Date Created: 10-14-2005 | Last Modified: 7-6-2011 | Index: 010 |
![]() ![]() ![]() ![]() ![]() |
5643 |
VMware ESX client and up.time show different memory values | Rating | Views | |
---|---|---|---|
![]() |
You may notice that the VMware Virtual Infrastructure Client memory graph doesn't match the memory values shown in up.time. This is because the default VMware graphs display a different metric than... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 312 |
![]() ![]() ![]() ![]() ![]() |
3500 |
Stopping and Starting the Windows Agent | Rating | Views | |
---|---|---|---|
![]() |
By: uptime Support | Date Created: 10-24-2005 | Last Modified: 7-7-2011 | Index: 016 |
![]() ![]() ![]() ![]() ![]() |
5055 |
Does the Windows agent support 64-bit systems? | Rating | Views | |
---|---|---|---|
![]() |
By: uptime Support | Date Created: 6-12-2007 | Last Modified: 6-28-2011 | Index: 183 |
![]() ![]() ![]() ![]() ![]() |
3207 |