Recently I came across packaging of individual features of Microsoft Office 2010 like Access 2010, Word 2010, Excel 2010 etc....But the problem is If MS Office (Word and Excel) 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.

The same is true with all the other patches creating(PowerPoint, Project, Visio or Publisher): installing any of them will uninstall all other Office 2010 features except the one that is left Not disabled.

AJ

 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

2

Leaving the install packages on the system rather than deleting them as usual allows the user to go into the control panel and choose modify installation to add further Office features.  We initially install machines without Access, and add it if needed.

Answered 04/23/2012 by: philologist
Red Belt

  • I got a job to package Office 2010 and every component (Word, excel, Powerpoint etc...) should install separately..... to clients... like if client requirement is Word 2010 and Excel 2010 then he will only install two component rather installing whole Office Suite .... i tried all my best to do that but still facing problem to complete the job.... HELP
Please log in to comment
2

I got a job to package Office 2010 and every component (Word, excel, Powerpoint etc...) should install separately..... to clients... like if client requirement is Word 2010 and Excel 2010 then he will only install two component rather installing whole Office Suite .... i tried all my best to do that but still facing problem to complete the job.... HELP

Answered 04/24/2012 by: amjadrehman24
Third Degree Blue Belt

  • You can create patch files for each installation type you need. I have a SlimOffice.msp that only installs Word, Excel, and Powerpoint. I call each one needed by using setup.exe /adminfile"\\sharedFolder\Office Install\Custom\SlimOffice.msp" I can also do the same for Access. This time saving the MSP file as AccessOnly.msp and calling it using setup.exe /adminfile"sharedFolder\Office Install\Custom\AccessOnly.msp"

    Keep in mind /adminfile can only be used for new installs.

    Another recommendation is install components on first use and hide the short-cut in the program files directory. Therefore, it can be added as needed when approval is given. So technically, it's all there it's just not visible to the end-user.
Please log in to comment
1

This is because you are creating a patch file and in that patch file you are specifying this to happen so this is what you will get.

Answered 04/23/2012 by: piyushnasa
Red Belt

  • I got a job to package Office 2010 and every component (Word, excel, Powerpoint etc...) should install separately..... to clients... like if client requirement is Word 2010 and Excel 2010 then he will only install two component rather installing whole Office Suite .... i tried all my best to do that but still facing problem to complete the job.... HELP
Please log in to comment
1

have you tried doing a check for already installed components and using the /modify parameter for setup.exe?

 

see here: http://technet.microsoft.com/en-us/library/cc178956.aspx#BKMK_modify


Answered 04/24/2012 by: pjgeutjens
Red Belt

  • I got a job to package Office 2010 and every component (Word, excel, Powerpoint etc...) should install separately..... to clients... like if client requirement is Word 2010 and Excel 2010 then he will only install two component rather installing whole Office Suite .... i tried all my best to do that but still facing problem to complete the job.... HELP
  • The above link looks like what you need to me. You can test what happens if you make a modify install and install it on a clean system that doesn't have any office components to modify. I wouldn't be surprised if it works. Otherwise, pick a component that everyone is going to have as your base install, most likely Outlook, and then create modify installs for everything else.
Please log in to comment
1

I recently worked with a client that had a similar issue, they wanted to restrict who got what office application. We went with the App-V which made the process quite simple. I don't know if this is something that you would be interested in looking into.

http://www.system-center.org/wordpress/?p=1038

http://www.microsoft.com/en-us/windows/enterprise/products-and-technologies/virtualization/app-v.aspx

http://madvirtualizer.wordpress.com/category/app-v/

Answered 04/25/2012 by: elgoosea
Yellow Belt

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

Share