It involved offline editing the registry, but once implemented, my virtual WHS finally booted fine.Īs mentioned at the beginning of the post, configuring remote management of the Hyper-V server seemed to be simple. Came across a Microsoft Technet Forum post, where a poster called Mali Stane pointed to Mark Minasi’s Forum, where a user called RKOET provided the solution i was looking for. Just to convince myself i haven’t gone mad, i tried to install WHS from scratch, which worked fine. I also tried to run a windows backup and restore that to the VM, but with a similar (no) result. I though this might be related to the fact i was using dynamic disks on my physical server. First i tried to run Sysinternals Disk2VHD, which created the VHD files, but when i tried to boot the VM from this, i was getting a BSOD. Next step was converting the data on the physical disks to VHDs. If you read carefully the text on the download page, under System Requirements you can find information that RSAT supports a list of languages, and if yours is not on the list, you are provided with a KB article on how to install it. Not so simple than after all! Or at least not in my case.
So what you normally do is you open the search engine of your choice, type in Remote Server Administration Tools download and off you go. Installing Remote Server Administration Tools Following was the next step, configuring my Windows 8 workstation for remote management. Setting up the network configuration and enabling remote management and remote desktop seemed to be easy – just a matter of selecting the items from the menu. The installation was pretty quick and i have been presented with the basic text based Server Configuration menu. I started with installing the Hyper-V server on a spare disk, just to be safe and make sure i can go back any time to my original setup (what a clever move this was). It helped me to learn a lot of new stuff (Powershell rules!) and now I have my WHS 2011 running on Hyper-V server 2012, just the way i wanted to. It caused a few headaches, brought me to the brink of giving up, but i kept trying and got my reward. There were many aspects of this project that didn’t go quite according to plan. One of the main reason was the use of Storage Spaces, which was allegedly done by the same guy who did the Drive Extender in the previous version of WHS. The more i was working with Microsoft’s latest Windows Server incarnation, the more i was thinking about using the free Hyper-V Server 2012 to virtualize my Windows Home Server 2011. Select your "Site" from the list on the left of sites hosted on your server.How i virtualized my physical Windows Home Server 2011.Ensure WebDAV Publishing is enabled, enable if it isn't.Scroll down to the Web Server (IIS) section.To enable WebDAV sharing through your server follow these steps: Enable the WebDAV Role These instructions have been tested on Windows Home Server 2011 with SP1.
0 kommentar(er)
