Hi Christian, I havn't been through an upgrade from Office 2000 to 2003 on the same servers, but I would have thought that this would be relatively painless, given that generally, Office seems to improve with every release, and document compatibility seems also to be improving. I'd say 2000 to 2003 is a relatively minor upgrade, but that's based on my own experiences at home and being on the perifery of corporate upgrades for the past 8 years. IIRC, you can set a lot more office settings through GPO with 2003 than you could with 2000. You'll find the relevant ADM templates in the Office 2003 resource kit, and you can download these from Microsoft. General advice for Office: I would have thought that a straight upgrade would be the way to go. You should of course test this, and watch out for anything containing Macros. Also, the file format could change. For Word 97 to Word 2000, this results in an increase in filesize. Look out for this - you might need to increase your fileserver space. Check out the MS Access runtime. We run all our "legacy" databases with an office 97 runtime. It works fine on the same servers that have Office 2003 installed. Test properly of course, but I don't think you'll see any major issues with standard roaming profiles. Jez. ________________________________ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Christian Sent: Tuesday 7 September 2004 20:31 To: thin@xxxxxxxxxxxxx Subject: [THIN] Office 2003 Questions We're planning on rolling Office 2003 on our Win2k/MFXP FR2 farm, and am looking to the group for any tips, gotchas, warnings, etc... you might have from your own deployments. I also have a couple of specific questions related to the rollout: How is the upgrade path from Office 2000? If we have the resources, is it better to rebuild the boxes and reinstall, or is the upgrade path clean? Any need to cleanup folders relating to Office for users with roaming profiles during the switch? Thanks for the advice. -Christian Dady, Target Corp.