Upgrade Office 2000 - 2010
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
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
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
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"
Posted by:
dunnpy
13 years ago
Posted by:
BillyWiz
13 years ago
Posted by:
BillyWiz
13 years ago
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
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
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.