Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using Remote Desktop to connect to an Azure Instance and I noticed the following for an extra-small instance of Windows 2008R2:

C:\ Drive for the purpose of storing log data. 13.6GB / 19.9GB used

D:\ Drive for OS functions 17GB / 25.9 used

E:\ Drive for my website, and is the location for the startup tasks 100MB / .99GB used

There are many interesting files, batch files and settings there. Does anyone have information on the configuration of the OS?

Does anyone have info what the batch files and scripts "do"?

I would love to see any rationale on why things were done this way so we can use the practices within our own IT department.

share|improve this question
up vote 1 down vote accepted

I'm not sure if Microsoft's model for pure automation surrounding the creation, management and destruction of millions of OS's is something of use to most IT departments, but I can give you my thoughts. I don't have the actual official reasons from MS Online teams but here's my 2 cents based on the little I know:

Azure Windows is designed around rapid deployment, separation of "their OS" and "your data", and the ability for Microsoft to update/manage their OS without affecting your data. Splitting these parts into separate drives is a clean way to do it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.