I guess now we understand why Microsoft is finally saying when App-V (formerly Softgrid) will support 64-bit clients. (Unfortunately what they're saying is that it will be the, which is when 2008 R2 is expected.) This could mean that the 'Parra' build of Citrix XenApp is 64-bit only. (Although Citrix might add as much as they can to XenApp 5 for 2008 R1 32-bit servers.) I wonder if this means that Parra will be 64-bit throughout, instead of the current hybrid 32/64-bit codebase? I know that a lot of people are using 64-bit terminal server and XenApp today. But these are the people who want to (or whose applications allow them too).Imagine the profound change 64-bit only will have in our world?

Oct 10, 2012  This download enables you evaluate Microsoft Windows Server 2008. Skip to main content. Download Center. Windows Server 2008 R2 SP1. A 64-bit system with hardware-assisted virtualization enabled and data execution prevention (DEP) is required.

Imagine all the pain of trying to get 32-bit apps to run on a 64-bit environment. I would guess that if you'd like to make an worthwhile investment in eduction now, learning about App-V or 64-bit behavior would be a good place to start. Yes, Windows Server 2008 R2 will be 64 bit only. But what if Microsoft is able to enhance the set of filter drivers integrated into the platform in a way that 32 bit apps believe they are running on 32 bit Windows? If you look at the stuff the Microsoft OS guys are already doing with redirecting file and registry access, I truly believe that it is possible to 'fool' 32 bit apps. Most of us already know this technology since there is install mode and execute mode for TS, modifying the standard behaviour of the application runtime environment through a filter driver called TsAppCmp.dll. With this experinece and with an App-V team in the background, why should MS not be able to make the 64 bit platform truly compatible to 32 bit apps?

And I'm not talking about true integration of App-V into the standard OS platform. Just my two cents. Besplatne igre za dzojstik gamespot. Benny Add My Comment. When talking about 64 bit terminal services, application compatibility is not the problem. That lies elsewhere: as I have detailed in the sixth part of my seven part article on Windows x64 (), all (OS application) installation and system management scripts must be reviewed and tested.

Many of your existing scripts will not run without modification due to out of process COM objects not being present as both 32 and 64 bit binaries. And then there is printing. Even though 32 bit print servers can host 64 bit drivers, it may in practice be advisable to set up an additional 64 bit printing infrastructure. These and other topics amount to quite some work, which is why so few (large) organizations have moved to 64 bit terminal services (including Citrix PS/XA, of course). This huge effort may even stall the adoption of 2008 R2 terminal servers.