Personally, given the interaction of office with the OS, given everyone needs it, given its components are core to, or at least utilised by, other apps - I'd put Office in the core build and not virtualise it at all. There's a minor admin overhead, but the user experience is going to be better. Virtualise the server that it's hosted on; virtualise the application via xenapp to remote users - but not virtualise the suite itself. Given the many ways you can quickly rebuild and re-provision a server, why bother? That sounds a sensible way to move the users; however - test that all the settings they expect to move are moved properly: .nk files in outlook, signatures, doc settings. Do not forget Access Databases - who is going to move them and when? And, it's not unusual for some users to need to access both environments - helpdesk, trainers, support may well need access to the original and the new: there may well be others. Do you have a user virtualisation solution in place at the moment? Likes of Appsense? Res? Tricerat? They can help with managing profile changes. Sure you can save files in an older version format - but then also remember disable functions and features and/or inform users that some changes may be lost when saving documents And of course, you've sorted out the user training and given the nod to the helpdesk because it's all different in 2010 and you're bound to get a calls with people just plain lost. From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Hamilton, Ronnie Sent: 29 March 2011 11:03 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Office 2010 Andrew, you have pretty much confirmed a lot of my suspicions, one other question if possible. With regards to streaming Office 2010 is there any other advantage other than allowing multiple versions of Office on the same box? If I can work it my preferred option would be to migrate a user to a box with 2010 and then prevent them from logging on to a box with Office 2002. I could them set GPO to force save to older version until everyone had been moved. As I say this is a first look but I need to get my vision straight so that I can force down the correct road instead of cobbling together something that will just give me more issues during the transition. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew Wood Sent: 29 March 2011 10:05 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Office 2010 Ronnie, You'll not be able to install both versions on the same server - and you may have to box clever if you've enabled roaming profiles. Also bear in mind the file format has changed as well; so you may need to ensure that either you've a way of forcing the 2010 to save in an older format; or allow the existing environment to be able to read the newer file format. To run on the same server you'll have to introduce application streaming to allow you to at least launch Office 2010. Bear in mind it'll get exciting with selecting documents in explorer or launch documents from and linking applications - this may be a lot of work and change for a looksee. Perhaps the easier method would be to build a new server with Office 2010 and set up this with a bunch of test user accounts - could have less impact on your existing environment and be easier to evaluate. From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Hamilton, Ronnie Sent: 28 March 2011 14:37 To: thin@xxxxxxxxxxxxx Subject: [THIN] Office 2010 Hi, just been asked to check out Office 2010 for XenApp, I would need to still run Office 2002 at the same time. Is this a good / bad idea ? Has anyone had any good experiences >? The Platform is Windows 2003 running XenApp 5. thanks Ronnie Visit our website : www.ltai.ie __________________________________________ Lufthansa Technik Airmotive Ireland Limited. Registered in Ireland. Reg. No. 45999. Registered Office: Naas Road, Rathcoole, Co.Dublin. Lufthansa Technik Airmotive Ireland Leasing Limited. Registered in Ireland. Reg. No. 140891. Registered Office: Naas Road, Rathcoole, Co.Dublin. __________________________________________ The information in this email and in any attachments is confidential and may be privileged. If you are not the intended recipient, please destroy this message, delete any copies held on your systems and notify the sender by return email. You should not read, retain, copy, disseminate, distribute, disclose or use this email or its contents in any way. Any such action is strictly prohibited. Thank you.