Dual Boot Windows Home Server – Possible Problems and Fixes
Since 2007, people have been using Windows Home Server (WHS) for connecting multiple computers to organize, share, and automatically back up photos, videos, music, and other important documents. Though there is no need for any other operating system with Windows Home Server, sometimes people may want to use Windows XP, Vista, Linux, or any other operating system on the PC that contains tWHS. Though it is practical, you may encounter some problems while using dual boot on Server.
The major problem is related to system related changes. For example, if you make any changes using the other operating system, chances are that they will be reversed as soon as you boot into the Windows Home Server. This is because the Windows Home Server keeps a record of entire settings and either displays an error when it finds something changed or automatically brings it back to its previous settings.
As of now, there is no known tweak that can solve this problem except that you make the same changes through the Windows Home Server. However, it is not necessary that you will be able to use the WHS to make the same changes.
There are no other known conflicts except that sometimes the other operating system may fail to load. This is attributed to a corrupt boot.ini file and is not really a problem with dual boot Windows Home Server. The problem can be solved by booting into the WHS and manually editing the boot.ini file.
Though the linked page shows editing boot.ini under Server 2003, the procedure is the same for Windows Home Server, too. In case you do not find the boot.ini file, you can create one based on the instructions given in the above link. If you do not want to risk it, call in an expert technician who can fix the boot.ini on the dual boot Windows Home Server PC.
NOTE: The boot.ini file should be opened only in Notepad. Attempting to open the file in WordPad may add some extra characters to the file, rendering it useless.