17

I found a comfortable way of doing this here: Allocate a static IP address to the VMware vCenter Server Appliance (VCSA) | Ivo Beerens' Blog It also allows you to change hostname, DNS, default gateway and proxy. To sum it up: Open a console session of the VCSA Login as: root Default password is: vmware Execute the following command: /opt/vmware/share/...


16

Grrr... VMware snapshots. If I had my way, they'd only exist for backup purposes and for testing changes. You can view the space consumed by snapshots (which is probably what you're really interested in knowing) by using the "Storage Views" tab at the cluster level in your vSphere client. Start there, then drill down to the individual VMs. The entries that ...


12

Yes, you can change the type. Use the Set-NetworkAdapter powercli cmdlet. The "Type" switch allows you to modify adapter. Note that the VM has to be turned off to do this. https://www.vmware.com/support/developer/PowerCLI/PowerCLI41U1/html/Set-NetworkAdapter.html vSphere PowerCLI can be downloaded here: https://my.vmware.com/group/vmware/details?...


11

By rights, the full process would be: Create a snapshot of the running machine; this frees up the underlying disk files and causes new data changes to be written to delta files Copy the main disk files to the new machine Create another snapshot of the running machine; this frees up the delta files and causes new data changes to be written to new delta files ...


11

The host can only be managed by one vCenter at a time. But you can move hosts to new vCenters in this manner without disrupting the virtual machines.


11

Sounds like a job for PowerCLI! Well, from a Windows workstation, anyway, which is what I have. Get-Snapshot The Surly Admin's blog even has a script that you can copy-pasta to get all the snapshots for all the VMs in your environment, the meat of which I'll post below for your convenience. $Report = Get-VM | Get-Snapshot | Select VM,Name,Description,@{...


10

is your domain "domain.local" or "vsphere.local" You are trying to authenticate with the domain "domain.local" but using the administrator account for "vsphere.local" change you setting for: Username: administrator@vsphere.local to Username: administrator@domain.local See if that doesn't help


8

That list is stored in a Registry key: HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences\RecentConnections. http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1032988


8

You can do this by logging into the host that vCenter is running on directly. Log into the host directly with the standalone console Shut down the vCenter VM Make changes (including deleting the floppy drive) Boot VM Log into VM and expand the disk Profit


8

HopelessNoob's answer is great for a human readable report. Sometimes I prefer to parse mine into other PS objects. It is very similar too HopelessNoob's - I guess we both started from the same code snippet to build our scripts: $VIServer = "vsphere.ad.example.com" If (-not (Get-PSSnapin VMware.VimAutomation.Core)) { Try { Add-PSSnapin VMware....


8

What happened Not sure what had happened, but maybe the whole description helps someone. The internal LDAP directory of vSphere running typically at port 11711 has ended up with corrupt entries. Resulting in strange observation - one could authenticate towards e.g. webclient, but couldn't do more there as it flooded with messages like "Client is not ...


7

There's no reason why not. I'm not aware if VMware specifically direct you to run vCenter on either physical or virtualised hardware, I believe it's supported on both. Depending on what sorts of failures you're trying to protect against, it's usually a good idea to separate your redundant / standby instances from the primary / live instances as much as ...


7

There doesn't seem to be a clean way to fully manage a cold start of a virtual infrastructure once HA is configured on the individual hosts. Enabling HA and DRS seems to disable the Virtual Machine Startup and Shutdown options on the host servers. However, any ordering set before the host is moved into the cluster seems to stick. If the number of hosts is ...


7

What you're talking about is called "hot-cloning," and doing such a clone will result in some level of inconsistency between the two copies. Every way I'm aware of, including the commercial and native implementations of hot-cloning involve taking a snapshot (in one form or another) and then cloning that. This freezes the disk at a certain point in time, so ...


7

You must upgrade vCenter to 5.1 in order to add a host with ESXi 5.1. No vCenter version prior to 5.1 supports ESXi 5.1. References Add an ESXI 5.1 host in vcenter server 5.0 [VMWare Communities] VMWare Product Interoperability Matrix [VMWare Compatibility Guide]


7

If you're not using DRS then you'll have to manually evacuate your powered on VM's to another host in the cluster before VUM will remediate the host. It's also recommended that if you're using HA Admission Control, Distributed Power Management or Fault Tolerance that you disable those features before you remediate the host. In short, migrate (vMotion) your ...


7

This question depends heavily upon your VMware vSphere licensing tier..., the applications and VMs you intend to run and the amount of storage space and performance profile you need. Answer that first, as an organization that can afford to properly license ten ESXi hosts in a vSphere cluster should be prepared for a higher-end storage solution and ...


7

Nope... Your scenario won't work. You will need vCenter Standard to manage more than three hosts. If you attempt to license the Essentials Plus hosts under vCenter Standard, you will receive an error like this: You have a couple of options before resorting to a keygen, though 🐼. You can look into converting your existing Essentials Plus licenses to ...


7

They can help with replication but they need DB quiecing support, otherwise you'll inherently get data corruption. In my experience it's always far better to get the DB engine itself to do the work - they're designed to do just that.


7

If you are ABSOLUTELY CERTAIN the .vmdk files are not being used anywhere else you should be able to safely delete them. I would suggest archiving them (copy them to some other system) first. Sometimes even when you're "absolutely certain" you're wrong and things break. It's useful to be able to restore the files in such cases.


7

In the Windows VMware vSphere Client program -- Select your Datacenter, cluster or host. Select the Virtual Machines tab. Right click an empty area of the window and select "Export List". Type a file name and click the "Save" button. Done. Note that the default file type when exporting the list is htm/html but you can change it to xls or csv (among others)....


7

We have over 100 separate vCenters and every one of them is a VM, it means we get all the usual virtualisation benefits and because we run them on a specific management cluster in the event of one crashing or whatever we can just connect directly to the host they're running on and restart or whatever as needed. We're something like the 4th or 5th biggest ...


7

VMware best practice now is to install vCenter on a VM with HA. That's from a VMware training class when 5 originally came out. HA doesn't require vCenter to actually be working once set up, as the hosts know what to do. I have Essentials Plus, use this setup, and can attest that it works well for us. Just make sure that you have enough capacity on your ...


7

Delete any outstanding snapshots of the vCenter VM, then you should be able to resize the disk while the VM is running.


7

No problems at all... Just deploy the new vCenter Server Appliance (vCSA) and add the extant vSphere hosts. They will lose their association with the old vCenter and join the new vCenter. You will need to reestablish your cluster settings, rules and resource pools, but that's not complicated.


7

Resolved. When looking at the datastore through the vSphere Web Interface (my fault, I still prefer the old client) it correctly shows the 62TB max size limit. Potentially a hardcoded value in the old GUI given it's now deprecated.


7

Add the DHCP role to the physical DC. Authorize the DHCP server. Create an appropriate scope with appropriate options. You'll need to create a Scope appropriate for your network with the appropriate Scope options.


6

I agree with voretaq7 - there is no reason NOT to put vCenter on a AD-joined server when you have the option. A word of advice though - vCenter behaves bad if you mess around with service accounts etc. I'd strongly consider reinstalling vCenter (and all it's children) if you're planning to join the server to AD and already have vCenter installed.


6

99% of the time it's because the power saving features of the underlying OS has suspended or hibernated the machine. We have this issue with our development testing virtual machines. A quick GPO deployment fixed this, but if you don't have a GPO, just go into each VM and tell it not to hibernate or suspend after inactivity. The biggest giveaway is this ...


6

HA's admission control uses something called "slots" for calculating whether there's room available to accommodate all VMs in the event of the configured number of hosts failing. The slot calculation is what is allowing you to continue powering up VMs even as the memory resources in the cluster start to look dire. Admission Control and Slots The "slot" ...


Only top voted, non community-wiki answers of a minimum length are eligible