vNext.be | Operations Manager, Opalis, PowerShell, …

CAT | VMWare

May/11

4

Extend System Center to VMware – Don’t miss Veeam Free Webinars in May!

Extend System Center to VMware

Protect your investments in Microsoft System Center and manage your physical and virtual environment from one console with the Veeam nworks Management Pack™ for VMware.

The nworks Management Pack provides scalable, fault-tolerant and agentless VMware infrastructure monitoring and management directly in Microsoft System Center, eliminating the need for a separate monitoring framework.

Discover the results of our valued customer feedback and what version 5.6 of nworks Management Pack includes.
May 9, Mon,
starts at 10:00 am (GMT+01:00)
Register

Learn how you can protect your investments in Microsoft System Center and manage your physical and virtual environment from one console.
May 25, Wen, starts at 10:00 am (GMT+01:00)
Register

Christopher KEYAERT

· · · ·

Sometime, you have a Virtual Machine in a Microsoft VHD format and you would like to use it with your VMware Workstation application. So this little guide will explain how to perform this operation.

Pre-requisites

 

Step 1

 

Create a working folder on one of your computer drive and paste your VHD file into it.

Step 2

 

For the conversion, VMware Converter needs a VMC file. A VMC is the configuration file of the Microsoft Virtual Machine, it’s in this file that you the all the settings of the VM.

So, download the VMC file that is available here (http://www.vnext.be/wp-content/uploads/2010/09/MyVM.Rename-to-dot-vmc.txt), rename the extension to .vmc and paste it to your working folder:

Open it with notepad and edit the path to your VHD file like below:

Step 3

 

Start VMware Converter 4 standalone

Click on Convert Machine:

  • Select source type : Backup image or third-party virtual machine
  • Virtual machine file : The path to your VHD file


Click on Next and choose the following parameters:

  • Select destination type : VMware Workstation or other VMware virtual machine
  • Select VMware product : VMware Workstation 7.0.x

Click on Next and choose the following parameters:
Adapt the parameters to your need, but be sure that Install VMware Tools is set to YES

Click on Next and review all the information:

Click on Finish and wait the end of the process:

After a few minutes, the process is complete:

Go to your working folder, enter in the new created folder and double click on the .vmx file.

VMware workstation will now start:

Review your Virtual Machine configuration and start your new VM:

After you’re first Log on, Windows will install the drivers related to VMware Workstation, so let the process continue and restart you virtual machine when it’s done:

When all the drivers have been installed and you virtual machine restarted, you will have to reactive your copy of Windows:

When the activation process ended, you could now enjoy your virtual machine with VMware Workstation:

Christopher KEYAERT

· · · · ·

Issue :
Yesterday, I upgraded our Acceptance environment with the version 5.5 of Nworks SCOM MP. And since this upgrade, I have every 5 minutes a disconnection from our Virtual Center servers.
Event Type: Information
Event Source: nworksSource
Event Type: Error
Event Source: nworksSource
Event Category: None
Event ID: 61
Date: 7/15/2010
Time: 9:38:24 AM
User: N/A
Computer: xxxxxxxx
Description:
VC200 Exception connecting to vCenter server xxxxxxxx, Exception: The operation has timed out. VC events will no longer be captured from this system.
Event Type: Information
Event Source: nworksSource
Event Category: None
Event ID: 62
Date: 7/15/2010
Time: 9:39:25 AM
User: N/A
Computer: xxxxxxxx
Description:
VC201 Connection restored to vCenter server xxxxxxxx. VC event capture from this system will resume.

Solution :
The issue has something to do with the VC creating an event filter.
For fixing it, locate files named “vcEvents.xml” on each collector (the default location is C:\Program Files\nworks\VIC\Collector\Resources). Back up these files, because it will be necessary to make changes to them.
Open the files with Notepad,
replace
severity=”verbose”
to
severity=”info”

for all events with “verbose” severity. Restart the collector after that, normally the issue is fixed.

· · · ·

Hello All,

If you only use the command GET-VM, you will receive back the VMs List only from the Virtucal Center that you last connect on. If you want the get all the VM from your both virutal centers, you absolutely need to add the parameter -server $vcs to you command.

If you want to connect to more than one virtual center at the same time, here the starting code :

1
2
3
4
5
6
7
$vcs = @()
$vcs += connect-viserver vc1.mydom.local
$vcs += connect-viserver vc2.mydom.local
# You could add many as you need...

# Command example
get-vm -server $vcs | export-csv C:\Export.csv

In a general way, don’t forget to add -server $vcs to every command than you use with the VI Toolkit.

As always, RTM -> the documentation on VI Toolkit :
http://communities.vmware.com/docs/DOC-4210

Christopher Keyaert

· · ·

Christopher Keyaert
Copyright 2010 © vNext.be