OEM workstation staging
We have gone away from using Ghost images in the build process as they have become too unwieldy to use now.
Would be happy to swap notes with anybody doing this or heading down this path.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
GB1
18 years ago
Hi,
This is a theory I have had exposure to. The approach has theoretical benefits, but it's not one that I particularly like. I'll share my thoughts, which might help you make a decision.
1. Consider how many different makes and models you will have on your estate.
In my experience OEM images vary in terms of build, vendors utilites installed, custom permissions (watch out for this), components such as DirectX version, other vendors software - Acrobat Reader etc.
To have process which can bring such a vast variation of machines into "a baseline standard" would be very very hard work -sounds like you are discovering this!
2. As soon as you get a vendor supplying you an OEM image with something you don't like or your process does not handle, you need more developement work - so possibly no saving over any other form of build in terms of catering for new models.
3. Utilising what is already on the machine might sound like a time saving, but what happens when you need a full rebuild? Building just one machine from scratch manually with your vendor OEM image CD, then layering everything on top will be slow - just think if you had to do a batch in this scenario - most other build methods - RIS, image, scripted installations etc would all be quicker.
Hope that helps.
This is a theory I have had exposure to. The approach has theoretical benefits, but it's not one that I particularly like. I'll share my thoughts, which might help you make a decision.
1. Consider how many different makes and models you will have on your estate.
In my experience OEM images vary in terms of build, vendors utilites installed, custom permissions (watch out for this), components such as DirectX version, other vendors software - Acrobat Reader etc.
To have process which can bring such a vast variation of machines into "a baseline standard" would be very very hard work -sounds like you are discovering this!
2. As soon as you get a vendor supplying you an OEM image with something you don't like or your process does not handle, you need more developement work - so possibly no saving over any other form of build in terms of catering for new models.
3. Utilising what is already on the machine might sound like a time saving, but what happens when you need a full rebuild? Building just one machine from scratch manually with your vendor OEM image CD, then layering everything on top will be slow - just think if you had to do a batch in this scenario - most other build methods - RIS, image, scripted installations etc would all be quicker.
Hope that helps.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
