Disclaimer: 

Please note: Although OBSOLETED patches are available on SunSolve, Sun recommends using the most recent patches and the most recent revision of those patches. OBSOLETED patches do not include the latest bug fixes and/or product enhancements, and may require the installation of additional patches as a corrective measure.

Status: OBSOLETE

Patch Id: 138482-03

***********************************************************************
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
***********************************************************************

Summary: Obsoleted by: 138482-05 Sun Virtual Desktop Connector version 1.0 Patch Update

Date:  Jan/16/2009

Installation Requirements:

Additional instructions may be listed below

Solaris Release: Note: 2000 2003 XP Vista

Sun OS Release: Note: Microsoft Windows

Unbundled Product: Sun Virtual Desktop Connector

Unbundled Release: 1.0

Xref: This patch available for SUNOS 5.10 as 127559-03, for 5.10_x86 as 127560-03 and for Linux as 127561-03

Topic: 

Relevant Architecture: i386

BugId's fixed with this patch:

6650027 6672114 6675420 6685500 6687257 6691333 6694759 6694761 6706634 6709313 6710031 6710038 6710050 6711633 6714371 6731373 6731375 6731386 6736783 6745813 6752948 6758284 6758696 6762429 6763389 6768489 6770583 6771149 6777673 6778423

Changes incorporated in this version:

6758284 6758696 6762429 6763389 6768489 6770583 6771149 6777673 6778423

Patches accumulated and obsoleted by this patch:

Patches which conflict with this patch: 

Required Patches:

Obsoleted by:

Files Included in this Patch: 

vda-agent.msi
vda-tools.msi

Problem Description: 

6758284 vms leave factory too soon
6758696 VMs with reuse policy gets recycled even when user logged in, in a scenario mentioned in description
6762429 ESC: Windows application launch script vda-wcpwts.exp is not compatible with SGD 4.41 or later
6763389 ESC - VDA Client fails to retrieve network address of (VMs) with space character(s) in name.
6768489 Users are being logged into another users VM
6770583 Intervals of 0 result in many open ( TIME_WAIT ) ports on VC and connection exceptions
6771149 Sun Ray 4.1 num lock key does not work with VMware via kiosk mode with XKB enabled
6777673 VDA Service fails to reconnect to SGD IF SGD is restarted.
6778423 Further tests required to check VM suitability for use
 
(from 138482-02)
6709313 ESC: Securing SOAP Connection in SGD stops VDA service.
6714371 Searching a VM located in a pool fails if you don't specify the pool
6731373 vc agent runs out of memory
6731375 VMs not removed from AD domain on deletion
6731386 revert to snapshot always results in a vm which is not running
6736783 ESC: can not configure VDC when there are more than 1 server in an SGD array
6745813 listing vms appears to hang
6752948 Domain tab needs localisation
 
(from 138482-01)
6650027 When assigning to a pool a VM previously assigned to a owner, it should be renamed
6672114 VMs will always be suspended during recycling ignoring the VM power options
6675420 VDA Agent cannot be installed on non-english Windows versions
6685500 When upgrading SGD installation vda-config does not detect it
6687257 VMs will not be renamed back to their original name during recycling when recycle policy is "reuse"
6691333 Select template dialog has javascript errors when clicking on tree node icons
6694759 It is not possible to assign a VM to a domain user
6694761 Pools are created across datacenters
6706634 reload action on Pools table is wrong
6710031 VMs will be recycled although somebody is actually logged in to the guest OS
6710038 With recycle policy is "reuse" VMs might be recycled accidentially
6710050 VMs that have been requested but where nobody ever logged in will not be recycled
6711633 UI: The Virtual Machines page takes too long to load.

Revision History: 

138482-02 138482-01

Patch Installation Instructions: 

-------------------------------- 
Follow this step to install the VDA Agent patch on Microsoft Windows:
 
	From the command line type:
 
	  C:\> msiexec /I <vda-agent.msi location> REINSTALL=AgentFeatures REINSTALLMODE=vomus
 
Follow this step to install the VDA Tools patch on Microsoft Windows:
 
    From the command line type:
 
      C:\> msiexec /I <vda-tools.msi location> REINSTALL=ToolsFeatures REINSTALLMODE=vomus
 
NOTE: For this patch to work properly you have to install the patched
versions of SUNWvda-service and SUNWvda-admin providaded in this patch
release.

Special Install Instructions: 

----------------------------- 
1. Virtual Center Agent runs out of memory
 
  With this release we have included the ability to specify the maximum amount
  of memory available to the Sun Virtual Desktop Connector Agent. This can be
  useful for larger deployments where the agent's default maximum memory (64m)
  is insufficient. The following steps are necessary to modify the maximum
  memory available to the agent.
 
    a. Log in as Administrator to your VirtualCenter host
 
    b. Start the registry editor, Click Start -> Run, type "regedit" and click OK
 
    c. Select the Virtual Desktop Connector Agent key
    "My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\Virtual Desktop Access\Agent"
 
    d. Right Click the MaxMemorySize entry and select "Modify"
 
    e. Enter the new value for MaxMemorySize
 
    The value entered must conform to the format <number>k|K|m|M where k|K
    indicate that <number> is to be interpreted as kilobytes and m|M indicate
    that <number> is to be interpreted as megabytes.
    For example a value of "128m" indicates a maximum memory size of 128
    megabytes and a value of "1000k" indicates a maximum memory size of 1000
    kilobytes.
 
    f. Click OK
 
    g. Restart the Agent using the Services dialog available in the Control Panel
 
2. Problems with VMware VirtualCenter 2.5 Update 2
 
  VMware VirtualCenter 2.5 Update 2 includes an update to VirtualCenter's jre 
  but doesn't correctly install this update during upgrade. This results in the
  Sun Virtual Desktop Connector Agent being unable to correctly use the jre.
  If you intend using VirtualCenter 2.5 Update 2, you can avoid this problem by
  either manually stopping the VMware Infrastructure Web Access service before
  upgrading VirtualCenter or by doing a fresh install of VirtualCenter.
 
NOTE: This patch is for the Sun Virtual Desktop Connector 1.0 
component.
 
Required Patches
----------------
 
Warnings & Errors
-----------------

README -- Last modified date:  Tuesday, April 28, 2009