Office 2003 and 2010 Dual Install

[enjay]

What is involved in getting 2003 and 2010 on the same PC? I know this has been problematic in the past, but wasn't sure if it had got easier. Our ICT teacher really wants 2003 back so the GCSE pupils can save their PowerPoints as HTML. Alternatively, if anyone has an alternative solution to that, I'm all ears.

[plexer]

App-V?

 

Ben

[K.C.Leblanc]

We did this for our assistant head, it worked but it was very unpredictable with things like file associations. It's not something I'd want to do with IT suite workstations.

 

Why does he want to save HTML out of powerpoint?

[enjay]

Why does he want to save HTML out of powerpoint?

GCSE students need to make HTML pages, and we didn't have Dreamweaver last year when these pupils started their projects so the decision was made to do it in PPT.

[winng]

Next they'll be using Publisher to make web pages. Aargh!

[pantscat]

I do it here... it's not really that tricky. Just make sure that they're installed in different directories and confirm with the teaching staff what they want the file associations to be.

 

NB: Outlook 2003 and 2010 can't co-exist.

[K.C.Leblanc]

Obviously it's no use for students who have started their projects, but Kompozer is a free piece of web design software.

 

KompoZer - Easy web authoring

[tigerstar]

We've been running dual installs in a couple of the labs here to help with the transition. It's not without its problems even after some tinkering and we plan to get rid of 2003 over the summer anyway. There are a few pitfalls to watch out for:

 

* Install Office 2003 first, then Office 2010.

* Don't install two versions of Outlook.

* If you plan to run both versions of Access, you may encounter some odd errors in 2003. Running Office 2003's detect and repair procedure after installing 2010 seems to fix this.

* The big pitfall with running two versions of Office is that whenever you launch one version of (most of) the programs, it will go through a partial setup where it rewrites a bunch of registry entries, and do this again every time you launch the other version, which makes switching back and forth time-consuming and irritating. To stop this, you need to add a couple of registry keys to every user:

 

[HKEY_USERS\[user hive]\Software\Microsoft\Office\11.0\Word\Options]

"NoReReg"=dword:00000001

[HKEY_USERS\[user hive]\Software\Microsoft\Office\14.0\Word\Options]

"NoReReg"=dword:00000001

 

(Yes, I know it says "Word", but it applies to other programs like Excel too.)

 

This is easy enough if you only use mandatory profiles on those computers, but if you have roaming profiles you might want to add those entries to HKCU with a login script.

* The registry trick doesn't stop Access from doing its own re-register procedure. I've not found a way to stop it, and combined with the hiccups this can cause in 2003 described above, frankly it's better if you only run one version of Access.

 

As I say, it's still not without its problems and some update or other could come along and ruin the show. If it's only PowerPoint they need an older version of, I say run both versions of PowerPoint alone, and the 2010 versions of all the other programs. It is technically possible to save from 2010 using a macro or VBA command, but it's fiddly and doesn't work with all of 2010's features.

[EvLPhenom]

We do it here currently. This was decided so that staff and students could get used to 2010, 2003 is being removed this summer and only 2010 installed. I have found that you have problems if you open for instance Word 2003 and then 2010 afterwards, it wants to do the mini setup/configuration. I fixed this with a regedit in the mandatory profile.

 

Also found that we got loads of errors if Access 2010 and 2003 are installed on the same system. In the end we just removed Access 2003 as it was causing too many head aches.

 

If you want/need/interested in the registry edit to stop the mini configuration let me know and i will send it over.

[EvLPhenom]

@tigerstar beat me to it.

[enjay]

I've just tried it, and it isn't all that complicated actually for the limited use I'm trying to get out of it.

 

I just ran the setup.exe for Office 2003, told it I wanted a custom install and then selected PowerPoint. I then had to go and change the file associations back to 2010, however that seems to have held for every user. Since this is a manual process per machine, I don't want to go too wide with it, however it will meet the current need.

Edited March 22, 2012 by enjay