fourseasons Posted March 21, 2014 Report post Posted March 21, 2014 We have been using OSD task sequences in SCCM 2012 for a few months without issue, recently however the task sequences will fail at the start. From logs, there is not enough free space to copy down the boot image as HD is full of partitions already evidently. I understand that if all packages in the task sequence have the checkbox enabled for "Copy the content in this package to a package share..." we would then get the option in the task sequence deployment to run content from DP rather than download locally, however this has never been set on our deployment(s) and we haven't had this issue before. I believe it should be able to PXE boot to the boot image (which clearly it is already doing prior to starting the task sequence), and for some reason something has changed which means it is trying to copy this locally and hence falling over. For the moment, we can run diskpart from f8 within the task sequence prior to commencing and remove existing partitions, at which point the OSD will complete successfully. Clearly, this would cause issues if we were doing user state migration, which we would like to deploy soon. Any ideas on where to start diagnosing this? I've had no luck tracking down what has changed to alter the behaviour. Quote Share this post Link to post Share on other sites More sharing options...
namahs Posted March 21, 2014 Report post Posted March 21, 2014 We ran into something similar to this when we updated our boot image. When you plug in the USB thumb drive to boot into SCCM, it will check with the copy on the source and if its different. It will download and cache the boot image and run it locally. The issue is when you have an encrypted drive. When you navigate to an encrypted drive, there wont be any space available until you diskpart it. So when it tries to copy the boot image, it will not have enough space and fail. Not sure if you have the same issue since you PXE boot. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted March 23, 2014 Report post Posted March 23, 2014 check where it's storing the boot image, more than likely it's placing it in the bdedrive partition which by default is approx 300mb, we have resized ours to between 1 and 2gb to get around this because refresh (reinstallation) scenarios where it has to disable bitlocker and reboot involve just this procedure, post your smsts.log and we'll take a look to confirm Quote Share this post Link to post Share on other sites More sharing options...
