Hi guys,

I've been tasked with pushing Office 2003 to a very large and decentralized site that mostly uses Office 2000 (and Access 97).

I'm starting the discovery phase and I'm creating a document that will gather information about what's in the environment.

I'm asking questions like:
- What apps exist that are dependant on Office?
- Do you have Access 97 databases in production?
- What's are the GUIDs of the versions of Office in your region (for uninstall)?
- Where are your PST files located?
- Do you have Word macros in your environment?
- etc.

Can you think of things I should be asking?

Any gothcas that you guys have run into when doing this upgrade that I should be thinking about?

Thanks all.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity



FYI, I just downloaded this doc (saw it in another post by Sparticus, thanks) and am reviewing it. Looks like it'll be helpful.

Would still be interested in hearing about others' experiences.
Answered 07/13/2006 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
I don't know if I'd rely on clients to supply back correct information especially about what apps are dependent on Office. There's an MS utility somewhere that scans network drives (possibly local drives) for access databases and reports back the version. Unfortunately, I can't recall the name. If I come across it, I'll post it.

You may want to use the USMT and backup all their settings before the migration.
Answered 07/13/2006 by: Rhys
Orange Belt

Please log in to comment
Sorry, I should have been more clear. The document will be delivered to regional technical support managers and they will task people in their regions to fill it out (it's a big company). =]
Answered 07/13/2006 by: turbokitty
Sixth Degree Black Belt

Please log in to comment