Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

missing cpu speed and memory

5 views
Skip to first unread message

Scott

unread,
May 14, 2008, 2:38:37 PM5/14/08
to
Hi,

when i go to resource explorer to view cpu and memory, it seems roughly a
third of the clients are not showing this information, it doesn't seem to be
platform dependent ie , servers, workstations, win 2 k or xp or w2k3. is
there some place i should be checking?

thanks,

Scott


Samson Li [MSFT]

unread,
May 14, 2008, 4:34:07 PM5/14/08
to
On the client, check inventoryagent.log under windows\system32\ccm\logs.
Search processor and memory. Check if there is anything wrong there.


"Scott" <scott...@hydroottawa.com> wrote in message
news:%23mUK$FftIH...@TK2MSFTNGP02.phx.gbl...

Scott

unread,
May 15, 2008, 9:53:53 AM5/15/08
to
thanks,

I looked at the log and searched for memory and then processor, this is what
i found:

LOG[Unknown error encountered processing an instance of class SMS_Processor:
80041017]LOG]!><time="14:58:52.201+240" date="05-14-2008"
component="InventoryAgent" context="" type="2" thread="3788"
file="collectiontask.cpp:549">
<![LOG[Collection: (80041017) Execute: Query
failed]LOG]!><time="14:58:52.201+240" date="05-14-2008"
component="InventoryAgent" context="" type="3" thread="3788"
file="invcommon.cpp:190">


TotalPhysicalMemory, TotalVirtualMemory FROM
CCM_LogicalMemoryConfiguration; Timeout = 600
secs.]LOG]!><time="14:58:51.248+240" date="05-14-2008"
component="InventoryAgent" context="" type="1" thread="3788"
file="collectiontask.cpp:330">
<![LOG[Collection: Class "CCM_LogicalMemoryConfiguration" does not exist
out.]LOG]!><time="14:58:51.248+240" date="05-14-2008"
component="InventoryAgent" context="" type="2" thread="3788"
file="collectiontask.cpp:482">
<![LOG[Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS,
__PATH, __RELPATH, Description, Manufacturer, Name, Status FROM
Win32_NetworkClient; Timeout = 600 secs.]LOG]!><time="14:58:51.248+240"
date="05-14-2008" component="InventoryAgent" c


Was this what you were looking for?

Scott
"Samson Li [MSFT]" <sams...@online.microsoft.com> wrote in message
news:O0gncHgt...@TK2MSFTNGP03.phx.gbl...

Sherry Kissinger [MVP-SMS]

unread,
May 16, 2008, 6:53:04 AM5/16/08
to
Strong possibility: The way memory was reported changed from SMS2003 sp2 and
earlier to SMS2003 SP3. Are the clients which are not reporting correctly
SP2 or earlier clients, and your server is SP3? Upgrade the clients to match
to fix this reporting issue.
--
Standarize. Simplify. Automate.

Scott

unread,
May 20, 2008, 9:03:56 AM5/20/08
to
I reinstalled a OS on a server and installed the sms client and everything
is reporting fine, so I think the client is definetly the issue. How do i
push the updated client to the workstations/servers that aren't reporting
correctly?

thanks,

scott

t
"Sherry Kissinger [MVP-SMS]" <mofm...@smsexpert.com> wrote in message
news:F43457C3-84C3-49D1...@microsoft.com...

Scott

unread,
May 22, 2008, 7:58:13 AM5/22/08
to
As a update to my problem. I went to each collection and r.clicked > all
task > install client. this updated about half of the clients. So my
problem is not as bad as a week ago. However, the clients that arent
reporting mem and cpu are version " 2.50.3174.1152" the clients that are
reporting correctly are running version " 2.50.4253.3000"

So what is the correct way to get these clients updated.

Any help would be greatly appreciated.

thanks,

Scott


"Scott" <scott...@hydroottawa.com> wrote in message

news:uJA51mnu...@TK2MSFTNGP04.phx.gbl...

Sherry Kissinger [MVP-SMS]

unread,
May 27, 2008, 9:11:02 PM5/27/08
to
Here's what I would do... it's one of the things I do at every upgrade.

Create a Collection of computers where the client version = 2.50.3174.1152
That's your target.
Create a Package where the source is the files contained in the \sms\client
folder
The program is CCMSETUP.exe + whatever switches you have in the client push
properties, like SMSSITECODE=XYZ SMSCLIENTCACHE=5000 ... whatever you have.
Set to run "whether or not a user is logged in", distribute to all of your
DPs.

Advertise that package/program to that collection; and they'll upgrade. You
might want to put just a few computers in the collection to test the
package/program/Ad, and then add in the query for all the old clients.

0 new messages