You have to watch out with triggering something like that in a task sequence. The client is set for an "Automatic (Delayed) Start", so you usually have to wait up to 5 minutes before you can trigger one of the policies after a restart. If you try to trigger it before the service starts, or right after the service starts, you'll get an error.
So it would only work if you don't have a restart right before it. On Tue, Apr 22, 2014 at 3:53 AM, Troy Martin <[email protected]> wrote: > If the thing being done to the collection of computers can be executed > by a task sequence, how about adding a wmic command to the last step in the > TS which executes the HINV for you? > > WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule > "{00000000-0000-0000-0000-000000000001}" /NOINTERACTIVE > > Here are other actions that can be triggered using wmic > > > http://sccmbrokeit.blogspot.com/2013/08/trigger-hardware-inventory-and-more.html > > Sent from my iPad > > On Apr 21, 2014, at 4:57 PM, "Daniel Ratliff" <[email protected]> wrote: > > Been thinking long and hard about this one Ryan, and finally found two > things I could use. Take that as a compliment that your tool does > everything else I need. J > > > > Schedule the tasks to go off. For instance, I may make a change to a > collection of computers, then kick off machine policy update for them to > get the change. Shortly after I need to run a hardware inventory scan > cycle. If I could do the machine policy change and then schedule the > hardware inventory scan cycle to go off say 10 minutes later that would be > very beneficial! > > > > The second thing to add would be the container location of whatever I am > clicking on, task sequence, collection, etc. That would be great! > > > > Thanks as always for the awesome tool. > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Beardsley, James > > *Sent:* Tuesday, April 15, 2014 10:26 AM > *To:* [email protected] > *Subject:* RE: [mssms] Help shape a right click tool! > > > > Looks good. I’d like to see logged on user and either cache available in > MB or % > > > > Looking forward to the new version! > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Ryan > *Sent:* Sunday, April 13, 2014 10:45 PM > *To:* [email protected] > *Subject:* Re: [mssms] Help shape a right click tool! > > > > Good idea. I just programmed it in. > > > > This is going to grab the information from the computer, not the server. > It gets the information from InventoryActionStatus in WMI under > root\ccm\invagt > > > > On Sun, Apr 13, 2014 at 6:32 PM, Eswar Koneti <[email protected]> > wrote: > > Last hardware inventory, that will help, when was the client contacted > site server. > > Regards, > Eswar Koneti > www.eskonr.com > > --- Original Message --- > > From: "Ryan" <[email protected]> > Sent: April 14, 2014 4:48 AM > To: [email protected] > Subject: [mssms] Help shape a right click tool! > > My next release of right click tools is coming soon, and I wanted to see > if anyone had ideas for one particular tool - System Information. In the > new version of this tool, users can pick and choose which columns they want > to show up when they run it. So I wanted to see if anyone had good ideas > for the system information tool columns. To give you an idea, here are the > columns you can pick from: > > > > Computer Name > > On/Off > > Last Restart Time > > Pending Restart > > Model > > OS > > % Cache Available > > % Cache Used > > Cache Available (MB) > > Cache Path > > Cache Size (MB) > > Cache Used (MB) > > Client Version > > Console User > > Domain > > IP Address > > MAC Address > > Site Code > > > > The point of the tool is to give administrators a quick way to grab live > information from a collection of computers. Can anyone think of things > they'd like to see in that tool or in general? Here is a screen shot of > the system information tool in action in case someone isn't familiar with > it: > > > > <image001.png> > > > > > > > > > ------------------------------ > > *IRS Compliance:* Any tax advice contained in this communication > (including any attachments) is not intended or written to be used, and > cannot be used, for the purpose of (i) avoiding penalties imposed under the > Internal Revenue Code or applicable state or local tax law or (ii) > promoting, marketing, or recommending to another party any transaction or > matter addressed herein. > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > > > > 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. > > > ------------------------------ > > > DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary > user of this email address. If you are not the intended recipient, please > delete without copying and kindly advise us by e-mail of the mistake in > delivery. NOTE: Regardless of content, this e-mail shall not operate to > bind 1E to any order or other contract unless pursuant to explicit written > agreement or government initiative expressly permitting the use of e-mail > for such purpose. > >
