Many clients that come to us have already bought new hardware devices, but because their imaging-based deployment solution of choice cannot handle this chosen hardware, they are forced to keep them in the warehouse un-opened. That’s until they come to us: with OneDeploy the hardware is abstracted away from the deployment of the operating system during the design phase. This architecture means that we can add new hardware within minutes with no need to update images and no other changes to the deployment environment.
Take for example our unique DriverApps solution. DriverApps are software installations that are installed after Windows has been put on a device by OneDeploy. The real trick here is driver usage is dependent on specific hardware being present. Once the DriverApps are loaded into the library, OneDeploy will automatically install the relevant software only when the supporting hardware is present.
This simple concept means that all challenges associated with separate images, post-image documents and resulting post-deployment helpdesk calls are eradicated at source. Machines that need the driver software or DriverApp will get that software, and those that don’t, will not.
This brings significant consistency and standardisations to the deployment environment as the core build remains identical while absorbing specific elements required to fully-exploit the hardware of the target PC, keeping ageing hardware, as well as the brand-new kit, working in an optimal way.
Take for example our unique DriverApps solution. DriverApps are software installations that are installed after Windows has been put on a device by OneDeploy. The real trick here is driver usage is dependent on specific hardware being present. Once the DriverApps are loaded into the library, OneDeploy will automatically install the relevant software only when the supporting hardware is present.
This simple concept means that all challenges associated with separate images, post-image documents and resulting post-deployment helpdesk calls are eradicated at source. Machines that need the driver software or DriverApp will get that software, and those that don’t, will not.
This brings significant consistency and standardisations to the deployment environment as the core build remains identical while absorbing specific elements required to fully-exploit the hardware of the target PC, keeping ageing hardware, as well as the brand-new kit, working in an optimal way.