By editing builds quickly in OneDeploy there is never a post-build set of instructions to work through. Every single build will be up to date, mirroring the live Windows estate as closely as possible.
But if you use an imaging deployment tool, the ‘standard image’, which the IT department or partner firm uses when devices need repairing or replacing, becomes out-of-date all too quickly. This can lead to the scenario in which an engineer will have an old image that they continue deploying to new devices.
However, because Windows continues to look much the same to both the engineer and the user alike, they aren’t going to be aware that the environment they are using is out-of-date - that is until the error messages start flowing in. Old image-based redeployments proliferate non-standard and inferior user experience which ultimately lowers productivity.
We’ve seen workarounds then being applied before they come across to OneDeploy. So, engineers might carry around an image dated June 2016 for rebuilds but they then have a supplementary document detailing how to bring his image up to the December 2016 standard.
In the best case, there is time spent by an IT team member making sure the gap between out-of-date image deployment and optimum user experience is filled. The worst case is that these steps are simply forgotten and the user wrestles on with a machine that is hampering his or her productivity.
More often, we see hard-pressed IT staff rushing through the supplementary gap-filling work. Human error inevitably creeps in as they interpret highly technical instructions incorrectly or simply fail to follow instructions properly. Deployment mistakes then lead to creation of a device experience which is different from others around the office. It all makes for delays in repairs, leads to non-standard desktops across the entire organisation which leads in turn to user frustration and increased IT support calls with their associated costs.