Loading

Follow Us

Follow us on Spiceworks

Subscribe by Email

Your email:

Browse by Tag

Current Articles | RSS Feed RSS Feed

(fr)Agile! It's a major award! Software deployment, redux.

  
  
  
  
Agility

When we decided to release the Pro version of PDQ Deploy one of the features that we were excited about was that it was "multi-user", meaning multi-admin. There are some other major features that differentiate Pro from its free step-brother such as scheduling and the all-important ability to run multiple actions within each Installer. But a funny thing happened on the way to the looney bin: Most of the feedback we have received showed that few cared about the multi-user and were more concerned with having to manage a new SQL server which, PDQ Deploy Pro required. "Whoa! Required? What's with the past tense?"

Heh heh, you don't miss much do you Eagle Eyes Keaton. Yes, we are removing the requirement to have a dedicated SQL Server installation.

You see, another goal that we, at Admin Arsenal, have is to be agile. We've made some great strides in achieving this goal and now we'll prove it.

We are going to release a new version of PDQ Deploy Pro that does not require a complex SQL Server to run. We will deliver a Pro version that has all the features that you love - quick deployments, multi-action, scheduling, bandwidth throttling, etc. - with the exception of being Multi-user. It was the multi-user feature that required the more complex SQL Server. By scrapping the feature that, according to our customers, wasn't going to be used anyway we are able to give you a much more manageable and intuitive software distribution tool.

You can expect to see this new version within the next few days. (Yes, days. Told you we were agile) We will put it out to a public beta and then give it a final release.

This change also serves notice that Hey, WE LISTEN TO YOU.

Let us know what you use in our products. What features would you like to see? What features do you think suck? To paraphrase Sam Kinison (I can't actually quote Sam since this, ahem, a PG rated blog) "Don't tell your mom! Don't tell your girlfriends! Tell US! We're the ones that [make the software for] you!"

Of course I'll contradict Sir Sam right now and say that if you like our software, please tell your friends, particularly your nerdy ones. Now go forth and deploy.



Follow us on Twitter @ShaneCorellian @AdamRuth @ShawnAnderson

Comments

i'm stuck at "authentication" step. 
i cannot test pdqpro1.3 from a workgroup test machine. 
seems to be necessary to join a domain. 
but why? pdqdeploy works beautifully from a machine in a workgroup.
Posted @ Monday, February 21, 2011 2:43 AM by joe
from two domain workstation. 
the installation return this Error: Unable to load DLL 'System.Data.SQLite.DLL': (Exception from HRESULT: 0x8007007E)
Posted @ Monday, February 21, 2011 3:00 AM by joe
Jumping on this right now! Thanks for letting us know.
Posted @ Monday, February 21, 2011 11:56 AM by Shane Corellian
1.3.0.2000 install fine. 
the new pro version still lacks of deployment credential's selection like the free. The why goes against my understanding.
Posted @ Tuesday, February 22, 2011 11:57 AM by joe
Glad 1.3.0.2000 installed fine for you. As far as the authentication issue, Pro uses a Windows Service to pass the deployment credentials. This is what allows you to schedule your deployments and have them executed without having to have the PDQ Deploy console running. You can change the service credentials from within PDQ Deploy Console by selecting the Manage PDQ DeployPro Service command from the File menu.
Posted @ Tuesday, February 22, 2011 1:08 PM by Shane Corellian
This limit is somewhat a hold-over from the previous versions of PDQ Deploy Pro which allowed for multiple users to start deployments from different consoles, as well as the scheduler which needs to be able to start deployments autonomously. The difficulty is in securely storing the credentials for use by different processes. 
 
We have as a high priority task for the next version of PDQ Deploy Pro to allow for multiple authentication credentials to be used for different sets of computers. This would allow for different workgroup or domain credentials to be used depending on which machine is being deployed to, even within the same deployment.
Posted @ Tuesday, February 22, 2011 6:14 PM by Adam Ruth
so, at the end, PDQ can be used for deployment in many domain and workgroup at same time. And the PRO version only in a single domain? I understand correctly?
Posted @ Wednesday, February 23, 2011 5:39 AM by joe
Yes, the current version of pro can only use one authentication identity at a time. If that identity has rights in more than one domain, then it can deploy to those domains.  
 
The next version will allow for multiple identities. 
Posted @ Wednesday, February 23, 2011 5:45 AM by Adam Ruth
Comments have been closed for this article.