103 is for discovery data collection and it comes when you enable heartbeat discovery after the policies applied.do you see the agent from configuration manager applet on the client ?
Sent From Galaxy Note, please excuse any typo's as result. www.eskonr.com --- Original Message --- From: "Jason Wallace" <[email protected]> Sent: November 14, 2013 12:21 AM To: [email protected] Subject: RE: [mssms] Trigger Discovery Hey Roger Thanks for coming back to me on this one. I think that you have a really good point. There really is no discovery enabled in this environment, which was the design as implemented. I was expecting that a workstation joining SCCM regardless as to its status would have been able to issue a discovery regardless as to the status of the heartbeat discovery. Or does HB being enabled affect client policy to turn this on? Jason From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 13 November 2013 14:46 To: [email protected] Subject: RE: [mssms] Trigger Discovery Hi Jason What kind of Discovery-Methods are enabled on your site ? Do you have Heartbeat Discovery disabled (it's enabled by default)? Without Heartbeat Discovery, you will not see the "Discovery Data Collection Cycle" on your Agents. Regards Roger From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Mittwoch, 13. November 2013 12:15 To: [email protected] Subject: [mssms] Trigger Discovery Howdy folks I'm planning to ask what could very well be the dumbest question of the week so here goes: We have SCCM 2012 SP1 deployed (no CUs) and we do not have any form of server side discovery. I am getting into a state where discovery records for some computers are ending up with BLANK MAC addresses. As you can imagine this is having a somewhat interesting effect on my OS build task sequences! So, I thought why not trigger a discovery from the client to ensure that the MAC address is correct but it errored. When I then went through the list of available actions: Software Metering Usage Report Cycle Action ID: {00000000-0000-0000-0000-000000000106} Request & Evaluate Machine Policy Action ID: {8EF4D77C-8A23-45c8-BEC3-630827704F51} Updates Source Scan Cycle Action ID: {00000000-0000-0000-0000-000000000113} Request & Evaluate User Policy Action ID: {3A88A2F3-0C39-45fa-8959-81F21BF500CE} Hardware Inventory Collection Cycle Action ID: {00000000-0000-0000-0000-000000000101} Software Inventory Collection Cycle Action ID: {00000000-0000-0000-0000-000000000102} Application Global Evaluation Task Action ID: {00000000-0000-0000-0000-000000000123} Software Updates Assignments Evaluation Cycle Action ID: {00000000-0000-0000-0000-000000000108} MSI Product Source Update Cycle Action ID: {00000000-0000-0000-0000-000000000107} Standard File Collection Cycle Action ID: {00000000-0000-0000-0000-000000000104} and the famous 103 entry n'est pas la So - where has it gone? how do I get it back? See - told you. Dumb question
