Jimmy, that sounds like a great concept. Can you share example on how you use it?
Thanks Cesar On Dec 12, 2014 8:19 AM, "Jimmy Martin" <[email protected]> wrote: > I use this to get a workstation use pattern ‘fingerprint’.... can be very > cool and you can also use the data find non use applications for potential > license reclamation. > > Sent from Windows Mail > > > Jimmy Martin > (901) 227-8209 > > *From:* Miller, Todd > *Sent:* Friday, December 12, 2014 10:15 AM > *To:* [email protected] > > > There was some discussion about Software Inventory recently and about > looking for alternatives due to its resource intensive nature on the client > – and the amount of (useless?) data sent to the DB. > > > > In looking for an answer to another problem, I tripped over this post by > Sherry and Garth (thanks!) on Technet Forum that had another suggestion for > inventorying applications. It is to use the CCM_RECENTLY_USED_APPS view. > > > > I can’t believe I’ve been doing SCCM for as long as I have without knowing > about this view. It would for the most part get rid of my need for SW > inventory. It is not *exactly* the same as SW Inventory – it only > inventories recently used (a few months) executables, and it won’t detect > unused executables at rest on the computer but it is comprehensive and will > detect applications being run not only from the Program Files area, but in > the user space too. > > > > the post is here… > > > > > https://social.technet.microsoft.com/Forums/en-US/43d1ed69-53f6-434d-838d-1a1024f1b80b/specific-software-title-not-displayed-in-inventoried-software-but-is-listed-in-software-metering?forum=configmgrinventory > > > > > > > > > > > > > ------------------------------ > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is > confidential and may be legally privileged. If you are not the intended > recipient, you are hereby notified that any retention, dissemination, > distribution, or copying of this communication is strictly prohibited. > Please reply to the sender that you have received the message in error, > then delete it. Thank you. > ------------------------------ > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the > foregoing messages, and delete it immediately. > > > P *Please consider the environment before printing this email...* > > >
