peterbrown05's Posts

Hi Xingchan It is really interesting to hear your internal webcam on your laptop isn't working. We have tested with a number of built in cameras and they all worked fine. However, we obviously c... See more...
Hi Xingchan It is really interesting to hear your internal webcam on your laptop isn't working. We have tested with a number of built in cameras and they all worked fine. However, we obviously can't test every single laptop camera combination! If you are still having problems, could you grab the client logs for a time when you have tried to use the built in camera and upload them? I'd like to take a look to see if I can spot what is wrong. The log file for the client can be found here: Windows XP C:\Documents and Settings\username\Local Settings\Application Data\VMware\VDM\Logs\ Windows 7 or Windows 8: C:\Users\%username%\AppData\Local\VMware\VDM\Logs\ titled “debug-20XX-XX-XX-XXXXXX.txt” so please reproduce the problem, and grab the latest debug file and send it through if you can. cheers Peter Brown
Hello, I am delighted to inform you that as of Horizon View 5.2 with Feature Pack 2 - View now supports webcams when using Windows clients. Please check out my blog post here that gives more ... See more...
Hello, I am delighted to inform you that as of Horizon View 5.2 with Feature Pack 2 - View now supports webcams when using Windows clients. Please check out my blog post here that gives more information about this: http://blogs.vmware.com/euc/2013/07/3370.html Previously we didn't support webcams because the bandwidth needed to run a webcam is huge and typically this does not scale over a real VDI environment. However the Real-Time Audio-Video functionality as described above works around this limitation. Let me know how you get on! cheers peterB
sure - with the power of virtualization you can do anything! So - a USB device can only be accessed by a SINGLE VM at any time. However if this was a "licence server" vm which has the dongl... See more...
sure - with the power of virtualization you can do anything! So - a USB device can only be accessed by a SINGLE VM at any time. However if this was a "licence server" vm which has the dongle connected, and your other vm's "check out" licences from that server then this should work well. I can't image you are intending that a single usb device is shared between multiple vms... Anyway, its really simple to set up. a 2 step process: Step 1: add a USB Controller to your VM Plugin the USB device that you want to use into the host machine From vSphere client Right-click the virtual machine you want to connect the USB device to and click Edit Settings. Click Add. Click USB Controller and click Next. Click OK. Step 2: add the USB device to the VM Right-click the virtual machine and click Edit Settings. Click Add . Select "USB Device" and click Next Click the desired USB device and click Next. Click OK. now login to your desktop using View, and the usb device should be available for use. This is all independent of View USB redirection which should continue to work as per your configuration. this KB gives more details along with limitations/considerations etc: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022290 hope this works for you, cheers peterB
I'm pleased to say that the Feature Pack 2 and Clients have now been released and are available for download. see:  Download VMware Horizon View 5.2  and Download VMware Horizon View Clients fo... See more...
I'm pleased to say that the Feature Pack 2 and Clients have now been released and are available for download. see:  Download VMware Horizon View 5.2  and Download VMware Horizon View Clients for View cheers peterB
ive sent you a private message with details. can you let us know the URL that the webbrowser is trying to get to when you get the 404? cheers p
also, can you copy paste the URL that the browser is trying to access, and identify if thats a URL pointing at your connection server, or one of the horizon workspace va's? this might help us un... See more...
also, can you copy paste the URL that the browser is trying to access, and identify if thats a URL pointing at your connection server, or one of the horizon workspace va's? this might help us understand what its trying to access and cant...
so if you can grab the logs from Horizon workspace (im not sure which one will be most useful here - so grab the connector, service and gateway logs). and please get the debug log from the view c... See more...
so if you can grab the logs from Horizon workspace (im not sure which one will be most useful here - so grab the connector, service and gateway logs). and please get the debug log from the view connection server. Knowing your user name that is trying to log in would also be helpful (or an approx time when the login failed) will help us find the offending info in the logs a bit quicker. cheers peterB
hi, ok some more questions  - hopefully we can figure this out soon for you; have you installed the VMware-Horizon-View-HTML-Acces component on your connection servers? (its part of the featu... See more...
hi, ok some more questions  - hopefully we can figure this out soon for you; have you installed the VMware-Horizon-View-HTML-Acces component on your connection servers? (its part of the feature pack downloads). This component provides the html access "portal page". I wonder if this is the page that is missing. Have you tried launching view using a native view client? (right click, select launch using pcoip). Can you launch a blast desktop from the portal page without using horizon workspace? When you authenticate with Horizon Workspace, then are you logging into it using your AD credentials? If so, then when it launches view then it can pass your ad credentials (via the magic of SAML) to the desktop and hence SSO you into view - and - your desktop. If you dont authenticate with workspace using AD credentials, then it will still get you into your desktop - but - Microsoft windows will prompt you for your usual ad credentials at its logon screen. for reference, SAML is a mechanism that allows View to "trust" horizon workspace, and it will authenticate the user with view. As mentioned above, if horizon workspace knows your AD credentials then it will permit the SSO into your desktop. Let me know about the above, and hopefully we can get your issue resolved asap, cheers peterB
so let's check a few basics first... (I dont think this will solve it based on your comments, but lets start here...) in view, under each connection server, have you configured the SAML Authen... See more...
so let's check a few basics first... (I dont think this will solve it based on your comments, but lets start here...) in view, under each connection server, have you configured the SAML Authenticator? and does that point at your horizon gateway? - on the View Admin Dashboard, the Saml Authenticator health should be showing a Green light. In Horizon Connector, under the View Pools tab, you should have configured the first connection server. (I am sure this bit is done since you say the desktop icons show in your workspace). However, for each of the connection servers listed, have you Accepted the certificates? and, most importantly, having Accepted the certs, you need to click save to ensure they are saved down to Horizon. If in doubt, please just go back and re-accept those certs and click save again. Note that you should be able to set SAML as "allowed", which means that launching view should work from the native client directly, AND also from the horizon workspace. Setting to required, means that you can only launch view from horizon workspace. Further analysis of the problem, then getting a copy of the debug log file from the connection server(s) would be most useful. cheers peterB
we have published a KB detailing this issue and its workaround; see http://kb.vmware.com/kb/2051801
Thanks for the update Geoff. Glad the workaround worked. We are trying to reproduce the problem, but many attempts to do so have always worked. We will keep trying to repro and find root cause. ... See more...
Thanks for the update Geoff. Glad the workaround worked. We are trying to reproduce the problem, but many attempts to do so have always worked. We will keep trying to repro and find root cause. Anyway, I'm glad method2 worked for you, cheers peterB
thanks for the update Geoff. and glad we are on the same page ref agent/client as I would have been very confused if the problem was fixed by reinstalling the client/ =D let me know how you get ... See more...
thanks for the update Geoff. and glad we are on the same page ref agent/client as I would have been very confused if the problem was fixed by reinstalling the client/ =D let me know how you get on tomorrow, cheers peterB
Hi Geoff we have seen some people with similar issues. We believe there may be a problem when the upgrade is done from an earlier version of View. In your original post you mention: "if I rei... See more...
Hi Geoff we have seen some people with similar issues. We believe there may be a problem when the upgrade is done from an earlier version of View. In your original post you mention: "if I reinstall or repair the View Client after running sysprep it's fixed". Did you mean reinstall/repair the agent rather than the client? The problems we have been investigating have all been caused by agent side issues rather than client problems. Wondering if you could try something to see if this resolves the problem. After getting your agent to the required version of view, but before performing the sysPrep operation. Please first confirm that the agent works for USB redirection. In order to solve the problem you are facing there are one of 2 possible ways to achieve this. One way works for some people, and another works for others. Would appreciate any feedback on your findings. prior to doing the sysPrep but having confirmed USB redirection is working; Method 1: (not works for some people, not all) 1. go into Device Manager, and delete the "VMWare View Virtual USB Hub" device. 2. right click in device manager, and scan for hardware changes. This should re-install the latest version of the vhub driver. 3. reboot the agent Now check if USB is still working, and then try your sysPrep as before. Method 2: (again prior to doing the sysPrep operation) 1. search the machine for "vmwvhub.sys". There will be several versions found, including in C:\Windows\System32\drivers\ and c:\Windows\System32\DriverStore\FileRepository. The version saved in C:\Program Files\VMware\VMware View\Agent\bin\drivers\should be the latest version for your agent install. (probably 5.5.0 xxxx) 2. delete instances of these files that have a version other than the latest of 5.5.0 build-949580. The older View drivers will probably shows a version of 5.1.0 build-668184. 3. now reboot, and confirm USB still functions. The driver loaded in device manager should be shown a 5.5.0. Now try the sysPrep operation. Let me know if one or other of these works for you, Kind Regards Peter Brown