arrgggg

Deploy is so aggravating to use!

First, I am an infrequent user. I have one program that needs simultaneous updating on about 25 computers across 3 sites, two or three times a year. Each time I use Deploy it is a new fight to make it work. My process to date is to start with Inventory, get all the computers in the list, run Inventory and get all the passwords and systems setup correctly until Inventory works without issues. This works.

Then I open Deploy, and deploy the package using the computer list from Inventory. Except, to my surprise, none of the passwords changes I make in Inventory were used in Deploy. Why in the name of Jesus are these programs not linked better together. Deploy had none of the password changes from Inventory. So the package deployment failed on half of the computers, leaving the whole system half setup... and totally unfunctional. Thanks. (read extreme sarcasm and frustration). Now, you have to go thru each failed computer and re-setup the correct password, then deploy again. Instead of a single deployment list with all the computers status, I have 10 individual deployment records... I literally had to write a checklist using paper and pencil to verify all the computers were updated. Perfect.

Go ahead, ask me what version of Deploy I'm using. An old one! Why, the last time I upgraded Inventory and Deploy it erased all my computer lists, and I had to start totally over. So, NO, I am not upgrading.

And now, add to the list; passwords. Now I need to all the computers have the same admin password so I can run Deploy. Perfect. This is really saving a lot of time for me!

Yes, I'm using the free version. I see no reason to pay for frustration.

The Front Climbing Club, yes, right here is SLC. Roger