<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wyse on myvirtualcloud.net</title><link>https://myvirtualcloud.net/tags/wyse/</link><description>Recent content in Wyse on myvirtualcloud.net</description><generator>Hugo</generator><language>en-us</language><copyright>Andre Leibovici</copyright><lastBuildDate>Sun, 10 Oct 2010 10:13:00 +0000</lastBuildDate><atom:link href="https://myvirtualcloud.net/tags/wyse/index.xml" rel="self" type="application/rss+xml"/><item><title>50,000-Seat VMware View 4.5 Deployment Reference Architecture</title><link>https://myvirtualcloud.net/50000-seat-vmware-view-4-5-deployment-reference-architecture/</link><pubDate>Sun, 10 Oct 2010 10:13:00 +0000</pubDate><guid>https://myvirtualcloud.net/50000-seat-vmware-view-4-5-deployment-reference-architecture/</guid><description>&lt;p&gt;VMware released a 50,000-Seat VMware View Deployment Reference Architecture in partnership with NetApp, Wyse, Cisco and Fujitsu. The RA posted on NetApp blog originally in August, 2010 has now been made available at VMware website.&lt;/p&gt;&#10;&lt;p&gt;The scenario deploys a 50,000-seat environment on 10 NetApp FAS3170 high-availability (HA) pairs using the Network File System (NFS) protocol. A 20,000-seat deployment and six 5,000-seat regular deployments are used in this scenario.&lt;/p&gt;</description></item><item><title>APAC Virtualization Roundtable (Wyse on thin clients) – Wed 8/9</title><link>https://myvirtualcloud.net/pac-virtualization-roundtable-wyse-on-thin-clients-wed-89/</link><pubDate>Mon, 06 Sep 2010 15:30:00 +0000</pubDate><guid>https://myvirtualcloud.net/pac-virtualization-roundtable-wyse-on-thin-clients-wed-89/</guid><description>&lt;p&gt;Alastair Cooke’s guest this week will be Sora Cho, who is the Director of Technical Services in the APAC region at Wyse.&amp;#160; We will be talking about the what, how and why of thin clients for VMware View and other server based computing solutions. &lt;/p&gt;</description></item></channel></rss>