Installing vCenter Server 4 with Windows 2008 64Bit and SQL2008 64Bit

Posted on Updated on

You might be asking yourself what are the benefits of deploying Windows & SQL 2008×64?

So far I have found one… If you want to position your server for x64 and 2008 then this makes sense.

See these articles for more information..

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010401

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1009080&sliceId=2&docTypeID=DT_KB_1_1&dialogID=101033551&stateId=0 0 101037544

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010023

http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_preparing_the_vmware_infrastructure_databases.html

http://support.microsoft.com/kb/149605

Here are the basic steps to setup vCenter 4 with Windows/SQL 2008 x64

This guide is for reference, like all articles I post up, they are my notes, so use them at your own risk…

SQL2008 Install…

  1. Setup your VM with ample – CPU, RAM, Disk C: for OS and D: SQL Data
  2. In this case drives are 1 x vCPU, 4GB RAM, C: [50GB] D:[150GB]
  3. Install Windows 2008 x64 Standard Setup
  4. Run the setup from the SQL2008 CDROM
  5. Click on Installation > New SQL Servers
  6. Click okay if your “SQL Support Rules” succeed
  7. Click Install to setup the support install files
  8. Validate that all Setup Support Rules status are Passed (if not remediate), click next
  9. Click next to Product Key
  10. Click next to accept the terms
  11. Choose Database Engine Services, All Management Tools – Basic, Click Next
  12. Change the location of the “Instance Root Directory” to your D: drive using the default folder path, Click Next
  13. Confirm Disk Usage Summary, Click Next
  14. Choose “NT Authority\SYSTEM” for the account for SQL Agent & Database Engine, Click Next
  15. Choose Mixed Mode, Enter the “sa” password, Click on Add Current User Or Add your own, Click Next
  16. Click Next to validate install Rules
  17. Remediate issues if necessary, else Click Next
  18. Click install to start installation, Allow to complete the install of SQL 2008
  19. Click Next to complete and close to exit
  20. Validate your install by opening SQL Server Management Studio
  21. Ensure the SQL Server Agent Service is set to Automatic and is started

SQL2008 Prep for vCenter Server

  1. Open SQL Server Configuration Manager, Click on SQL Server Network Configuration, Choose Protocols for MSSQLserver, Right click on named pipes and choose enable, Restart the SQL Services or reboot
  2. Apply any vmware approved SQL Patches (Ensure a snapshot, backup or other has been taken)
  3. Create the user vcdb, Click on security > Logins > Right Click Choose New User
  4. Type in the user vcdb
  5. Choose SQL Server Authentication then enter a password
  6. Uncheck Enforce Password Expiration
  7. On the left, click on Server Roles
  8. Choose sysadmin, then click on OK
  9. Create the Database vcdb, Right Click on Databases > choose New Database
  10. Enter the Name vcdb for the database name
  11. Click on ‘….’ to add the owner, use vcdb as the owner, click OK
  12. On the left, click on Options, choose simple for recovery mode
  13. Choose OK at the bottom
  14. Click on Security > logins > right click on vcdb choose properties
  15. Change default database to vcdb, choose OK
  16. Create the user vmupd, Click on security > Logins > Right Click Choose New User user
  17. Type in vmupd
  18. Choose SQL Server Authentication then enter a password
  19. Uncheck Enforce Password Expiration
  20. On the left, click on Server Roles
  21. Choose sysadmin, then click on OK
  22. Create the database vmupd, Right Click on Databases > choose New Database
  23. Enter the Name vmupd for the database name
  24. Click on ‘….’ to add the owner, use vmupd as the owner, click ok
  25. On the left click on Options, choose simple for recovery mode
  26. Choose OK at the bottom
  27. Click on Security > logins > right click on vmupd choose properties
  28. Change default database to vmupd, choose OK

Setup ODBC Connectors…

  1. Create a link to the 32Bit ODBC Admin tool (C:\Windows\SysWOW64\odbcad32.exe)
  2. Open the 32Bit ODBC Data Source Admin
  3. Create System DSN for vcdb database, Click on System DSN Tab
  4. Click on Add
  5. Choose ‘SQL Native Client 10.0’ (Don’t Choose SQL Native Client only)
  6. Enter the database name of vcdb
  7. For Server Choose the local server name, Click on next
  8. Choose With SQL Server Authentication
  9. Ensure Connect to SQL is checked
  10. Enter Login ID of vcdb and the password Click on Next
  11. Ensure that Change the Default Database to is checked and vcdb appears below it, Click on Next
  12. Choose Finish
  13. Click on Test data source and look for TESTS COMPLETE SUCCESSFULLY!
  14. Click on OK, then OK again
  15. Create System DSN for vmupd database, Click on System DSN Tab
  16. Click on Add
  17. Choose ‘SQL Native Client 10.0’ (Don’t Choose SQL Native Client only)
  18. Enter the database name of vmupd
  19. For Server Choose the local server name
  20. Click on next
  21. Choose With SQL Server Authentication
  22. Ensure Connected to SQL is checked
  23. Enter Login ID of vmupd and the password Click on Next
  24. Ensure that Change the Default Database to is checked and vmupd appears below it, Click on Next
  25. Choose Finish
  26. Click on Test data source and look for TESTS COMPLETE SUCCESSFULLY!
  27. Click on OK, then OK again

     

Install vCenter Server 4

  1. Open the vCenter Installer
  2. Choose vCenter Server from the Installer screen
  3. Choose Ok for English
  4. If prompted Choose Yes to continue to possible IIS port issues
  5. Click Next on the Welcome Screen
  6. Choose I agree to the terms, click next
  7. Enter your User and Organization Names, Enter your license Key, Click Next
  8. Choose Use an existing supported database
  9. Choose the DSN name of vcdb, click next
  10. Enter the password for vcdb, click next
  11. Ensure Use System Account is checked, click next
  12. Click Next for the Default folder name
  13. Choose create a standalone VMware vCenter Server Instance
  14. Ensure all the TCP Ports are okay, Adjust as needed (MS KB149605), Click next
  15. Click on Install

Install vCenter Update Manager

  1. Open the vCenter Installer
  2. Choose vCenter Update Manager from the Installer screen
  3. Choose OK for English
  4. Click Next on the Welcome Screen
  5. Choose I agree to the terms, click next
  6. Enter the user name and password for the vCenter Server system.
  7. Choose Use and existing support database, Choose vmupd for the DSN, click next
  8. Enter the password for vmupd, click next
  9. Leave defaults for Update Manger Ports, If needed choose Yes to Proxy Settings, else Click next
  10. Click next for default Directories (Ensure more the 20GB for Location for Downloading Patches)
  11. Click Install to complete

Install vCenter Converter

  1. Open the vCenter Installer
  2. Choose vCenter Converter from the Installer screen
  3. Choose OK for English
  4. Click Next on the Welcome Screen
  5. Choose I agree to the terms, click next
  6. Choose Typical, click next
  7. Enter username and password for vCenter Server connection, click next
  8. Click next for default ports
  9. Click next for default server ID
  10. Click Install

Install the vCenter Client

  1. Open the vCenter Installer
  2. Choose vCenter Client from the Installer screen
  3. Choose OK for English
  4. Click Next on the Welcome Screen
  5. Choose I agree to the terms, click next
  6. Enter your User and Organization Names, Enter your license Key, Click Next
  7. Click next on the Custom Setup windows, Choose install vsphere update utility if needed
  8. Click next for the default install folders
  9. Click install to finish

Well that’s it… I’m so glad I decided not to post up screen shots!

From here you should be able to bring up vCenter Server via the client, and with some minor configuration pull down updates too..

Good luck…

Introduction to vSphere 4 Link

Posted on Updated on

This link is well worth bookmarking and has been a great reference for me…

http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=welcome/welcome.html

Installing ESX 4.0 and vCenter 4.0 best practices

Posted on Updated on

This is one of my favorite references… I seem to need it from time to time… 

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009080

Installing ESX 4.0 and vCenter 4.0 best practices

Purpose

This article provides quick reference to the information needed for a trouble free installation of vSphere ESX 4.0 and vCenter Server 4.0.

Note: Because each environment is different, many installation decisions require knowledge and understanding beyond the scope of this article, consult the vSphere 4.0 document set for more detailed information regarding your installation at http://www.vmware.com/support/pubs/vs_pubs.html.

Resolution

Note: Read the VMware vSphere 4.0 Release Notes for known installation issues.

On the vCenter Server

1.Make sure your hardware and operating system requirements are compliant:

Note: For more information, see ESX and vCenter Server Installation Guide and VMware Infrastructure Compatibility Guide.

•Processor – 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor may be higher if the database runs on the same machine.

•Memory – 3GB RAM. RAM requirements may be higher if your database runs on the same machine.

•Disk storage – 2GB. Disk requirements may be higher if your database runs on the same machine.

•Microsoft SQL Server 2005 Express disk requirements. The bundled database requires up to 2GB free disk space to decompress the installation archive.

•Networking – 1Gbit recommended.

2.Make sure your database requirements and patch levels are compliant:

Note: For more information, see VMware Infrastructure Compatibility Guide and vCenter Server Database Patch and Configuration Requirements.

•Microsoft SQL server Database Support:

•Microsoft SQL Server 2005 Express

Note: Microsoft SQL Server 2005 Express is intended to be used for small deployments of up to 5 hosts and/or 50 virtual machines.

•Microsoft SQL Server 2005 Standard edition (SP1, SP2, SP3)

•Microsoft SQL Server 2005 Standard edition (SP2, SP3) 64bit

•Microsoft SQL Server 2005 Enterprise edition (SP1, SP2, SP3)

•Microsoft SQL Server 2005 Enterprise edition (SP2, SP3) 64bit

•Microsoft SQL Server 2008 Standard Edition

•Microsoft SQL Server 2008 Standard Edition 64bit

•Microsoft SQL Server 2008 Enterprise Edition

•Microsoft SQL Server 2008 Enterprise Edition 64bit

•Oracle Database Support:

•Oracle 10g Standard edition (Release 1 [10.1.0.3.0])

•Oracle 10g Enterprise edition (Release 1 [10.1.0.3.0])

•Oracle 10g Standard edition (Release 2 [10.2.0.1.0])

•Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0])

•Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0]) 64bit

•Oracle 11g Standard edition

•Oracle 11g Enterprise edition

3.Download and fill out the vCenter Server Installation Worksheet.

Note: For more information about the fields in this form, see the Required Data for Installing vCenter Server section of the ESX and vCenter Server Installation Guide.

4.The vCenter Server install wizard gives you the option to use the Windows system account or a user-specified account for the purpose of running vCenter Server.

The primary reason to use a user-specified account is to enable the use of Windows authentication for SQL Server.

If you choose this option:

•The user-specified account must be an Administrator on the local machine and act as part of the operating system and login as a service rights.

•You must specify the account name as DomainName\Username in the vCenter Server install wizard.

•You must configure the SQL Server database to allow the domain account access to SQL Server.

5.Make sure your system has all the software prerequisites for vCenter Server:

Note: For more information, see the vCenter Server Prerequisites section of the ESX and vCenter Server Installation Guide.

•Make sure your operating system meets the requirements:

Note: For more information, see the Operating System Compatibility for vSphere Client, vCenter Server, and VMware vCenter Update Manager section of the VMware Infrastructure Compatibility Guide.

•Windows XP Pro SP2 (SP2 required)

•Windows Server 2003, SP1 and SP2 32bit and 64bit all editions

•Windows Server 2003, R2 and SP2 32bit and 64bit all editions

•Windows Server 2008 32bit all editions

•Windows Server 2008 64bit Standard and Enterprise editions

•Make sure that the system you use for your vCenter Server installation belongs to a domain, rather than a workgroup.

•It is critical that you have reliable DNS and Time services.

•During the installation, the connection between the machine and the domain controller must be working.

•Log into the system using an account with local administrator rights. If joining another vCenter Server in Linked Mode, the account must be a local Administrator on both systems.

•The computer name cannot be more than 15 characters.

•Assign a static IP address and host name to the Windows server that will host the vCenter Server system. This IP address must have a valid (internal) DNS registration that resolves properly from all managed ESX hosts.

6.Configure your database prior to the vCenter install, unless you are using default Microsoft 2005 Express:

Note: Schema creation scripts mentioned in the documentation for both Microsoft SQL and Oracle are optional and intended for experienced Database Administrators. The vCenter Server installer performs the schema creation automatically if one does not already exist.

•Microsoft SQL Database:

•As the Database Administrator, use a script to create a local or remote Microsoft SQL Server Database.

Optionally, the database can be created as it was in vCenter 2.5 by using SQL Server Management Studio.

•Configure a SQL Server ODBC Connection

When you install the vCenter Server system, you can establish a connection with a SQL Server database.

•Configure Microsoft SQL Server TCP/IP for JDBC

If the Microsoft SQL Server database has TCP/IP disabled and the dynamic ports are not set, the JDBC connection remains closed. This causes the vCenter Server statistics to malfunction.

•Oracle Database:

•As the Database Administrator, use a script to create a local or remote Oracle database.

•Configure an Oracle Database User

If you plan to use an Oracle database when you install vCenter Server, you must configure the database user.

•Configure an Oracle Connection for Local Access or Configure an Oracle Connection for Remote Access depending on where the database is located.

•Connect to an Oracle Database Locally

7.VMware recommends using a separate database for vCenter Server and vCenter Update Manager.

8.Run the vCenter Server installer using the vCenter Server Installation Worksheet filled out in step 3.

On the ESX Server

1.Make sure your hardware is compliant on the Hardware Compatibility Guide.

This includes:

•System compatibility

•I/O compatibility (Network and HBA cards)

•Storage compatibility

•Backup software compatibility

2.VMware ESX 4.0 only installs and runs on servers with 64bit x86 CPUs. 32bit systems are no longer supported.

3.Make sure Intel VT is enabled in the host’s BIOS.

4.If you are installing to the local disks and SAN is connected to the ESX host, detach the fiber before continuing with the installation.

Note: Do not disable HBA cards in the BIOS.

5.The /, swap, and all the optional partitions are stored on a virtual disk called esxconsole-.vmdk. Set a size minimum of 8GB for this virtual disk.

Note: For /var/log, VMware recommends a separate partition to prevent unexpected disk space constraints due to extensive logging.

vSphere 4 – Partition Sizing

Posted on Updated on

Here are some new guidelines I found today for setting up your vSphere 4 hosts partitions.
Thanks to my buddy Kevin Less at vmware for this information.

Best Practices and URL’s

Posted on Updated on

Here’s a great check list that I came across today…  Enjoy!

Component Check (per Best Practice)

Host Verify equipment was burned in with memory test for at least 72 hours

Host Verify all host hardware is on the VMware Hardware Compatibility List (HCL)

Host Verify all host hardware meets minimum supported configuration

Host Check CPU compatibility for vMotion and FT

Host Check ESX/ESXi host physical CPU utilization to make sure that it is not saturated or running in a sustained high utilization

Host Verify all hosts in the cluster are compatible versions of ESX/ESXi

Host Check ESX/ESXi host active Swap In/Out rate to make sure that it is not consistently greater than 0

Host Check to make sure that there is sufficient service console memory (max is 800MB)

Host Verify that ESX service console root file system is not getting full

Host Check if any 3rd party agents are running in the ESX service console

Host Verify that NTP is used for time synchronization

Network Verify that networking in configured consistently across all hosts in a cluster

Network Check to make sure there is redundancy in networking paths and components to avoid single points of failure (e.g. at least 2 paths to each network)

Network If HA is being used, check that physical switches that support PortFast (or equivalent) have PortFast enabled

Network Check that NICs for the same uplink have same speeds and duplex settings

Network Check that Management/Service Console, Vmkernel, and VM traffic is separated (physical or logical using VLANs)

Network Verify that portgroup security settings for ForgedTransmits and MACAddressChanges are set to Reject

Network Check the virtual switch portgroup failover policy for appropriate active and standby NICs for failover

Network Verify that VMotion and FT traffic is on at least a 1 Gb network

Network Check that IP storage traffic is physically separate to prevent sharing network bandwidth

Storage Verify that VMs are on a shared datastore

Storage Check that datastores are masked/zoned to the appropriate hosts in a cluster

Storage Check that datastores are consistently accessible from all hosts in a cluster

Storage Check that the appropriate storage policy is used for the storage array (MRU, Fixed, RR)

Storage Check to make sure there is redundancy in storage paths and components to avoid single point of failure (e.g. at least 2 paths to each datastore)

Storage Check that datastores are not getting full

Virtual Datacenter Check that all datacenter objects use a consistent naming convention

Virtual Datacenter Verify that hosts within a cluster maintain a compatible and homogeneous (CPU/mem) to support the required functionality for DRS, DPM, HA, and VMotion

Virtual Datacenter Check that FT primaries are distributed on multiple hosts since FT logging is asymmetric

Virtual Datacenter Verify that hosts for FT are FT compatible

Virtual Datacenter Check that reservations/limits are used selectively on VMs that need it and are not set to extreme values

Virtual Datacenter Check that vCenter Server is not running other applications and vCenter add-ons (for large environments and heavily loaded vCenter systems) and is sized appropriately

Virtual Datacenter Check that the DB log setting is Normal unless there is a specific reason to set it to High

Virtual Datacenter Check that the vCenter statistics level is set to an appropriate level (1 or 2 recommended)

Virtual Datacenter Check that appropriate vCenter roles, groups, and permissions are being used

VM Check any VMs with CPU READY over 2000 ms

VM Check any VMs with sustained high CPU utilization

VM Check any VMs with incorrect OS type in the VM configuration compared to the guest OS

VM Check any VMs with multiple vCPUs to make sure the applications are not single threaded

VM Check the active Swap In/Out rate of VMs to make sure it is not consistently greater than 0

VM Check that NTP, windows time service, or another timekeeping utility suitable for the OS is used (and not VMware Tools)

VM Check that VMware Tools are installed, running, and not out of date for running VMs

VM Check VMs that are configured and enabled with unnecessary virtual hardware devices (floppy, serial, parallel, CDROM) and any devices that prevent VMotion

VM Check VMs that are not yet on virtual hardware v7

VM Check VM configuration (memory reservation) for VMs running JVM to consider setting reservation to the size of OS+ java heap

Item URL

Documentation http://www.vmware.com/support/pubs

VMTN Technology information http://www.vmware.com/vcommunity/technology

VMTN Knowledge Base http://kb.vmware.com

Discussion forums http://www.vmware.com/community

User groups http://www.vmware.com/vcommunity/usergroups.html

Online support http://www.vmware.com/support

Telephone support http://www.vmware.com/support/phone_support.html

Education Services http://mylearn.vmware.com/mgrreg/index.cfm

Certification http://mylearn.vmware.com/portals/certification/

Technical Papers http://www.vmware.com/vmtn/resources

Network throughput between virtual machines http://kb.vmware.com/kb/1428

Detailed explanation of VMotion considerations http://www.vmware.com/resources/techresources/1022

Time keeping in virtual machines http://www.vmware.com/vmtn/resources/238

http://kb.vmware.com/kb/1006427

VMFS partitions http://www.vmware.com/vmtn/resources/608

VI3 802.1Q VLAN Solutions http://www.vmware.com/pdf/esx3_vlan_wp.pdf

VMware Virtual Networking Concepts http://www.vmware.com/resources/techresources/997

Using EMC Celerra IP Storage (VI3 http://www.vmware.com/resources/techresources/1036

VMware vCenter Update Manager documentation http://www.vmware.com/support/pubs/vum_pubs.html

VMware vCenter Update Manager Best Practices http://www.vmware.com/resources/techresources/10022

Performance Best Practices for VMware vSphere 4.0 http://www.vmware.com/resources/techresources/10041

Recommendations for aligning VMFS partitions http://www.vmware.com/vmtn/resources/608

Performance Troubleshooting for VMware vSphere http://communities.vmware.com/docs/DOC-10352

Large Page Performance http://www.vmware.com/resources/techresources/1039

VMware vSphere PowerCLI http://www.vmware.com/support/developer/windowstoolkit/

VI3 security hardening http://www.vmware.com/vmtn/resources/726

VMware HA: Concepts and Best Practices http://www.vmware.com/resources/techresources/402

Java in Virtual Machine on ESX http://www.vmware.com/files/pdf/Java_in_Virtual_Machines_on_ESX-FINAL-Jan-15-2009.pdf

CPU scheduler in ESX 4.0 http://www.vmware.com/resources/techresources/10059

Dynamic Storage Provisioning (Thin Provisioning) http://www.vmware.com/resources/techresources/10073

Understanding memory resource management on ESX http://www.vmware.com/resources/techresources/10062

06.08.2010 VMUG Event

Posted on Updated on

The big Phoenix VMUG meeting is tomorrow… I hope you all can make it… some of the buzz will be about the FREE VMware CookBook and the workshop around Building your home lab around Workstation 7.

For all you night owls… I posted my Workshop lab a day early…. Go here to see it…

http://communities.vmware.com/docs/DOC-12763

Enjoy!

Matt..

Network – Edit Hosts file on ESX

Posted on

Here are the simple commands to edit a hosts file on an ESX server…

Log on as root
Enter vi /etc/hosts

Press ESC, then i to insert
Edit Text
Press ESX, the :wq press enter to save

Here are some common commands with vi

“you have to enter command mode first using ESC “

i = insert at this charachter

x = delete a charachter

dd = delete a line

yy = copy

p = paste a copied line

a = append to the next charachter

A = append to the end of aline

I = insert at the beginning of a line

:w = write

:q = quit

:w! = force a write (read only files)

:q! = force a quit no changes

ESX 4 – Windows 7 VM cannot connect via RDP

Posted on Updated on

Today I noticed when rebooting my Windows 7 VM under ESX 4 remote desktop would not allow connections until I logged on locally.

I also noticed vCenter Server reported VMTools wasn’t running.

 

I did a bit of research and found that Remote Desktop Services was in manual mode.
By changing the startup type to Automatic it not only fixed the Remote Desktop issue but vCenter Server reported in properly as well.

ESX 3.5 – Network DNS Settings

Posted on Updated on

Here’s the quick way to see your DNS settings from command line..

cat /etc/resolv.conf

ESX 3.5 – Keyboard Issues displaying wrong characters

Posted on Updated on

I ran into an issue getting an ESX 3.5 server to join a Virtual Center 2.5 server today..

For some reason I couldn’t get it to join my VC server and when I tried to I would get the error bad password or user name. Connecting the VI client straight to the server failed, trying to use the web interface failed, but I could remote into the server via an IP KVM and log on without issue.

What I found was my keyboard map on this individual server was set to UK and not US.

Here is how I resolved this issue.

Logged in to the host as root

cd /etc/sysconfig
vi keyboard
Press esc twice
Press insert to edit
Changed KEYTABLE=”uk″ to KEYTABLE=”us″
Press esc twice
Enter :qw > to save the file and exit
Reboot the ESX server
And now it works like a champ..