Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all articles
Browse latest Browse all 9126

C drive seems abnormally large for the deployment (.WIM taking up all the space)

$
0
0

I just started using SCCM 2012 R2.  I've gotten everything setup to do my deployment but it turns out I clicked deploy on a .wim file I had and it filled up the C drive.  This is a virtual machine and I never intended to store the data on the C:\ drive.  But by following a install online it seems that the default DP puts it there.  My SCCMContentLib seems to grow uncontrollably and I can't figure out why.  At first I started with a 40GB vm.  Then moved it up to 60 to give me 20GB of free space.  Next I noticed that my image wasn't getting sent via the client pc because of a error which tracked back to the operating system status being red.  This tracked to not enough space on the C:\ when I clicked the error.  I noticed somehow this WIM file took up the 20GB I had given it extra.

My image is for a Dell Optiplex 3020.  The .wim file is 9GB in size on the file share.  Yet when I right click and check the properties under Operating System Images it shows as 22,083.82MB.  Which doesn't seem all that confusing understanding that this is probably the extracted size?

So no problem I increased the drive size by 40GB again.  I then went to the operating system and right clicked and said distribute content.  But it didn't seem to turn yellow.  So I went to Task Sequences, Distribute content on the task sequence that is set to push out that image, then went back to the OS and clicked distribute again.  This time it went Yellow.  I waited and waited then it failed out again.

Now when I check the C:\ drive it has 4GB or so free, and the status is red again with the error not enough space on the C:\ NTFS drive.  I have no idea how a 9GB .wim file can turn into 60GB of space eaten up?  What am I not understanding about SCCM.  Just using WDS seemed like a much better solution as it didn't require a insane amount of space to push a single image.  I understand that SCCM has many other capabilities which is why I moved to it.  Yet this is not a acceptable solution using up 60+GB for a single 10GB wim file to image a few machines.

There must be something wrong here and I am not doing correctly.


Viewing all articles
Browse latest Browse all 9126

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>