Re: missing cpu speed and memory

Tech-Archive recommends: Fix windows errors by optimizing your registry

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.
--
Standarize. Simplify. Automate.


"Scott" wrote:

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" <scottfranks@xxxxxxxxxxxxxxx> wrote in message
news:uJA51mnuIHA.5876@xxxxxxxxxxxxxxxxxxxxxxx
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]" <mofmaster@xxxxxxxxxxxxx> wrote in message
news:F43457C3-84C3-49D1-BB13-FCCD65AF65C4@xxxxxxxxxxxxxxxx
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" wrote:

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]" <samsonli@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:O0gncHgtIHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
On the client, check inventoryagent.log under
windows\system32\ccm\logs.
Search processor and memory. Check if there is anything wrong there.


"Scott" <scottfranks@xxxxxxxxxxxxxxx> wrote in message
news:%23mUK$FftIHA.5832@xxxxxxxxxxxxxxxxxxxxxxx
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











.

Relevant Pages

  • Re: ISA Restict Internet Question
    ... While I totally agree that they should upgrade to XP Pro here is one way to ... to prevent those computers from accessing the internet. ... His only problem is that he has a few clients that are running XP Home ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS Not Yet Reported
    ... Small Business Server Update Services Client Computers Policy ... updating the clients. ... I've found a few postings where no clients are reporting but nothing on ...
    (microsoft.public.windows.server.sbs)
  • No Inventory on Newly Discovered Clients
    ... portion of my clients were not reporting HW or SW inventory. ... SP1, every client then started reporting inventory correctly. ...
    (microsoft.public.sms.inventory)
  • Re: Windows Updates - WSUS resolution 0x80248008 error
    ... All our xp and w2003 clients are picking up their updates. ... We have a WSUS server V2 happily getting updates from a parent server, the client WSUS settingsare are configured in an OU policy. ... We have a problem with the XP clients not reporting their status in the WSUS web browser - our servers do show which updates are required. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Unable to Send and Receive Mail
    ... The error you are reporting is from the Outlook client. ... Any errors reported in the application log on the Exchange server? ... Is it possible for you to configure your clients not to be POP3 clients? ... contact your server administrator or Internet ...
    (microsoft.public.exchange2000.connectivity)