With OneDeploy solutions to all deployment problems are baked into our product. But in other deployment scenarios, even those built using SCCM, internal team or deployment consultants end up having to double as developers - writing power-shell scripts, batch files and other unmanaged code that then forms part of the core imaging solution hence forward. Unmanaged code will evolve over time and often becomes fragile, offering limited or non-existent error-state checking.
These scripts then become a fundamental part of the deployment solution. Essentially, what should be a standard process becomes a highly-customised one. The deployment solution becomes highly specific to the organisation. The ability to make changes, adopt new hardware, software or other elements must be fully-checked and tested by the few in-house developers that are knowledgeable about these customisations and now become your ‘IT heroes’
These developers and IT heroes must step up to solve the increasingly difficult challenge of making changes. You become dependent on one person, or a very small number of developers, to keep ‘the show on the road’. However, when this rare knowledge leaves your IT team because that person is needed on another IT project or leaves the company, then the ‘image’ and its deployment across the organisation enters the realms of the ‘dark arts’. Barriers to entry are high now and everyone who comes in to lead OS deployment projects spends a great deal of time and IT resource deciphering what has gone before.
Typically, they will give up and claim that the solution needs re-engineering and the hero-creation cycle starts once again. By contrast, OneDeploy is in perpetual development and improvement. A large team of engineers are using the product in live deployment and support scenarios day-in-day-out. The standard product has a significant number of features and capabilities baked into it – completely squeezing out customised-development cycles for OneDeploy customers.
Even if there is a special requirement, the chances are our team has seen it before and have developed ways to make it work without custom script development. Th large OneDeploy team mitigates against knowledge loss should a key person leave your organisation.
These scripts then become a fundamental part of the deployment solution. Essentially, what should be a standard process becomes a highly-customised one. The deployment solution becomes highly specific to the organisation. The ability to make changes, adopt new hardware, software or other elements must be fully-checked and tested by the few in-house developers that are knowledgeable about these customisations and now become your ‘IT heroes’
These developers and IT heroes must step up to solve the increasingly difficult challenge of making changes. You become dependent on one person, or a very small number of developers, to keep ‘the show on the road’. However, when this rare knowledge leaves your IT team because that person is needed on another IT project or leaves the company, then the ‘image’ and its deployment across the organisation enters the realms of the ‘dark arts’. Barriers to entry are high now and everyone who comes in to lead OS deployment projects spends a great deal of time and IT resource deciphering what has gone before.
Typically, they will give up and claim that the solution needs re-engineering and the hero-creation cycle starts once again. By contrast, OneDeploy is in perpetual development and improvement. A large team of engineers are using the product in live deployment and support scenarios day-in-day-out. The standard product has a significant number of features and capabilities baked into it – completely squeezing out customised-development cycles for OneDeploy customers.
Even if there is a special requirement, the chances are our team has seen it before and have developed ways to make it work without custom script development. Th large OneDeploy team mitigates against knowledge loss should a key person leave your organisation.