ESX

Importing Virtual Machine Templates: vCenter

Note:
In most cases, only system administrators can import virtual machines from vCenter

To import a virtual machine template from vCenter

In the left pane, select VM Templates.

Click Import VM Template.

Type a name.

(Optional) Type a description.

Select vCenter and select a virtual machine that is not managed by Lab Manager.

Click Next.

(Optional) Deselect the Perform customization check box if you do not want Lab Manager to customize the network settings for the virtual machine template or virtual machines based on the virtual machine template.

Specify the networking information for each NIC in the imported virtual machine template:

Select the Connected check box.
Choose a default virtual or physical network.
Choose a default IP addressing mode.

Select a storage lease.

Select a deployment lease.

Select the datastore to which you want to import the virtual machine template.

Select whether to copy or move the source virtual machine template.

If you copy the virtual machine template, it continues to exist in the original location, but if you move the virtual machine template, it will not exist in this location.

Click Import and then you wait…

Lab Manager imports the virtual machine template into the current organization and displays it on the VM Templates page.

vSphere – Creating User and Group Permissions

Create Privileges

  1. Click “View | Administration | Roles”
  2. Right client and cick “Add”
  3. Select a name and select the required privileges

Create User

  1. Click on the “Users and Groups” tab
  2. Click on the “Users” button
  3. Right click and select “Add”
  4. Specify the desired User Name, Password, etc and Click “OK”

Create a Local Group

  1. Click on the “Groups” button
  2. Right click and select “Add”
  3. Enter the group name you want and enter the User Name you created above in the User Name field and click Add
  4. Click “OK” to create the group

Assign Permissions

  1. Click on the “Permissions” Tab
  2. Right click and Select “Add Permission”
  3. Click on the “Add” button and select the Group you created above and click on the Add button.
  4. Click on the OK button.
  5. Choose the Assigned Role (Priviages) and click “OK”.

Note : You can use the permissions tab in either the main inventory (main page) or per Virtual Machine. This is useful to know if you need to allow one user to access just one Virtual Machine.

ESXi 4 – Tech Support Mode

Tech Support Mode (TSM) provides a command-line interface that can be used by the administrator to troubleshoot and correct abnormal conditions on VMware ESXi hosts. TSM can be accessed in two ways:
  • Logging in directly on the console of the ESXi server
  • Logging in remotely via SSH
Both of these methods can be disabled, and an optional timeout value can be configured to disallow local and remote TSM access after the specified timeout period.

Enabling and Accessing Tech Support Mode

To enable local or remote TSM from the Direct Console User Interface (DCUI):
  1. At the DCUI of the ESXi host, press F2 and provide credentials when prompted.
  2. Scroll to Troubleshooting Options, and press Enter.
  3. If you want to enable local TSM, select Local Tech Support and press Enter once. This allows users to login on the virtual console of the ESXi host.If you want to enable remote TSM, select Remote Tech Support (SSH) and press Enter once. This allows users to login via SSH on the virtual console of the ESXi host.
  4. Optionally, if you want to configure the timeout for TSM:
    1. Select Modify Tech Support timeout and press Enter.
    2. Enter the desired timeout value in minutes and press Enter.
  5. Press Esc three times to return to the main DCUI screen.
To enable local or remote TSM from the vSphere Client:
  1. Select the host and click the Configuration tab.
  2. Click Security profile > Properties.
  3. Click Local Tech Support or Remote Tech Support (SSH) and click Options.
  4. Choose the desired startup policy and click Start, then click OK.
  5. Verify that the daemon selected in step 3 shows as running in the Services Properties window.
To configure the TSM timeout value using the vSphere Client:
  1. Select the host and click the Configuration tab.
  2. Click Advanced Settings.
  3. Change the UserVars.TSMTimeOut field to the desired value in minutes.
  4. Click OK.
To access the local TSM:
  1. At the main DCUI screen, press ALT+F1 simultaneously. This opens a virtual console window to the host.
  2. Provide credentials when prompted.Note: When typing the password, characters are not displayed on the console.
To access the remote TSM:
  1. Open an SSH client.
  2. Specify the IP address or domain name of the ESX host.Notes:
    • Directions may vary depending on what SSH client you are using. For more information, consult vendor documentation and support.
    • By default, SSH works on TCP port 22.
  3. Provide credentials when prompted.

ESXi 4 on USB Thumb Drive

I have no doubts there are many people writing about this; so add me to the list.  I wanted to setup my small ESXi 4 Server to boot from USB media so that I no longer needed to have a local drive in the machine I use as a server.

Using VMware Player and a USB Stick, I was able to do this in a few simple steps.

[Step 1] Create a new 64bit virtual machine – this is very important as ESXi requires this.  Make sure that the virtual machine is configured with a USB controller.  I had also removed the virtual hard disk and other devices such as sound card, and printers, etc.

[Step 2] Mount the ESXi Install ISO and insert a USB Thumb Drive

[Step 3] Power on the virtual machine and make sure the USB Thumb Drive is made available

[Step4] Run thought the ESXi installer and select the USB drive as the installing disk – At this point we are just waiting for the installation to complete.

[Step 5] When completed, you will be asked to reboot the system.  At this point you can reboot and remove the USB Thumb Drive from the computer and plug it into your server.   Make sure your server is set to boot from the USB Thumb drive

When completed you will have ESXi running and you are good to go.  Enjoy!

VIM_VCDB database ‘PRIMARY’ filegroup is full (part 2)

After cleaning up your Virtual Center Database to get us back and running I came across the following

vCenter Server 4.x has a Database Retention Policy setting that allows you to specify when vCenter Server tasks and events should be deleted. Since this setting does not affect performance data records it is still possible to purge or shrink old records from the database using the scripts attached to this article. To access the Database Retention Policy setting in the vSphere Client, click Administration > vCenter Server Settings > Database Retention Policy.

By |How-To, Software, Technical|Comments Off on VIM_VCDB database ‘PRIMARY’ filegroup is full (part 2)