Take the time to learn some basic powershell. PowerCLI is just powershell commands for VMware. Just an added module with a bunch of cmdlets. Send-MailMessage -To "email@domain.com" -From "No...
See more...
Take the time to learn some basic powershell. PowerCLI is just powershell commands for VMware. Just an added module with a bunch of cmdlets. Send-MailMessage -To "email@domain.com" -From "Noreply@domain.com" -SmtpServer "IP address of email server or DNS name" - Subject "Snapshot Report" -Attachments C:\scripts\ssmail.txt
I can't get VUM to work at all using Webclient. I try to do a scan of a host and the status of the task just sits at "starting" and nothing ever happens. I have to use the thick client to use Up...
See more...
I can't get VUM to work at all using Webclient. I try to do a scan of a host and the status of the task just sits at "starting" and nothing ever happens. I have to use the thick client to use Update Manager.
I have a powershell script that emails me daily each VM that has a snapshot and the snapshot name. It integrates with powerCLI. I use it to clean up stale/obsolete snapshots other admins forget ...
See more...
I have a powershell script that emails me daily each VM that has a snapshot and the snapshot name. It integrates with powerCLI. I use it to clean up stale/obsolete snapshots other admins forget about. Get-VM | Select-Object -ExpandProperty Name | Out-File "C:\scripts\VMList.txt" Get-Snapshot -VM (Get-Content C:\scripts\VMList.txt) | Select-Object VM,Name | Format-List | Out-file C:\scripts\ssmail.txt
Yep make sure the check box under the virtual CDROM is set to 'Connect at power on'. That's usually what gets most people who aren't familiar with VMware.
Install ESXi on your two hosts. After that you have a choice for vCenter. 1. Build a windows server and install vCenter on it with a DB backend. 2. Deploy the virtual vCenter appliance. Once...
See more...
Install ESXi on your two hosts. After that you have a choice for vCenter. 1. Build a windows server and install vCenter on it with a DB backend. 2. Deploy the virtual vCenter appliance. Once installed download the ViClient and point it to the IP address (or dns name) of your vCenter server. Once logged in you can then add your ESXi hosts by IP or DNS name. What is your connection speed between your two sites. You are going to need a healthy link if you want to use it for D/R purposes.
What exactly takes 45 minutes to boot? vCenter or ESXi? When we upgraded our vCenter to 5.5u1b and rebooted our vCenter server services took about 45 minutes to start running. Subsequent rebo...
See more...
What exactly takes 45 minutes to boot? vCenter or ESXi? When we upgraded our vCenter to 5.5u1b and rebooted our vCenter server services took about 45 minutes to start running. Subsequent reboots did not take that long, we attributed it to the upgrade and perhaps vCenter was doing things behind the scenes after the 1st reboot post upgrade.
Did you check Unisphere to make sure the SAN came up cleanly? We have a CX4-120. I would start with that first check all the communication path's between the SAN, your FC switches and the ESXi...
See more...
Did you check Unisphere to make sure the SAN came up cleanly? We have a CX4-120. I would start with that first check all the communication path's between the SAN, your FC switches and the ESXi hosts. If all looks good I would do a reboot of each ESXi host and see if maybe it was an issue because both the SAN, switches and ESXi hosts were powering up at the same time. Sounds scary. Good luck.
Actually one of our admins did this exact process yesterday. He accidentally used an older ISO (Non R2) to create the VM originally. A couple of mouse clicks later and a reboot and it was upgrad...
See more...
Actually one of our admins did this exact process yesterday. He accidentally used an older ISO (Non R2) to create the VM originally. A couple of mouse clicks later and a reboot and it was upgraded to R2 with no issues. Childs play!
I know for a fact you can run them with the same - uuid.bios I know this because our Trend Micro Deep Security Manager was burping this exact alert on a few VM's another admin cloned and di...
See more...
I know for a fact you can run them with the same - uuid.bios I know this because our Trend Micro Deep Security Manager was burping this exact alert on a few VM's another admin cloned and didn't clean up properly. I had to power off the VM and delete that line in the VMX file of the VM. When you power it back on it generates a new randing UUID. Interestingly enough VMware itself didn't seem to care or alert in any fashion. I cannot speak to the other portions being the same as the poster above mentioned. I am merely speaking about the bios ID.
That would be nice Nasshan, I pitched VMware to my current company back in the ESX 3.5 days, since then we have spent an ungodly amount of money for VMware. I would like to think my opinion is va...
See more...
That would be nice Nasshan, I pitched VMware to my current company back in the ESX 3.5 days, since then we have spent an ungodly amount of money for VMware. I would like to think my opinion is valuable to VMware but in reality I know better. I can tell you this I wouldn't pitch VMware anymore. If and when I move on in my career and they are looking to virtualize systems I would voice my suggestion for Hyper-V over VMware at this point. The on going cost of VMware for support is insanity not mention that vSphere seems to get more buggy/slow/cumbersome ect.. on every release. Remember the nightmare rollout of SSO with vCenter, how many updates to the updates did they put out before they got it half right!? THANK GOD we held off on upgrading vCenter after reading horror story after horror story on these forums. Eventually they got most of the upgrade woes resolved and that's when we finally upgraded. Remember way back when no one would install Microsoft service packs as soon as they came out because everyone was afraid of it blowing up their machines? Then MS would release an updated SP that fixed the issues. Kinda how I feel about VMware's updates now. No first adopter here anymore. Now I sit back and watch the carnage unfold on the forums and wait to upgrade vSphere. Lets also not even get started on VMware's HORRID documentation that contradicts itself and points to other documents that can put you in an endless loop.
Just for kicks I tried yesterday to force myself to use the web client. All I wanted to do was kick off a simple scan of Update Manager to see if my hosts needed patches. It said it was 'startin...
See more...
Just for kicks I tried yesterday to force myself to use the web client. All I wanted to do was kick off a simple scan of Update Manager to see if my hosts needed patches. It said it was 'starting' the task and just sat there forever. Nothing ever happened. Looking in the fat client I saw that it made no attempts to scan the host for patches. In short it didn't work. Then I tried to look at my vShield / Endpoint settings through the web client.....no where to be found. Web client is garbage.
I've been using the VIC to manage our environment since forever. I am starting to move away from the VIC to use the vSphere web client. I cannot seem to find the vShield section for the hosts. ...
See more...
I've been using the VIC to manage our environment since forever. I am starting to move away from the VIC to use the vSphere web client. I cannot seem to find the vShield section for the hosts. On the VIC its simple click on a host and there you see the vShield tab. Where the heck is this in the web client?! Thanks
Our DRS does the same (sort of). We will have some hosts with 80% memory usage on while others sit at 40-50%. I would think DRS would balance that out but it doesnt. It has to get real bad before...
See more...
Our DRS does the same (sort of). We will have some hosts with 80% memory usage on while others sit at 40-50%. I would think DRS would balance that out but it doesnt. It has to get real bad before DRS kicks off an automatic migration.
I had to purge all the updates from the folder where VUM stores the updates (we are running vCenter on Windows not the virtual appliance). After purging them VUM redownloaded everything. This wa...
See more...
I had to purge all the updates from the folder where VUM stores the updates (we are running vCenter on Windows not the virtual appliance). After purging them VUM redownloaded everything. This was back in vCenter 4.x days..
Download the ESXi 5.5 software from VMware, it will come as an ISO image. Burn to a DVD or virtually mount the image to your physical server and set the machine to boot from CD-ROM. It will w...
See more...
Download the ESXi 5.5 software from VMware, it will come as an ISO image. Burn to a DVD or virtually mount the image to your physical server and set the machine to boot from CD-ROM. It will walk you through setting up/installing ESXi. Its nothing more than a few mouse clicks and providing some network info (IP,subnet,gateway ect..) That will get you ESXi installed on your physical server. After that download the VMware Viclient and point it to the IP of your ESXi server and connect. From there you can proceed to create VM's ect..