There are some sample queries in the integration guide that may point you in the right direction.
http://pubs.vmware.com/view-52/topic/com.vmware.ICbase/PDF/horizon-view-52-integration.pdf
There are some sample queries in the integration guide that may point you in the right direction.
http://pubs.vmware.com/view-52/topic/com.vmware.ICbase/PDF/horizon-view-52-integration.pdf
Is this a full desktop or a linked clone? Have you reviewed esxtop during the scan to see if you can identify the bottleneck that way?
Hello,
I recently installed View Horizon 6.
A few months back I had installed 5.2 and noticed that that version had a View Desktops Plug-in at the documentation which helped a lot to find which user was logged to which VM. At the View 6 Documentation there is no such entry. Does this feature still exists?
And a second question, I know that through a GPO you can "shadow" a VM from the Vcenter Webclient that a user is still already logged in. Does Anyone know if it is possible to do something like this through the View Admistration cosole? I am not interested in shadowing the VM it is ok if the user knows that I am also able to see his screen.
Thank you
If I remove ProfileUnity the same thing happens. When I login the "Please Wait" message appears.
Thanks for the link. I tried following the instructions but I had the same results.
Dear all,
is it somehow possible (without having vCOPs yet) to have historical data on the vmware view administration dashboard?
I am currently having a report from liquidware showing the number of connected and disconnected desktops at a certain point in time.
I would also need available and all other statuses for some reports for our business.
Running View 5.X
Thanks in advance for any ideas.
best regards,
Niko
Then it probably comes down to some changes in the master image.
Can you list the optimization steps you took? Any possibility to try with a vanilla master-image?
OS is Windows 7, no VCSA. I have a parent machine which I've been using for different kinds of testing, everything works with Quickprep. This time I decided to go with Sysprep and created a new spec in vCener Customization Spec Manager.
I've never heard of "to_be_default", but a quick google search shows... Here's how to create a Default Profile in Win 7 without using SysPrep and avoiding issues
Are you sure this wasn't implemented by someone in your org on your parent/template image? Maybe create a new template from a clean ISO and try it again to see if it's the spec or the image.
I am starting to have a sporadic and random issue where a user reboots their VDI (agent 5.3.2), and is then unable to access it because the Windows Firewall Service is not starting Automatically like it is set to do. I have the service set to Started and Automatic in the template. In order to start the service so that the user can access their VDI, I have to go in through the console. Sometimes I even have to restart the Guest through Console to gain access. After restarting the Guest and accessing the machine through the Console, the Windows Firewall Service will sometimes be started.
As an update, I can "Reset Desktop" from the View Client and about 50% of the time, the VDI will come up successfully. The other 50% will be connection timeout errors where the Firewall didn't start.
I have a parent machine with a default profile which I modified slightly, but there are no other accounts on the machine other than Administrator, it is a domain machine I am the only person who is working with View, it is still in testing phase. As I mentioned everything works fine with Quickprep, I created dozens of various pool. It happens only when I try to use Sysprep as follows, as simple as it gets. Please take a look.
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
If you do use the bat file and run 64-bit, this entry breaks IE 10/11...
reg ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" /v MoveImages /t REG_DWORD /d 0x0 /f
So you may want to comment that one out.
I encounter the same issue. Can you share your solution ?
I had the same problem and I found that I missed the HMTL Access checkbox in the Desktop Pool. Now I can access from a remote browser the desktop.
Hi Linjo,
I have the same error as this post. I am just trying to access the desktop, not any applications. I have enabled the pool for HTML access but still get the message. Any other ideas?
Thanks,
Robert
Hi Sennen69,
After you enabled HTML access in the pool, did you have to reboot or reprovision your desktops?
I still get the error even though I enabled the pool for HTML access.
No bacically click on the OK to end the editing and retied the remote login.
I currently have a Production View instance with a few hundred users, that is running View 5.3 on vCenter 5.5 U1. We want to do an upgrade to View 6, but I was curious about potentially installing and setting up a completely new View instance (new primary, replica, and composer) with different names and different IPs, that were all running View 6. This would allow us to test out View 6, some new parent desktop images we built, and the newer version of AppSense that we want to start using. If I can have a separate environment where we could do all our testing, then when the time comes we could just tell our users to switch over to using the new one, and simply take down the old.
My question is would there be any issue having two instances of View pointing to the same vCenter server? The connection servers and composer servers would be completely seperate, but they would have to point to the same vCenter server. The new instance would remain quite small as we do our testing, and would only scale up at the point we are ready to move everyone over.
Has anyone done this kind of side-by-side upgrade before, or know of any potential issues?
Thanks.
Hi Daniel,
Thanks for bringing up the issue. The issue is one known issue due to technical limitation of remote client audio. Suggest that you‘d better play one word during playing one piece of light music.