We have a parent image that was defined as a 64bit machine during creation. But when it was time to install from the Windows 7 ISO, a 32bit version was installed. We have taken snapshots and recomposed with this parent vm... performance appears to be great! We did not have any issues with VMTools and the View agent seems fine... is there any reason why we should not do it this way? Is this the same as installing a 32bit Operating System on a system that has a 64bit processor?

Hello,

I'm going through an eval of View and three issues came up while working on external access via the Security Server in our DMZ.

1. Using this article: VMware KB: Guidelines for generating and importing an SSL certificate for the View Connection Server for View 5.0.1 … I bought a certificate from an external CA (Thawte) and imported it into the keystore on the security server.  I created the locked.properties file in C:\Program Files\VMware\VMware View\Server\sslgateway\conf.  After restarting the Security Server, it still seems to be using its self-signed certificate.  Is there some other step missing from this document?  I came across one guy's blog who walks through doing this without keytool, and one of his steps says that the friendly name on the cert had to be vdm... not sure if that's specific to his environment, or a VMWare requirement.

2. I was able to log into the Horizon client externally after acknowledging that the self signed certificate wasn't trusted.  However if I launch a desktop from the linked clone pool using PCoIP it won't connect.  It looks like it's connecting (the screen goes black, and I get the control bar on the top of the screen, but then it closes out and I get a message saying ""The connection to the remote computer has ended".  I assume this is a firewall issue, and I've looked at http://blogs.vmware.com/consulting/files/2014/06/Horizon-6-Firewall-3.png and View TCP and UDP Ports.  I'm fairly certain that I got all of them.  For PCoIP, is all that I need TCP/UDP 4172 open from external in to the Security Server and from the Security Server in to the desktop VMs?

3. If I change the protocol to Microsoft RDP, the connection works from external, however I get a permissions error when it starts to log in to the desktop saying that I need to be in the Remote Desktop Users group.  I'm able to connect to the same Linked Clone pool from an internal machine using the same credentials though.  Is there something different about how the desktop launches externally vs internally?

Thanks in advance for any help!

Dylan

Hi there,

We have a Horizon View 6 deployment going live soon (ish). One of the steps we would like to take either now or soon after go-live is to have all internal users connect directly to their desktops after the initial connection, and for external users to be tunnelled via the Security/Connection server pairing. I am pretty happy with how the config would roughly look, but in lieu of a decent test bed (and not wanting to go installing/re-configuring/uninstalling on the Prod platform for the sake of cleanliness) can anyone answer some basic questions about the practicalities?

Assuming I don't care about resilience it seems that I should have one Connection Server handling the tunnelled users and another connection server paired with a Security Server handling the external users (reference here:Documentation Center for VMware Horizon 6.0 with View). However, should either of those Connection Servers be a replica of the other or would they then simply inherit the tunnelling config of the other? If that is the case and the Connection Servers had to be two standalone instances with their own pairings and tunnelling config does that then mean managing two identical sets of desktop pools or can that be aggregated across the Connection Server instances.

Sorry if this seems like a fundamental question but I don't see everything I've asked definitively answered all in one place.

Hi All,

I need to generate audit login for our VMware Horizon security server. I need to create this report to show management who try to log into our environment from public network.

I am looking for automate way to generate this report on daily or weekly basis. I looked in VRealize and log insight but couldn't found what I am looking for.

Back in July we had published a Support Insider blog post about using the ViewDbChk command to remove invalid linked clone entries, which applied to Horizon View 5.3 and later. Apparently a similar situation can arise in earlier versions of the product as well, but the steps to fix it are different.

For users of View 5.2 or earlier, we have created KB article: Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View.

(view original post)

We are migrating our new purchases to include slim clients, but we can not afford to do all of them at once.  I am a system admin at a college and will need to setup a lab with older machines to go directly into VMware View to run the virtualized desktop.  Does anyone have a recommendations/faq/instructions/references that help lock down a machine so that the end user can only use the virtual desktop and can not get out of it?

So recently we had some DNS issues at some locations and it brought down access via the Horizon View Client.  Each location had three DNS servers configured and only the primary was having issues.  There were no other software having issues resolving addresses that I know of.

So here is what I found in my testing...

- If the primary server is completely down and not responding, Horizon View Client can resolve the host address fine.

- If the primary server is up but not responding in a proper manner to requests, Horizon View Client cannot resolve the host name.

-Horizon View Client 5.4.0.1219906 handles the issue appropriately and can resolve the host.

-Horizon View Client 2.2.0.13999, 2.3.3.18259, and 3.1.0.21879 all fail to resolve the host

It would be nice if the newer versions handled bad DNS responses as well as the old client did.

Please share if you know anything.

Thanks

When the user accesses the first time and generates  the perfil from zero , profile works perfect! But when  close the session and then you log back in, it keeps  starting.

Hi *.

we have a couple of pretty specific business applications which we make accessible to a broad user group via linked clones.

Now, certain workflows within the Apps strongly depend on the date of the underlying operating system.

This is why we added a script which changes the current date to a required date in the past to make the App and its workflows working.

Unfortunately this has a side effect. After connecting to the linked clone the date gets automatically and successfully changed. App works a treat.

Then after approx. 18m:

- the user gets forcibly disconnected

- the linked clone persists, does not get automatically deleted as we have configured the pool

- the linked clone will not be reused if the user tries to reconnect

- the user gets assigned to a new linked clone while reconnecting / a single user can occupy multiple linked clones as they wont get automatically deleted anymore

- BIG MESS

- Is there any possible configuration/setting which can avoid being disconnected from the linked clones with that huge date / time sync gap?

- what is actually verifying the date / time of the linked clone and actively initiates the loss of connectivity

Any idea / hint / workaround is highly appreciated!!!

cheers

Hi all,

first of all i'm french so, sorry for my bad english

I'm trying to install a VMware View solution (6.0.1) , i've deploy some servers in the company that i work (all on Windows 2008 R2) :

     - on the same domain (horizon.local) :

               -view connection server : 172.16.15.1/24

               -view composer server : 172.16.15.3/24

               -an Active Directory server : 172.16.15.2/24 with a DHCP server

     -without domain :

               -view security server : 172.16.15.14/24 and 194.3.x.x/24 (public IP address to external access). In this server, i installed a SSL certificate for the FQDN corresponding to public IP address.

AND virtual desktops have ip address between 172.16.15.100/24 and 172.16.15.200/24 (Windows 7 Pro, view agent installed and html access installed).

So, my problem : when i'm at home and try to connect on the security server (the FQDN is horizon.mycompany.net), all is ok. I write my user and password, it's ok. There is the allow pool but, when i click on the pool, in the navigation bar on google Chrome, the FQDN was replaced by the virtual desktop IP address : 172.16.15.101, so when i'm at home i can't be connected (because of private address).

Someone knows how can i keep public IP address during all the time ?

Thanks for all, if you want other informations, just ask me.

Tom

In my test enviroment:

1. view-connection server 6.1  (ip: 192.168.10.81)
2. not setup vcenter in view administrator
3. windows 7 installed view client 3.4    (192.168.10.123)
4. view managed desktop windows 7  (192.168.10.117  name: rawc01.view.com  )
5. AD windows 2008 r2  (192.168.10.80  domain: view.com)

on windows 7 installed view clietn 3.4     (192.168.10.123),    I run "vmware-view.exe -serverURL 192.168.10.81 -userName user1 -password tsdc@123 -domainName view -desktopLayou windowSmall" to show desktop pool and logon desktop "rawc01.view.com" sucessfully.    But when I run  "vmware-view.exe -serverURL 192.168.10.81 -userName user1 -password tsdc@123 -domainName view -desktopName rawc01 -desktopLayou windowSmall" command, It show desktop pool then tip unauthority to use the desktop or application.

     What mistakes I made ? thanks for help.

Hi,

I am using VMware Horizon View Client version 3.4.0 build-2769709 and having issues with the proxy configuration.

Using Windows 7, does it use the pac file configured in Internet Explorer? If there is a proxy server configured, does it use it? I have settings by simply specifying the pac file and the connection to the server continually times out, however when manually specifying the proxy server, I am able to connect, however not every time.

This leads me to suggest, it does not support the use of a pac file. During testing the IT Support Team created a pac file that directed all traffic to the proxy regardless of rules and it still failed to connect to the server -simply timing out.

Can anyone shed some light on this and if there is a way round it by forcing it to use the specified pac file?

Thanks,

Paul

Hi

I entered the office this morning to find that most colleagues couldn't login on their thin clients. When I accessed the Horizon View admin console, i noticed that provisioning had been disabled and therefore all available desktops were not visible or accessible. There were some active connections where some people had connected at 8:30. The issue appeared to of occurred from 8:45.

I then noticed this error was being reported via the console: "error during provisioning: view composer ad fault: failed to perform active directory operation. COM Error code:-2147016651"

I re-enabled provisioning and the desktops started to provision and within 10 minutes all desktops were available again.

Problem solved but not understood! I have researched online but cannot find substantial information regarding the root course.

Has anyone experienced this issue or know what the problem was? Any ideas would be much appreciated.

We are using Horizon View 6.0.1

Thanks

Matthew

I am setting up a View 6.0.1 with Persona Management.

Persona MGT is used to redirect the AppData\Local folder to our file server.

This seem to be working fine, replication is executed every 10 mins, all files are stored on the file server and data is available for the users in the next session.

So far so good…

We also have an application which seems to be a ClickOnce application
More info: https://en.wikipedia.org/wiki/ClickOnce

This application stores data in C:\users\%username%\AppData\Local\Apps\2.0\%generated folder name%\%generated folder name%\
In the tree I see lots of folders, this may grow when the application is used. One folder in this tree seems to contain the basis of the application. This base folder has problems with the replication.
When Persona MGT is replicating the profile to the file server only a few files are to be found on the file server. Not all files are present. But the application is working since all files are in the View.

In the next session only the files on the file server are in the View, so the application is not working since it’s missing a lot of files.

When I manually copy the missing files to the file server and start a new View session the application seems to be working.
So replication to file server does not work, replication for next View session is working.

My question is how to make sure Persona MGT can replicate all files to the files server?

I already tried to make sure the application is not running during the replication, this does not solve the issue.

It’s not an option to clear the application folder after the logon, this will make the startup of the application very slow, since it’s have to download all files each time.

Whenever we try to connect to a vGPU enabled pool with two monitors the Zero Client (Wyse P25) crashes and reboots. If the pool is set to refresh then you will never be able to login.

I set the pool to not refresh and I'm able to login. The issue is specific to two monitors if i use only one the connection works properly on the first attempt.

06/05/2015, 09:13:08.011> LVL:0 RC:   0    IMG_FRONTEND :Calling open display in Tera2 mode.

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x5

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY3, flags 0x1

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY4, flags 0x0

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 0 NoWDDM 0, force win32 0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 2 NVFBC disabled 0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: profiling disabled.

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x5

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY3, flags 0x1

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY4, flags 0x0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0

06/05/2015, 09:13:08.088> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:08.088> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 2560 x 1600 

06/05/2015, 09:13:08.088> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:2560 cy:1600 leftMost:0 topMost:0

06/05/2015, 09:13:08.089> LVL:0 RC:   0          EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll

06/05/2015, 09:13:08.352> LVL:2 RC:   0        MGMT_KMP :>>> Rxed SET_KBD_LOCALE: language=0x0409 layout=0x0000

06/05/2015, 09:13:08.352> LVL:1 RC:   0        MGMT_KMP :>> Feature status with errcode 0x0000ff00 received

06/05/2015, 09:13:08.354> LVL:2 RC:   0        MGMT_KMP :>>> Rxed SET_KBD_RATE: interval=33 delay=250

06/05/2015, 09:13:08.367> LVL:1 RC:   0          SERVER :InputDevTap_GetKeyboardState @ timer: LEDs = 0xFFFFFFFF ==> 0x00

06/05/2015, 09:13:08.367> LVL:1 RC:   0          SERVER :InputDevTap_GetKeyboardState @ timer: typematic [delay 0 ==> 250] [rate 0 ==> 33]

06/05/2015, 09:13:08.865> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is NOT possible,          trying to enable capture device

06/05/2015, 09:13:08.868> LVL:0 RC:   0          EXTERN :svga_devtap ==> NVBackend::EnableNvFBC. CreateProcess MontereyEnable error 2

06/05/2015, 09:13:08.970> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:08.970> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 2560 x 1600 

06/05/2015, 09:13:08.971> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:2560 cy:1600 leftMost:0 topMost:0

06/05/2015, 09:13:09.073> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:09.073> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1280 x 960 

06/05/2015, 09:13:09.073> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:1280 cy:960 leftMost:0 topMost:0

06/05/2015, 09:13:10.339> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:10.339> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1280 x 800 

06/05/2015, 09:13:10.339> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:1280 cy:800 leftMost:0 topMost:0

06/05/2015, 09:13:10.599> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:10.645> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1280 x 960 

06/05/2015, 09:13:10.649> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:1280 cy:960 leftMost:0 topMost:0

06/05/2015, 09:13:10.721> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:10.721> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 2560 x 1600 

06/05/2015, 09:13:10.721> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:2560 cy:1600 leftMost:0 topMost:0

06/05/2015, 09:13:11.339> LVL:0 RC:   0          EXTERN :svga_devtap ==> NVBackend::EnableNvFBC. CreateProcess succeeded

06/05/2015, 09:13:11.556> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC - Fixed capture by enabling NvFBC

06/05/2015, 09:13:11.556> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: can't find monitor for display \\.\DISPLAY3

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC can't get adapter ID from name \\.\DISPLAY3

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: UpdateDisplayWatcher ERROR

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: usermode backend init failed

06/05/2015, 09:13:11.562> LVL:0 RC:-500    IMG_FRONTEND :cSW_HOST_FRONTEND::open_display - Error attaching to SVGADevTap, error 1: Failed

06/05/2015, 09:13:11.562> LVL:0 RC:-500        MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. 10 retries remaining. Trying again...

Hello,

I have some questions about webcam support in VMware View 5.1.  Ideally, I'd like to get a Logitech Pro 9000 physically connected to a laptop with the VMware View client installed working inside a Windows 7 x64 View desktop so that I can use it with Microsoft Lync 2010.

There seems to be some conflicting information about webcam support.

http://kb.vmware.com/kb/1003777 states quite clearly that webcams are not supported in any version of VMware View.

Seemingly to the contrary, I found this whitepaper (see link below) from September 2011 entitled "Validating Adobe Connect Client on VMware® View Desktops." The whitepaper discusses validating webcams for use with with Adobe Connect - the webcams being plugged into thin and zero clients connecting to VMware View 4.6 desktops.  There is even a section titled "End User Experience Matrix for Webcam Video."  The Logitech Pro 9000 is one of the cameras that was validated.

http://www.vmware.com/files/pdf/techpaper/vmw-validating-adobe-connect-client-vmware-view-desktops.pdf

This has left me somewhat confused about webcam support for VMware View and regardless of the official support stance, I am wondering if anyone knows any tips or tricks to get a Logitech Pro 9000 attached to a laptop with the VMware View client installed working inside a Windows 7 x64 View desktop.

Presently, the camera is recognized inside the View desktop but doesn't work.  I have the Logitech webcam software (version 2.5.1) installed on both the endpoint (which is also Windows 7 x64) and in the View desktop.  If I try to use quick capture for photo or video in the Logitech webcam software inside the View desktop, I just see a black screen.  Inside Microsoft Lync (also running in the View desktop), the camera is also recognized but displays an empty gray box in the video configuration area of Lync along with a message that says "Cannot connect to this webcam.  Close any active conversations or other programs that are using your webcam, and then try again."

Does anyone have any tips or tricks to get this camera working with my particular setup and does anyone have an explanation for the seemingly contradictory information I've found regarding webcam support with VMware View?

In the planning stages of the migration of my existing Horizon View environment (some linked clones & static vm's) to new hardware.  All infrastructure vm's (e.g., Vcenter) are virtual.  Because I'm moving to new hardware, I am not able to do an in-place upgrade.  Current environment: Vcenter 5.5 & Horizon View 6.0 with 4 ESXi hosts.  I'd like to move to Vcenter 6, Horizon View 6.1 with 3 ESXi hosts.  Most documentation that I've read refers to in-place upgrades using the same hardware.  Because of the marriage of Vcenter with View Connection & Security Servers, I'm hesitant to roll forward.  I would like to keep as much of the VDI environment intact without breaking everything.  One option, off the top, is to stand up a new Vcenter 6 server with old & new clusters (hardware) in the same datacenter?  Then slowly migrate from the old to the new cluster.

The migration to the new hardware doesn't have to be overnight.  I wasn't able to find any great documentation on this goal.  I'm sure that someone else has gone through this before.  If anyone has basic steps for the process, I'd greatly appreciate it.

Anyone who has installed the vmware horizon client for chromebook if the app si working? I notice in the app is not launching when you click the app on you chromebook.

My chrome OS version is 44.xx. Hope can shred some light to this. thanks

Just purchased a Chromebook to access my hosted virtual desktop through the vmware view client.  I do not see a download for the Chromebook.  Is there a solution for this issue or is the Chromebook just not supported.  It is the perfect option for my virtual desktop access.  I have been using the client with a Windows laptop previously.  Please help.  Thank You.

Hey everyone,

I have VMware Horizon with view 6.1.1, vsphere 6.0, vcenter 6.0 as well.

Problem is that when you instal Windows 10 and then vmware tools and then view agent, in Hypervisor everything works, but in Horizon View Client (3.3.0 and 3.4.0) Windows 10 works only on full screen. Whenever you try to resize window or minimize, it just closes desktop and disconnects. I believe its a poor support of VMware tools drivers.

Anyone has same problem? Maybe someone came to solution how to fix this problem with Resizing Window on Windows 10 (using View Client 3.4.0)?

Thank you in advance