Auto Deployment allows you to automatically deploy new versions of Auto Download packages as they become available in the PDQ Deploy Package Library. (Enterprise mode required.). While using Central Server, if the Server console is not connected to the Internet. This requires both PDQ Inventory and PDQ Deploy in Enterprise mode. If you are moving your database from one console to another, start here at Step 1 and review the following documentation Moving PDQ Deploy and/or Moving PDQ Inventory: 1. On the computer you wish to move the PDQ Deploy or PDQ Inventory console to, install the same version or higher of PDQ Deploy and/or PDQ Inventory you have installed on.

A reddit dedicated to the profession of Computer System Administration.Community members shall conduct themselves with professionalism.Do not expressly advertise your product.More details on the may be found.For IT career related questions, please visitPlease check out our, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read!Checkout the Users are encouraged to contribute to and grow our Wiki.So you want to be a sysadmin?Official IRC Channel - #reddit-sysadmin onOfficial Discord -. Hi guys, our team been asked to inventory a department of our company with around 50 computers and 1 server with AD. We have the servers administrator account and decided to remote log on the server, and install PDQ Inventory thinking it would be the best way to get a full inventory.

The thing is, PDQ prompt a PDQ window asking for an admin account / password, we typed in the servers administrator account and let the software run.We reported back to our boss, and he yelled at us saying that entering the company's server administrator password on a third party software (PDQ) was very risky and irresponsable regarding data security, that it was a security breach and that we have to quickly change all of the servers passwords (hundreds hours of work on the batch files and scheduled tasks.) or we can apply somewhere else.What do you think about that? Could PDQ retrieve our password and get the company in trouble?. To be clear, proprietary software cannot be open source software. For example, Microsoft has released the source code for MS-DOS v1.1 and v2.0, but it's still proprietary and not open source software, because its license restricts redistribution and lots of other things.Also, it's not that rare for proprietary software to have source code available: a fair number of proprietary, commercial internal web-based applications are written in an interpreted language like perl, PHP, python, ruby, or classic ASP, and those languages by design have to have the source code available. They don't necessarily have to be open source, though. PDQ.com here. As mentioned on this thread, we do use AES encryption to store all passwords.

4 keys are needed to decrypt the passwords (in the registry, database, application, and finally the windows machine key). All 4 must be valid in order to read the password. This is the reason that if our customers move their database to another machine, all credentials are unreadable and must be re-entered.That being said, it's smart to follow best practices.

As system administrators ourselves, we prefer to use dedicated accounts for 3rd party applications.If you have any questions, hit up our.

So I've got and the feedback has been sufficiently dismal that I've started looking into piecemeal alternatives, which I'd hoped to avoid.A couple of people have mentioned PDQ Deploy in the past, and its website certainly suggests that it's a great little product. But then again, so did the KACE website (and demo). PDQ's pricing is certainly quite nice, as is the free/trial option to evaluate it for ourselves. All the same, I thought I'd check and see if any fellow Arsians are using either product, and what their experiences are. I'd especially like to know about the Package Library; does it cover, say, the same range of applications you'd find on, and is it really as simple as downloading the package and deploying it?As ever, thanks in advance for the hive mind's knowledge. As is the free/trial option to evaluate it for ourselvesThere ya go. Deploy it on a test system and see if it works for you.

There's no better way to evaluate software. Specs could have omissions, sales people are full of it, testimonials can be faked or the people genuinely happy with the product have vastly different requirements than you, front end features may look fine but they may be classic ASP and back-end could be Access, etc etc etc./me: in the middle of a million dollar ERP migration. There's no way to test this ahead of purchasing licensing and going down the migration path blind. The sales sharks at a major software company had just been caught lying about their software capabilities. You don't say?! I posted in the kace thread and linked to a few programs we use. The PDQ Library repository they have is for the paid version sans maybe flash.

It is small anyway and consists of the common programs that are easy to setup for deployment yourself anyway.Its cheap enough it might be beneficial just to purchase to support these guys. On their forums they help people work around any limitations of the free version. Cpac imaging pro 5 keygen. Also buying looks to give you access to the inventory database.

If we didn't use OCS for inventory I would just use this.The program is so simple to use and doesn't require pushing any client agent you should just give it a test run. It has the ability to group pc's by various criteria (32/64, OS, etc, etc) It will give you status codes for what failed. You can group the pc's that failed the install and try just those later.The only drawback I find is although convenient not having an agent you get a small percentage of pc's you can't connect to. They have an faq for this but it tends to be mostly dns issues.Regardless of what program/interface you use for deployment I find you have to have a working msi file or batch file regardless and having a library of the common programs helps a little. I use PDQ Deploy and PDQ Inventory I actually introduced this to my previous company. It is a terrific piece of software we used it in conjunction with SCCM 2012.SCCM 2012 - Really good at deploy windows updates, software center is nice for HelpDesk users and employees that like to use it to get different software. Works really nice with Direct AccessPDQ Inventory (a lot easier to create queries on software and registry keys and files than in SCCM), its agentless could be a pro or con depending upon your environment.

Our helpdesk really took a liking to this over SCCM which I completely understand the computer details and applications are inventoried a lot better than SCCM. There is a bug in how SCCM inventories certain application such as ClickOnce applications are not inventoried correctly, PDQ picks this up without incident.PDQ Deploy - can deploy software to a specific machine without having to to deploy to a collection like in SCCM.

A lot of customization options and they are constantly updating the software and responding positively to feedback.Let me know if I can answer any more of your questions as I have a lot of experience with PDQ Deploy/Inventory and SCCM 2007 and 2012.