mpryor's Posts

Is this for Windows web access (which utilises an active-x control installed by the native client) or Linux/Mac web access (Java webapps and applets)? When you say the 'initial page' is this befo... See more...
Is this for Windows web access (which utilises an active-x control installed by the native client) or Linux/Mac web access (Java webapps and applets)? When you say the 'initial page' is this before you log in or after?
Command line parameters are not supported in the 2.0.0 client. This is something that will very likely change, though I'm afraid I can't say any dates. For 2.0.0, you will have to use a thirdpart... See more...
Command line parameters are not supported in the 2.0.0 client. This is something that will very likely change, though I'm afraid I can't say any dates. For 2.0.0, you will have to use a thirdparty utility or send keys to the application with a script.
On the note of DNS resolution, since our internal firewall rules at present will not allow internal clients to resolve external addresses, does this kill the ability to estabish the tunnel s... See more...
On the note of DNS resolution, since our internal firewall rules at present will not allow internal clients to resolve external addresses, does this kill the ability to estabish the tunnel session? Example, our externally resolvable name is vdm.sealy.com and is configured in the locked.properties file. Internal clients are unable to resolve this (does this negate a successful tunnel init)? Thanks again! You will not be able to establish a tunnel from the internal clients if they cannot resolve the DNS address set in the locked.properties. I would recommend either pointing internal users to the connection server address and not the security server, or utilizing zones on your DNS server so that it serves up the internal IP address to internal clients.
Afraid not. The session data is collected directly from the agent when requested by the connection server, it is not stored anywhere so cannot be collected remotely. The only way for you to see i... See more...
Afraid not. The session data is collected directly from the agent when requested by the connection server, it is not stored anywhere so cannot be collected remotely. The only way for you to see it is to look in the admin ui.
The VDM client uses it's own registry settings for the connection, you can find the group policy file defining these within the server install under the ADM directory. In the case of drive red... See more...
The VDM client uses it's own registry settings for the connection, you can find the group policy file defining these within the server install under the ADM directory. In the case of drive redirection, this file contains: >KEYNAME "Software\Policies\VMware, Inc.\VMware VDM\Client\RDP Settings" >POLICY !!RedirectDrives > VALUENAME "RedirectDrives" > VALUEON true > VALUEOFF false >END POLICY i.e. creating 'HKCU\Software\Policies\VMware, Inc.\VMware VDM\Client\RDP Settings\RedirectDrives' with the string value of 'false' will give the behaviour you want. Edit: For clarity, in a default VDM Connection Server install, you will find the group policy file at C:\Program Files\VMware\VMware VDM\Server\ADM\vdm_client.adm
You can grow the virtual disk files within ESX by using vmkfstools within the console, and since 3.5 you can also now do it through the viclient. Simply edit the VM properties while it's powered ... See more...
You can grow the virtual disk files within ESX by using vmkfstools within the console, and since 3.5 you can also now do it through the viclient. Simply edit the VM properties while it's powered down and you'll be able to increase the disk size. Note that this won't affect the partitions within the VM, you can grow those by using 'diskpart' within the XP VM. If it's the system partition you need to resize, you will need to use a Linux boot CD or similar to achieve it. I've used gparted (http://gparted.sourceforge.net/livecd.php) for this for a while, it's extremely easy.
Ratheesh, there are a couple of common causes for this problem: 1. The agent has not configured correctly or is unable to talk to the connection server - the quickest way to see if this is the... See more...
Ratheesh, there are a couple of common causes for this problem: 1. The agent has not configured correctly or is unable to talk to the connection server - the quickest way to see if this is the case is to log into the VM and into the connection server's admin UI. You should see the user shown as 'connected' for the VM. If not, you should check that there are no firewalls blocking the agent from talking to the connection server (details of the ports required can be found in the manual). 2. The VM already has a user logged in - VDM will not allow someone to connect to a desktop that already has an active session for another user, make sure any user is logged out before attempting to connect through the client.
VMware's QA team ran these tests, they've also tested against five VDM servers behind a load balancer (i.e. a standard server with four replicas). I've not seen a whitepaper on official recommend... See more...
VMware's QA team ran these tests, they've also tested against five VDM servers behind a load balancer (i.e. a standard server with four replicas). I've not seen a whitepaper on official recommendations for broker scaling, perhaps someone else can jump in with that if it's around? Edit: Well spotted Tim, didn't realise Mark had already covered this.
Frank, VDM 2.0 was stress-tested with 1000 tunnelled users to a server for the release. From that, a pair of connection servers should be sufficient for your needs, especially as the majority ... See more...
Frank, VDM 2.0 was stress-tested with 1000 tunnelled users to a server for the release. From that, a pair of connection servers should be sufficient for your needs, especially as the majority of your clients will be bypassing the tunnel. Mike
The pool VMs will sit in the "customising" state until the connection server hears back from the agent. Assuming that sysprep has completed successfully, you should check the following: 1. The... See more...
The pool VMs will sit in the "customising" state until the connection server hears back from the agent. Assuming that sysprep has completed successfully, you should check the following: 1. The VDM agent is installed on your VM 2. The string 'Broker' in registry key HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Configuration is set to your connection server address 3. Values 'Server DN' and 'Server Pool DN' in HKLM\SOFTWARE\VMware, Inc.\VMware VDM\Node Manager are populated 4. The VM has an IP address and that the value for Broker in (2) is resolvable from the VM. 5. There is no firewall blocking connections from the VM to port 4001 on the connection server.