Rodos's Posts

As various people have mentioned there are ways to re-purpose the existing machines. One option that has not been mentioned is the hardware refit. Some vendors have migration kits to transfor... See more...
As various people have mentioned there are ways to re-purpose the existing machines. One option that has not been mentioned is the hardware refit. Some vendors have migration kits to transform the PC into a client. For example the PC to TC Conversion Card from IGEL. The principal or argument behind these is management cost. Its all good to convert the existing machines but what about moving forward. When you have a new employee do you by another PC or a new thin client. Now you are maintaining two sets of TC, the old re-purposed ones and the new terminals. The argument is when you can turn those existing machines into the same device from a functionality and management view point as your new terminals there are savings to be had. After all its the maintenance and management costs which are major drivers for people to move to VDI. Just a thought. Considering awarding points if this is of use
To get the poor mans VDI here are some tips. Read the Wyse Admin guide, not that is very clear. Read the section "Understanding User Accounts and User Profile Ini Files". You need SignOn=NT... See more...
To get the poor mans VDI here are some tips. Read the Wyse Admin guide, not that is very clear. Read the section "Understanding User Accounts and User Profile Ini Files". You need SignOn=NTLM and DomainList=yourdomain in your global wnos.ini file. In the individual user ini files put a connection string which goes to their hostname/ip address and any other connection string settings you want. Once you have it all done when the terminal boots it will give the username, password and domain prompt. The domain should already be filled in with yourdomain. User enters details and hits enter. the terminal validates the username and password as correct and then pulls the username.ini file of the FTP server and launches the connection string you have in their ini file. You have to put the $UN and $PW variable into the connection string so the single sign on works, that way you don't have to embed them into the ini file and it takes them from the user. That might be enough to get you going. I have some detailed docs at work if you get stuck. It can be a pain to get going but once done works well. Again great for a small number of users and pilots, anything bigger start thinking broker. Keep us informed of your progress and lets get the current wiki fleshed out over the next few days. Rodos Considering awarding points if this is of use
Rodos, Wyse Device Manager is it worth using on the VC1 2.5 server?? I figured for now we can just configure each V10L with the users RDP to his vm? What do you think? My preference for... See more...
Rodos, Wyse Device Manager is it worth using on the VC1 2.5 server?? I figured for now we can just configure each V10L with the users RDP to his vm? What do you think? My preference for "poor mans VDI " with the V10L is to use the NTLM authentication and a config file for each user with their machine name which gets set from DNS. That way you have single sign on, integration with AD and you just script or cut and paste the config file for each user, all you have to change is the filename and the hostname within it. Of course with no broker you don't get all those nice features and it does not scale well but hey it works great for small numbers of seats. But once you use a broker you won't want to go back (says Rodos working at home on my mac via the secure VDM gateway to my personal XP machine in the data center in the office!). Considering awarding points if this is of use
>Here's my thing the TCX USB Virtualizer does that need to be installed on the VC1 2.5 server or does that need to be installed on each vm and does the same apply to the Mulit-Display? It jus... See more...
>Here's my thing the TCX USB Virtualizer does that need to be installed on the VC1 2.5 server or does that need to be installed on each vm and does the same apply to the Mulit-Display? It just seems confusing. It has to go into each VM. VC is not involved, or even the broker, its the terminal talking to the OS inside the guest. Considering awarding points if this is of use
Answered previous post in original thread. Rodos
Okay I created a wiki for some documentation. I fleshed out an outline. I will grab my documentation and start to flesh it out over the next few days. Its an open Wiki for the community to put... See more...
Okay I created a wiki for some documentation. I fleshed out an outline. I will grab my documentation and start to flesh it out over the next few days. Its an open Wiki for the community to put content into as well. Rodos Considering awarding points if this is of use
This document describes the process of configuring a Wyse V10L to work with TCX. This is an open Wiki for the community to evolve and improve. What is TCX TCX are enrichment extensions t... See more...
This document describes the process of configuring a Wyse V10L to work with TCX. This is an open Wiki for the community to evolve and improve. What is TCX TCX are enrichment extensions to allow additional features to your remote sessions. There are currently three extensions and more planned. Multimedia - TCX Multimedia is a software layer on the server that intelligently redirects the multimedia processing tasks dynamically between the client and server. The multimedia stream decodes locally on the client using the local processing power of the device thereby providing complete multimedia playback capabilities overcoming any limitations that are inherent in traditional thin computing architectures. USB Virtualisation - Enables the sharing and discovery of local USB devices as if they were connected directly on the Virtualized Desktop environment. Solves the USB peripheral issues when it comes to deploying thin clients. No more compromise on limited local drivers. The Wyse thin clients now can seamlessly access their USB-based printers, scanners, storage devices, Palm, BlackBerry, and Pocket PC hand­helds over VDI environment. What do I need? You will need : a terminal, a license key for the component of TCX you are enabling (either multi-media or USB redirection) the Wyse software for the virtual machine an FTP server to place the config files a DHCP server to place some options string in Step 1 - Get your V10L working and pulling its config off the central FTP servers wnos.ini file. An example entry into your wnos.ini file. SignOn=yes autoload=1 EnableKeyboardMouseSettings=no SessionConfig=ALL MapDisks=yes DomainList=YOURDOMAIN VDIBroker=https://192.168.1.100/ Timeserver=192.168.12.40 TimeZone='GMT + 10:00' ManualOverride=yes Daylight=yes Start=100107 End=040107 TimeZoneName="AUS Eastern Standard Time" DayLightName="AUS Eastern Daylight Time" Language=Au Step 2 - Add the settings for TCX to your wnos.ini file Put your license code for TCX into the wnos.ini file. If you have multiple separate by a comma. TCXLicense=AAAAA-BBBBB-CCCCC-DDDDD-EEEEE,FFFFF-GGGGG-HHHHH-IIIII-JJJJJ Step 3 - Install the Wyse software into your VM Get the latest extensions from the Wyse website. You then need to install them inside the virtual machine that the terminals will be connected to. You are going to want to make them part of your SOE or template which drives your pools. Step 4 - Test Now you can do your testing to make sure it all works. For multimedia you just need to play video of a supported format. Try it full screen and see if the sound is in sync. You can also look on the log file in your client and you will see an entry showing that decoding has started. Another way to see if video is working if you have dual screens is sit the video across the two screens, you will see that only half the video plays, depending which screen has the greater view of the video. A current limitation is spanning two monitors. To test the USB attach a simple USB device such as a storage device. Again you should see the entries on the clients log showing a new device has been inserted. You virtual machine should report new hardware detected and load the driver or the device will just start working. It does not work. What now? If USB is not working you may need to set the terminal to map through the USB device. Put an entry of "unmapusb=no" into your wnos.ini file. Further reading and helpful links The ThinOS Admin guide has the details of the configuration options, especially for the important ones for the wnos.ini file. The next thing your will want to do is get it working with VDM, see Using the Wyse V10L and S10 Thin Clients with VDM.
Okay, here is a summary, maybe we should create a Wiki document for this, umm more hours in the day. 1. Get your V10L working and pulling its config off the central FTP servers wnos.ini file. ... See more...
Okay, here is a summary, maybe we should create a Wiki document for this, umm more hours in the day. 1. Get your V10L working and pulling its config off the central FTP servers wnos.ini file. 2. Update the wnos.ini file with the IP address of your time, as the license will not work without one. Timeserver=yourtimeserver 3. Put the TCX license codes into the wnos.ini file with a comma between each one. TCXLicense=a-b-c-d-e,a-b-c-d-f 4. Install the Wyse software into your VM 5. Test and enjoy. For each of these there are obviously a few details behind each one. When testing look at the log messages on the terminal and in windows. If you have troubles with the USB redirection ensure the USB is enable which can be done through the connection manager or the undocumented (well it was when I had to figure it out) unmapusb=no setting in the ini file. Cheers, Rodos Considering awarding points if this is of use
The V10L runs Wyse Thin OS so you can't add apps to the thin client like you can with other models which run an embeded OS such as XPe. Considering awarding points if this is of use
The processing is done at the server for the desktop. However there are a few edge cases. If you are using any of the TCX extensions such as the multimedia the actual client will be decoding and ... See more...
The processing is done at the server for the desktop. However there are a few edge cases. If you are using any of the TCX extensions such as the multimedia the actual client will be decoding and playing the video stream, so in this case "some" processing does occur on the client. Also USB redirection will require a small amount of local processing. You are correct, you don't need a high end client. However to do want to ensure that there is enough resource to do whats required today and into the future. Remember the lifetime of a terminal is going to be longer hopefully that a PC and you want to be sure it can take the latest firmware for a while. Hope that helps. Rod Considering awarding points if this is of use
For the single image you want to look at and prepare for the SVI (Scalable Virtual Image) which was presented at the last VMworld. The other thing would be load balancing. If you don't have sh... See more...
For the single image you want to look at and prepare for the SVI (Scalable Virtual Image) which was presented at the last VMworld. The other thing would be load balancing. If you don't have shared storage you can't run DRS. How many desktops are you thinking of running in the pool. Are you going to have to run a pool per host? Its not really going to balance the load well so you may need to oversize it or not have the performance you might otherwise have. Are there some other creative ways you might be able to provide some shared storage? Certainly something to consider in your larger design. Considering awarding points if this is of use
Not sure for the V90L, thats the XPe box. Know all the details for the V10L which is ThinOS. You will certainly require the license key. You can get trial keys from your Wyse partner. If yo... See more...
Not sure for the V90L, thats the XPe box. Know all the details for the V10L which is ThinOS. You will certainly require the license key. You can get trial keys from your Wyse partner. If you don't get any luck I can find out what the scoop is with the V90L. Considering awarding points if this is of use
No I don't think VMware VDI is going to be left behind. There a number of factors here. First is the platform for hosting all of those Virtual Machines. What technology are you going to implem... See more...
No I don't think VMware VDI is going to be left behind. There a number of factors here. First is the platform for hosting all of those Virtual Machines. What technology are you going to implement to host 1000 desktops? At the moment ESX is proven and tested, rock solid. That is not the case with the competitors. This lead is enhanced when you consider that many environments will be a mix of Server and VDI machines, and again VMware has the lead in that area and will for quite some time. Multimedia. A lot of the development work is being done, but its not released. You can use Wyse TCX or RGS today with VMware. A lot of these technologies in development are platform independent so if Microsoft improve RDP, as long as the clients are updated, everyone benefits. VMware should be able to consume the benefits in the client arena like everyone else will. The biggest threat here is Citrix and them being able put the ICA stack right on the VM, lets see how they license it. My biggest bug bear with VMware VDI is the thin provisioning of the VMs. You can play around with the Netapp techniques but it should be built into the product. VMware have previewed the now renamed Scalable Image Management Sept '07 but its still not coming for a while, and this is going to hurt adoption. It can be worked around but it would be great to have it now. Considering awarding points if this is of use
Also note that webcams are not supported under the Wyse TCX as yet. I have not tested one either.
Which thin clients are you using and what software? Are you using Wyse TCX, the VDM2 client or a USB/Ethernet device? Considering awarding points if this is of use
Contact Wyse or a reseller. Where did you get your terminal from? AFAIK its not available for download but as you need a trail license code you need to contact them anyway. Sounds like a pain but... See more...
Contact Wyse or a reseller. Where did you get your terminal from? AFAIK its not available for download but as you need a trail license code you need to contact them anyway. Sounds like a pain but as it only works with the hardware device which you need to have too its not really a barrier. If you can't get hold of anyone or have trouble let me know and I will pass on through my contacts. Considering awarding points if this is of use
Sorry for so many posts. The details are on the US website, not the Australian one. Us Australians are a little behind. http://www.wyse.com/products/software/tcx/index.asp The datasheet ... See more...
Sorry for so many posts. The details are on the US website, not the Australian one. Us Australians are a little behind. http://www.wyse.com/products/software/tcx/index.asp The datasheet for the USB is at http://www.wyse.com/products/software/tcx/Wyse_TCX_USB_Virtualizer.pdf Also note that the datasheet specifically states that "USB to Serial Converter" are tested and working.
Being CE rather than WTOS its most likely going to be on a different release track. If you look at the datasheet for the V10L it mentions support for VDI brokers already however for the V30L i... See more...
Being CE rather than WTOS its most likely going to be on a different release track. If you look at the datasheet for the V10L it mentions support for VDI brokers already however for the V30L it has not mention. So it does not bode well for VDM2. If it was the V90L you could load the VDM2 client on. So I will bet no at this stage. I did drop a message to my Wyse SE though just in case. Considering awarding points if this is of use
Correct, its only just been released but it has been in Beta for a while. Don't know why they have not updated their web site yet. Your Wyse reseller should have details about it. The cool thi... See more...
Correct, its only just been released but it has been in Beta for a while. Don't know why they have not updated their web site yet. Your Wyse reseller should have details about it. The cool thing is you don't need to add any drivers into the terminal, like you would if you were to use a XPe device. I have a serial to USB cable. I might give it a try next week of a V10L with my GPS.
The Wyse V10L are a great client and with the TCX extension you can use the USB. Not sure about the serial port though. What do you want to use that for? You could always use a Serial to USB c... See more...
The Wyse V10L are a great client and with the TCX extension you can use the USB. Not sure about the serial port though. What do you want to use that for? You could always use a Serial to USB converter cable. With some testing that might give you a good simple solution. They are a great terminal, simple to manage and don't run XPe or CE. Considering awarding points if this is of use