new1234.jpg

Archive

Posts Tagged ‘Console’

VMware: Repeated characters when typing in remote console

April 7th, 2015 1 comment

Everyone knows the hanging keyboard console session issue, when you type your username or password the keyboard hangs. If you access a virtual machine console over a slow connection, you’ll encounter keyboard sync issues

If you open a remote console to a virtual machine from a slow network connection (such as a VPN) while tethered to a mobile phone providing Internet access, the experience is not optimal, as keyboard and mouse gestures aren’t timed exactly the same. This is especially problematic if you try to enter a password where the characters are masked.

image

  

Solution

There are two ways to add a extra line in the configuration file of the virtual machine,

 

Option 1. Edit VMX file directly

1. Power off the virtual machine.

2. Add a line, similar to this, at the end of your virtual machine’s configuration (.vmx) file

keyboard.typematicMinDelay = "2000000"

The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it.

image

3. Power on the virtual machine.

 

Option 2. Edit VMX via vSphere Client

1. Power off the virtual machine.

2. Edit settings > Options > General > Configuration Parameters, add new row with text:

keyboard.typematicMinDelay = "2000000"

The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it.

image
3. Power on the virtual machine.

 

Ps. You can edit the .VMX files directly, but a better practice is to configure this value within the vSphere Client for a virtual machine template. When you consider that most of the access to a virtual machine is provided by tools such as remote desktop, there is no harm in configuring this value globally for all virtual machines that originate from a template

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: How to check HBA firmware version without rebooting ESX host

February 25th, 2011 4 comments

I need to find out witch firmware version is running on my HBA without rebooting the ESX host.. I thought this was possible by GUI but couldn’t find it, so I decided to check this by console. Give the following commands:

Navigate to:

– cd proc/scsi/qla or lpfc820
– ls –lia

To view the HBA information:

– cat 6
– cat 7

Result:

image

 

It wasn’t so difficult!

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Console-setup, Configure or Troubleshoot the ESX Service Console

December 2nd, 2010 No comments

Oke.. I didn’t know this feature, last week a colleague consultant shows me a little menu to (re-)configure the ESX service console. With the command “console-setup” you can add or delete some vSwitches, create a new SC and view current configurations.

If you never worked with ESX CLI then will this a nice feature to setup/troubleshoot the SC.

image

The option “Console-setup” is available since ESX 4.0 update 2

Menu structure:

When you console-setup as root from the service console, you are presented with this menu:

1. Show Current Service Consoles

2. Show Network Adapters

3. Show vSwitch/vDS Information

4. Delete Service Console

4.1 Select the interface to delete, defaults to vswif0

5. Configure Service Console

5.1 vswif ID, default to vswif0

5.2 Name of service console port group: default to “Service Console”

5.3 vSwitch for service console, default to vSwitch0

5.4 IP Address:

5.5 Subnet mask:

5.6 Default gateway:

5.7 VLAN ID: default to 0

5.8 vmnic to use for the service console

5.9 Save Changes

5.10 Return to Menu

6. Exit

Use:

  • Options 1,2 and 3 for display current information
  • Option 4 to remove an existing service console interface (vswif). You may also do this, if you want to recreate it.
  • Option 5 to change the configuration of an existing vswif interface, or for creating a new one.

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Cleanup bootloader after upgrading from ESX 3.x to vSphere 4.0

November 5th, 2009 2 comments

After upgrading from VMware ESX 3.x to ESX 4.0 you can cleanup the bootloader from the older ESX 3.5 installation. You can do this from the console of by connection the host with ssh, give the command “cleanup-esx3”

image 

Little note: You can run the cleanup-esx command as long as everything works for you in 4. If you use the -f flag, the software prompts you to confirm that you want to disable the ability to roll back to the ESX 3.x.x.

Thanks xchello from Dutch VMug for the tip!

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , , ,

VMware: VM Console error: Unable to connect to the MKS: Failed to connect to the server (1010828)

August 29th, 2009 29 comments

“Unable to connect to the MKS: Failed to connect to the server 172.16.254.202:902” or “Unable to connect to the MKS: Failed to connect to the server no such host is known”

image

Solution:

To avoid losing access to the ESX host, perform the following steps:

1. Add the ESX server in your DNS

2. Edit your hostfile on the workstation (C:\Windows\System32\Drivers\etc\hosts\) and add your ESX server

 

After adding the ESX by DNS in my hostfile and restarted the VI Client I was able to open Console screen.

[ad#ad-banner]

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

Categories: VMware Tags: , , , ,

Microsoft: Black RDP/Console screen on Windows 2003

March 16th, 2009 1 comment

Het kan wel eens voorkomen dat een server spontaan een zwart scherm geeft op de console of tijdens een RDP sessie. Enkel is dit op te lossen met een herstart van de server, soms ook niet. Het is vaak gokken waar het gebruikersnaam, wachtwoord en domain moet invullen. Zie voorbeeld:

image

 

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn