Imaging from Restore Partition

[#1]

Hello all,

Wondering if anyone on the list utilizes a restore partition for imaging
their machines. If so, dose Casper prompt you that you are running out of
disk space during imaging? If so, is there a way to prevent getting this
message? If not, any way to work around it? My restore partition is 10 GB
and restore and have a pretty stripped down OS for restore. Currently using
Casper 4.1, OS 10.4.10.

Any input is appreciated.

Thanx,
Cyrus

[ernstcs]

Are you caching packages? If so then as larger packages get expanded to be installed they take up space on that drive temporarily. For example...if you have a large package like Creative Suite 3.

The solution...bigger Restore partitions, or don't cache packages. We increased our Restores from 10GB to 25GB a while back...this will also help when you move to Leopard.

If you aren't caching...no idea accept maybe a VERY large package you deploy.

Unless you re-image large numbers of machines at one time, like labs, or don't have large amounts of bandwidth to your file server for the JSS, then caching isn't really necessary IMO. We actually started to not put on a Restore partition in our faculty office installs since NetInstall images do what we need them to for imaging on a one at time basis as they typically are.

Labs still use a restore so I don't kill the file server when I launch a lab of 30 machines, at least when there aren't many package changes since last time. =)

Hope that helps.

Craig

[#3]

Craig,

Thanx for your feedback. Did forget to clarify a couple of items in my
original post which you brought up. They are:
no packages are being cached.
in the last instance I've run across this issue I had Final Cut Pro as
part of the configuration. I've run across this issue before without Final
Cut Pro too. I was only imaging one machine, not a whole lab.
Working on getting away from using Restore partition as soon as I can
setup a SUS.

Thanx