So I am trying out IBM Tivoli, and have run into a few speed bumps.
We are a Ghost shop here. We build our custom images, then upload them to a Ghost server and manually connect the computers to the Ghost server to deploy the images. So building an image using ImageX, MDT, AIK was a new experience for me.
Near as I could figure, I syspreped my test machine using the same answer file we have been using, booted it into PE, and created a WIM file. I then uploaded that WIM to my BES server for deployment.
I also created a MDT following the instructions on the OSD PDF.
Once that was all complete, I tested it by pushing it out to a system. The image seemed to push just fine, as I could see the extra files on the computer, and the computer booted up into PE…
Then nothing…
It sat at a command prompt window, waiting for input.
It is here that I am stuck. The OSD v2.0 document does not provide much information on LiteTouch or MDT or even what to do after you get the computer setup to reimage.
Not really help with this as I have only done a bit with it, so hopefully someone replies.
Another tool you can look at that you may have access to with your license is the TPM for OSD. This one is more of a bare metal tool like you would be used to with ghost. The process that you use for the image in ghost is almost like TPMfOSD as you do not need MDT/ImageEx/WAIK.
Big differences though are:
Dynamic driver injection - at deployment time, TPMfOSD determines the drivers to use to be used in the OS.
Shared repository - if you have multiple XP profiles, the repository goes not grow according to the # of profiles, just the difference in the profiles. so for example, the first time you capture an XP profile, the repository grows by 5 GB (or whatever your image is). The next time you upload a different XP profile, only the differences are uploaded. Also if you upload a Windows 2003 image and XP and 2003 share some of the same files, only these are uploaded.
If you are looking at doing in place migrations, then I would recommend you continue with the TEM OSD as currently it is better for that.
I know that there is work in place to get TPMfOSD and TEM OSD to work together so really waiting for that
Is there any reason in particular you’re not using the TEM-OSD Capture Dashboard to generate the image? The process for capturing can be quite complex if you’re unfamiliar, and in an attempt to abstract this from users, we built the capture dashboard.
Also, I’m not sure what you mean by “once you get the computer setup to be re-imaged” – the only thing you should need to do to “setup a computer to be re-imaged” is install the TEM Client.
