You can register for this event here:
I will be there 😉
If you want to look up this event in your country please take a look here :
If you have not patched your esx/esxi, do it!
Patch overview : http://www.vmware.com/security/advisories/VMSA-2011-0007.html
ESX3.5 and ESX3.03 are safe.
Patch can be obtained here: (ESXi410-201104001 )
Unzip it and copy files to your esxi box(you should have embeddedEsx directory after unpacking)
esxupdate -m metadata.zip update
Make sure that host is in Maintenance mode, and machines are powered off, or migrated to other host in cluster if you have one. After installing all patches reboot your host.
After reboot check if patches were installed by typing:
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_esxupdate.pdf -> you can read vmware manual regarding updating your host
http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/vihostupdate.html -> here is short manual for vihostupdate if you want to upgrade it using rcli like vMA
My friend had to convert a machine from vhd to vmdk, i was really suprised that this can be done using the software that i have been using for 2 years 😉
and the winner is : WINIMAGE 🙂
On ntpro.nl it is well documented with screenshots.
PS C:\> gc c:\test.out
The reason why ‘gha’ is in second line is that $var2 had a special sign of new line in it.
What i wanted to see in this file is to see 1 line ” abc def gha”. That’s just an example. I was printing to file some vms report and noticed that instead 1 line i had several variables that were making new line. In order to be sure that there is no additional characters besides text we can trim our variables.
PS C:\> echo “$var1 $($var2.trim()) $var3” > c:\test.out
PS C:\> gc C:\test.out
abc def gha
So whenever you will see in output files unexpected new lines, just trim the variable. For people who are starting with powershell : $() means sub-expression, you can read about it here :
or you can read about it from your powershell console typing:
help about_operators | more
I was wondering why my script does not show any iso files mounted for a VM. It took me some time to find it out…
So when you are suspecting your powercli version that you have the same buggy version, just remember that there is wrong property name, there is no “iso”, instead use isopath . Quick example:
get-cddrive -vm VM-NAME | select-object name, isopath
I was reading deinoscloud blog, and noticed 1 news, a GREAT NEWS !!!!
You can register for free vmware online course at:
About the course, let me paste the overview :
” This self-paced training course covers the requirements and effects of transitioning your VMware vSphere™ environment to VMware® ESXi. It provides the knowledge necessary to make fundamental design decisions and successfully add ESXi to a deployed vSphere environment. This course is based on ESXi 4.1.”
As deinosCloud writes :
“By completing the Transition to ESXi Essentials course and the short survey that follows at the end, you will also receive a FREE ebook copy of “VMware ESXi: Planning, Implementation, and Security” authored by Dave Mishchenko and edited by VMware technical experts. Dave’s book is truly a phenomenal resource for all VMware users to learn everything there is to know about ESXi. While the Transition to ESXi Essentials course will remain available for free in the VMware Education Services portal, we’ll be able to also offer Dave’s book for free only while supplies last. So, hurry up, complete the training and turn in your survey as soon as possible!”
I hope there will be still 1 for me 😉
in next few days i will try to write some lessons on basic powercli usage, i thought that we could do a simple program that demontstrates retreiving data from ESX. Here is a small preview of how this program will look like. I will divide this course into 4-5 lessons, and on the last one you should see the same result on your screen as on this screenshot.