That has been our issue with x64. We have been able to get all of our old crappy 32bit apps running(I agree not all will) but the vendor support issue is a major sticking point with management. This keeps us from being able to deploy this solution. ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Cannon Sent: Saturday, September 05, 2009 1:56 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Memory recommendations Not all of them do...Some older apps such as those in the healthcare industry do not or you have to upgrade to the latest and greatest version which also means money.....Also you have to consider vendor support - there are still lots of vendors out there that will not support their app on a 64 BIT platform even if it does seem to run just fine.... From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Reese Sent: Saturday, September 05, 2009 10:21 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Memory recommendations 32bit apps run just fine on x64 servers and operating systems. On Sep 5, 2009, at 9:46 AM, "Jim Cannon" <Mach1-70@xxxxxxxxx<mailto:Mach1-70@xxxxxxxxx>> wrote: Also I am sure you already know this but R2 is only available as X64 so all your apps, printers, etc need to be 64 BIT Server compatible as well.... From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Friday, September 04, 2009 10:02 AM To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Memory recommendations You'll have to wait until the release after that. Feature Pack 2 does not support R2 either. R2 support is coming tho. Joe From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Carl Stalhood Sent: Friday, September 04, 2009 6:33 AM To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Memory recommendations FYI, XenApp 5 does not work on R2. You'll have to use R1 or wait for the next XenApp. On Thu, Sep 3, 2009 at 6:48 PM, Christopher Wilson <christofire@xxxxxxxxx<mailto:christofire@xxxxxxxxx>> wrote: Awesome. Thanks guys. On Thu, Sep 3, 2009 at 5:32 PM, Foster, Bill <Bill.Foster@xxxxxxxxxxxx<mailto:Bill.Foster@xxxxxxxxxxxx>> wrote: Same here. We use C Class 460c's and for around the last year we have been ordering them with 16gb. Bill Foster Sr. Systems Engineer, IT Infrastructure WellCare Health Plans, Inc. 8735 Henderson Road Ren1, 1st Floor Tampa, Florida 34609 Office: 813-290-6200 ext 1158 bill.foster@xxxxxxxxxxxx<mailto:bill.foster@xxxxxxxxxxxx> From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf Of Doug Rooney Sent: Thursday, September 03, 2009 6:14 PM To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Memory recommendations My last server I got 16GB and that is now my new starting point going forward. Thank You ~Doug Rooney Sonoma Tilemakers IT Manager 7750 Bell Rd. Windsor Ca, 95492 (707) 837-8177 X211 (707) 837-9472 FAX it@xxxxxxxxxxxxxxxxxxxx<mailto:it@xxxxxxxxxxxxxxxxxxxx> From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf Of Wilson, Christopher Sent: Thursday, September 03, 2009 2:59 PM To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Memory recommendations Hey, server hardware fans. I'm ordering some new BL460 blades from HP. Plan to use them for a Windows 2008 R2 + XenApp 5 proof of concept. Windows 2008 can handle more memory - how much more are you guys throwing at these puppies? I realize it's a very general question, and I plan to do some load testing in the POC. But do you have any recommendations for a starting point - 8GB, 16GB, etc? As always, thanks for your sage Thin List advice. Regards, CW Privacy Notice: This electronic mail message, and any attachments, are confidential and are intended for the exclusive use of the addressee(s) and may contain information that is proprietary and that may be Individually Identifiable or Protected Health Information under HIPAA. If you are not the intended recipient, please immediately contact the sender by telephone, or by email, and destroy all copies of this message. If you are a regular recipient of our electronic mail, please notify us promptly if you change your email address. Privacy Notice: This electronic mail message, and any attachments, are confidential and are intended for the exclusive use of the addressee(s) and may contain information that is proprietary and that may be Individually Identifiable or Protected Health Information under HIPAA. If you are not the intended recipient, please immediately contact the sender by telephone, or by email, and destroy all copies of this message. If you are a regular recipient of our electronic mail, please notify us promptly if you change your email address.