Re: SMS Working except Hardware/Software Inventory

Tech-Archive recommends: Speed Up your PC by fixing your registry

Thanks for the tip... I'm going to check that out as soon as I get a chance.

"Jeff Gilbert [MSFT]" <jeff.gilbert@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23DZc%23zjSHHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
So sounds like the clients are conducing inventory, that's good. Once the
inventory is completed on clients, they send up their inventory report the
management point (I'm assuming you're using Advanced Clients here), check
the MP_Hinv.log on the management point to see if it received the
inventory reports from the clients. The management point forwards the
inventory reports to the site server so then you can check the
dataloader.log file on the site server for record processing of the
inventory reports and adding inventory data to the site database. Once the
data is in the database, it should be viewable for clients via resource
explorer.

(This process may take some time--generally not long in a lab environment
though)

There is a tool called SMS Trace (trace.exe) in the SMS toolkit 2
(http://www.microsoft.com/technet/downloads/sms/2003/tools/toolkit.mspx)
that helps out reading log files--you can even read them in real time as
they are being updated. It's a little more user friendly than notepad :-)

Hope this helps,
--
Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation

This posting is provided "AS IS" with no warranties and confers no rights.

"Some Clown" <SomeClown@xxxxxxxxxxxxxxxx> wrote in message
news:%23hSobqjSHHA.600@xxxxxxxxxxxxxxxxxxxxxxx
Schedule is for once a day (just for testing) and the log doesn't show me
anything that looks like an error, though it's a bit hard to decipher...

"Jeff Gilbert [MSFT]" <jeff.gilbert@xxxxxxxxxxxxxxxxxxxx> wrote in
message news:%233bZFbjSHHA.3592@xxxxxxxxxxxxxxxxxxxxxxx
What is the schedule you set for the inventory actions to occur--after
you enabled the inventory agents? Do your client inventoryagent.log
files show any errors?

Thanks,
--
Jeff Gilbert, MCSE
Technical Writer | Windows & Enterprise Management Division
Microsoft Corporation

This posting is provided "AS IS" with no warranties and confers no
rights.

"Some Clown" <SomeClown@xxxxxxxxxxxxxxxx> wrote in message
news:Ol2FHVjSHHA.480@xxxxxxxxxxxxxxxxxxxxxxx
Apologies if that came across as too snippy... I've just wasted too
much time with this product already, and I'm getting a little punchy.
:)

"Some Clown" <SomeClown@xxxxxxxxxxxxxxxx> wrote in message
news:%23xXv7QjSHHA.1600@xxxxxxxxxxxxxxxxxxxxxxx
Yes, yes... good read, good tips.

I've tried reducing the cycle, changing the schedule, and initiating
from a client. It's all fun and exciting, but it doesn't work. To be
honest, I'm just evaluating the suitability of SMS replacing our
Track-it Server and at this point I'm not impressed. I appreciate the
insight, but "...is your computer plugged in" and "read the user
guide" aren't particularly useful to me... they're the equivilent of
what our help desk tells our users when they don't want to work on a
problem.

"Sean Cai [MSFT]" <v-secai@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:rLsTscaSHHA.2268@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

Thank you for posting in the Microsoft newsgroup!

From your post, my understanding on this issue is: the software
inventory
and hardware inventory are not working. If I'm off base, please feel
free
to let me know.

The software inventory and the hardware inventory run periodically.
By
default, it's a weekly job. On the server side, the only way to get
inventory information as soon as possible is to reduce the cycle (one
hour
minimum). However, this will generate massive network traffic.

You can initiate an inventory cycle on the client side manually. The
following article describes the detailed steps on forcing hardware
inventory on a SMS client. The steps of the software inventory are
almost
the same.
Scheduling Hardware Inventory
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/opsguide/ops_63kx.m
spx?mfr=true

I also recommend the SMS 2003 Operations Guide to you. It's very good
to
anybody whom is not familiar with SMS.

Please let me know if you have any other concerns, or need anything
else.

Have a great day!

Sean Cai, MCSE2000
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader
so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.













.

Relevant Pages

  • Re: Inventory Warnning!!
    ... It sounds like SMS is attempting to fix the problem by issuing re-sync ... Depending on how many clients you ... and send a full inventory to stop the re-syncs, ... Microsoft Systems Management Server ...
    (microsoft.public.sms.admin)
  • Re: SMS_DEF.MOF and new Hardware Inventory Info on SMS Server
    ... then a hardware inventory on that client. ... Checking HWinventory.log on the clients there ... On the sms server I copied the edited mof file to \SMS ...
    (microsoft.public.sms.admin)
  • Re: SMS SUS Distribute Software Updates - No Update type available
    ... CLASS - Process Class: Win32_PatchState $$<Hardware ... $$<Hardware Inventory Agent><Wed Mar 31 15:54:06.759 ... GMT Daylight Time> ... >> clients, wondering if the behavriour would be different ...
    (microsoft.public.sms.tools)
  • Re: Enable inventory of bitlocker drive status
    ... every one of our clients are all of a sudden missing the "Hardware ... Inventory Cycle" on the action tab. ... I also tried a fresh computer, installed the SMS client, and it does not ...
    (microsoft.public.sms.inventory)
  • Re: SMS 2003 MP and SLP
    ... -how frequently your run inventory and how large the inventory is ... An MP can handle up to 25K clients under normal load. ... You really should spend some time reading the deployment planning docs so ... SMS 2003 Technical FAQ: ...
    (microsoft.public.sms.admin)