Feb 21 2015

VMware Horizon Workspace – Portal Management URLs

In previous versions of VMware Horizon Workspace, it was always hard to know which URL to use for what purpose. In the current version (2.1.0) there is a single webpage within the VMware Horizon Workspace Portal displaying the Workspace Portal Administrative Links. So there is only one single URL to remember:

https://HorizonWorkspaceFQDN:8443

VMware_Workspace_Portal_Administrative_Services_Links

  • Appliance Configurator: Update and change settings for the Workspace database, SSL certificates, and external syslog server; change Workspace and system passwords, and view log files.

VMware_Workspace_Portal_Appliance_Configurator

  • Workspace Admin Console: Set up and manage the resources catalog; administer your users and groups entitlements, and review the Workspace dashboard for user activity.

VMware_Workspace_Portal_Admin_Console

  • Connector Services Admin: Manage the Workspace directory, enable or disable authentication adapters, select Active Directory users and groups for Worksapce, and set up resources used in Workspace, including View pools, Citrix-based resources, and ThinApp packages.

VMware_Workspace_Portal_Connector_Services_Admin

Permanent link to this article: http://ituda.com/vmware-horizon-workspace-portal-management-urls/

Feb 17 2015

VMware Horizon View – Maximum machine account password age

Have you ever had situation where you get the message “the trust relationship between this workstation and the primary domain failed” when you try to logon to a Windows machine?

trust_relationship_failed

This situation happens when there is a “password mismatch”. Typically passwords are being thought of as something related to a user account, but in Active Directory environments each computer account also has an internal password, which by default, is configured to change every 30 days.

The problem can be fixed in the following ways:

  • Re-establish the trust relationship between Active Directory and the workstation by rejoining the computer account to the domain.
  • Resetting the computer account in Active Directory.
  • Changing the computer machine password using netdom:
    • netdom resetpwd /s:fqdn_AD_server /ud:domain\user /pd:*
  • Changing the computer machine password through a powershell command
    • Reset-ComputerMachinePassword -Credential domain\user -Server fqdn_AD_server

It is good to know how to fix the problem, but it is even better to know how to avoid the problem. You can avoid the problem by doing one of the following:

  • Changing the default 30-day password change interval within Active Directory by changing the value of the group policy “Domain member: Maximum machine account password age
  • Disabling the password change interval within Active Directory by enabling the group policy “Domain member: Disable machine account password change

Be aware however that Increasing this default 30-day interval significantly, or setting it to 0 so that the computers no longer change their passwords, or disabling the password change all together gives a malicious user more time to undertake a brute-force password-guessing attack against one of the computer accounts.

Therefore, I suggest to change this Group Policy not on the default group policy object, but only on the group policy object related to your VMware Horizon linked clone VMs and the golden templates you use to construct these linked clone VMs.

The policy setting is located at GPO_name\Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options

gpo_domain_password

 

References:

VMware KB 2084433

Microsoft KB 162797

Permanent link to this article: http://ituda.com/vmware-horizon-view-maximum-machine-account-password-age/

Dec 27 2014

VMware Horizon View – Cloud Pod Architecture Installation

The configuration of the VMware Horizon View Cloud Pod Architecture is done entirely through command line. The lmvutil command line tool is used to configure and manage a VMware Horizon View Cloud Pod Architecture environment. The lmvutil tool is installed as part of the VMware Horizon View installation. You can use the VMware Horizon View Administrator to investigate the pod health and desktop session information.

At this moment, there is no GUI available to configure and manage the VMware Horizon View Cloud Pod Architecture. I hope this will change in the future because at this moment and time it is in my opinion not advisable to handover the operation of the VMware Horizon View Cloud Pod Architecture to standard Horizon View operators who might not be aware of all the details of the lmvutil command line.

Initialization Pod Federation

Log on to the first connection server in DC1

Open a command line (Run as Administrator)

cd C:\Program Files\VMware\VMware View\Server\tools\bin

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –initialize

Join Pods to the Pod Federation

Log on to the first connection server in DC2

Open a command line (Run as Administrator)

cd C:\Program Files\VMware\VMware View\Server\tools\bin

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –join –joinServer <fqdn_First_Connection_Server_in_DC1> –userName NETBIOSDOMAIN\<view_service_account> –password xxxx

Change Default Pod Names

Log on to the first connection server in DC1

Open a command line (Run as Administrator)

cd C:\Program Files\VMware\VMware View\Server\tools\bin

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –listPods

Note: This command will show the default names of the Pods: <defaultpodname_in_DC1> and <defaultpodname_in_DC2>

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –updatePod –podName <defaultpodname_in_DC1> –newPodName DC1-POD01

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –updatePod –podName <defaultpodname_in_DC2> –newPodName DC2-POD01

Create Sites and assign Pods to the Sites

Log on to the first connection server in DC2

Open a command line (Run as Administrator)

cd C:\Program Files\VMware\VMware View\Server\tools\bin

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –listSites

Note: This command will show the default names of the Sites: <defaultpodname_in_DC1> and <defaultpodname_in_DC2>

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –createSite DC1-SITE01

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –createSite DC2-SITE01

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –assignPodToSite –podName DC1-POD01 –siteName DC1-SITE01

 lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –assignPodToSite –podName DC2-POD01 –siteName DC2-SITE01

Create and Configure a global Entitlement

For each pool which will be created the following will need to be done:

  • a global entitlement will need to be created
  • a VMware Horizon View pool will need to be associated with this global entitlement
  • an Active Directory group will need to be added to this global entitlement

In the example below a global entitlement with the name GLOBAL_ENT-POOLTEST will be created for pool with Pool ID POOLTEST

Log on to the first connection server in DC1

Open a command line (Run as Administrator)

cd C:\Program Files\VMware\VMware View\Server\tools\bin

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –createGlobalEntitlement –entitlementName GLOBAL_ENT-POOLTEST –scope ANY –isFloating –multipleSessionAutoClean –defaultProtocol PCOIP

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –addPoolAssociation –entitlementName GLOBAL_ENT-POOLTEST –poolId POOLTEST

lmvutil –authAs <view_service_account> –authDomain xxxx –authPassword “*” –addGroupEntitlement –entitlementName GLOBAL_ENT-POOLTEST –groupName NETBIOSDOMAIN\group_POOLTEST

Permanent link to this article: http://ituda.com/vmware-horizon-view-cloud-pod-architecture-installation/

Dec 27 2014

VMware Horizon View – Upgrade from version 5.x to 6.x

Upgrading from VMware View 5.x to VMware Horizon View 6.x is a fairly straightforward process. Below is a small overview of the steps to undertake.

Document existing View environment

  • Document View topology
  • Document OS versions used
  • Document VM settings for Connection, security and composer servers (vCPU, RAM, HDD, …)
  • Document database settings (ODBC on Composer)
  • Document accounts used
  • Document IP addresses, hostnames, DNS entries, …
  • Document all View global settings and pool settings
  • Document configuration of load balancer
  • Export LDAP database using vdmexport.exe from a connection server. c:\program files \VMware\VMware View\Servers\tools\bin\vdmexport -f myexport_beforeupgrade.ldf -v
  • Make a copy of the folder that contains the SSL certificates on the View Composer server: %allusersprofiles%\Application Data\VMware\VMware Virtualcenter

Preparation

  • Stop/halt all VMware View scheduled tasks
  • Disable provisioning of all linked-clone desktop pools
  • Edit Desktop/pools settings: set “Refresh OS disk on logoff” to “never”

Hardware Requirements

  • Composer Server:
    • Win Server 2008 R2 / 2008 R2 SP1 / Win 2012 R2
    • 2 (4) vCPUs – 4 (8) GB RAM – 40 (60) GB HDD [minimum (recommended)]
  • Connection/Security Server
    • Win Server 2008 R2 / 2008 R2 SP1 / Win 2012 R2
    • 1 (4) vCPUs – 4 (10) GB RAM [minimum (recommended)]
  • SQL Server
    • 2008 Express R2 SP2, 2008 SP3, 2008 R2 SP2, 2012 Express, 2012 or 2012 SP1

Upgrade Process

  • Upgrade View composer server
    • Download and run the View Composer installer
    • Choose to let the installer upgrade the database
  • Upgrade View Connection Server
    • Download and run the View Connection Server installer on all View Connection servers (one-by-one)
    • Edit the VMware View Horizon license and enter the VMware Horizon 6.0 license key
    • Export LDAP database using vdmexport.exe from a connection server. c:\program files \VMware\VMware View\Servers\tools\bin\vdmexport -f myexport_afterupgrade.ldf -v
  • Upgrade View Security Server
    • Specify a security server pairing password on the Connection server that will be paired with the security server you are upgrading
    • Select “prepare for upgrade of reinstallation” to remove the existing IPsec rules
    • Download and run the View Connection Server installer on all View Security servers (one-by-one)
  • Upgrade GPOs
  • Upgrade View Agent on parent machines
  • Recompose linked clone pools
  • Upgrade View Clients

VMware Documentation

https://pubs.vmware.com/horizon-view-60/topic/com.vmware.ICbase/PDF/horizon-view-60-upgrades.pdf

 

Permanent link to this article: http://ituda.com/vmware-horizon-view-upgrade-from-version-5-x-to-6-x/

Dec 26 2014

VMware Horizon View – Settings I should not forget

Below is a list of non-default settings and configurations I use in VMware Horizon View deployments.

Horizon View Infrastructure

Create an index on the SQL Event Database (not needed anymore for version 6.1.1 and later)

When browsing the monitored events in the VMware Horizon View Administrator console, the performance might be extremely slow. The larger the Event database becomes, the slower the queries run.

To resolve this issue create an index on the SQL Events database

  • Open SQL Server Management Studio
  • Browse to the View Event Database
  • Browse to the dbo.event_data table
  • Right click and select “New Index”

ViewEventDB_create index

 

 

 

 

 

 

 

 

 

 

 

  • Create an index on column EventID

ViewEventDB_create index_2

 

 

 

 

 

 

Reference: http://kb.vmware.com/kb/2094580

Enable ‘High Performance’ host power policy

Poor performance may be related to processor power management implemented either by ESXi or by the server hardware. Certain applications that are very sensitive to processing speed latencies may show less than expected performance when processor power management features are enabled. It may be necessary to to turn off ESXi and server hardware power management features to achieve the best performance for such applications.

ESX_High_Performance

 

 

Reference: http://kb.vmware.com/kb/1018206

Limit domains visible to end-users

You can configure domain filters to limit the domains that a Horizon View Connection Server instance or security server makes available to end users.

  • Log on to a connection server
  • Open a command prompt (as administrator)
  • Change Directory to C:\Program Files\VMware\VMware View\Server\Tools\bin
  • To display the currently active domains for the View Connection Server instance, run the below command:
    • vdmadmin -N -domains -list -active
  • To make only the domain MYDOMAIN visible to the end-user run the below command:
    • vdmadmin -N domains -include -domain MYDOMAIN -add

Reference: VMware Horizon View documentation

Certificate Revocation Checking

Each Horizon View Connection Server instance performs certificate revocation checking on its own certificate and on those of the security servers paired to it. Each instance also checks the certificates of vCenter and View Composer servers whenever it establishes a connection to them. By default, all certificates in the chain are checked except the root certificate.

If you have your own CA but do not or cannot include certificate revocation information in your certificate, you can choose not to check certificates for revocation by adding a registry key to your connection servers to not perform certificate revocation checking:

REG ADD "HKLM\Software\VMware, Inc.\VMware VDM\Security" /v CertificateRevocationCheckType /t REG_SZ /d 1

Reference: http://kb.vmware.com/kb2000063 and VMware Horizon Documentation

Enable Touch ID

Since VMware Horizon 6.2 a new functionality has been introduced to be able to log in to your VDIs and RDSH applications using the Touch ID on iPhones and iPads.

This functionality is however not enabled by default.

To enable the functionality

  • Open ADSI Edit on a connection server
  • Connect to the View ADAM database (See VMware KB 2012377)
  • Open the object DC=vdi, DC=vmware, DC=int ==> Properties – Global – Common
  • Edit Attribute “pae-ClientConfig” attribute
  • Add the value “BioMetricsTimeout=-1”
  • BioMetrocsTimeout

See also VMware Horizon View 6.2 Documentation

Pools

Set pae-DirtyVMPolicy to 2

When using VMware Horizon View with a pool set to refresh or delete the virtual machines after log off, you can experience the following symptoms:

  • VMware Horizon View virtual machines are unavailable.
  • The VMware Horizon View Administrator console shows the status of virtual machine as: “Already Used”  or  “Agent Disabled”

To resolve the issue set the pae-DirtyVMPolicy to 2

  • Start the ADSI Edit utility on the VMware Horizon View Connection Server host.
  • Select or type a Distinguished Name or connect to DC=vdi, DC=vmware, DC=int.
  • Select or type a domain or server to localhost:389.
  • Locate the OU=Server Groups for editing.
  • Under the Server Groups OU, double-click CN=pool_name. This opens the properties of the CN.
  • Click the pae-DirtyVmPolicy attribute and click Edit.
  • Set the pae-DirtyVmPolicy attribute to the selected mechanism described above.

pae-dirtyvmpolicy

 

 

 

 

 

 

Note: This needs to be done on every pool.

Reference http://kb.vmware.com/kb/1000590

Golden Image

Disable the HotAdd/HotPlug capability

To remove the option for users to remove NICs and SCSI controllers appear as removable devices

  • Connect to the ESXi/ESX host or vCenter Server using the vSphere Client.
  • Power off the virtual machine.
  • Right-click the virtual machine and click Edit Settings.
  • Click the Options tab.
  • Click General > Configuration Parameters > Add Row.
  • Insert a new row with the name devices.hotplug and a value of false.
  • Power on the virtual machine.

Reference: http://kb.vmware.com/kb/1012225

Install Microsoft Hotfix 2550978 on your golden image

Install Microsoft hotfix http://support.microsoft.com/kb/2550978 (See also VMware KB 2007319)

  • The 32-bit version for Windows 7 SP1 and Windows Server 2008 R2 SP1 Datacenter Edition can be downloaded here
  • The 64-bit versionfor Windows 7 SP1 and Windows Server 2008 R2 SP1 Datacenter Edition can be downloaded here

Enable Verbose or Highly Detailed Status Messages

Windows offers the option to display certain messages during its startup and shutdown. These are referred to as Verbose Status Messages (win7/2008) or Detailed Status Messages (win8/2012) and tell us the processes or steps that the Windows operating system is taking during startup, shutdown, logon, and logoff operations. These verbose messages tell you what Windows is doing in the background while carrying out these operations.

With these verbose status messages turned on, the end-user will see more things moving on the screen, which gives him/her the perception that logon is faster as he/she sees something is going on.

Add the following registry key to your parent image:

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

Add DWORD verbosestatus with a value of 1

Reference: http://www.thewindowsclub.com/enable-verbose-status-message-windows

Pre-compile .NET Framework assemblies

Microsoft .NET compiles framework assemblies on an as-needed basis when .NET-dependent programs are launched for the first time. This process can be both CPU-and disk-intensive, so you should pre-compile all .NET Framework assemblies on the Virtual Desktop master image prior to deployment. The following steps outline how to pre-compile all versions of the .NET Framework assemblies:

  1. Open an elevated Windows command prompt.
  2. Navigate to the C:\Windows\Microsoft.NET\Framework\v4.0.30319 directory.
  3. Type ngen.exe update /force This process may require several minutes to complete.Microsoft .NET 3.5 or 4.0 is not installed by default on Windows 7 or Windows 8. If Microsoft .NET 3.5 or 4.0 is required on the desktop image, it should be installed prior to running the ngen.exe executequeueditems command.

Disable some Active Setup components of Windows

As per VMware KB 2100337 logon time will be a lot faster when disabling all the Active Setup components of Windows.

Delete stubpath under
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{2C7339CF-2B09-4501-B3F3-F3508C9228ED}”
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{2D46B6DC-2207-486B-B523-A557E6D54B47}”
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{44BBA840-CC51-11CF-AAFA-00AA00B6015C}”
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{6BF52A52-394A-11d3-B153-00C04F79FAA6}”
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4340}”
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4383}”
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{89B4C1CD-B018-4511-B0A1-5476DBF70820}”
“HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\>{22d6f312-b0f6-11d0-94ab-0080c74c7e95}”

Permanent link to this article: http://ituda.com/vmware-horizon-view-settings-i-should-not-forget/

Nov 19 2014

vCenter Operations Manager – blog series

I found  a very nice, well written blog serie about tuning and using vCenter Operations Manager written by Phil Barlow on http://www.definedbysoftware.com/

Here are the links to this 5-part serie blog:

http://www.definedbysoftware.com/2014/01/19/tuning-vcops-for-your-environment-1/

http://www.definedbysoftware.com/2014/01/21/tuning-vcops-for-your-environment-part-2-badge-tuning/

http://www.definedbysoftware.com/2014/01/22/tuning-vcops-for-your-environment-part-3-creating-and-applying-policies/

http://www.definedbysoftware.com/2014/01/28/tuning-vcops-for-your-environment-part-4-capacity-management-models/

http://www.definedbysoftware.com/2014/01/30/tuning-vcops-for-your-environment-part-5-capacity-management-tuning/

Permanent link to this article: http://ituda.com/vcenter-operations-manager-blog-series/

Nov 19 2014

VMware Horizon View – “Already Used” status and pae-DirtyVMPolicy

When linked-clone desktops are not cleanly logged off and the “Refresh on logoff” policy is used, VMware Horizon View marks the desktop as “Already used” and blocks other users from accessing the machine.

This “Already Used” state is a default VMware security feature which prevents other users from accessing the previous user’s data and allows a VMware Horizon View administrator to investigate potential problems with the desktop.

The VMware Horizon View desktop can also go into the “Already Used” state if a virtual machine is powered on on another ESXi host in the cluster in response to an HA event, or if it was shut down without reporting to the broker that the user had logged out.

The problem with this “Already Used” state is that the default within VMware Horizon View waits until a View Administrator actually does something to resolve the issue.

To resolve the “Already Used” issue, you can

  • Refresh or delete the desktop through teh VMware Horizon View Administrator console (this is a manual action)
  • Set an LDAP attribute pae-DirtyVMPolicy in the VMware Horizon View ADAM database under OU=Server Groups,DC=vdi, DC=vmware, DC=int
    • pae-DirtyVMPolicy=0 – This is the default behavior of leaving the desktop in the error state and not available for use.
    • pae-DirtyVMPolicy=1 – This allows desktops that were not cleanly logged off to be available without being refreshed. The desktop is available in the pool for another user.
    • pae-DirtyVMPolicy=2 – This setting will automatically refresh a desktop in the “already used” state and make it available again in the pool.
I prefer to set the pae-DirtyVMPolicy to 2 so “Already Used” situations will be automatically resolved by VMware Horizon View.
Changing the pae-DirtyVMPolicy needs to be done for each pool.
Manual method of setting the pae-DirtyVMPolicy value:
  • Start the ADSI Edit utility on your VMware Horizon View Connection Server host. Go to Start > Programs > ADAM > ADAM ADSI Edit.
  • Select or type a Distinguished Name or connect to DC=vdi, DC=vmware, DC=int.
  • Select or type a domain or server to localhost:389.
  • Locate the OU=Server Groups for editing.
  • Under the Server Groups OU, double-click CN=pool_name. This opens the properties of the CN.
  • Click the pae-DirtyVmPolicy attribute and click Edit.
  • Set the pae-DirtyVmPolicy attribute

PowerCLI method of setting the pae-DirtyVMPolicy value:

  • Create a function “Set-DirtyVMPolicy”

 function Set-DirtyVmPolicy([string]$desktopid, [int]$policy) {
     $pool = [ADSI](“LDAP://localhost:389/cn=” + $desktopid + “,ou=server groups,dc=vdi,dc=vmware,dc=int”)
     $pool.put(“pae-DirtyVmPolicy”, $policy )
     $pool.setinfo()
     }

  • Run the function on the desktop pool

Set-DirtyVMPolicy -desktopid <yourdesktoppoolid> -policy 2

AlreadyUsed

 

References: VMware KB 1000590 and Blogpost from TheFinalByte

Permanent link to this article: http://ituda.com/vmware-horizon-view-already-used-status-and-pae-dirtyvmpolicy/

Nov 18 2014

VMware Horizon View Recomposing – Don’t forget to cleanup after you finished

Linked clone pools are recomposed on a regular basis. Mainly to install the monthly Windows updates and maybe also to upgrade/patch some applications installed on the parent VM.

Administrators often forget to cleanup the parent VM after they finished installing patches and before they take a new snapshot.

Copy the below lines into c:\windows\system32\vdi_cleanup.bat and run it each time you finished installing patches on your golden image.

REM *********************
REM Stop and disable Windows update service
REM *********************
sc stop wuauserv
sc config wuauserv start= disabled
REM *********************
REM Delete any existing shadow copies
REM *********************
vssadmin delete shadows /All /Quiet
REM *********************
REM delete files in c:\Windows\SoftwareDistribution\Download\
REM *********************
del c:\Windows\SoftwareDistribution\Download\*.* /f /s /q
REM *********************
REM delete hidden install files
REM *********************
del %windir%\$NT* /f /s /q /a:h
REM *********************
REM delete prefetch files
REM *********************
del c:\Windows\Prefetch\*.* /f /s /q
REM *********************
REM Run Disk Cleanup to remove temp files, empty recycle bin
REM and remove other unneeded files
REM Note: Makes sure to run c:\windows\system32\cleanmgr /sageset:1 command 
REM       on your initially created parent image and check all the boxes 
REM       of items you want to delete 
REM *********************
c:\windows\system32\cleanmgr /sagerun:1
REM ********************
REM Defragment the VM disk
REM ********************
sc config defragsvc start= auto
net start defragsvc
defrag c: /U /V
net stop defragsvc
sc config defragsvc start = disabled
REM *********************
REM Clear all event logs
REM *********************
wevtutil el 1>cleaneventlog.txt
for /f %%x in (cleaneventlog.txt) do wevtutil cl %%x
del cleaneventlog.txt
REM *********************
REM release IP address
REM *********************
ipconfig /release
REM *********************
REM Flush DNS
REM *********************
ipconfig /flushdns
REM *********************
REM Shutdown VM
REM *********************
shutdown /s /t 0

 

Permanent link to this article: http://ituda.com/vmware-horizon-view-recomposing-dont-forget-to-cleanup-after-you-finished/

Nov 05 2014

Memory tuning of VMware vCenter Server Appliance (VCSA)

When you deploy a VMware vCenter Server Appliance it comes configured with a standard of 8 GB Memory. For a lot of smaller environments this is too much and you can re-configure the JVM heap size for the vCenter Server processes and therefore consume less memory.

List Configured Memory

ssh to your vcsa server

login with the root account

execute command: vpxd-servicecfg jvm-max-heap read

The output gives you three values:

VC_MAX_HEAP_SIZE_QS

== Indicates the amount of RAM configured for the Query Service (inventory service)

VC_MAX_HEAP_SIZE_SPS

== Indicates the amount of RAM configured for the Policy Based Storage Management (storage profile service)

VC_MAX_HEAP_SIZE_TOMCAT

==> Indicates the amount of RAM configured for Tomcat (vSphere Web Client Service)

VC_CFG_RESULT = 0

==> Indicates that the vpxd-servicecfg command was successful

Change Configured Memory

ssh to your VCSA server

login with the root account

 

Reconfigure memory for Tomcat (vSphere Web Client Service)

Edit usr/lib/vmware-vsphere-client/server/wrapper/conf/wrapper.conf

Change the value for wrapper.java.maxmemory to 1024 (default = 2048)

Reconfigure memory for the Query Service (Inventory Service)

Edit /usr/lib/vmware-vpx/inventoryservice/wrapper/conf/wrapper.conf

Change the value for wrapper.java.maxmemory to 1536 (default = 3072)

Reconfigure memory for the Policy Based Storage Management (Storage Profile Service)

Edit /usr/lib/vmware-vpx/sps/wrapper/conf/wrapper.conf

Change the value for wrapper.java.maxmemory to 512 (default =1024)

Shut down the virtual machine where teh vCenter Server Appliance is installed

Reconfigure the VM to 4 GB RAM

Reboot the Virtual machine

 

See also VMware KB 2005086 and article Arthur Krzywdzinski

Permanent link to this article: http://ituda.com/memory-tuning-of-vmware-vcenter-server-appliance-vcsa/

May 26 2014

Install Horizon View Agent on Windows Server 2008 R2 SP1

Since VMware Horizon View version 5.3 it is possible to use Windows 2008 R2 SP1 (Datacenter edition) as a desktop operating system.
To be able to install the Horizon View Agent on a Windows 2008 R2 SP1 operating system, you need to install the Horizon View Agent in desktop mode. The procedure to do this is the following:

  • Verify that the Remote Desktop Services role is not installed
  • Configure the Windows 2008 R2 Virtual Machine as you would configure a Windows 7 Virtual Machine
  • Install the Horizon View Agent with the VDM_FORCE_DESKTOP_AGENT flag set to 1.
    • This flag can be set a a system environment variable or can be passed as an argument to the Horizon View Agent installer.
    • E.g. VMware-viewagent-x86_64-5.3.1-xxxxx.exe /v”VDM_FORCE_DESKTOP_AGENT=1”

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

Permanent link to this article: http://ituda.com/install-horizon-view-agent-on-windows-server-2008-r2-sp1/

Older posts «

» Newer posts

Fetch more items

%d bloggers like this: