Doubt in installation part of sccm
As a "general" statement, not related to ConfigMgr as a specific instance, but in general, it is not a good idea to install anything (if you can avoid it) on whatever drive letter resolves to %windir%, which is normally the C: drive. Some applications, and sure, I'll mention ConfigMgr or SQL, if, for example, your forget to use "Simple" for the DB for SQL for ConfigMgr, the tempdb might balloon and balloon and balloon, and take up all of the free space on the drive. If that drive happens to be the one that %windir% is on, you could crash your server. If tempdb were elsewhere, SQL might fail/stop, but the server won't reboot/stop. Note there are some things for SQL (at least for 08) that absolutely refuse to go anywhere but c:. You can't avoid it; but put as much as you can elsewhere.Standardize. Simplify. Automate.
March 21st, 2012 4:55pm

Hi there The main reason why we'd choose to not install anything apart from teh OS onto C: is to try and avoid using up valuable space for the OS with other stuff. You'd be right to install SCCM into D: and even better to install SQL into a different drive again because the same constraints would apply
Free Windows Admin Tool Kit Click here and download it now
March 21st, 2012 4:56pm

Hi, Im newbie to sccm and im learning it, i have small doubt in the installation part of sccm, i have learnt that we should install sccm in separate drive assume it as D drive, in this case should we install sql server also in D drive.
April 8th, 2012 9:59am

As a "general" statement, not related to ConfigMgr as a specific instance, but in general, it is not a good idea to install anything (if you can avoid it) on whatever drive letter resolves to %windir%, which is normally the C: drive. Some applications, and sure, I'll mention ConfigMgr or SQL, if, for example, your forget to use "Simple" for the DB for SQL for ConfigMgr, the tempdb might balloon and balloon and balloon, and take up all of the free space on the drive. If that drive happens to be the one that %windir% is on, you could crash your server. If tempdb were elsewhere, SQL might fail/stop, but the server won't reboot/stop. Note there are some things for SQL (at least for 08) that absolutely refuse to go anywhere but c:. You can't avoid it; but put as much as you can elsewhere.Standardize. Simplify. Automate.
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2012 10:09am

Hi there The main reason why we'd choose to not install anything apart from teh OS onto C: is to try and avoid using up valuable space for the OS with other stuff. You'd be right to install SCCM into D: and even better to install SQL into a different drive again because the same constraints would apply
April 8th, 2012 10:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics