Take a look at inventoryagent.log. -----Original Message----- From: Roland Janus [[email protected]<mailto:[email protected]>] Sent: Tuesday, June 23, 2015 05:43 AM Eastern Standard Time To: [email protected] Subject: [mssms] hardware inventory not triggered on new client installation
I have that same issue on two 2012 R2 SP1 installations and never noticed that before: The schedule for hw inv is set to once a day (regular, not custom). When installing a system using OSD the ddr is sent right away, but hardware inventory isn’t (software inv is empty). The action is available, so it knows that it needs to or at least that it is enabled, I can trigger it manually and it works fine then but unless I trigger it manually it just sits there . The same happens when installing the client on existing machines. Not on all of them but some. (given they are a mess and will be refreshed later on) But as it seems to have the policy, why isn’t it triggering it right after the agent install or OSD? I’ve never noticed that behavior on previous versions (I think) -R The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
