locked
Move SCCMContentLib on Primary Site Server to a separate drive? RRS feed

  • Question

  • With ConfigMgr 2012 SP1 Primary Site Server, do you usually leave SCCMContentLib and related directories on the drive you install ConfigMgr to, or do you move them to their own drive?  I'm trying to figure out the best way to handle that before I do the install.
    Thursday, April 4, 2013 12:44 PM

Answers

  • Hi,

    I plan for the additional disk space needed for the SCCMContentLib on the drive where you install Configuration Manager.

    Regards,
    Jörgen 


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Thursday, April 4, 2013 12:48 PM
  • You can also place the no_sms_on_drive.sms on partitions where no ConfigMgr components should be placed.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, April 4, 2013 1:46 PM
  • Also, setup will automatically pick the volume with the largest amount of free space on it so you really shouldn't have to "move" it anywhere.

    Jason | http://blog.configmgrftw.com

    Thursday, April 4, 2013 2:32 PM

All replies

  • Hi,

    I plan for the additional disk space needed for the SCCMContentLib on the drive where you install Configuration Manager.

    Regards,
    Jörgen 


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Thursday, April 4, 2013 12:48 PM
  • You can also place the no_sms_on_drive.sms on partitions where no ConfigMgr components should be placed.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, April 4, 2013 1:46 PM
  • Also, setup will automatically pick the volume with the largest amount of free space on it so you really shouldn't have to "move" it anywhere.

    Jason | http://blog.configmgrftw.com

    Thursday, April 4, 2013 2:32 PM
  • Just to further clarify this point.  if I have a C and a D drive, I install configmgr on C, it seems like I get the SCCMContentLib on C.  In the past I have moved it to D which is possible.

    Are you saying that if D has more free space than C, the install automatically places the ConfigMgr content lib on D?

    If I use the non_SMS file on C and point the CM2012 installation to C, what happens?  I was going to try that to see if the content lib was then installed on D.

    It just seems like it is confusing to get the primary site's SCCMContentLib on D when CM is installed on C? 

    Tuesday, January 28, 2014 6:30 PM
  • Installing ConfigMgr on the C: drive is not the best idea (from a performance point of view) - given that the OS is also installed there.

    Torsten Meringer | http://www.mssccmfaq.de


    • Edited by TorstenMMVP Tuesday, January 28, 2014 6:40 PM
    Tuesday, January 28, 2014 6:40 PM
  • Are you saying that if D has more free space than C, the install automatically places the ConfigMgr content lib on D?

    Yes.

    If I use the non_SMS file on C and point the CM2012 installation to C, what happens?

    Not sure, but see Torsten's point as this is generally a bad idea for all but the smallest of sites.

    Jason | http://blog.configmgrftw.com

    Tuesday, January 28, 2014 7:19 PM
  • Good point, I still find it confusing to try to get the SCCMContentLib on a drive other than where CM is installed.

    I am going to test the no_sms_on_drive.sms on the drive that I install CM and see if that moves JUST the content lib.  Of course that will be a one off in my lab, more out of curiosity.

    Thanks again.

    Tuesday, January 28, 2014 7:31 PM
  • It won't move the sccmcontentlib for sure. It will/should prevent it from being created in the first place which means you have to create the no_sms_on_drive.sms file before installation.

    You can use the content transfer tool to move the contentlib after creation. Note that ConfigMgr will always create and place content on the drive with the most space though so make sure that non_sms_on_drive.sms file is in place before you add more content again.


    Jason | http://blog.configmgrftw.com

    Tuesday, January 28, 2014 7:41 PM
  • I've used the content transfer tool before, surprising easy and it worked!
    Tuesday, January 28, 2014 7:43 PM