I see this post is from 2009 but I'm going to answer it anyway, better late than never, right?
The short answer: Recapture thie image.
The best practice is to shrink the partition as small as possible and then capture. That way you will most likely not run into this problem again.
When we restore we expand to the size of the drive anyway.
Hope this helps anyone else in the future as I have a feeling Sean has figured it out by now.
"It should not matter what size drive I capture and deploy on as long as the hard drive space is over the image size."
When you use a sector base imaging tool like imageW.exe it definetly does matter.
Yeah I had to start from scracth again and make sure I capture on a small drive such as a 20GB. Bummer but I eventually got it done. Thanks!
Thanks for clearing this up for me. Is there a better image tool to use with Landesk or is this the best option?
1 of 1 people found this helpful
There are 3 main tools to use for imaging. 2 of them are file based - Ghost and ImageX and then you have ImageW
They all do the same thing, it is all personal preferrence, they all have pros and cons
I use ImageW.
I prefer the GUI for the end users, you will most likely get better support from LANDesk using their tool and the big one, Its free.
Just go with a small partition to capture the image and you can do whatever you want to the partiton after the image is laid down using DISKPART scripts. So it really is not that bad.