VMware SOFTWARE REPOSITORY FOR WINDOWS 1.1 Bedienungsanleitung

AutoLab 1.1a vSphere Deployment Guide Alastair Cooke

VMware ESXi Setup The lab runs extremely well under ESXi; in my lab the basic vSphere cluster consumes a peak of 4.5GB of RAM during build and about 4

If your ESXi environment is not able to run multi VM vApps then you will need to follow these instructions. If you can deploy they multi-VM vApp then

VMware Fusion Setup Huge thanks to James Bowling @vSential for documenting the whole Fusion 4 setup process and Damian Karlson @sixfootdad for updatin

Next we will actually change the subnet. To do this, open a terminal and do the following: cd /Library/Preferences/VMware\ Fusion Now we need to o

Open VMware Fusion menu > Preferences > Network tab Unlock the window if necessary Click the plus sign at the bottom left to create vmnet3 In t

The vmnet3 interface on the host Mac will get an IP set to 192.168.199.1 automatically Placement of AutoLab Virtual Machines (all Fusion versions) In

Alternatively, you can run this script in order to quickly change all of the virtual machine folder names. ls -dF ~/Documents/Virtual\ Machines/Lab_Lo

VMware Player Setup The following process has been tested with VMware Player version 5.0.2 Install VMware Player Find the program directory, on my PC

The Virtual Machines The VMs in the download package are setup so you can run the core lab under VMware Workstation on an 8GB physical machine. The Wi

AutoLab 1.1a vSphere Deployment Guide © 2013 Alastair Cooke All rights reserved

Ideal: 2GB or more VBR - Veeam Veeam Backup & Replication Minimum: 1GB Ideal: 2GB or more CS1 & CS2 - View Connection Server Minimum: 1GB

Build the Lab These steps use the full set of automation to build a complete lab environment. The steps should be completed in order with each step co

Power on the NAS VM, wait for it to boot to the logon prompt If you watch the console of the NAS VM you may see messages about not having enough RAM

The VMTools folder must contain the extracted contents of the Windows VMware Tools ISO for the outer virtualization platform, for VMware Workstation t

Automation Control In the Automate folder on the build share you will find Automate.ini, this file controls the level of build automation. The file h

Do not move on to Task 2 until the build share is fully populated and you are happy with the automation options in the automate.ini file. Task 2 – Bui

After installing AD the VM will restart and install SQL Express and setup the PXE environment followed by installing the VMware tools. If these steps

As you would expect green is good, yellow is OK, red not so good. If the build share is not correctly populated then the DC VM will need rebuilding a

There are a few scripts that can be run on the VC; they are wrapped up in the Script Menu script on the desktop. The menu script does not require ele

Router from your external network, you will need to run the Add Route… option from the script menu. The desktop shortcut named vSphere launches the vS

Contents vSphere AutoLab ... 4 Ack

Build the second server as required. Confirm that both ESX servers have the correct static IP addresses before moving to the next stage. Task 5 – Pop

Task 6 - Add vSphere Management Assistant The vSphere Management Assistant (VMA) virtual appliance is not included with the AutoLab kit as it is large

Lab Build Time This table gives an indication of the time to build a core vSphere lab using a computer with a quad core i7, lots of RAM and an SSD, yo

Shutting the lab down Since the lab takes up so much of the resources on a PC you will probably want to shut it down when you’re not actively working

Accessing the built lab While the VMware Workstation console is perfectly functional you may wish to use guest OS native tools, like RDP. If your PC h

The DC VM is available via RDP on the external IP address of the router using port 3388. The router also provides access to SSH access to the ESXi s

As Built Documentation The following information outlines the built environment when all of the automation is executed correctly. This is also useful

IP Storage Network VLAN ID: 17 Subnet: 172.17.199.0 Subnet Mask: 255.255.255.0 Host1 IPStore 1: 172.17.199.11 Host2 IPStore 1: 172.17.199.12 Host1 IPS

Host and Shared Storage ISCSI port binding is not implemented, nor is the NIC teaming configuration required for port binding. ISCSI traffic uses th

Rebuild Process Open Source Infrastructure The NAS VM should not require rebuilding, nor should the router. If either of these machines requires rebui

vSphere AutoLab This AutoLab kit is designed to produce a nested vSphere 5.1, 5.0, or 4.1 lab environment with minimum effort. Prebuilt shell VMs are

Veeam ONE Installation Like most management tools Veeam ONE uses a client server model. We will use a dedicated VM named V1 as the server. The environ

6. Since we're evaluating we will use the free edition, Select Install Veeam ONE in a free mode and click Next 7. The Lab build has installed

8. Enter the usual lab password VMware1! for the service account 9. To minimise the RAM footprint we will use the SQL instance on the DC, the servi

10. Click on VMware vCenter Server to add our vCenter 11. Enter the lab vCenter vc.lab.local and the Veeam service account credentials, username lab

12. Once the install completes you will be prompted to log off, click Yes 13. When you log back on you will find three new desktop shortcuts for the

16. Veeam ONE Business View, this shows some data on the Workspace tab 17. Veeam One Reporter, here the VMware Trends dashboard shows data immediate

20. Double click the Veeam ONE Administrators group, click the Add… button, enter VI-Admin and click OK a couple of times, then close Computer Manage

After the install completes you will have a desktop shortcut for Veeam ONE Monitor, the other two components are web services. 5. On the first run

6. Once the client connects it should show you exactly the same environment as you saw in the client on V1 7. Business View and Reporter are web ap

Acknowledgements This project would not have come to the world without the contributions of numerous others. First of all my Wife, without whom I woul

8. You can login to the web applications using the VI-Admin username and VMware1! Password Now that you have the server and clients installed it’s ti

Veeam Backup & Replication installation Server component install on VBR 1. Build the VBR VM, this follows the usual boot from CDROM with floppy at

6. Since I’m a fan of PowerShell I included it’s snapin

7. Select Use existing instance of SQL Server and enter the SQL server instance on DC, DC\SQLEXPRESS, leave the default database name 8. Enter the u

9. Once the installer has completed you will find a shortcut on the desktop 10. Now that the software is installed head on over to the Veeam web si

VMware View Installation Three shell VMs are provided with the lab kit, these provide the main components of the View environment. To run these VMs un

First Connection Server: CS1 Second Connection server: CS2 Security Server: SS View Composer server: VC View Composer Database Server: DC\SQLEXPRESS V

VMware vCloud Director Installation Automated build Damian Karlson’s (@sixfootdad) excellent work has brought vCloud Director to the AutoLab. Required

After procuring the necessary software, copy the following files to the Build folder on the NAS VM, typically //192.168.199.7/Build/vCD_15: oracle-xe-

Add the vCloud VM from the AutoLab distribution folder. Mount the CentOS-6.3-x86_64-bin-DVD1.iso in the vCloud VM’s CD-ROM drive. Ensure that the driv

Lab Outer Platform Required Hardware The core lab can run on a single PC, a dual core 64bit CPU and a minimum of 8GB RAM is required, along with aroun

This version integrates with SSO and the Lookup service, which is not supported by the PowerCLI commandlets so the install is all manual, follow this

Edit the vCenter connection information, you will need to accept the vCenter server’s thumbprint. VMware vCloud Director setup instructions: Connect

Connect to vShield Manager: Host name or IP address: vshield.lab.local User name: admin Password: default Click Finish to complete attaching a vCente

Running Multiple AutoLabs One aim in AutoLab was to make it easy for a team to share one ESXi server and each team member to have their own AutoLab.

Troubleshooting A few things can go wrong along the way here are some we’ve seen DC Build stalls If the NAS is not accessible from the DC then the bui

Host1 build fails –Resolved in V1.1 If the VC build script cannot identify the version of ESXi in your B:\ESXi50 folder then it won’t setup the PXE e

vCenter 4.1 does not respect VM boot order from PowerCLI. Use the BIOS settings in the VM to boot Hard Disk and CDROM before floppy. Router VM crashe

AutoLab Version Changes V1.1a Addition of vCloud 5.1 Cleaned up requirement to have vCenter 5.0 installer for successful install Added support for com

AutoLab Futures Insert your favourite disclaimer here, only things that get added to AutoLab will be added. If there’s something you really want added

VMware PowerCLI installer; use the same version as the oldest vSphere & vCenter version you will deploy. vCloud binary and vShield (aka vCloud Net

Outer platform setup In the next few pages we will look at setting up the virtualization platform that will host the AutoLab: VMware Workstation, ESXi

VMware Workstation Setup The VMware Workstation build is designed to work with a host with at least 8GB of RAM and VMware Workstation version 8.0 or l