scnguye2's Posts

Just uploaded PCoIP Zero Client firmware 3.1.1, downloaded from Wyse P20 support page to my NC240, here are the results: RDP connection to Windows 7 VM works! PCoIP connection to Windows 7 ... See more...
Just uploaded PCoIP Zero Client firmware 3.1.1, downloaded from Wyse P20 support page to my NC240, here are the results: RDP connection to Windows 7 VM works! PCoIP connection to Windows 7 does NOT work (anymore). It used to work with firmware 3.0, but only after the screen flickers several times, then the screen will stabilize. Multi-monitor display does NOT work with RDP or PCoIP. I have a second 22" monitor connected to the NC240 DVI-in port. I am able to get dual display on XP VM via PCoIP. Has anyone gotten multi-display to work with Windows 7 VM on the NC240?
Hello all, I would like to know all of the (REQUIRED) port # that I need to open in order to use PCoIP with a NAC-port i.e. HTTPS = 443 RDP = 3389 UDP = ??? Thank you, Sang
Hello all, My Samsung NC-240 is set to connect to my VMware View Connection Manager server. I can connect to any of my WinXP virtual desktop via PCoIP or RDP just fine, but I cannot connect to... See more...
Hello all, My Samsung NC-240 is set to connect to my VMware View Connection Manager server. I can connect to any of my WinXP virtual desktop via PCoIP or RDP just fine, but I cannot connect to my Windows 7 virtual desktop. Each time I try to connect, it will error out and say "Session Lost!" Looking at the NC-240 Event Log, I see the following: 11d,00:01:09.260> Ready to connect with host 11d,00:01:21.990> Connecting with host (10.3.70.110, 00-00-00-00-00-00) 11d,00:01:22.020> Using resolution 1920 x 1080 at 60 Hz on DVI port 0 11d,00:01:22.150> CONNECTED (10.3.70.110, 00-00-00-00-00-00) 11d,00:01:22.160> Setting host power state to: S0 11d,00:01:22.960> SESSION ACTIVE 11d,00:01:23.600> (MGMT_RDP): Invalid capability length (20) 11d,00:01:23.600> Connection dropped (detected RDP protocol error) 11d,00:01:23.680> Session lost! 11d,00:01:23.680> (MGMT_RDP): INIT: Received unrecognized event 0x20! Here is the current version info of my NC-240: Firmware Part Number: FW010034 Hardware Version: Firmware Version: 3.0 Firmware Build ID: v250 Firmware Build Date: Dec 7 2009 15:55:15 PCoIP Processor Revision: 1.0 Bootloader Version: 2.1 Bootloader Build ID: v163 Bootloader Build Date: Aug 28 2008 16:56:13 Here is the current version info of my VMware View VCM and Agent: VMware View 4.0.0-210939 I appreciate any input. Thanks, Sang
Thanks everyone for your feedback/advice. I logged in to the NC240 via the web management interface and checked the USB permission. And yes, by default it is set to allow any device. I also check... See more...
Thanks everyone for your feedback/advice. I logged in to the NC240 via the web management interface and checked the USB permission. And yes, by default it is set to allow any device. I also checked the "Attached Device" tab and saw that NC240 did recognized the USB flash drive that I plugged in. So I logged off my current PCoIP session, plugged in the USB flash drive, then logged in again, and this time the drive showed up. Now when I switched from PCoIP to RDP, the USB drive would not show up. I believe this is because I have a an OU where I put all of my virtual desktop in, and it has a GPO that disable "Allow local drive mapping". I will eventually setup another VM without applying the OU GPO to see if my USB drive will show up in an RDP session. I guess the "Allow local drive mapping" setting does not apply if you are using PCoIP, since it is intended for Terminal Server. I could be wrong...
Hello all. I recently purchased the Samsung NC240 Monitor/PCoIP Thin-Client. It has several USB ports, but when I insert a USB flash drive into one and connect to my virtual desktop via the View ... See more...
Hello all. I recently purchased the Samsung NC240 Monitor/PCoIP Thin-Client. It has several USB ports, but when I insert a USB flash drive into one and connect to my virtual desktop via the View Connection Manager, using PCoIP protocol, the USB drive does not show up on my virtual desktop. I have called Samsung Tech Support, but they are not familiar with VMware View at all and cannot address my issue. I verified that USB re-direction worked on my virtual desktop by using the View Client with USB re-direction enabled. Using the View Client, I can mount the USB drive via PCoIP or RDP session. On my virtual desktop, I have a GPO to disable local drive mapping, but that is so that if I access my virtual desktop from a PC client, the local C: and will not show up in My Computer. I am hoping someone has an NC240 and can test the USB re-direction with VMware View and let me know. On a side note, other than the USB re-direction issue, this particular model of NC240 that I was able to purchase did not come with internal speakers. Unfortunately the box and manual did not specify whether or not it had speakers. Not that I am fan of internal speakers, but it would be nice to have, since this product is market as an all-in-one solution. Overall, I am pleased with its performance and ease of use/administration. Hopefully Samsung will produce more of these because stock is limited.
Hello all, Is anyone using a complete App Virtualization Solution other than ThinApp? I have heard of the following: Symantec Endpoint Virtualization Suite (formerly SVS) Microsoft App-V... See more...
Hello all, Is anyone using a complete App Virtualization Solution other than ThinApp? I have heard of the following: Symantec Endpoint Virtualization Suite (formerly SVS) Microsoft App-V Virtual Storm (DVS4VDI by Dinamiqs) I would like to deploy virtualized app through streaming, but I am particularly concern with network bandwidth saturation, specifically when multiple users are accessing the same share. I got on a WebEx demo with Virtual Storm and they basically told me that with their product, I would be able to reduce the base virtual desktop image to 1.2GB in size, because quote "With the DVS4VDI add-on Symantec Workspace Virtualization will be reading the applications form a centralized disk. So instead of having a FSLRDR directory on every image we share this with all the images." This essentially means that virtualized apps are streamed via SAN protocol and not over the network. Very cool concept! Does anyone have any experience with using DVS4VDI? I suppose then Symantec SVS will only stream apps over network. If I am to use VMware ThinApp, what is a good software management product, that I can use in conjunction with ThinApp, to deploy and manage all the virtualized apps?(i.e. Microsoft, Altiris, etc...) Thanks, Sang
Solution: After submitting a support case with Wyse Tech Support, this is what I have to do on the Wyse V10L in order to connect... 1. Export certificate (.cer) from Internet Explorer... See more...
Solution: After submitting a support case with Wyse Tech Support, this is what I have to do on the Wyse V10L in order to connect... 1. Export certificate (.cer) from Internet Explorer 2. Change .cer extension to .crt and create a folder called "CACERTS" in the Wyse FTP "wnos" folder 3. Copy .crt certificate to the CACERTS folder 4. Add the following line to the wnos.ini file: Connectionbroker=VDM addcertificate=filename.crt 5. Wyse Tech Support discovered that the only V10L system version, compatible with VMware View Connection Manager 3.1 using SSL is 6.2.0_08 6. Replace your current VL10_wnos file with the correct 6.2.0_08 VL10_wnos 7. Reboot and wait for the V10L to flash itself 8. You should now be able to connect Comment(s): - Down-grading to 6.2.0_08 may affect some advanced functions, such as SmartCard Auth., VOIP, etc... - I have attached a copy for the 6.2.0_08 with this thread - See all above threads for instruction on configuring View Connection Manager to use your existing SSL Certificates
Yes. The article was helpful in setting up the View Connection Manager server to use my existing certificate. However, I am having trouble getting the Wyse V10L running WTOS to connect to... See more...
Yes. The article was helpful in setting up the View Connection Manager server to use my existing certificate. However, I am having trouble getting the Wyse V10L running WTOS to connect to the View Connection Manager server, after the certificate change and the service restart. This is what I have in the Wyse FTP folder: 1. V10L_wnos file (version 6.4.0_06) 2. CACERTS folder with the extracted .cer (renamed with .crt extension) certificate from Internet Explorer 3. This is what my wnos.ini file looks like: Connectionbroker=VDM VDIBroker=https://(name of connection broker goes here) AdminMode=yes Admin-Username=MEAFMNABMK Admin-Password=MEAFMNABMK Privilege=none ShowDisplaySettings=no EnableKeyboardMouseSettings=no MaxVNCD=2 VncPrompt=no Accept=2 FormURL=logo.jpg addcertificate=keys.crt Timeserver=time.windows.com timeformat="12-hour format" Dateformat=mm/dd/yyyy TimeZone='GMT - 06:00' daylight=yes start=030207 end=110107 TimeZoneName="Central Standard Time" DayLightName="Central Daylight Time" autoload=1 Not sure what I am missing, but the V10L will not authenticate to the connection broker. The certificate shows that it has been installed.. No problem with time server or connecting to the connection broker, but when I put in my username/password, it acts like it's trying to load the profile, then stops and the nothing shows up on the Wyse event_log.
Hello all, I purchased a certificate from Starfield Inc. and would like to use it on my View Connection Manager server. I tried the following: 1. Copy the "locked.properties" file and... See more...
Hello all, I purchased a certificate from Starfield Inc. and would like to use it on my View Connection Manager server. I tried the following: 1. Copy the "locked.properties" file and the certificate "name.p12" from my View Security Server, to the View Connection Manager under "C:\Program Files\VMware\VMware View\Server\sslgateway\conf" 2. Edit the "locked.properties" with the following parameter: keyfile="name".p12 keypass="password" 3. Restart the "VMware View Connection Server" service Note sure if this is the correct method. Please provide me with instruction on how to configure the server to use my existing certificate. Also, if I am using Wyse V10L thin-client running WTOS, how do I set the V10L to use the certificate? Thank you, Sang
I want to a question regarding the HP RGS protocol. Last week I attended VMWare Partner Exchange 2009 in Orlando, FL, and was given a demonstration of what I believe was the option to select ei... See more...
I want to a question regarding the HP RGS protocol. Last week I attended VMWare Partner Exchange 2009 in Orlando, FL, and was given a demonstration of what I believe was the option to select either MS RDP or RGS within the View Client. I forgot to ask what version of the View Client the instructor was using, and if it was even available for download right now. So I would like some clarification. Does the current version of both the View Agent and Client have integrated support for the RGS Protocol? VMware-viewagent-3.0.1-142034.exe VMware-viewclient-3.0.1-142034.exe Because I believe without integrating with the View Agent and Client, there is no point in using the View Connection Manager "Entitlement" function, because one can just load the RGS Receiver client on any PC and connect to a virtual desktop with the RGS Sender installed. Any feedback is appreciated.
I have a customer who is planning to deploy VMWare View. They want to backup every single virtual desktop they create. They will be using the automated persistent-pool. My question is, if I dep... See more...
I have a customer who is planning to deploy VMWare View. They want to backup every single virtual desktop they create. They will be using the automated persistent-pool. My question is, if I deploy linked-clone, what should I backup, the linked-clone's source and replica, or parent vm. I guess I should just perform file level backup to preserve user data, instead of a full image backup of the virtual desktop. I don't think vRanger Pro is capable of just regular file level backup, so I will need something like TSM or NetBackup. Is that correct? Also, how should I go about backing up the user profile drive, if I choose the option to keep it on a separate drive, during the virtual desktop pool deployment?
Hello all, I would like to know what is the best method to backup the linked-clone virtual desktop on VMWare View. At the moment, I am using the latest version of vRanger Pro with VCB inte... See more...
Hello all, I would like to know what is the best method to backup the linked-clone virtual desktop on VMWare View. At the moment, I am using the latest version of vRanger Pro with VCB intergration. I am not sure if I should backup the linked-clone itself or the parent VM. What about the parent snapshot? Please advice. Thanks. Sang
Hello, Everytime a linked-clone is created, a replica and source VMs are also created. VC automatically assigns a different unique name to each replica and source VM. I would li... See more...
Hello, Everytime a linked-clone is created, a replica and source VMs are also created. VC automatically assigns a different unique name to each replica and source VM. I would like to know if it is possible to renamed the replica and source VM without causing any disruption to the linked-clone. Thanks, Sang
Hi Troy. I believe it is a bug. I did not deploy VM from the broker. I actually went through the painful process of "Add New Virtual Machine", to make a new virtual desktop. A... See more...
Hi Troy. I believe it is a bug. I did not deploy VM from the broker. I actually went through the painful process of "Add New Virtual Machine", to make a new virtual desktop. After installing the VDM Agent, I would then add the virtual desktop to the VDM Connection Broker, and entitle it to a user. It is here that I am unable to connect to the newly added virtual desktop, unless I login as local administrator, restart the VDM Agent service, logout, and restart the virtual dekstop. Then when I attempt to reconnect, via Wyse V10L terminal or VDM client from a workstation, it works. Seems to me like the VDM Agent service needs to be restarted every so often, in order to reconnect.
Hello all, I want to ask a question regarding intermittent VDM connection error. In particular, the error message below: "The desktop has failed to open. This desktop is currently not... See more...
Hello all, I want to ask a question regarding intermittent VDM connection error. In particular, the error message below: "The desktop has failed to open. This desktop is currently not available. Please try connecting to this desktop again later or contact your administrator" I intermittently get this error message, when adding a new virtual desktop to the VDM Connection Broker Server, and entitling a new user to it. One method that I use to fix the connection issue, is to login locally to the virtual desktop, launch "services.msc" from Run, then restart the VMWare VDM Agent service, and logoff. After doing this, I can access the virtual desktop. I have tested with both the VDM Client 2.1 on a workstation and Wyse V10L Thin-Client terminal running the lastest BIOS. If the VDM Client cannot connect, the Wyse V10L will not connect either, and vice-versa. This is my current VMWare Infrastructure: (1) ESX 3.5.0 build 98103 host with all baseline updates (1) Virtual Center 2.5.0 build 84767 (1) VDM Connection Broker 2.1.0 build 596 (1) Virtual desktop runing WinXP Pro w/ VDM Agent 2.1 & VMWare Tools - static IP Are there any patches, fixes, or tweaks, that I can run to stabilize the connection broker server for a solid connection every time? I read on another discussion that the issue maybe DNS related, and someone suggest turning on DHCP, but specify the DNS server manually. Could it be that the connection broker server connection to the DNS server timeout after a while, or there is a refresh delay, after adding new virtual desktop to the connection broker? Thx for reading...
To all, I would like to know, how many virtual desktops can a single VDM Connection Broker Server manage, before another connection broker server needs to be added for load balancing? Tha... See more...
To all, I would like to know, how many virtual desktops can a single VDM Connection Broker Server manage, before another connection broker server needs to be added for load balancing? Thanks. Sang
Problem SOLVED!!! I disabled the drive mapping, by accessing gpedit.msc on the virtual desktop, and enabled the Do not allow drive redirection. Here is the complete procedure: ... See more...
Problem SOLVED!!! I disabled the drive mapping, by accessing gpedit.msc on the virtual desktop, and enabled the Do not allow drive redirection. Here is the complete procedure: - Login to virtual desktop - Start -> Run -> type gpedit.msc - In Computer Configuration, Administrative Templates, Windows Components, Terminal Services, Client/Server data redirection - Enable Do not allow drive redirection - Start -> Run -> type cmd - Type gpupdate, to refresh the changes - Logout and log back in You can also create an OU in Active Directory, move all virtual desktop into the OU, create a domain group policy, and link it to the OU to apply this change across all virtual desktops. Hope this will help anyone who's interested in disabling auto drive mapping. Sang
I went and edit the following key on my machine (laptop) registry: Windows Registry Editor Version 5.00 "fAutoClientDrives"=dword:00000000 The value was set to 0 to disable aut... See more...
I went and edit the following key on my machine (laptop) registry: Windows Registry Editor Version 5.00 "fAutoClientDrives"=dword:00000000 The value was set to 0 to disable autoclientdrives. It still did not work. Could it that the VDM custom policy is overriding the existing local machine policy?
I am sorry but I am confused. The custom policy file is only available on the VDM Server. Please provide instruction on how I can point the policy to my local machine (my laptop). Th... See more...
I am sorry but I am confused. The custom policy file is only available on the VDM Server. Please provide instruction on how I can point the policy to my local machine (my laptop). Thanks.
I modified the custom policy on the actual VDM server, not the local machine (my laptop) that I use to connect to the virtual desktop.