Backtrack:  
 
showing posts tagged with 'vmware'
by lunarg on April 20th 2015, at 15:42
There are two methods of uninstalling vSphere Replication from your vcenter, depending on whether or not the replication appliance is still present and accessible.

Unregister the appliance from vCenter, then turn off and delete the appliance.

If not turned on, turn on the replication appliance.

Stop all replications in both directions.

Disconnect any open connections to other replication sites.

Connect to the VAMI of the appliance through web: https://vr-appliance-address:5480

From the Configuration tab, click Unregister from vCenter server.

In the vSphere Web client, power off and delete the replication appliance. The plug-in will be uninstalled automatically.

...
by lunarg on March 19th 2015, at 12:39
Using the vSphere (Web) Client, it is only possible to "upgrade" your virtual hardware to the latest version supported by your ESX host. Sometimes, it's necessary to set the hardware version to a specific version, rather than just the latest supported one. This can be done through PowerCLI (for use with vCenter) or ESXi Shell (for free ESXi).

Before you begin, note that you have to power down a VM before you can change the hardware version.

You need VMWare vSphere PowerCLI installed on a computer, and access to a vCenter server (can be appliance or full version for Windows) with the necessary credentials.

Connect to the vSphere server:

$cred = Get-CredentialConnect-VIServer -Se  ...
by lunarg on March 9th 2015, at 11:15
You can easily reset the root password on linux-based VMWare appliances through the boot loader. For this to work, you need access to the console of the appliance (i.e. through vSphere (Web) Client), and needs to be performed during offline hours as the appliance has to be rebooted.

Reboot the appliance, and as soon as you see the GRUB boot loader, halt the automatic boot timer by hitting any key (I usually move the selection using the arrows).

Select the first entry, and press e, allowing you to type in some text. At the end of the line that starts with kernel, add the following text:

init=/bin/bash

Do not remove any other text. Then press Enter to confirm.

Press b to continue the boot  ...
by lunarg on February 18th 2015, at 14:19

ViewDbChk is a free tool that helps you overcome and clean up database inconsistencies for VMware Horizon View, the VMware solution for VDI.

The tool, available for version 5.3 and 6.0, can be downloaded through the link below. When downloading, be sure to select the correct version.

https://labs.vmware.com/flings/viewdbchk

by lunarg on January 27th 2015, at 12:56
You may get an error during the upgrade of Veeam Backup & Recovery to version 8, stating that the vPower NFS service is unable to start. Alternatively, when updating the individual components, you may also get a similar error (such as: "Error 1920.Service Veeam vPower NFS Service (VeeamNFSSvc) failed to start. Verify that you have sufficient privileges to start system services.").

There are several reasons possible for this, but the most likely one is a wrong NFS Datastore path specified in the registry, usually because the drive that the datastore is pointing to, is no longer present.
Another reason could be that your server has the "NFS sharing" feature installed,   ...
by lunarg on December 12th 2014, at 12:52
When you have some VMs with thin provisioned disks, you may have noticed that these will continue to grow, and never shrink, even after cleaning out data from within the VM. Currently, VMware does not have automatic space reclamation, unless you're running a SAN which supports this (and you have the necessary components installed, such as EqualLogic's HIT-kit). Luckily, there are some tools to allow you to reclaim unused space from your virtual thin disks. The only downside is that you have to power off the affected machines.

Reclaiming disk space only works when the blocks on your virtual disk are really empty. Deleting data usually only removes the entries from the file allocati  ...
by lunarg on November 26th 2014, at 10:19

You can use the Guided Search Wizard for VMWare Compatibility Matrix to figure out if a certain version of ESX or feature is supported by a certain server or hardware platform:

http://www.vmware.com/resources/compatibility/wizard/request.php

by lunarg on September 9th 2014, at 12:04

Shutdown the VM.

Open .vmx file with Notepad or another plain text editor.
Add these lines:

hypervisor.cpuid.v0 = "FALSE" 
mce.enable = "TRUE"
vhv.enable = "TRUE"
vpmc.enable = "TRUE"

Save and start the VM. Now you can install the Hyper-V role.

by lunarg on August 14th 2014, at 14:17
In certain cases when deploying machines from a template using deployment customization, parts of this process may fail. As a result, upon each reboot, the system may try to re-run the customization process, and the following message is displayed at each startup:

VMware Image Customization in progress

To remove any pending sysprep customization routine, you can manually remove the reference to it by editing the Windows Registry

Start regedit.exe.

Navigate to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\.

Change the value of BootExecute. Remove the part that says sysprepDecryptor.exe. Leave the other parts of the value as they were (so only remove the one w  ...
by lunarg on January 8th 2014, at 12:34
Even though you've unchecked the time synchronisation checkbox in VMware Tools, synchronisation may still occur. Particularly when a certain action is performed, such as a power-off/power-on, suspend/resume, snapshot handling, etc., time synchronisation will still occur.

To complete disable time synchronisation, even during the events mentioned, you have to add additional parameters to the VMware VM configuration. There are two ways to do this.

Note that you need to have the machine powered off before you can do these changes.

Use a text editor to directly edit the .vmx-file, adding the required parameters:

tools.syncTime = "0"time.synchronize.continue = "0"time.synchronize.restore = "0"  ...
by lunarg on December 16th 2013, at 16:06

Before installing ROK licenses on your virtual machines on VMware, be sure to allow SMBios reflection of the host to the VM's. Otherwise, authorization will fail with a This system is unsupported message.

To do this, go to the settings of your newly created VM. Click the tab Configuration, then click General, then the button Configuration Parameters. Add a new row:

SMBIOS.reflectHost = TRUE

by lunarg on April 3rd 2013, at 10:15
Currently, vCenter Server 5.1 is not supported on Windows Server 2012. Trying to install usually results in several errors, but they can be resolved with some workarounds and things to consider. This post is a gathering of (some of) those things.

First of, be sure to install .NET 3.5 using the Server Manager. It can be found as a feature. The installation delivered in the vCenter installation cannot be installed.

It's best to install the required components (SSO and Inventory Service) separately to ensure the installation of the different components goes smoothly. You will have to type in and remember the SSO passwords though.

Upon installation of the vCenter Server, it will insta  ...
by lunarg on March 19th 2013, at 14:29
If a host cannot be managed via vCenter or from vSphere client, you can still use the CLI (on the host itself or via network using SSH or vSphere CLI/RCLI) to partially manage the VMs on the host.

For this to work you must have already enabled the local console, Tech Support Mode and/or SSH access:

Enabling root SSH login on an ESX host (8375637)

Tech Support Mode for Emergency Support (1003677) (ESXi 3.5 and 4.0 only)

Using Tech Support Mode in ESXi 4.1 and ESXi 5.0 (1017910)

Once logged in, you can use these commands to control the VMs. Note that there are differences between ESX and ESXi.

table.score th { border-left: 1px solid #094269;}table.score th.first { border-left: none} tabl  ...
by lunarg on February 13th 2013, at 16:41
After upgrading ESXi to 5.1 on an USB device, you may get a warning message stating that the system logs are stored on non-persistent storage.



Since version 5.1, system logs are kept on the default scrap partition. If it's not specified, it defaults to ramdisk, which is non-persistent; upon rebooting, the system logs will be cleared.

To resolve the issue, you can manually specify a location for the logs to be stored. This can be any configured datastore (VMFS or NFS). To configure this, go to the configuration of your ESXi host, Software, Advanced Settings.



In the tree on your left, find the Syslog, global configuration section and enter a datastore name in the field Syslog.global.log  ...
by lunarg on November 14th 2011, at 15:29
If you're running RDS on a vSphere server with VMware Tools installed, you may have noticed the evergrowing presence of vmwaretray DMP files in the user profiles. These are crash dumps from the VMware Tray icon, which is ran during every session.

The reason for this crash dump is an error which is caused by lack of read access to a certain key in the Windows registry by your regular (domain) users.

This key is called HKEY_LOCAL_MACHINE\Software\VMWare. Inc.\VMWare Tools.

Set the permissions on that key to read access for the users logging on to the server, and your problem should go away.

Hint: you may also wish to remove the icon altogether. This is done by setting a certain registry va  ...
by lunarg on November 14th 2011, at 15:28

If you're running RDS on a vSphere server with VMware Tools installed, you may wish to remove/hide the system tray icon. This can be done by setting a certain registry value.

The registry value is:

  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Tools
  • Value: ShowTray

Change the value to 0 will effectively disable the icon the next time a user logs on.

by lunarg on April 4th 2011, at 15:51
With the installation of VMware ESXi 4, data stores will automatically be created using the default settings. This includes a block size of 1 MB. If you don't want that, you could delete the empty datastore and create a new one.

Sometimes, deleting the empty datastore fails with the message:

Quote
Call "HostDatastoreSystem.RemoveDatastore" for object "ha-datastoresystem" on ESXi "xx.xx.xx.xx" failed.

VMware's KB 1017104 provides the solution for another problem, but this works just as well with this issue, with a little variation.

Notice
Performing the steps in this solution will totally utterly destroy your data store. Do not use it if there's still any req  ...
by lunarg on March 7th 2011, at 15:22

In VMware ESXi 4.1, by default, the video drivers are not correctly installed. This is because of the fact that the old driver (which is installed by default) is a WDM type of driver. This type of driver has been kicked out of Windows 7 and Windows 2008R2 in favour of the newer WDDM driver architecture. As a result, the video is reverted to the Standard VGA adapter, which has terrible performance.

However, installing the VMware Tools does provide a correct driver, even though it is not installed by default. To install it, see the second chapter of the article: Windows 2008 R2 console freezes in vSphere console.

by lunarg on October 15th 2010, at 11:54
At work, I'm currently deploying a Windows 2008 R2 on a VMware ESXi 4.0, and noticed an odd behaviour. At irregular intervals, the console of the guest OS simply locks up and doesn't do anything anymore. Networking and remote access seem to work fine, it's just the console that is freezed. Restarting the vSphere client doesn't help, and the only way to get rid of the problem is by hard-resetting the VM. The issue only occurs on Windows 2008 R2, the other VMs run fine.

The problem is caused by the VMware SVGA II driver, and has two underlying issues: the driver itself, and an apparent lack of video RAM (due to the new HW-accelerated GDI of 2008R2/Win7).

The most quickest way is to get rid o  ...
showing posts tagged with 'vmware'
 
 
« January 2018»
SunMonTueWedThuFriSat
 123456
78910111213
14151617181920
21222324252627
28293031   
 
Links
 
Quote
« Have you tried restarting your computer, Sir? »
first answer of any tech support