![]() ![]() I still see your report being a "Custom Tool" you may have to build for yourself to be able to track your licensing for your environment but for the rest, we would have to see if Admin Arsenal sees value in this "User" tracking functionality for Inventory and Reporting. One of the many benefits to PDQ is that it sits right on top of "PowerShell" which, by nature, can see and do almost anything in a Windows Environment. ![]() "PDQ Inventory" does an amazing job of giving valuable insight into Software, Services, Registry, and Hardware Information but would need a totally different module and approach to manage "Individualized User Experience" on your machines if your users are moving from machine to machine often. That should satisfy the "is it possible" tooth even though it's not available just yet as a core function in "PDQ Inventory". You can't script against a "User" as they house nothing but an identity but you can script a "User" against your software and hardware giving the "User" a tailored experience. Assist customers in managing your assets more efficiently, the initiative would focus on topics, including login screen, motion sensor, Telnet, activity. Solid experience in Technical Operations and Supply Chain areas. My theory on why "PDQ Inventory" does not house this functionality, by default, is that "PDQ Inventory" and "PDQ Deploy" were designed to go hand in hand, for the most part, and are heavily geared toward management at the hardware level as this is the most "Static" thing to code/script against.
0 Comments
Leave a Reply. |