ESX: How to allow the root user to login to VMware ESX Server with SSH

To allow the root user to login to a VMware ESX Server over the network using SSH, do the following:

1. Go to the service console on the physical server & login
2. nano /etc/ssh/sshd_config
3. Change the line that says PermitRootLogin from “no” to “yes”
4. do service sshd restart or etc/init.d/sshd restart

Note:
1. Firewall allow SSH Services.
2. Allowing root logins via SSH is not considered. (security best practice)
3. Users should create non-privileged accounts to use with SSH (not root), then use su or sudo once you have logged into the console.

ESX: Guest Customization

If you’re getting the “windows customization resources were not found” error when trying to clone a vm from a template, then here is the answer.

Copy the contents of “Windows 2003 –  CDSUPPORTTOOLSDEPLOY.CAB” into the folder “C:Documents and SettingsAll UsersApplication DataVMwareVMware VirtualCentersysprepsvr2003” on your Virtual Center server.  Everything should be working now.

Windows Requirements for Guest Customization

Guest customization of a Windows guest operating system can occur if:

o The guest operating system is not a primary or backup domain controller.

o The clone or template has one of the following Windows versions installed:

1. Windows 2000 Server or Advanced Server
2. Windows XP Professional
3. Windows Server 2003, Web, Standard, or Enterprise Editions

         Note: A Windows XP Home operating system guest customization is not supported.

o The Microsoft Sysprep tools are installed on the VirtualCenter management server.

o Microsoft Sysprep tools : http://www.microsoft.com/downloads/details.aspx?FamilyID=a34edcf2-ebfd-4f99-bbc4-e93154c332d6&DisplayLang=en

 

ESX: Install Windows XP on ESX

For Bus Logic Driver:

1. Download .flp file from VMware site: http://download3.vmware.com/software/vmscsi-1.2.0.4.flp
2. Create a new Windows XP Virtual Machines
3. Set the BusConfiguration within the Server Configuration to use BusLogic instead of Default
4. Attach the Windows XP Volume-license iso media and floppy file to the server configuration
5. Startup the Application Configuration
6. Within the VI client attach the flp file found in your local folder. Select “Use existing floppy in datastore” and enter the following: /vmimages/floppies/vmscsi-1.2.0.4.flp

   Insure power is on and connect for the floppy. 
7. Restart the machine while Consoled into the box
8. Select ESC on startup and Select CD-ROM Device on the Boot Menu
9. During the OS install select F6 in order to use of a 3rd party VMware scsi driver found on the A: Drive (floppy drive).
   This will allow the OS to see the Hard drive for installation.
10. Push “S” to select “S=Specify Additional Device”
11. Push “Enter” to select ”VMware SCSI Controller”
12. Install OS

For LSI Logic Driver:

Donload driver at http://www.lsilogic.com/cm/DownloadSearch.do and search for a driver for the LSI20320-R controller.  Extract all files in the symmpi_wXP_1201800.ZIP. Use a program such as WinImage to create an LSILogic.flp

ESX: To verify the current networking configuration is valid and correct

1. Verify the format and content of /etc/hosts.The hosts file is expected to have the following format: 

   
   127.0.0.1       localhost.localdomain localhost
   192.168.1.10    server.domain.com server

2. Verify the contents of /etc/sysconfig/network. Confirm that the proper values for your environment exist for the fully qualified hostname and gateway. Consult your network administrator if you are unsure. For example:  

   NETWORKING=yes
   HOSTNAME=server.domain.com
   GATEWAY=192.168.1.1
   GATEWAYDEV=vswif0

3. Verify that /etc/sysconfig/network-scripts/ifcfg-vswif0 has the correct settings for IP address (IPADDR), subnet mask (NETMASK), and network (NETWORK). Consult your network administrator if you are unsure. For example:  

   DEVICE=vswif0
   BOOTPROTO=static
   BROADCAST=192.168.1.255
   IPADDR=192.168.1.10
   NETMASK=255.255.255.0
   NETWORK=192.168.1.0
   ONBOOT=yes
   PORTGROUP=”Service Console”
   MACADDR=00:50:56:4a:66:ba

4. Run the following command to display the routing table:[root@server root]# route –n 

   You will see output similar to the following:
   
   Kernel IP routing table
   Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
   192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 vswif0
   169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 vswif0
   0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 vswif0                                                Ensure that the second column of the row flagged with UG matches the gateway address for your environment.

5. Verify the DNS information in /etc/resolv.conf is correct for your environment.  

   search domain.com
   nameserver 192.168.1.2
   nameserver 192.168.1.3

6. Verify network connectivity between systems with PING command.