Hi!
I have the task of upgrading 500 users who have Office 2000 Professional installed but with Outlook 2003 up to Office 2010 Standard edition

I Have created a batch file which upgrades 2000 to 2003 reboots (to complete the installation) and then uses RUNONCE to run a second batch file wich uses the OCT to Upgrade 2003 to 2010. The Office 2010 upgrade installer won't upgrade directly from 2000 as it ends up with both installed

It works but there are a number of small problems, the primary being the double reboot and logon required to complete each installation. The forced reboot works fine but my question is can I get around the need to physically logon each time. I plan to use LANDesk to deploy the batch files and obviously its fine that the installation kicks off when users switch on but I don't like the requirement to do so twice and getting LANDesk to tackle the 2nd batch file may be difficult.

I'd welcome any comments, suggestions etc.

if you need further information, please let me know

Cheers
Bill
0 Comments   [ + ] Show Comments

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.

Answers

0
How about uninstalling Office 2000 and then installing 2010?
Outlook 2003 will be upgraded to 2010 as part of the installation process, if set up correctly in the OCT.

This would remove the need to upgrade from 2000 to 2003 first.

Just thinking out loud...

Dunnpy
Answered 09/09/2011 by: dunnpy
Red Belt

Please log in to comment
0
Dunnpy
Thanks for the reply.
Yes. I was trying to get the Word/Excel customisations carried over by performing these as upgrades but perhaps you are right and simplest is best
Cheers
Bill
Answered 09/10/2011 by: BillyWiz
Yellow Belt

Please log in to comment
0
Hi!
Generally this works well, by using versions of :
set ProductName=Office9.xxx
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==0 (msiexec /x {00000409-...} /qn)

I have, however, circumstances where I need to retain MSAccess2000 on the PCs. One option is to reinstall just this component at the end but I'd prefer to just uninstall all the other components. I tried using the resource kit and installation wizard but it did nothing.

Does anyone know the easy method?

Thanks Bill
Answered 10/03/2011 by: BillyWiz
Yellow Belt

Please log in to comment
0
The quickest route would be to note down the top-level feature names in the orginal package and then specify those names in the REMOVE property. For example, let's say Outlook's parent feature is called 'OutlookFiles', Word's parent is 'WordFiles' and so on. Your REMOVE property would then be set like this:REMOVE="Outlookfiles, WordFiles"
Answered 10/03/2011 by: VBScab
Red Belt

Please log in to comment
0
That looks good. Thanks VBScab. I'll give it a try!
Answered 10/07/2011 by: BillyWiz
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity