Server data and OS best practices

I have gotten some inquiries as to why we keep our Operating system (C: drive) and our programs and data (E: drive) separate.  My main reason was so some application file or configuration does not fill up the root volume and shut down the whole server.  If an application or configuration fills up the data volume I can still get on the server to correct.  I am looking for some hard evidence or best practices to back me up.

Thanks,
Tom
wnc123Asked:
Who is Participating?
 
Jerry MillerConnect With a Mentor Commented:
You can lock down the C:\ drive so that normal users cannot make any changes. If they can only write to other drives, there is little chance they can mess anything up.

You can control the size of the C: as you stated.

PC recovery is easier, because you are not concerned with user data and rebuilding a PC simply requires an image with the appropriate software installed to the C:\ drive. Then you are not even touching their data.

I am sure that there are many more as well.
0
 
wnc123Author Commented:
Thanks for the reply.  That is all true but I am looking for some concrete best practices from Microsoft or other on why to keep your Server OS and your data/applications separate.  I need something to reference to backup my explanation.

Thanks,
Tom
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.