Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

My thoughts on PDQ and our challenges

I work in a medium-sized company with several IT departments, all of which are responsible for different subcontractors. Everything is in an AD structure. After years of struggling with applications like FCS or Matrix42, PDQ shined with simplicity and with the easy options in the inventory to do certain analysis, it is just right for us in many aspects.

Now let's move on to the challenges. On the one hand, there is licensing. I can evaluate these with PDQ conditionally. Nice. But what about, for example, a second right of use? Where can I store and link the OEM documents / keys / photos? I know, PDQ was never intended for this.

But in larger companies, documentation cannot be avoided. And what I can't stand at all is a bunch of individual systems that can all do something, but nothing really well.

Now it would normally be quite easy to use the PDQ database and extend the whole thing with a few columns and a web interface, where you can then tinker with a few workflows using forms (from the computer being handed over to the user, to the installation of software initiated by the user himself).

Unfortunately this doesn't work either, because the database is SQLite and external access is a problem...

Why can't my CTI software tap PDQ and recognize the user and their hardware based on the information from AD?

 

So many questions... so many stop signs. What are your thoughts on this?

2

Comments

1 comment
Date Votes