Where did you pull this list? From the client COM object on one of your 
machines?

-Daniel Ratliff

-----Original Message-----
From: Jason Wallace [[email protected]<mailto:[email protected]>]
Sent: Wednesday, November 13, 2013 06:16 AM Eastern Standard Time
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


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.

Reply via email to