/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Here is my situation:

I am new to deploying software installations via Kbox but i have a office wide move to Office 2010. I have gleamed from this forum and from the notes on 2010 specifically the following:

I use the OCT to create an MSP file with all my customizations, leave the MSP file in the root and zip everything in the folder. I "manually configure" kbox to open the zip file and run the setup.exe with the /adminfile pointing to my MSP file in the root. I also added the activation line to run in post installation.

Now i have successfully run the installer over the network before zipping it for kbox and it did great for a silent install. It uninstalled the current install of office without any problems and installed 2010 activated. When I run the distribution through kbox it prompts me to upgrade from 2007 instead of silently uninstalling as it had done previously in an over the network installation. I am not sure why it is not using the MSP file even though i am specifically calling it in my command line.

I dont have enough experience with kbox to see what i am doing wrong so i wanted to reach out to you folks on the forum to see if i missed something or could help me come up with the fix.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
So a quick update to my situation. It appears that while i was working on the initial steps of getting a MSP going, someone else had saved a copy of their own MSP to the updates folder. I have since removed it from the ZIP file and replaced it with the correct version i have created. I have not removed the MSP from the root as I am using the /adminfile custom.msp for the configure manually command line.

I am still having a problem with office 2k7 prompting to upgrade or cancel installation which i was hoping the above would have corrected. I am not sure why the silent installation options are not kicking in and uninstalling all previous versions as it states.
Answered 08/10/2011 by: lira.j
Senior Yellow Belt

Please log in to comment
0
IIRC, for UI stuff, you also need to use the XML file, a template for which - CONFIG.XML - lives alongside SETUP.EXE. To disable all prompts, you need<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
Answered 08/11/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

IIRC, for UI stuff, you also need to use the XML file, a template for which - CONFIG.XML - lives alongside SETUP.EXE. To disable all prompts, you need<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />



I dont appear to have a Config.xml file in my installation directory. Could this be the reason things are not working they way they should?

Where would i look for this file if it is not there?

Thank you for your reply by the way, I am getting close to having to install this manually on 60+ computers and this may be the missing clue i needed to fully automate this process.
Answered 08/11/2011 by: lira.j
Senior Yellow Belt

Please log in to comment
0
I did some additional googling into the config.xml and found a Tech Net article on it here:

Based on the information i created a very simple config.xml file as follows:

<Configuration Product="ProPlus">

<!-- <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> -->

<Setting Id="AUTO_ACTIVATE" Value="1" />

<Setting Id="SETUP_REBOOT" Value="AutoAlways" />

</Configuration>

I simply want it to do a silent install, install using the customizations from the MSP, activate the product after installing and reboot the computer once completed.

Since i am not calling any values such as Company Name, will it pull these values from the MSP file?
Answered 08/11/2011 by: lira.j
Senior Yellow Belt

Please log in to comment
0
For the UI stuff, you'll need to remove the comment marks from the 'Display' element of the XML. That is to say, change <!-- <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> -->to<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />IIRC, you need to populate the PIDKEY element in the same file with your Office product key.
Answered 08/12/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

For the UI stuff, you'll need to remove the comment marks from the 'Display' element of the XML. That is to say, change <!-- <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> -->to<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />IIRC, you need to populate the PIDKEY element in the same file with your Office product key.


Caught that one after i posted as i was going through. Does it not pull the office product key from the MSP? I will add that to my config.xml file. Also, it still does not appear to be working properly but would the PIDKEY element be a possible cause for it to not install silently?
Answered 08/12/2011 by: lira.j
Senior Yellow Belt

Please log in to comment
0
thanks. i really appreciate it..
Answered 08/20/2011 by: DanKaplans
Yellow Belt

Please log in to comment
0
Hello,

I was wondering if we can update Office 2007 to Office 2010 without installing the whole package?

Regards
Answered 11/09/2011 by: krisstewart
Yellow Belt

Please log in to comment