RE: Since 2003 SP3 upgrade hardware inventory no longer reports me

Like Marcio mentioned, it may be your clients have not yet upgraded to the
SMS 2003 SP3 client. If you check the Systems Management applet, what is the
SMS Client Version? In looking at my own client (vista) it's 2.50.4253.3000
It's the .3000 which indicates SP3. If it ends in .2000; that's an SP2
client, .1000, an SP1 client.
--
Standarize. Simplify. Automate.


"Andrew E Chapman" wrote:

Thanks. I followed your advice and read the article, but couldn't see
anything out of the ordinary.

In looking through the inventory logs on one of the clients, though, I
noticed there were a number of warnings, and in particular:

Collection: Namespace = \\.\root\cimv2; Query = SELECT __CLASS, __PATH,
__RELPATH, Name, TotalPageFileSpace, TotalPhysicalMemory, TotalVirtualMemory
FROM CCM_LogicalMemoryConfiguration; Timeout = 600
secs. InventoryAgent 29/08/2007 5:02:16 PM 2728 (0x0AA8)
Collection: Class "CCM_LogicalMemoryConfiguration" does not exist
out. InventoryAgent 29/08/2007 5:02:16 PM 2728 (0x0AA8)

which seems like it might be relevant.

"Sherry Kissinger [MVP-SMS]" wrote:

Although it seems wierd that an upgrade to Server 2003 SP2 is the trigger for
the problem you are seeing, what I'd start with is to run through the tips
here: http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq02.mspx
specifically the ones under the "I would like to upgrade my site systems to
Windows Server 2003 sp1..." The resetting of the dcom permissions still
holds true for Server 2003 sp2.

PS: if you ever do a "site reset" of your SMS site, or uninstall/reinstall
the MP/Reporting Point, things like that; you usually have to run through
resetting the dcom permissions again. It trips people up a lot. If
resetting of dcom permissions doesn't seem to help, we can delve deeper into
the HW Inventory process; log files, your sms_def.mof, etc.
--
Standarize. Simplify. Automate.


"Andrew E Chapman" wrote:

I kind of figured it works properly for most people.

I did not knowingly restore anything; I did however upgrade from SP1
directly to SP3 (the modify date for my sms_def.mof is from this date). A
week later I also upgraded the server from Windows Server 2003 SP1 to SP2,
and I've just realised that the latest modified history dates in SMS -- when
the memory vanished from the inventory -- occured on that day and not the day
I upgraded SMS. Could Windows Server 2003 SP2 be responsible? At the same
time I also installed Business Desktop Deployment (BDD) 2007 - Patch 1 and
Windows Application Installation Kit.


"Sherry Kissinger [MVP-SMS]" wrote:

I know how horrible this sounds, but "it works for me". Just checked my lab;
Memory and processor look fine.

Question: when you upgraded, did you perhaps restore the sms_def.mof you
used for SP2 back into \inboxes\clifiles.src\hinv? There were some
significant changes in the sms_def.mof for SP3.
--
Standarize. Simplify. Automate.


"Andrew E Chapman" wrote:

After upgrading to SMS 2003 SP3, I have noticed that neither memory nor
processor are listed in the resource explorer. They are still there in
hardware history, but from the day I upgraded to SP3, the last entry in the
history displays a memory chip icon, but no information next to it. Other
elements of the hardware inventory are being reported properly. All site
systems appear to be functioning correctly in the system status area of the
console.

I've seen a couple of other reports of this problem on the net, but no
resolution. Any ideas please?
.

Relevant Pages

  • Re: SP2 Client upgrades
    ... Development SMS with SP2 successfully, however, in my readings, such as in the 'SMS 2003 SP2 Upgrade Checklist', I was under the impression that the clients do not automatically upgrade. ... With this information I prepared a package and found during my testings of my upgrade package push to one test client, ...
    (microsoft.public.sms.admin)
  • RE: Upgrading SMS 2.0 SP5 to SMS 2003 SP2
    ... multiple newsgroups. ... advanced client is different with the previous upgrading process. ... be used to control the client upgrade behavior in your site. ... upgrade automatically from SMS 2.0 to SMS 2003. ...
    (microsoft.public.sms.setup)
  • Re: Side by Side Upgrade of SMS 2003
    ... I have nothing in writing but I went on the official Managing SMS 2003 ... could just upgrade the client using a different site code. ... So you can control your upgrade using the client push installation ...
    (microsoft.public.sms.setup)
  • RE: Upgrading SMS 2.0 SP5 to SMS 2003 SP2
    ... advanced client is different with the previous upgrading process. ... be used to control the client upgrade behavior in your site. ... upgrade automatically from SMS 2.0 to SMS 2003. ... newer version of the Advanced Client software is available at the SMS site. ...
    (microsoft.public.sms.admin)
  • Re: SP3 install
    ... Sms 2.0 used to do this automatically and it was nasty in large environments. ... for all clients that have the old version and then install/upgrade the client agent. ... But I was hoping that this would have been an automatic process since the Primary and secondaries are already running the latest SP3. ...
    (microsoft.public.sms.admin)