I have an article on using one Web Interface site with multiple XenApp farms.
http://carlwebster.com/using-one-citrix-web-interface-site-with-multiple-xenapp-farms-3/ You can do this to migrate users to the new 6.5 farm while they are still using the 4.0 farm. It is totally transparent to your users. As I show in the article, you can even have test users who are using both farms for TAT and UAT. Did you get the 2 for 1 trade up on the XA/XD licenses? A XenDesktop license gives you the right to use XenApp. IMNSHO, Citrix does this to say we sold another 75 XenDesktop licenses today so we now have (Previous XD User Count) + 75 XenDesktop users even though very few actually use XD. Sorry, I don't know anything about pricing. The next version of XenApp will use the same infrastructure as XenDesktop. IOW, IMA is going away. IMA is the bottleneck in scalability of XenApp farms. That has been greatly improved with 6.5. Even for 75 users, I would recommend a dedicated Zone Data Collector/XML Broker, a dedicated Web Interface server and three Session-host only servers. Let me know if you need any additional info. Thanks Carl Webster Consultant and Citrix Technology Professional http://www.CarlWebster.com<http://www.carlwebster.com/> From: David Mazzaccaro [mailto:[email protected]] Subject: RE: moving to virtual Thx for the reply. Currently 75 Citrix users on 3 PS4.0 servers +1 web interface server. Typical published apps (Office, Adobe reader, IE, my docs) I guess not technically migrating... the plan would be to create a new farm, and move users from old farm to new. XenDesktop Enterprise - I was told that gives up XenApp for now and we will have the ability to move to xendesktop in the future. IIRC, it was $72 more per user than XenApp Enterprise. Is this correct? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
