Saturday, 8 November 2014

Installing VCD 5.5 in a VMware Workstation 10 lab Part 1

This is intended to be a VERY quick and dirty multi-part guide to installing VCD 5.5 in a VMware Workstation 10 lab.

It is NOT intended to be a step by step guide, so it's mainly for experienced professionals, BUT if you are starting out with this stuff, I feel you would learn more by following this guide and searching for, or working out yourself, the bits you don't know, rather than following a prescriptive step by step guide that a 12 year could follow (no offence 12 year olds!).

LAB SETUP
Things I have in my one-machine lab - you might be able to get away with less;
32GB RAM
500GB free space
VMWare Workstation (I have 10 but 9 or better should be ok)
One custom network (see NETWORK SETUP below)

SOFTWARE REQUIRED
As well as VMWare Workstation 10, you will need the following software - ALL of it is available in free trial form from the microsoft.com or vmware.com;
Windows Server 2008\2012
VMWare ESXi 5.1\5.5 (comes with the vSphere Trial)
VMWare vCenter Server 5.1\5.5 (comes with the vSphere Trial)
VMware vCloud Director 5.5 (comes with the vCloud Director Trial)
VMware vShield Manager 5.5 (comes with the vCloud Director Trial)

NETWORK SETUP
The Workstation VMs are all joined to a custom network, vmNet8, which I have set to use NAT (for connecting out to the real world - this is important to provide centralised time for your VMs via NTP), as well as DHCP.
My subnet IP is 192.168.89.0 with a mask of 255.255.255.0, it may make things easier for you if you use these values.

VMWARE WORKSTATION SETUP
Running in VMWare Workstation I have the following VMs;
One ESX 5.5i server with 18GB RAM, a 6GB install disk and a 200GB datastore disk
One vCenter Server 5.1 Appliance (4GB RAM default)
One Windows 2003 Server domain controller (512MB RAM)

DOMAIN CONTROLLER SETUP
I created a VM with 512MB RAM, 30GB disk space (suggest 768MB RAM with 40gb disk space (thin provisioned) for Windows 2008 and 2012) and 1 vCPU, connected to vmNet8
After a normal install of Windows Server, I set the server's IP as 192.168.89.20 (mask 255.255.255.0), Primary DNS as 192.168.89.20, and the gateway as 192.168.89.2 (the VMware workstation NAT router for this subnet).
I renamed the server to dc01, rebooted, then ran DCPROMO, using the domain name "domain.local", and all the defaults.
After another reboot, I ran dnsmgmt.msc and created host records for;
vcs01(.domain.local) at 192.168.89.10
esxi01(.domain.local) at 192.168.89.11
vcd01(.domain.local) at 192.168.89.40
vcd01cp(.domain.local) at 192.168.89.41
vshield01(.domain.local) at 192.168.89.45

Finally I installed VMWare tools.

VCENTER SERVER APPLIANCE SETUP
I deployed the appliance into VMWare Workstation, using a thin provisioned  disk.
Once it was deployed, I edited the VM's setting to use network VMNET8, then powered it on and connected to it's "console" to see the DHCP IP it had picked up.
I then went to https://192.168.89.<DHCP-assigned-IP>:5480 from my laptop's browser and set up the installation. Further details on that part can be found here;
https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-25FCBA87-5D2F-4CB6-85D7-88899B4AC174.html
I used the hostname vcs01(.domain.local), and IP 192.168.89.10 (mask 255.255.255.0, gateway 192.168.89.2). I also used (important!) NTP Time Server of 0.uk.pool.ntp.org as I am in the UK.

In the next part of these instructions, I shall continue by installing and configuring ESXi Server.

1 comment:

  1. very informative post. I will use the suggestions discussing here for optimizing my new blog site.This post will be very helpful for the begaineer SEO worker who are new in this field.
    Keep posting this type of helpful post.
    With best wishes.VMware Workstation 14

    ReplyDelete