Day: Oct 1, 2016

VMware View 4.0 Installation and Configuration

Posted on Updated on


VMware View 4 allows you to consolidate virtual desktops on datacenter servers and manage operating systems with improved reliability, better managementOverview

Features

  • Print from a virtual desktop to any local or networked printer that is defined on the client device.
  • Use multiple monitors With VMware PCoIP multiple-monitor support.
  • Access USB devices and other peripherals that are connected to the local device that displays your virtual desktop.
  • Use Microsoft Active Directory to manage access to virtual desktops and to manage policies.
  • Use the Web-based administrative console to manage virtual desktops from any location.
  • Use a template, or master image, to quickly create and provision pools of desktops.
  • Send updates and patches to virtual desktops without affecting user settings, data, or preferences.

Components of VMware View Enterprise:

  • View Connection Server 4 (Install on dedicated server)
  • View Agent (Install on virtual desktop VM)
  • View Client (Install on client physical desktop

Components of VMware View Premier:

  • View Connection Server 4 (Install on dedicated server)
  • View Composer 2 (Install on vCenter server)
  • View Agent (Install on virtual desktop VM)
  • View Client (Install on client physical desktop)
  • View Client Offline Desktop (Install on client physical laptop)

Pre-requisites:

Components Requirements
View Connection Server 4.0 ·  32bit or 64bit server

·  Pentium IV 2.0GHz processor or higher

·  2GB RAM or higher

·  One or more 10/100Mbps network interface cards (NIC)

·  Windows Server 2003 Standard or Enterprise with Service Pack 2

·  Valid View 4.0 license keys

·  Administrator rights on the domain user account used to install View Connection Server 4.0

·  VMware Infrastructure 3.0.2, VMware Infrastructure 3.5 Updates 3 or 4 or vSphere 4 Update 1

·  RSA Authentication Manager

·  Windows 2000, 2003 or 2008 Active Directory

View Composer 2.0 ·  Windows Server 2003 Standard or Enterprise with Service Pack 1 or Windows XP Professional with Service Pack 2

·  A supported SQL database.

View Administrator ·  Internet Explorer 7, Internet Explorer 8, Firefox 3.0 or Firefox 3.5

Installation Overview

The complete setup of Vmware View 4.0 environment includes 3 steps:

  • Installing VMware View Connection Server 4
  • Installing VMware View Composer 2
  • Configuring VMware View Connection Server 4 with View Manager

Installing VMware View Connection Server 4

Note:

  • The View Connection Server must be installed on its own dedicated server. It cannot be installed on the vCenter server.
  • It acts as a broker for client connections by authenticating directing incoming remote desktop user requests to a virtual desktop, physical desktop, or terminal server.
  1. Double Click “VMware-viewconnectionserver-4.xxxxx.exe” to start the installer.
  2. The installation wizard is displayed. Click Next.
  3. Read and Accept the VMware license agreement, Click Next.
  4. Enter the destination folder to install VMware View Composer. Click Next.
  5. Select “Standard” for the server instance type (as this is the first server). Click Next.
  6. Read and Accept the Microsoft ADAM license agreement, Click Next.
  7. Click Install to start the installation of the View Connection Server.
  8. Once the installation has completed Click Finish.

Installing VMware View Composer 2

Note:

  • VMware View Composer 2 is a component of View 4 Premier Edition.
  • Composer must be installed on the vCenter Server.
  1. Double Click “VMware-viewcomposer-2.0.0-210930.exe” to start the installer.
  1. You may receive a message about updating Microsoft .NET depending on which version you have installed. Click Ok to update .NET.
  1. After updating .NET (if it was required) the installation wizard is displayed. Click Next.
  1. Read and Accept the license agreement, Click Next.
  1. Enter the destination folder to install VMware View Composer. Click Next.
  1. VMware View Composer requires a MS SQL database. Enter the required details and Click Next.
  1. Confirm the SOAP port to use and note the SSL certificate being created. Click Next.
  1. Click Install to start the installation of Composer.
  1. Once the installation has completed Click Finish.
  1. It is required to restart the server to complete the installation. Click Yes to Restart.

Configuring VMware View Connection Server 4 with View Manager

  • View Manager 4 is a core component of VMware View 4 that is installed on the View Connection Server.
  • View Manager is a single console used to manage and deploy virtual desktops

Follow the below steps to configure the Vmware View Connection Sevrer

  1. Login to View Manager Administrator
  1. License the server.
  • Navigate to the “Configuration” tab and the “Product Licensing and Usage” section.
  • Click “Edit License” and enter the license.
  1. Add the vCenter Server.
  • Navigate to the “Configuration” tab and the “Servers” section.
  • Click “Add” to add the vCenter server.
  1. Enter the vCenter server details:
  • Server Address (FQDN)
  • Username
  • Password
  1. Optionally (If Premier Edition) enter View Composer Server details:
  • Click “Add” to add a Quick Prep domain.
  • Click Ok to save all the settings.
  1. Confirm the vCenter Server details are added correctly.
  2. Confirm the View Connection Server is activated.
  • Navigate to the “Configuration” tab and the “Registered Desktop Sources” section.
  1. Configure Connection Server Settings.
  • Select a Connection Server and Click “Edit”.
  • By default these settings do not need to be changed for View to work. However here you will find settings for smart cards, 2-factor authenication and backup of the View Manager Configuration.
  1. Configure any additional Administrators of VMware View Manager.
  • Navigate to the “Configuration” tab and the “Administrators” section.
  • Click “Add” to add any additionally groups that require administrator permissions in View Manager.
  • By default this is only BUILTIN\Administrators group on the connection server.
  1. Configure any require global settings.
  • Navigate to the “Configuration” tab and the “Global Settings” section.
  • Under the global settings configure any additional settings for session timeouts, login messages and forced logoff messages.
  • Click Ok to save the settings.

Zerto vs vSphere Replication

Posted on Updated on


Zerto vs vSphere Replication (focusing around data replication)

Zerto Replication vSphere Replication
Generally recommended for: Any size vSphere infrastructure Small infrastructures, remote offices, and non-critical applications
Max number of VMs protected per appliance and vCenter Server: 500/5000 500/500
Linked clone and template support: Yes No
Physical RDM and Virtual RDM support: Yes, virtual and physical mode RDMs are supported No/Yes, Physical RDMs are not supported but virtual RDM are supported
RPO range: Seconds 15 minutes to 24 hours
Application consistent?: Supports Windows VMs using VSS and Linux with Application Quesicense Only with Windows VMs using VSS
How VMs are chosen: VMs can be organized into Virtual Protection Groups VMs can be selected individually or multi-select but virtual protection grouping is not available
Automated failback support: Yes No, VMware recommends SRM
Allows you to plan, test, and automate failover and failback: Yes No, VMware recommends SRM
Compression included: Yes No, and neither does SRM
RE-IP addressing of virtual machines: Yes No, VMware recommends SRM
Cloning of recovery sites: Yes No
Point in time recovery: Yes, up to 5 days with standard recovery, up to 1 year with extended recovery using the Offsite Backup feature Yes, up to 24 snapshots
Compatible with vApps: Yes No
vCloud Director integration: Yes No
Snapshot-based? No Yes/No, VMware says that vSR doesn’t use snapshots technology but does use a modified version of CBT, still many of the same snapshot-based limitations apply. For example, vSR uses VM snapshots at the recovery site when recovering to a different point-in-time.

Zerto vs VMware Site Recovery Manager (focusing around automation of disaster recovery planning, testing, and automation)

Zerto SRM (with vSphere Replication)
Provides planning, testing, and execution of disaster recovery for vSphere: Yes Yes
Designed for: Zerto was designed for hypervisor-based replication AND disaster recovery orchestration SRM was designed for disaster recovery orchestration only
Licensed: Per-VM Per-VM
Replication granularity: Per-VM and/or Per- Virtual Protection Group Per-VM or multi-select but virtual protection grouping is not available
Configure consistency groups (virtual protection groups): Yes No
Replication recovery points: Yes, up to 5 days with standard recovery, up to 1 year with extended recovery using the Offsite Backup feature Yes, up to 24 snapshots
Compatibility: Zerto works with ESX 4.0 U1 and above. Zerto can replicate between different versions of vCenter. vSR works with ESX 5.x and above. SRM requires the same version of vCenter and SRM be installed at both sites.
Managed with: vSphere Client Plugin and stand-alone browser UI vSphere Client Plugin
Replication is performed with: Zerto Hypervisor-based replication vSphere Replication