If smaller branch offices don’t warrant this level of IT investment they may miss out, or see delays, on operating system upgrades or new hardware roll outs. Sometimes this can even cause morale issues where branch office staff are aware of IT services delays that their headquarters colleagues are already benefiting from. OneDeploy has eliminated this issue by working on any site, even if there aren’t any servers present.
With OneDeploy a standard PC can act as a build source and the Windows deployment can be proliferated to multiple devices from there. Incremental update to our builds are really small, so we can synchronise each location regularly, keeping everyone fully up-to-date.
OneDeploy has also been used successfully in multiple projects, to remotely upgrade devices, implementing organisations’ chosen versions of Windows or even in-place line of business applications. Baked into the product is the live reporting engine which gives centralised step-by-step progress reports of the builds as they run through in remote branches or outlets.
This gives our customers the confidence to remotely deploy to PCs where they may have traditionally sent an engineer or even couriered ready-built replacement devices to remote sites. The OneDeploy approach reduces time to deploy significantly as multiple machines can be upgraded in parallel, all outside working hours if necessary.
By contrast without OneDeploy, it’s not unusual to see IT teams developing sever-based Windows deployment solutions that only work close to the IT department, because the processes involved are so network-intensive that they need to be in close proximity to the server sharing the deployment. So, if a device in an outlet needs Windows deployed onto it, that PC may need to be in the same building as the IT team. For organisations with many branch offices or outlets the server-based approach quickly becomes too expensive and impractical.