Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

We are planning to perform an Rolling Pool Upgrade using the "automatic method" described in the Citrix XenServer ® 6.1.0 Installation Guide (at

In order to use the "Automatic Mode" (to avoid installing with media at each host), we attempted to set up a local HTTP repository (or mirror) with the contents of the ISO. We chose this method because we have no NFS or FTP services in place, currently.

Because it was handy, I added a virtual directory (named "media") to an existing IIS web instance and enabled Directory Browsing (mostly for troubleshooting). Then I extracted the ISO into a sub-directory (named "xenserver-6.1") and verified the directory listing matched the contents of the ISO.

At this point I thought I was ready and I performed a test install using HTTP as the method and the address ("http://servername/media/xenserver-6/1"). When this test failed, I began researching the required contents of the directory and several other theories.

share|improve this question

The root problem ended up being unspecified MIME Type entries required for IIS to serve the contents of this directory. You can read more about this problem here:

To solve the problem, I added a "*" entry using the "application/octet-stream" MIME Type in the configuration of the virtual directory.

Credit to "Don Nelson" in this thread for pointing out the solution:

Note: Several hours were spent on this solution, mostly with research and troubleshooting. I have added this question (with an answer) to hopefully make this easier on the next person.

Note: Based on the nature of XenServer, I assume this "fix" may apply to other Linux-based installs.

share|improve this answer

Realise this is answered and it helped me a lot in getting my servers configured. However I want to raise an issue that people may encounter (and that I did) if you are intending to use IIS7/7.5. What happened to me was that I entered the wilcard mime type, and it would serve any file that had an extension it didnot have explicitly defined, however it would not server extensionless files (and this is needed for the xenserver install).

In the end I discovered its a bug in a certain config of IIS7/7.5 on Windows 2008

Now I have to say I did not apply the hotfix, I moved to a windows 2012 R2 server running IIS8.5 and entering the wildcard mime type here allowed me to get this working...

I have put together a rushed blog entry here

share|improve this answer
It would be much better to make this an actual question and answer. e.g. "Why does IIS7/7.5 not serve extensionless files needed for Xenserver Install?" then you can come back and answer the question a day later and score more points. :-D – tudor Jan 8 at 4:25

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.