You are currently browsing the category archive for the ‘Virtualization’ category.

Was running a Lync Server 2010 Training (MOC 10533A) throughout this week and in order to use the licenses within the MOC Labs, the date & time needs to be reverse (back to the future!)

As most of the lab machines are cloned using the actual date & time, Hyper-V creates a certificate the moment the Virtual Machine is being created and started; only during the class, the date & time will be reverted back in time. When attempting to Connect (or literally remote control) the VM, the status of the VM will show as ‘Starting…’ and subsequently throw with errors:

An Error Occurred while attempting to start the selected Virtual Machine(s):

‘Virtual Machine Name’ could not initialized

Could not initialize machine remoting system. Error: ‘Element not found.’ (0x80070490).

Could not find a usable certificate. Error: ‘Element not found.’ (0x80070490).

To resolve this matter, follow the steps below:

  1. Start > Run > MMC
  2. Add the Certificates Snap-In
  3. Select Service Account
  4. Under the Select Account to Manager, select Hyper-V  Image Management Service
  5. Complete the Snap-In Wizard
  6. Expand the Certificates under Personal Category
  7. Notice the certificate generated has been created ‘for the future’ (assuming you’re suppose to revert the date & time to 2010, the certificate should display as invalid because it was created at 2013)
  8. Delete the Certificate(s)
  9. Go to the Services Console and Restart all Hyper-V Services

Now, go back to the Hyper-V Manager and the VMs should be able to be ‘Connected’ right now.

Happy New Year to all of my visitors

For the benefit for all my blog visitors, if you’re running a Lync lab environment and needed to test out audio output & input (recording), only Windows 7 Enterprise & Ultimate editions supportd these 2 functions when RDP into the Virtual Machine (link)

By default, Audio Recording is disabled. To enable it, go into the registry of the VM: HKLM\System\CurrentControlSet\Terminal Server\WinStations\RDP-TCP\fDisableAudioCapture. Change the value from 1 to 0 and reboot the machine to take effect.

As curious as anyone else, Chrome OS was a hot topic with Windows 7 out there and I couldn’t wait till the final release. So, I’ve manage to get hold on the beta download of Chrome OS Beta 0.5.307.  Although the download states is a LiveCD, worry not as you’ve got an option to install the entire OS into your hard drive. For this article, I’m gonna walk-through the installation of Chrome OS running on Hyper-V.

Chrome OS is built based on OpenSuse’s kernel, hence if you happen to use other Linux OS such as OpenSuse, Chrome OS has nothing far of a difference, just additional embedded applications on its own like Picasa.

One thing to take note about Chrome installation is: You need as much bandwidth as possible, reason is most of the installation are downloaded from the Internet during the process.

Beginning of the installation is pretty simple:

1. Create an empty VM just mount the ISO onto your VM and boot it up. I’ve create about 40GB of dynamically expanding hard disk with 1GB of memory allocated

2. Once the Image has been fully loaded, click the Live Installer from the Desktop. The installer will download components from the Internet to begin the installation. Along the progress, accept the default configurations Chrome.

3. Once complete, shutdown the VM and unmount the ISO to get the VM fully loaded.

Although this is just a desktop level of OS, wanted to see the difference on having Hyper-V Linux Integration Components(Linux-IC) installed onto Chrome OS. You can get the

1. Part of the pre-requisite, the C/C++ Compiler and Tools are required before installing the Linux-IC. To get these components installed, go to the Start Menu, ops, should be Computer Menu at the bottom of the taskbar and select Install Software. You’ll be prompt for the root password, so just go ahead and key in the password that was key in during the first installation of Chrome OS.

2. As you can see, Chrome OS will then download the available list of software/components from OpenSuse.

3. Once the Software Manager is loaded, search for the C++ component at the Right. I’ve got mine installed but you should see something similair below. During this installation process let, make sure your Internet bandwidth is clear else you’ll need to keep on clicking on the RETRY button to continue downloading the packages from the Internet.

4. When is done, mount the Linux Integration Component ISO onto the VM and launch the Gnome Terminal. Run the following commands to copy the Linux Integration Components files into the local machine

Terminal > su
Terminal > yourpassword
Terminal > cd /
Terminal > mkdir /opt/linux_ic
Terminal > cp -rp /media/CDROM/* /opt/linux_ic -r
Terminal > /opt/linux_ic -r/ drivers
Ops….a problem:
Checking if required components are installed…
No kernel-devel or kernel-source package installed. 
You must install this package before installing the drivers.
Worry not, from the same terminal, run the following command:
Terminal > sudo zypper in -t pattern devel_kernel
There’s almost 124 packages that Yast2 (Chrome Control Center) would required to be downloaded, it took me almost 1 night to complete the download. Again, make sure your Internet bandwidth is clear for this operation. Once completed, you’ll run the same command again
Terminal > /opt/linux_ic/ drivers
Terminal > Checking if required components are installed…done.
Installing Linux integration components (vmbus, enlightened ide, enlightened scsi
and network drivers) for Hyper-V…
Building vmbus driver…An error has occured during the setup!
Please view the drvinstall.err for more details.
What’s this? Another error? Grrr…OK, the problem comes about is because we’ve updated the system with a ‘new’ kernel and Yast2 needs to be updated as well, so run this command (Again, you need bandwidth):
Terminal > sudo zypper update
When the download is complete, reboot the VM; and now, we’re ready to go! Launch the Gnome Terminal again:
Terminal > su
Terminal > yourpassword
Terminal > /opt/linux_ic/ – drivers
Terminal > You’ll get a bunch of Done output
Terminal > reboot
Before you end here, run this command after the VM has come back online, launch the Gnome Terminal to verify the installation is successfull:
Terminal > lsmod | grep vsc
Terminal > (output as below)
Overall, the sytem is smooth but nevertheless, I’ve yet to explore the full functionalities out of it. Probably I’ll reserve this till for my next posting 😉 
%d bloggers like this: