Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Packaging Individual Features of Microsoft Office 2010

Created: 29 Apr 2011 | 13 comments
Language Translations
CableGuy41's picture
+19 19 Votes
Login to vote

Recently I came across packaging of individual features of Microsoft Office 2010 like Access 2010, Word 2010, Excel 2010 etc...

This packaging method is slightly different from the standard MS Office 2010 packaging. So I thought I will share this with you guys so that if it will be helpful in case you haven't done yet.

Office Customization Tool [OCT] is used for packaging/customizing MS Office 2010 by creating PATCHES which will be created and copied to UPDATES folder. All the patches [setup.msp] inside UPDATES folder will be executed during MS Office 2010 installation in an alphabetical order.

In commandline, navigate to the folder where SETUP.EXE reside and execute the following command to run OCT:

setup.exe /admin

It open up with OCT GUI as follows:

Click on OK to create a new PATCH.

Scenario 1: MS Office 2010 is already installed on the machine without MS Access 2010

Requirement 1: Create a Package that will install only Access 2010

In this scenario where MS Office 2010 is already installed on the machine and there is no MS Access 2010. We need to create a package [PATCH] in which only Access 2010 feature is set to "Run from the computer" and make sure to disable all other features. Check the following screenshot:

Now save the PATCH and name it as MSAccess2010_Install.msp, just to reflect in the naming conventions. You can execute the PATCH directly on the machine where you have MS Office 2010 is installed. The PATCH will install only MS Access 2010 on the target machine.

In the same way, we can creaye PATCHES for individual feature installations. Check the following:

Scenario 2: MS Office 2010 is already installed on the machine with all the features

Requirement 2: Create a Package that will uninstall only a particular feature Access 2010

In this scenario we need to create a PATCH with only Access 2010 feature disabled in it. Check the following screenshot for more information:

Now save the PATCH and name it as MSAccess2010_Uninstall.msp, just to reflect in the naming conventions. You can execute the PATCH directly on the machine where you have MS Office 2010 with all the features is installed. The PATCH will now uninstall only MS Access 2010 from the target machine.

This way you can customize the individual feature installation and uninstallation. You can directly execute the PATCH in the commandline. You can use the same commandline options as MSI.

Installation Commandline:

MSIEXEC /I <PATH_TO_MSAccess2010_Install.msp> /QB!  

Uninstallation commandline:

MSIEXEC /I <PATH_TO_MSAccess2010_Uninstall.msp> /QB!  

You can also create a Wise script to install the PATCH in silent mode and also you can display a progress bar with customized message to the end user. For more information of how to create a wise script, please refer to the following article:

https://www-secure.symantec.com/connect/articles/readywise-script-install-application-progress-bar-and-exit-code-altiris

Comments 13 CommentsJump to latest comment

taneja's picture

Perfect timing. Thanks man. I can deliver my package now. :-)

0
Login to vote
EdT's picture

@CableGuy41

Does MSIEXEC /i  work with Office 2010 patches, or should you be using MSIEXEC /p  ?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

0
Login to vote
Chaganti's picture

I have tried installing PATCHES [setup.msp], created by OCT for Office 2010 and they install with MSIEXEC /I commandline. :-)

Thanks & Regards,

Chaganti

0
Login to vote
EdT's picture

As far as I recall, the OCT allows you to specify silent installation when creating the configuration msp.

You can then put the required MSP files into the Upgrades folder and just run setup.exe  - no need for wisescripts or any other complexities.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

0
Login to vote
CableGuy41's picture

Ed,

I agree with you that we need to create a PATCH and copy to UPDATES folder. But this applies when you are installing Office 2010 application.

Scenario: Office 2010 already installed on the machine [Lets us say Acces 2010 is not part of office]

In our organisation, Access 2010 is not part of Office suit. But we still need to package Access 2010 as a separate application to cater special requests. In this case you don't have to use the office source for installing. Create Access_2010 patch and using a wise script install ONLY the patch.

I hope i'm clear this time :-).

Thanks,

CableGuy
Do not forget to mark a SOLUTION

0
Login to vote
EdT's picture

OK, my misunderstanding. I thought you were discussing the packaging of individual components of Office 2010 for first time installation, rather than as an "update" to an existing installation.

I presume the wisescript is used to encapsulate the correct command line for a silent install and does not do anything else - or does it check for a valid Office 2010 install?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

0
Login to vote
CableGuy41's picture

We can implement the logic of finding the instance of Office 2010 on the machine and then apply the update. But i would prefer to do that using Altiris by creating a collection that consists of machines with Office 2010 installed. 

So my wise script will act not do anything other than installing the UPDATE silently. :-)

Thanks,

CableGuy
Do not forget to mark a SOLUTION

0
Login to vote
Aabhisheksoni's picture

I am new to packaging and I have one query that If any vendor suggest that all the patches (lets say 5) should be installed along with the msi. (not by creating diff patches and run them through cmd line). How exactly they can be incorporated inside MSI?

Thanks a lot in advance!!  

0
Login to vote
EdT's picture

The normal technique is to create an administrative installation point (AIP) by running msiexec /a <path to msi> and specifying a folder for the administrative install to go into when prompted for it.

You then apply each patch to the AIP in turn, using msiexec /p <path to patch> /a <path to MSI in AIP>

Once this is done, you can run the install using the updated MSI in the AIP.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

+2
Login to vote
piyushnasa's picture

If MS Office is already installed on the machines and if I want to install MS Access on top of it, then I will have to enable all the features in the package to make Access install on the machine. If we disable all the features then all installed applications will be removed and only Access will be available.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

0
Login to vote
Darren Collins's picture

In the scenario 1 / requirement 1 it is not clear, but in my experience that will actually uninstall all the components of Office 2010 that are already installed and install Access 2010, leaving Access 2010 as the only part of the whole Office 2010 Professional Plus installed. That is absolutely fine if that is the required result, but I would believe that requirement to be very very rare indeed.

The same is true with all the other patches you suggest creating: installing any of them will uninstall all other Office 2010 features except the one that is left Not disabled.

Regards,
Darren.

Darren Collins
Applications Packaging and Deployment for IT Services,
Oxford University, UK.

+1
Login to vote
CableGuy41's picture

Sorry Guys,

Its been very busy year for me as we are targetting 30000 desktop deployments this year. We have hundreds of applications piling to be packaged.

I have an update for this article. In order to package individual features in MS Office 2010, we no longer need to create PATCHES in OCT. I found an issue with PATCH [MSP] creation process.

Every time we save a customization .msp file in the OCT, the tool updates the customization file’s patch sequencing number with the current computer date and time stamp and generates a new GUID. The OCT .msp files are applied chronologically according to their time stamps. I figured out that the package cannot be reused for reinstallation. It fails to reinstall.

So if there is a reinstall requirement then we may need to create a new MSP file. So in order to resolve this issue, we need to install individual features via XML file instead of MSP file. My next article describes the problem step by step along with resolution.

Keep watching.

Thanks.....  

Thanks,

CableGuy
Do not forget to mark a SOLUTION

+1
Login to vote
HK101's picture

awesome info. This info is really helpful.

0
Login to vote