This may help as a starting point - How to Install Office 2010 And Keep Office 2007 Side by Side Together
Using that idea, I'd create an MST file with orca and install it via GPO applying that MST.
I hope you can help me, I have been asked to install Office 2010 onto the network and make sure I keep the old version aswell.
I was wondering if any of you know if there is a way to dispatch Office 2010 over the network while keeping our Office 2003 installed aswell.
If you use the /admin switch on the setup.exe command, you can build an MSP. One of the dialogues of the wizardy-thing is whether to uninstall older versions. You can then drop the MSP in the updates folder or specify it with the /adminfile switch.
I would highly recommend NOT running the two side-by-side as bad things will happen. If you need both, virtualise one (or both) using something like App-V.
thank you for your help guys, it is greatly appreciated, I shall try both of them when I get time.
Probably next week now.
If 2010 is anything like 2007, it wont play well with 2003.
Basically, every time you open a 2003 office app after a 2007 (10?) then you have to go throught the whole "Configuring office 2003" stuff
Not tested 2010 but 2007 you could deploy 2007 with Group Policy.
My colleague has both installed and he does not suffer such problems. Office 2010 and 2003 seem to play well together so far.
Maybe that is good news for some people then?
Iím the person who asked for Office to be installed by anerney, but I got all excited and had to intervene. Here is the arduous process I had to go through to get it installed on my Server 2003, Windows XP network.
1. Create an MSP file with all customisations and settings, using Office Customisation Tool (OCT), then File Ė Save As.
2. Create a startup script which starts the installation of Office and uses the MSP file created for the settings etc. I have included a quick check to see if Office 2010 is already installed before installing.
Code:if EXIST "C:\program files\microsoft office\office14" ( goto :EOF ) ELSE ( if EXIST "C:\Program Files\Microsoft Office 2010" ( goto :EOF ) ELSE ( \\[ServerShare]\office14\setup.exe /adminfile "\\[ServerShare]\office14\config-pupil.msp" ) )
3. Create a group policy object, which uses this startup script to install Office 2010.
Computer Config | Windows Settings | Scripts | Startup
4. Finally, activation! As we use MAK keys we have to activate every installation of Office 2010. This logoff script I have created automates this process. I will leave this activation script running for a few days and then disable it.
Code:C:\WINDOWS\system32\cscript.exe "%ProgramFiles%\Microsoft Office 2010\Office14\ospp.vbs" /act
One problem with the activation is that after Office is activated and the logoff script tries to run again it takes about 2 minutes. So I created yet another script to create a flag once activated, then it can be checked against to stop the activation trying to run for a second time. Here it is:
Code:if EXIST "C:\program files\microsoft office\office14" ( if EXIST "C:\program files\microsoft office 2010-Activated" ( goto :EOF ) ELSE ( cd \ cd c:\ cd "c:\Program Files\" md "C:\Program Files\Microsoft Office 2010-Activated" cd \ cd \ cd \ C:\WINDOWS\system32\cscript.exe "%ProgramFiles%\Microsoft Office\Office14\ospp.vbs" /act ) ) ELSE ( if EXIST "C:\Program Files\Microsoft Office 2010" ( if EXIST "C:\program files\microsoft office 2010-Activated" ( goto :EOF ) ELSE ( cd \ cd c:\ cd "c:\Program Files\" md "C:\Program Files\Microsoft Office 2010-Activated" cd \ cd \ cd \ C:\WINDOWS\system32\cscript.exe "%ProgramFiles%\Microsoft Office 2010\Office14\ospp.vbs" /act ) ) ELSE ( goto :EOF ) )
Of course you could then insert a line at the end to install Office if these folders do not exist, but we are using two different MSP files and group policies, Staff and Pupil, they differ greatly!
Iím sure there is probably a much better way of doing this, but this works for us. Any questions guys, feel free to ask.
Peter J Hughes
Colne Park High School
Start up script do not start on microsoft 7 enterprise
I've tried using start /wait and extended the maximum wait time for group policy scripts, but it doesn't stop the log-on screen from coming up.
Anyone experienced this or used the start /wait successfully before?
might do better doing it as a shutdown script?
ive found its hit and mis as startup cos sophos interferes/gets there 1st and then office setup cant load grrrr
I would only ever do it using something like App-V - this way the two applications are totaly isolated from each other preventing the conflicts that will happen reguardless of any other fancy deployment methods.
Yeah, might do a shutdown script. Wouldn't mind knowing about the start /wait and how to get that working properly.
There are currently 1 users browsing this thread. (0 members and 1 guests)