Build Standardisation
Build standardisation addresses one of the major blocks to client deployment
success regardless of the deployment mechanism used. We have seen in many
customers over the years that there has been a desire to maintain a large number
of image based builds to support their client base.
Common Mistakes
One of the common mistakes
when trying to standardise a build is adding too many items into the base image
such as applications that are frequently updated or changed. The other mistake
is creating builds that are hardware dependant. As soon as the hardware changed
a new build is needed. These techniques soon require a number of builds to meet
a number of functions / tasks and very quickly they become un-manageable.
Embrionic Recommendations
Embrionic recommend that when you are designing your new client / desktop
deployment, one of the key areas is a carefully planned standardised build that
meets the base criteria for the majority of the organisation. A single build
should meet all your requirements. It is also very important to agree this
standardised build early in a deployment project as this can lead to huge delays
and expensive changes further in the project. Any application delivery,
packaging and user acceptance testing is reliant on a standard build that wont
change.
Embrionic Involvement
Build standardisation and management can often be difficult to deliver when
you organisation only has experience in Ghosting a pre-built platform or hasn't
updated their desktop estate in recent years. The options have grown and the
tools have improved immensely. Embrionic can deliver many benefits when helping
you organisation and can plan your route to a guaranteed problem free
deployment.
