Preventing SCCM 2007 from using all volumes: default installation
Hi everyone, I came across an article which suggests how to prevent SCCM 2007 from installing files on certain disk volumes. I'm referring to following article: http://technet.microsoft.com/en-us/library/bb632890.aspx Now consider the situation where I had installed SCCM 2007 (Primary Site server) on its default location "C:\Program files\"....and I saw SMS shares created on folders unerneath default installation folder; ideally we would like C: drive not to be over used by applications like SCCM. Would it be ok to follow the procedure and create the file to prevent SCCM 2007 from adding any further files on C: drive? Would it create issues for the product to function properly if prevention measure is taken after SCCM 2007 is installed on default location? Please share your ideas. Thanks. Regards, Shahzad.
October 31st, 2011 9:37pm
Yes, no_sms_on_drive.sms file to be created and place in C drive or what ever the drives that you want to stop utilization for sccm. Read this artical this still applicable to SCCM (Forget/ignore about CAP) also.. http://support.microsoft.com/kb/871234 This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
November 1st, 2011 12:17am
Hi Paddy, Thanks for the link. My concern is: "What would happen if I create this file and place it on C:\ drive AFTER I've installed SCCM 2007 on C:\ on default location?" Changes will be made to files at default location all the times, new files added, existing files modified etc. If I create such a file after installation SCCM; would application function properly? Regards, Shahzad.
November 1st, 2011 12:37am
The no_sms_on_drive.sms will have no effect in your scenario as you have already installed ConfigMgr. binares on the drive. It is a file that you can prior to installing a ConfigMgr. binaries. The articles also states that any files already present will not be removed. Remember that you can use remote servers to host most of the roles used in your ConfigMgr. environment. like MP, DP, reporting services points, SLP etc.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
November 1st, 2011 1:35am