VSphere client on a server running terminal server

Salvation; I think to offer vSphere Client access to some customers who wish to access a virtual computer a complete console.


Someone at - configure a server terminal server (win2008 R2) and published the customer, so that the user can launch the vSphere client and access their virtual machine?

As I read about it, it seems that a requirement is to have 6 Client RDP, which leaves the linux and Mac users, am I correct?
Are there problems with it? In executing vCenter 4.1 at the moment, but will switch to the v5 this year.

I tried to find some information about it, but can't find much.

We provide the client vSphere (version 4.x and 5.0) on the servers Windows Terminal Server (Windows 2003 with Citrix XenApp 5.0) and it works flawlessy.

Tested with all sorts of Citrix ICA clients, but also via RDP (including the old version of 5.1 client built into Windows XP).

I never tested the RDP clients non - Windows, but I don't really expect any problems with them.

-Andreas

Tags: VMware

Similar Questions

  • vSphere Client exe file take run

    Hello

    I downloaded the client vSphere exe file and double click it.

    It shows the normal 'open file - security warning' like any what other exe and I press button 'run '.

    Nothing happens.

    When I run the file as an administrator, nothing happens too. nothing. as I have not yet pushed.

    my computer:

    CPU Intel i7 2600 3.4 Ghz

    4 G memory

    Win7 Enterprise

    64 bit.

    Why nothing is happening when I ru the vSphere Client install exe?

    More questions than one. Run any software protection AV or endpoint on the host? In this case, make sure that these applications do not block installation. Even if this was not a problem with the vSphere Client - but only with VMware Workstation/Player - looking for a process of "fixcamera.exe". If this is the case, you can try to kill him before starting the installation.

    André

  • PowerCLI equivalent to vSphere client "Detach" memory card?

    I'm trying to find the PowerCLI equirvelent to disconnect an adapter of the ESX host storage device. Preferably using the LUN ID.

    For reference, in the vSphere client GUI I have run the command by selecting a host configuration tab, then select adapters and storage in detail looking at the peripheral view, I can right click on a device and have the ability to "unpin".

    I've been watching the cmdlets Get-ScsiLun and Set-ScsiLun.

    I have also been watching the ScsiLunPath together and wonder if Active the parameter false, that's what I'm looking for?

    I am also looking to hard drive Set and remove hard drive but these commands seem to be relevant to VM and hosts no.

    Any help or hints would be appreciated.

    This new feature in the vSphere client 5 is not taken in charge by a cmdlet PowerCLI AFAIK.

    But you can get the same result by using the DetachScsiLun method.

    2 following functions (I added a function to fix as well) will allow you to detach and attach the lun.

    I chose to spend the LUN target via its canonicalname, but you can easily adapt the functiosn to use another LUN property.

    function Detach-Disk{
        param(
            [VMware.VimAutomation.ViCore.Impl.V1.Inventory.VMHostImpl]$VMHost,
            [string]$CanonicalName    )
    
        $storSys = Get-View $VMHost.Extensiondata.ConfigManager.StorageSystem
        $lunUuid = (Get-ScsiLun -VmHost $VMHost | where {$_.CanonicalName -eq $CanonicalName}).ExtensionData.Uuid
    
        $storSys.DetachScsiLun($lunUuid)
    }
    
    function Attach-Disk{
        param(
            [VMware.VimAutomation.ViCore.Impl.V1.Inventory.VMHostImpl]$VMHost,
            [string]$CanonicalName    )
    
        $storSys = Get-View $VMHost.Extensiondata.ConfigManager.StorageSystem
        $lunUuid = (Get-ScsiLun -VmHost $VMHost | where {$_.CanonicalName -eq $CanonicalName}).ExtensionData.Uuid
    
        $storSys.AttachScsiLun($lunUuid)
    }
    

    You can call the function like this

    $esx = Get-VMHost MyEsx $name = "The-canonical-name-of-the-target-LUN"
    
    Detach-Disk -VMHost $esx -CanonicalName $name
    
  • Impossible to connect to vCenter Server 5.5 using the vSphere Client

    Hello


    I'm trying to configure VMware Lab home using the link below and I have reached a stage where I need to connect to vCenter Server using the vSphere client.


    http://boerlowie.WordPress.com/2011/12/13/building-the-ultimate-vSphere-lab-part-9-ESXi/


    I installed the package of 5.5 full vCenter server using the simple installation option and it includes vCenter server, single sign - on, Webclient vSphere, vCenter server and vCenter Server inventory service. All the the latter is installed on a virtual machine that is running Windows server 2008 R2 guest OS.


    Whenever I try to open a session on the vCenter Server uses the vSphere client, one of the following error is displayed.


    1. you do not have the permissions to connect to the server 'vCenter server IP address.

    2. cannot complete the connection incorrect username or password-, this error is visible when I do not specify domain\username domain user name and simply enter the user name.


    For the details of the error, please see the screenshots - vSphere_client_1, vSphere_client_2 and vSphere_client_3.


    As suggested in the link below, I tried to create an SPN and then set the SPN (Principal of Service name) and the UPN (User Principal name) in the Active Directory identity Source using the web of vSphere client (please see screenshot vSphere_Webclient_2)


    http://vinfrastructure.it/2014/01/issue-in-logging-into-vCenter-server-using-Windows-ad-credentials/


    To fix the permission error, I tried to add the domain user to the Administrators group on the server vCenter (see screenshot vSphere_Webclient_1).


    However, none of the above-mentioned resolution has worked.


    So can someone please help? I am stuck because of this problem and badly need help to move forward.


    Thank you

    AJMAL

    Able to connect to the vSphere Client do you use the [email protected] account?

    Have you already set up permissions on the server vCenter object?

    André

  • Server.getCredential () and vSphere client web 5.5.0b

    When connected customer orchestrator Server.getCredential () returns an object of the current user's credentials... However, if you run this method in a workflow from the web client, it does not seem to pass through and you end up with a null value.

    Anyone else see this issue?

    See you soon,.

    When you lo in vCO customer, you provide a user name and password, one internally, this is represented by an object of type UserToken

    When you run a workflow of vSphere Web Client, it calls the REST API of vCO not passing the name user and password, but token SSO - one object of type SamlToken. In this case, there is no available password so we cannot construct the appropriate UserToken object. That's why this particular API returns null.

    If you must pass the name of user and password to your technical workflow of customization and want to be able to invoke this workflow from vSphere Client Web - it is impossible to do, because there is no way to get the password of the user logged into vSphere Web Client. You can only get the user name.

  • Saving a vCenter Server in vSphere Client Web (5.5)

    Hello

    I was wondering if it is possible to save multiple vCenter servers (all vCenter Server devices) with a single instance of vSphere Web Client that runs on one of these devices to vCenter?

    VCSA1 > use built in Web Client to manage all vCenter servers.

    VCSA2 > register with VCSA1.

    VCSA3 > register with VCSA1.

    I find no 5.5 specific information but what I've read I think it's possible on 5.1. The ' admin - cmd.sh' script does not seem to be present in my 5.5 VCSA however.

    VSphere Documentation Centre

    The Server system, a device to vCenter Server vCenter is pre-recorded with the vSphere Client Web inside the unit. To register for another system of vCenter Server with the vSphere Client Web installed as part of a vCenter Server Appliance, you must use the admin-app script from the command line rather than the Web-based administration tool.

    vCenter Infrastructure Navigator 5.7 Documentation Center

    /usr/lib/VMware-vSphere-client/scripts/Admin-cmd.sh register https://WebClient.mydomain.com:9443 / vsphere client Director of VC.mydomain.com 'CENSORSHIP'

    Thanks for any help.

    The admin app is no longer available with vCenter 5.5. If you register all the vCSA to a SSo central, they will all see the place in the web client unique management this SSO Server vCenter.

  • vSphere Client for server 2012

    I installed Windows Server 2012 on my laptop and tried to install the vSphere client (VMware-viclient-all - 5.0.0 - 623373), but it comes up with "this product cannot be installed on Windows XP SP2 and more.

    Is there a way to get around this, or there at - it a newer version of the client that I can download that will work?

    See you soon.

    Martin

    Copy the file on your server and do a right click and properties and set compatibility, run as win7.

    installs and works very well, the MSI just the knowledge that there is a new version of windows.

  • After the blackout, VMs will not start and Vsphere Client cannot be re management/access / start VMs on a physical server.

    After the blackout, VMs will not start and Vsphere Client cannot be re management/access / start VMs on a physical server.

    Get the error message...

    [[: start: W: 1] 2016-06-09 14:41:36.562 Log for vSphere Client Launcher, pid = 4532, version = version 5.0.0 = build-455964, option = released
    [[:QuickInf:W: 6] 2016-06-09 14:42:20.421 the value of the search dll C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\5.0 path
    [[:QuickInf:W: 6] 2016-06-09 14:42:24.281 load shared dll: C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\5.0
    [[ : start: w: 6] 2016-06-09 14:42:41.406 Log for vSphere Client, pid = 4532, version = version 5.0.0 = build-455964, option = release, user = root, url = https://192.168.10.200/sdk
    [[:ShowExcp:W: 6] 2016-06-09 14:42:42.406 error: an internal error has occurred in the vSphere Client.

    Details: The initializer for type for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.

    Contact VMware support if necessary.

    System.TypeInitializationException: The initializer for type for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.

    at VirtualInfrastructure.Utils.ClientsXml.FetchIfClientsXmlExists (String serviceUrl)

    at VirtualInfrastructure.LoginUtils.LoadMatchingVI (String serviceUrl)

    at VirtualInfrastructure.LoginUtils.CreateNewService (String serviceUrl, ClientSpec clientSpec, Boolean waitForTopology, Assembly / viAssembly)

    to VMware.Vim.Client.VimClient.StartUp (2 specMap, String [] arguments dictionary, Manager of LoginEventHandler)

    to VpxClient.UI.InitializeVimClient (dictionary 2 specMap, String [] arguments)

    to VpxClient.UI.StartUpIfNotMultiVcSecure (dictionary 2 specMap, SecureString password, String [] arguments, LoginEventHandler Manager, String, dllPath, list 1 listOfVcUrls)

    System.TypeInitializationException: The type to 'VirtualInfrastructure.Utils.TypedXmlSerializer ' 1' initializer threw an exception.

    to VirtualInfrastructure.Utils.TypedXmlSerializer'1.ctor)

    to VirtualInfrastructure.Utils.ClientsXml... cctor()

    System.IO.IOException: The process cannot access the file "C:\Documents and Settings\XXXXUSERNAMEXXXX\Local Settings\Temp\nyhn4bev.dll" because it is used by another process.

    ...

    to System.Xml.Serialization.XmlSerializer... ctor (Type type)

    to VirtualInfrastructure.Utils.TypedXmlSerializer'1.cctor)

    -End of the exception stack trace internal-

    -End of the exception stack trace internal-

    After many unsuccessful attempts tried to connect Vsphere client, the client has finally connected and was able to on all virtual machines. Thanks to Luciano Patrão for study. For all in the community, peace out...

  • How to connect to the server ESXI vSphere Client side WAN?

    How to connect to the server ESXI vSphere Client side WAN?

    through firewall

    I tried to open the ports 902 903, 443... and so on...

    and I tried several sites to find the solution but...

    nothing works...

    connectivity works on local network

    Help, please...

    Source Destination Port

    ESXI 443/TCP client

    ESXi 902/TCP client

    ESXi 902/TCP Client

    ESXi 902/UDP Client

    ESXi 903/TCP client

    Edit: Also check if the firewall ESXi all IP addresses are allowed to connect:

    Example:

    See attachment...

  • ESXi 5.5u1 added iscsi storage adapter - reboot and now vSphere Client could not connect to "my ip" an unknown error has occurred.  The server could not interpret the customer's request.  The remote server returned an error (503) server unavailable

    I have not yet connect to an iSCSI target device.

    I can ping my host

    when I open http:// "hostip" in a web browser, I get a 503 service not available.

    restart the host gets me nowhere.

    SSH opens somehow, but can not connect

    Console seems OK

    vSphere Client can not connect

    If I reset to the default values of the console it is ok, but when I reconfigure the host, this error will be returned.

    I tried to reinstall from DVD

    I'm completely corrected to date via SSH esxcli

    This happens on both my hosts, although they are almost identical Lenovo thinkserver TS140s with broadcom 10Gig NIC and intel NETWORK card integrated

    It almost always seems to happen the next time I reboot after enabling iscsi support

    The only weird thing I have is that my Integrated NIC is a processor intel 217's and I have to use a special VIB so that it can be used in ESXi

    Customer's winning 8.1

    Here is my installation notes

    Install on USB/SSD stick with custimized ISO i217 NIC driver, reset the configuration and reboot

    Management NIC set to NIC0:1Gig

    IP management: hostIP/24 GW: my gateway

    DNS:DNS on windows vm1, vm2 Windows dns

    HostName:ESXi1.Sub.myregistereddomainname custom DNS Suffixes: sub.myregistereddomainname

    Reset

    Patch to date (https://www.youtube.com/watch?v=_O0Pac0a6g8)

    Download the VIB and .zip in a data store using the vSphere Client

    To get them (https://www.vmware.com/patchmgr/findPatch.portal)

    Start the SSH ESXi service and establish a Putty SSH connection to the ESXi server.

    Put the ESXi server in maintenance mode,

    example of order: software esxcli vib install /vmfs/volumes/ESXi2-2/patch/ESXi550-201404020.zip d

    Re install the Intel 217 NIC driver if removed by patch

    Change acceptance ESXi host sustained community level,

    command: esxcli software - acceptance-level = CommunitySupported

    Install the VIB

    command:esxcli vib software install - v /vmfs/volumes/datastore1/net-e1000e-2.3.2.x86_64.vib

    command: restart

    Connect via VSphere client

    -Storage

    Check/fix/create local storage. VMFS5

    -Networking

    vSwitch0

    Check vmnic0 (1)

    Network port group rename VM to the 'essential '.

    Rename management group of network ports for management of basic-VMkernel traffic.

    -Configuration time

    Enable NTP Client to start and stop the host. ntp.org set 0-3 time servers

    DNS and routing

    Start the virtual machine and stop

    -enable - continue immediately if tools start - stop - prompted action Shutdown - the two delay to 10 seconds

    Security profile

    Services

    SSH - startup - enable the start and stop with host

    Cache host configuration

    -Properties to start SSD - allocate 40GB for the cache host.

    Flashing warnings SSH:

    Advanced settings, UserVars, UserVars.SuppressShellWarning, change from 0 to 1.

    Storage adapters

    -Add - add-in adapter software iSCSI

    I think I saw that I was wrong.  In fact, I applied two patches when only suited. I started with 5.5u1rollup2 and then applied the ESXi550-201404001 and ESXi550-201404020.  Strangely I did not t o had problems until I worked with iSCSI.

  • Unable to connect to vCenter Server 5.0 using the vSphere Client - unknown error.

    I am trying to connect to vCenter using vSphere client (from different computers, including the server itself) and get this:

    vSphere Client could not connect to "vCenter_Server_IP_Address".
    A unknown connection error has occurred. (The request has failed because of a logon failure. (Unable to connect to the remote server))

    I am able to connect to the host directly, but of course, can't do anything with it since the vCenter is "in da house".

    There is no problem with it, not big changes and nothing indeed directly on the server vCenter (i.e. W2008r2x64) so, my confusion deepens. 5.1 ESXi

    Any ideas what could have happened and how to fix it?

    observe the following error in the logs.

    2014-04 - 04T 13: 35:23.506 + 01:00 [error 02720 "Default" opID = SWI-f3a52464] [VdbStatement] given the driver diagnosis are 42000:1:1105: [Microsoft] [SQL Native Client] [SQL Server] could not allocate space for object ' dbo. VPX_EVENT'. 'PK_VPX_EVENT' in 'VIM_VCDB' database because the 'PRIMARY' filegroup is full. Create disk space by deleting unnecessary files, removing objects in the filegroup, a

    Follow this article to fix the problem.

    http://alexjs.EU/VMware-ESX-and-a-full-SQL-Server-database/

  • VSphere Client multiple connections to a single server vCenter Server?

    I have a vCenter Server that manages a few hosts. I know it's a bad habit to manage guests individually using vSphere Client, but I was wondering if I can have multiple connections to the same server vCenter Server vSphere client using the same Windows credentials?

    It seems counterproductive to only allow a connection to the server vCenter Server...

    Yes - by default, a connection up to 25 to vCenter

  • Cannot access the server from vsphere client

    Hi, people.

    After having been very well for a few weeks, now I'm unable to access my server from vSphere client, I get an error of:

    Call 'ServiceInstance.RetrieveContent' to object 'ServiceInstance' on the server '192.168.6.2' failed.

    I've attached screenshots of the error message.

    The pc and the server are on the same subnet, and the error comes from several PCs that try to connect.

    Help, please!

    NM

    So I think you must restart these services as vivari said.

    If you are unable to log in via ssh, you must have access to the consoles. Then, you can restart the services or enable ssh to do via ssh.

  • vSphere Client could not connect with the server

    Hello

    I just built a new server ESX 4.0 (update1) and tried to connect directly from the VI Client.

    He keeps fails with the following error message:

    VSphere client could not connect with the server {ip address}

    Details: The server could not interpret the customer's communication... (The remote server returned an error: (503) server unavailable.)

    I can ping the server successfully.

    Has anyone seen this problem before?

    Thank you

    for many of my cases, it's just 2-3 minutes. can you do back to the rear for connection between the server and your laptop to see there is nothing between that is causing the problem?

  • vSphere Client running on Windows 7 RC

    I am running Windows 7 RC and it worked perfectly with the Virtual Server Client 2.5. However, I recently installed a host using ESX 4.0 and I also improved the client Virtual Server 2.5 for the vSphere Client. I was not able to connect to host servers. I keep getting the following error messages:

    "Error analysis of the server" server_name'"clients.xml" "file. Login will continue, contact your system administrator.

    When I click Ok to this message then I get the following:

    'The initializer for type for 'VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception.

    Any ideas.

    See this thread, http://communities.vmware.com/thread/211440 , apparently someone figured out how to make it work.

Maybe you are looking for