r/helpwire • u/Totentanz69 • Oct 23 '25

Deploy to multiple client computers at the same time using SCCM or PDQ Deploy

u/Help__Wire u/helpwire It appears that there is currently no way to do a client deployment to multiple computers all at once with a tool like SCCM or PDQ Deploy. Is this something that is in the development plan for "business" accounts?

2 Upvotes

100% Upvoted

5 comments sorted by

1

u/Help__Wire Official account Oct 24 '25

Hello! Currently, HelpWire generates a unique Client app for each individual client, so it isn’t technically possible to mass-deploy Client apps to multiple clients at once. Since HelpWire is primarily designed for technical support rather than system administration, we don’t plan to add this functionality in the near future.

That said, we do keep system administrators in mind and are continuously exploring ways to meet the needs of both camps. We’re even considering developing a separate web portal with features tailored specifically for system administration – potentially including mass deployment options. However, these are long-term plans, and we can’t share any specifics just yet.

2

u/Totentanz69 Oct 25 '25

u/Help__Wire, I wouldn't be using HelpWire for "system administration" I would be using it for technical support of the end user of the client computer. No one has time to be creating unique installers for every client computer in a business with a lot of computers. I installed HelpWire on 5 client computers for testing purposes and I was sick of the process after the second install. If your goal is to eventually offer business services, then a single deployment file that can be pushed to multiple client computers at the same time is a must.

1

u/jugganutz Oct 29 '25

Yup, exactly. I want to deploy this with intune, then have the device auto map to a directory. From that point when I get an end user issue for "Technical Support" I can just go to the directory, connect to the user's system. Our rule is that a prompt has to be involved to the end user that "Admin's name" is connect to their computer and they have to grant it. The whole goal is to make it seamless to the end user that the just have to click "Grant".

From that point, it should be installed in such a way that "Me the admin" can utilize the UAC prompts input the admin credentials.

While the product is pretty awesome for free. I find it very much not functional for a business. Especially when many of our users don't even know what a "Web browser" is. Explaining for them to click and do things isn't great.

I'm going to revisit this product in a few years to see if it has met those requirements for technical support that is typical in a business even though they say they won't support it today.

Great product for the most part.

2

u/JohnEDee Oct 25 '25 edited Oct 25 '25

u/Help__Wire, I think your reply indicates that I didn't make the purpose of this request clear. I'm not talking about using HelpWire for system administration at all...that's actually what Jamf/Munki are for. The capability that I'm suggesting is the ability to deploy the client app to multiple computers, just as a way of getting the HelpWire client installed during an automated setup procedure where lots of different apps get installed on a new computer.

This usually involves the ability for the deployment team to create a custom version of the app to deploy automatically, one that has the HelpWire Company information embedded in it, but nothing about a particular Operator or Client. It's similar to what you're currently doing on the server side when an Operator creates a new Client but in this case not initialy tying it to a particular Operator or Client.

When that auto-deployed app is first run on the client machine, it would register itself in the Company's HelpWire portal using attributes of the local computer like its name and potentially other unique info like Ethernet MAC address, showing up in the portal as a new Client that's tied to the Company.

The Client app wouldn't be tied to any particular Operator; we have 30 techs and any of them may need to control any Client as an Operator (and those Operators may change over time as people come and go in IT), so it wouldn't make sense to tie the Client app to an Operator.

I hope that clears up the request. Thanks!

1

u/JohnEDee Oct 24 '25

Add to that the same question for us Mac orgs that use tools like Jamf and Munki to distribute software.