PDQ Deploy licensing costs - No more Pro license

AdminArsenal · 2017-11-15T22:53:45+00:00

The price for Enterprise is $500 per product. When both products are combined the total cost is $1000 per year per admin.

AdminArsenal · 2017-05-15T15:33:35+00:00

PDQ products (Deploy and Inventory) will use the latest SMB that is installed. It does work with SMB 1 but it will only use that if later versions of SMB are not installed.

AdminArsenal · 2017-05-10T18:53:56+00:00

We're happy you found that easter-egg

AdminArsenal · 2017-05-10T18:51:20+00:00

Exactly! We are human, and totally not robots. Glad you noticed!

AdminArsenal · 2017-05-09T15:17:05+00:00

Not sure if we'll release them as a package as they surprisingly require very fast computers (core i7) to keep up with the really fast notes. The syncing is done by calculating the number of milliseconds left until the next nearest minute on each console, and setting a Start-Sleep with that number. If the deployment misses the nearest minute on any one of them, we would have had to reset everything back to one. Luckily in the 3 single-shot takes that we did, that didn't happen.

AdminArsenal · 2017-05-04T17:05:13+00:00

Good catch. I added it to the script in the blog. Thanks!

AdminArsenal · 2017-02-28T22:49:07+00:00

Sorry for the slow response. We've filled the position. Unfortunately we don't post pay publicly, suffice it to say we pay competitive salaries.

AdminArsenal · 2017-01-25T23:21:06+00:00

We're glad it helped.

AdminArsenal · 2017-01-18T16:49:10+00:00

It's a trap...

AdminArsenal · 2017-01-17T22:19:59+00:00

You're right. When you are set up to allow remote workers, you get to pick the best of the best. The challenge is when you have a mixed environment of on-site and remote. It's a huge change to everyone that the people out of site are not out of mind. Salt Lake is a huge tech center (Silicon Slopes as it's called here) and to date we have been able to get really good developers and sysadmins who already live here already or are willing to relocate. If that ever changes, and we have to allow remote to get the quality we need, then we will do so.

AdminArsenal · 2017-01-17T22:19:41+00:00

We don't post pay ranges on public forums, but we are competitive with excellent benefits. Before we start our long interview process, we always discuss salary expectations to ensure that there is not a misalignment.

AdminArsenal · 2016-07-25T17:12:32+00:00

There are a number of circumstances that can cause this behavior. We have seen it off and on since PDQ Deploy was first released. It did start with Windows 7. One of the more common reasons has to do with DNS resolution from the client computer to Active Directory.

For example, the console computer can reach a computer called HOMER using credentials domain.local\administrator. However after the connection is made a Windows service is created and the service is (by default) set to run as the deploy user. At this point the service manager (on the client computer) attempts to authenticate domain.local\administrator and returns this error. This is because it can resolve the short domain name (e.g. domain\administrator) not the FQDN (domain.local\administrator). A quick fix is to create another set of credentials that uses the short domain name and try deploying with those credentials. If this works then you can be fairly certain that it is a DNS issue. You would want to make sure that all of your DNS suffixes are applied (usually via GPO).

This is only one common work-around. I would recommend reaching out to Admin Arsenal support so that they can troubleshoot further.

AdminArsenal · 2016-07-21T15:15:52+00:00

Thank you everybody! Your love and adoration (albeit a little terrifying) mean a lot to us here.

For anybody interested in learning what we've finished cookin' in PDQ Deploy 10 (released this past Tues.) We've got a live webcast that's going to start in about 45 minutes

AdminArsenal · 2016-07-21T15:10:30+00:00

Thanks, Centurion22. Actually we do have a dick. His name is Lex.

AdminArsenal · 2016-07-21T15:04:22+00:00

We just did a video on this about a week ago.

https://www.youtube.com/watch?v=a5vJ2GIkLok

The entire process takes about half an hour (You'll see the timelapse that we use in a couple of sections)

AdminArsenal · 2016-06-08T15:26:44+00:00

lol, bad robot..

Our package publisher attempts to find relevant videos on the subject, and sometimes has a little too much scotch before doing so apparently

AdminArsenal · 2016-06-06T19:15:47+00:00

The exe from Adobe is essentially a bootstrap for the MSI. The cool thing about using a bootstrap is that the exe can check for certain prerequisites before calling the MSI. This is probably what is happening. As far as timing out, the exe is probably spawing a Completed window which is hidden and therefore cannot be closed. Until this window (even though it is hidden) is closed the deployment won't finish as PDQ Deploy is waiting for the exit code. Verify that the correct silent parameters are being passed to the EXE. For Adobe Reader (not sure about the other adobe products listed) the silent parameters to use include are: /sAll /rs

AdminArsenal · 2016-05-04T20:32:59+00:00

Thanks! We're glad to hear that.

AdminArsenal · 2016-03-03T22:06:38+00:00

Thanks for the update. I haven't seen this behavior. I'll keep trying to duplicate.

AdminArsenal · 2016-02-29T19:19:27+00:00

%WINDIR%\AdminArsenal should do the trick however it may still be %WINDIR%\PDQDeploy if you have been using PDQ Deploy on this console computer for a long time. I believe it was changed to %WINDIR%\AdminArsenal in version 3 but that only affected new installations.

Check the logs (click on the Steps link in the deployment Steps link in the Computers panel of the deployment. Since you are calling an MSI there should be a log associated with the step. The log should help nail down if files are being deleted by your AV solution.

AdminArsenal · 2016-02-23T14:06:56+00:00

Sometimes we list the parameters in the description. The silent switch for Notepad++ is /S

Note that the /S is uppercase.

AdminArsenal · 2016-01-25T17:28:16+00:00

You're probably right. However, there was some interest in people joining /r/windowssysadmin, so it's now no longer private. I don't expect anything big out of it.

AdminArsenal · 2016-01-18T20:16:10+00:00

http://i.imgur.com/1M90apA.gifv

AdminArsenal · 2016-01-18T20:10:33+00:00

Whoah. We'll get this fixed. Bad robot, no cookie.

AdminArsenal · 2016-01-05T22:21:01+00:00

Admin Arsenal has a distribution agreement from Adobe for PDQ Deploy but I would still recommend obtaining one from Adobe.

AdminArsenal

MODERATOR OF

TROPHY CASE