TL;DR: Choose a software deployment approach based on how your devices connect, which operating systems you support, and how much infrastructure your team wants to maintain. On-prem tools offer tighter control for local Windows environments, while cloud-based deployment makes it easier to reach remote, roaming, and mixed Windows and macOS fleets without a VPN.
On-prem software deployment is best for domain-joined, workgroup, or otherwise reachable Windows devices on a local network or VPN. Remote or cloud deployment is best for distributed and hybrid teams managing internet-connected Windows and macOS devices, including endpoints that regularly move between office and home networks.
The right model depends on device location, operating systems, network access, security requirements, and licensing. Some organizations will choose one approach. Many hybrid teams will use both. The comparison below shows where each model fits.
What is on-prem software deployment?
On-prem software deployment runs from infrastructure your organization hosts and manages. It gives IT direct control over the deployment server, data, network access, and workflows, but your team is responsible for setup, maintenance, security, backups, and availability.
What is remote software deployment?
Remote software deployment uses a cloud-hosted console and an endpoint agent for remote deployment. It is best suited to remote or hybrid fleets because devices can receive inventory scans, packages, scripts, and other tasks without connecting to the corporate LAN or VPN.
Because the agent communicates with the cloud over the device’s existing internet connection, IT teams can deploy software, run scripts, and collect endpoint information without requiring the device to connect to the corporate network or VPN. Pending tasks are retrieved when the device reconnects to the internet.
Cloud software deployment solutions are fully managed and maintained by the solution provider. It’s like ordering pizza at a restaurant. You don’t have to deal with messy ingredients or watch the oven constantly to make sure that your crust is baked to perfection. And you don’t even have to clean up after. All you need to do is sit back and enjoy that cheesy, savory goodness — AKA using a software deployment tool that you don’t have to build or maintain yourself.
How do on-prem and remote software deployment compare?
On-prem and remote deployment tools differ most in reachability, control, setup, operating system support, and licensing. On-prem tools fit devices that are reliably reachable on the corporate network. Remote tools fit devices that connect from many locations and need to be managed over the internet.
Factor | On-prem: PDQ's solution | Remote or cloud: PDQ's solution |
|---|---|---|
Operating system support | Windows workstations and servers | Windows and macOS endpoints |
Device location | Best for devices regularly reachable through the LAN or VPN | Best for devices connected from offices, homes, field locations, and other internet connections |
Mixed-OS management | Requires an additional workflow or platform for macOS devices | Manages supported Windows and macOS deployment workflows from one console |
Commands and scripts | Runs Windows scripts and commands on reachable endpoints | Runs Windows commands and scripts, plus supported shell commands on macOS |
Software patching | Deploys Windows software packages and updates | Automates supported Windows and macOS application deployments and updates |
Inventory | Detailed Windows inventory for reachable endpoints | Centralized Windows and macOS device and software visibility |
Manage Windows & macOS devices from anywhere
With PDQ Connect, get real-time visibility into remote and local devices, deploy software, remediate vulnerabilities, automate routine maintenance, and remotely troubleshoot endpoints from one easy-to-use platform.
When should you use a remote deployment tool?
If you’re managing remote or off-site devices and you don’t want to use a VPN, a remote tool will work best. But there are other considerations, too.
Remote deployment tools are often less expensive than setting up and operating an on-prem solution, and they scale more easily if your company is growing quickly. But on-prem tools offer you much more in-depth control and customization. We’ll break down the details behind these deciding factors.
Security and availability
On-prem: On-premises software lives in self-managed, private environments that are often perceived as more secure. But this also means that organizations are entirely responsible for their own security measures, from setting up firewalls to regular software patching. They must also design redundancies to serve as backups in case of technical disruptions that could cause significant downtime.
Cloud: With any cloud solution, a third-party provider is responsible for ensuring security and service availability. They are hosted on public cloud platforms that have invested heavily in security with robust safeguards and features in place. Some cloud services come with specialized security features that can be expensive for organizations to implement themselves. Service-level agreements between customers and solution providers help ensure solution availability and uptime.
Control and customization
On-prem: In on-prem environments, companies have complete control over their data, hardware, and software. They can configure, upgrade, or change their server hardware, applications, and workflows to meet their needs. Systems can also be designed to meet compliance standards around data protection and sharing.
Cloud: Cloud solutions may offer only a specific set of customizable options that are built into the product design. This may be enough for some sysadmins, but not for others with more complex needs. It’s like building your own pizza from a restaurant menu with only 10 toppings to choose from versus making one yourself with any ingredient you want. When using services like cloud storage, you also get less technical control. For example, data encryption keys could reside with the cloud provider.
Cost
On-prem: On-prem software deployment costs usually include administrator licenses, infrastructure, maintenance, power, storage, and staff time. Organizations with existing servers and a small number of administrators may find this model cost-effective, especially when one license can cover many endpoints.
Cloud: Cloud software deployment costs usually scale with the number of managed devices or users. This model reduces the need to host and maintain deployment infrastructure, but costs can rise as the fleet grows. Bundled software licenses, devices per user, and subscription minimums can also affect the total price.
Scalability
On-prem: When you’re managing on-prem physical servers, it can be difficult to scale your operations. This expansion usually requires purchasing and deploying new servers to support future growth — and in-house IT staff to handle the upgrades and expansions.
Cloud: On-demand cloud solutions are more scalable. Service plans can be modified easily to cater to increased usage. This allows organizations to grow quickly with fewer logistical constraints.
Different strokes for different folks
On-prem: If you already have the necessary IT infrastructure in place and most employees are working in person at the office, an on-prem software deployment solution would be a natural choice. And if you've set up your corporate VPN, you can even manage remote devices.
Cloud: Cloud or remote solutions can be used to manage any device as long as it’s connected to the internet. For sysadmins supporting hybrid environments, you can use a remote software deployment solution to support on-prem and remote machines from one platform.
Which software deployment model is best for your organization?
Whether you opt for an on-prem or a cloud solution depends on factors like the kind of industry and users you support, your existing IT infrastructure, and your IT management style. Consider these factors.
Cloud migration can feel very overwhelming. Using a SaaS-based or cloud-based solution can provide critical advantages without involving a complete overhaul of your IT architecture.
Industry
Some industries like finance and government are more tightly regulated than others. Air-gapped organizations with strict compliance policies may not be allowed to use public cloud services or solutions.
Workforce
If you’re supporting a fully remote or hybrid workforce, cloud-based solutions are an ideal way to centrally manage employee devices, no matter where they’re located.
Existing infrastructure
Organizations that have already invested heavily in existing on-prem IT infrastructure and equipment may prefer to build on what they have rather than pivot to the cloud.
Resources
Do you have the time and budget to set up, upgrade, or configure in-house hardware and software? Or do you need a solution that you can just install and get started on right away? If the latter, we recommend a cloud-based deployment solution.
IT management approach
Some IT teams prefer to have full control over their corporate infrastructure and networks. By choosing to build on prem, they can decide how to design their setup, what technologies to use, and how it’s implemented to solve specific problems. Love being in control? Stick with on-prem deployment solutions. Prefer quick and simple? Consider a cloud option.
Can on-prem and cloud deployment tools work together?
Yes. PDQ offers both on-prem and cloud software deployment solutions, and IT teams can use them together. On-prem deployment uses infrastructure your organization hosts and maintains, while cloud deployment manages internet-connected devices online without requiring local deployment infrastructure.
A practical split might look like this:
Use on-prem deployment for Windows endpoints, servers, air-gapped networks, and environments that require locally hosted infrastructure or LAN-based management.
Use cloud deployment for internet-connected Windows and macOS devices, whether they are in the office, at home, or in the field.
Use both when different devices, networks, or security requirements call for different deployment methods.
Standardize testing, approvals, maintenance windows, and reporting across both workflows where possible.
The two approaches are not limited to separate office and remote environments. Cloud deployment can manage on-prem devices as long as they have internet access, allowing IT teams to choose the method that best fits each device or use case.
How do you deploy software to Windows and macOS devices in a hybrid environment?
IT teams can deploy software to Windows and macOS devices in a hybrid environment by using a cloud-based platform that communicates with both types of endpoints over the internet. This allows teams to install applications, automate software updates, and run deployment scripts without requiring devices to connect to the office network or VPN.
With PDQ, IT teams can:
Deploy supported applications to Windows and macOS devices from one console.
Create custom deployment packages for software that is not available in the Package Library.
Automate application updates across supported Windows and macOS endpoints.
Run PowerShell or command-line deployment steps on Windows and shell commands on macOS.
Target deployments using device and software inventory data.
Deploy software to office-based, remote, and roaming devices over the internet.
This approach can be especially useful for small IT teams transitioning from a primarily Windows environment. Instead of creating a separate software deployment process every time another Mac appears, the team can use consistent packaging, automation, and scheduling workflows across both operating systems.
For a detailed workflow, see how to manage Macs in a Windows shop without Jamf.
How do you choose a remote software deployment tool?
If you’ve decided to go with a remote deployment solution, you’ve still got to pick one of the many different types of cloud-based solutions in the market today.
The right remote software deployment tool should match your operating systems, security requirements, automation needs, reporting needs, support expectations, and budget. Small IT teams should prioritize a platform that combines inventory, software deployment, automation, reporting, remote commands, and troubleshooting in one console. Reducing the number of separate workflows can make it easier to manage a distributed or mixed-OS fleet without adding specialized administrators.
Evaluate the following factors before committing to a platform.
Ease of setup and use
Avoid solutions that require complex configurations or integrations with other software to do what you need it to do. Better to know up front what functions you need — and choose the service that can do it all.
Reliability and performance
Set clear benchmarks and enforceable clauses in your contract or service-level agreements to hold solution providers accountable for reliability and performance. If you’re going to trust a third party, make sure they can do everything you need them to.
Security features
Look for solution providers that use established security standards and frameworks, and make sure to review their System and Organization Controls (SOC) reports.
Free trials or demos
Always try before you buy. Explore key features and functionalities through free trials and demos to see if the solution meets your requirements.
Technical support
The quality and availability of technical support matters. Besides well-developed documentation, you should have ready access to support staff if needed.
Whether devices are in the office, at home, or somewhere in between, sysadmins need a software deployment approach that keeps endpoints secure, updated, and manageable. PDQ helps IT teams support on-prem, remote, and hybrid environments without making deployment more complicated than it needs to be. Easy as pie. Or pizza.
