Best Practice for preparing a master image to use in TEM OS Deployment
Whether an organization is new to imaging or has been doing it for years, the content and maintenance of a gold image is a potential subject of debate.
Resolving the problem
Whether an organization is new to imaging or has been doing it for years, the content and maintenance of a gold image is a potential subject of debate. A wide spectrum of options is available, ranging between the larger "one-size-fits-all" image and the smaller "all-stripped-down" image.
Larger images: less setup, more maintenance
A "one-size-fits-all" image with more software packages and more drivers in it is easy to design, fast to deploy, difficult to maintain, and a significant licensing burden. This sort of image is produced by installing everything necessary for any end user onto a single system and capturing it for redeployment. Setup for such a deployment method can be measured in hours or days, which represents a very speedy entry into OS imaging; for an organization starting a new imaging program, this method is a fine way to start. There are two important drawbacks to the larger image method though:
- The image must be rebuilt to take advantage of new package versions. Typically organizations doing "large" images will have to rebuild the image once per quarter.
- All licenses must be site licenses, because all software packages are installed for all users.
Smaller images: more setup, less maintenance
A "stripped-down" image with the bare minimum of packages and drivers takes more effort to develop because of the post-imaging packages required; these packages can also increase the time required to deploy a new OS. However, the stripped-down image model decreases operational costs by allowing administrators to troubleshoot and maintain packages and drivers individually without re-building images. Furthermore, licensing costs are reduced by only providing software packages to the end users with real need for those packages. While this method requires a greater amount of initial setup time, it can greatly decrease the amount of labor devoted to on-going image maintenance. IT Departments are also able to provide more flexible service by having access to these software and driver packages outside of the OS imaging context. This is the TEM recommended approach.
TEM Platform Agent
TEM recommends installing the TEM agent in images before capturing them. This is done to ensure that all newly deployed systems will report in promptly and enforce policy compliance as soon as possible. Some customers may elect to use TEM Client Compliance tasks to automatically quarantine these new systems until patches and policies are enforced.
More support for:
IBM BigFix family
Software version: All Versions
Operating system(s): Platform Independent
Software edition: All Editions
Reference #: 1506260
Modified date: 10 April 2015
Translate this page: