Oddities Using Disk2VHD to Virtualize

  
   Recently I was performing due diligence preparing for an upcoming server consolidation by means of virtualizing two existing servers, one from failing hardware. Since one server is coming from hardware that has started showing signs of impending doom I decided to start with that one. When I created the VHD, I chose to mark up HAL for Virtual PC to lessen the probability of BSOD while trying to boot the virtual machine of a 2003 server. When I tried to boot the machine on my Hyper-V test server, I would get the splash screen and then BSOD, unmountable volume. If I mounted the VHD using Disk Manager the Primary partition showed up as RAW, the secondary had all of its data there. Since this was from a failing server I assumed that the array may not have been read correctly by Disk2VHD. I used testdisk to try to repair the VHD. I ran it and it found errors, I saved the correction and ended up with a readable Primary Drive of the wrong size. The second partition was now RAW but the VHD would boot, the next issues was that it was in a "The HAL must be upgraded before integration services can be installed, a reboot is necessary" loop.

       So.. I made a VHD of the other server and tried to mount it with the same results. At this point I am starting to get a little worried that my Virtualization adventure could turn into a nightmare. After considering numerous other possible methods to get these servers from P2V, I decided I could try ghosting the individual partitions to blank VHDs that I created in Hyper-V and mounted with Disk Manager. I was quite surprised when Ghost actually read the Data from the RAW partitions and copied them to the blank VHDs. This still Left me with the HAL loop, unable to install integration services.

   I now had a real plan emerging, I would create the VHDs using Disk2VHD, being sure to leave the HAL fixup unchecked. I would then create blank VHDs and ghost the contents to them. Success !!!!! I now had 2 new virtualized servers. A little bit of configuration and I had working mirrors of their physical counterparts. I was once again fully comfortable that I could get this done for the customer.

    Finally the new server arrived I took it to my office, assembled the parts, Installed the Server 2008 R2 and Hyper-V. I decided just for kicks to try and mount one of the VHDs that were freshly created without the HAL fixup checked. It booted like it had always lived there, no BSOD no HAL fixup loop, no need to ghost. Live and learn, never take anything for granted and it sure helps to have the same hardware to test something as what it will end up on.

     One of the main things that I learned is that Disk2VHD is an awesome tool for Virtualization and DR but depending on hardware you can end up with many varying results.

WHS and Hamachi

    So, I was sitting in my office/workshop/man cave getting ready to watch "The Battle of Ohio" when I decided to test the ability of WHS to back up a remote workstation or server. I had seen many different posts on various ways to accomplish this. I chose to try Hamachi VPN now owned by LogMeIn. I then needed to figure out what remote machine I could test this with. I chose my test server in the Dublin office about 40 some miles away from my location.
    I created an account with LogMeIn Hamachi and downloaded the VPN software on to both servers.
I configured the type of network as hub and spoke, with the home server being the hub. Once connected with the VPN I tried to RDP into the test server from the home server no luck. So to save time I disabled the firewall on the virtual adapter created by Hamachi on both machines. I now had complete 2 way communication going between the servers. I then downloaded the connector software from the home server to the test server and installed it.
   After installing the connector software I configured the backup. I thought this will be interesting, how long will it take to backup over 20 gigs of Data over the Internet, will it actually work or will it time out or just fail outright. Well I got my answer 21 hrs later with a successful completion of the backup. It has been backing up now for over a week successfully, with the ongoing backups taking less that 2 hrs. Pretty cool stuff, Bare Metal Restore would not be feasible over the remote connection but random file restores would be just fine.
   The big question would be is it actually a violation of the EULA to use WHS in this manner and how are Vail and Aurora going to compare functionality wise.

Bypass SBS 2008 RWW Website to connect to Work Computer

I was troubleshooting remote access for a customer when I decided to try to connect to the clients machine using the built-in RDP client. I used the customers computer name as the computer to connect to and the external website name as the gateway address. I clicked connect and much to my surprise it started to connect, gave me a warning about not trusting the machine's certificate, which I promptly by-passed and viola I was connected to their machine without going through the website.

This can come in real handy when you just can't get that darn self signed server certificate installed\ on the home computer. I would have to assume that the proper permissions would need to be in place in the Console as far as connecting to the computer, I have not tested this. Beats having to configure the firewall and the registry to use some non-standard port so a customer can get right into their machine.