Deploy Succeeded, but didn't really

[randy]

Hi all,

 

I created an install for Office 2010. Tested it on one machine that had Office 2007 Pro on it, it worked as it should.

 

Tested it on another machine that has Office 2007 Ent. on it. The advertisement report says it was successful, however, it still has 2007 on it. It takes about 30 seconds for it to report back that it succeeded.

 

any ideas on this would be appreciated

[jeaostro]

Hi all,

 

I created an install for Office 2010. Tested it on one machine that had Office 2007 Pro on it, it worked as it should.

 

Tested it on another machine that has Office 2007 Ent. on it. The advertisement report says it was successful, however, it still has 2007 on it. It takes about 30 seconds for it to report back that it succeeded.

 

any ideas on this would be appreciated

 

Hello

 

Are you sure you can upgrade from Office 2007 Enterprise to the version of Office 2010 you are running?

A workaround can be to write a script that first remove office 2007 enterprise (msiexec /x "the ID for Office2007Pro")

Then a new step for installing Office 2010 setup.exe /adminfile "nameoftheadminfile".

 

This can be used in a task for example(you can also use tasks to deploy applications like you deploy Operating Systems).

[randy]

I figured it out. I was following Microsoft's suggestion to cache the install. They say to edit the configuration.xml and turn on caching for something large like Office. I turned that off and it installs now.