• Click "Download Now" image upwards.
• Here is the link Office 2010 msi installer if the image doesnt shows
• Then, after you click the image you'll go to the 100% protected site where your download will start shortly
• The small window should appear. Click RUN, and thats all. Just follow the instructions of the installer.

�TourStart here for a quick overview of the site�Help CenterDetailed answers to any questions you might have�MetaDiscuss the workings and policies of this site�About UsLearn more about Stack Overflow the company�BusinessLearn more about hiring developers or posting ads with us I have been breaking my head for several days now trying to install Microsoft office 2010 through group policy. Unfortunately Microsoft decided it would be fun to release office without an MSI and so I either� Need to create an msi for it or� Need to install it through a logon script that would run the setup.exe from a network location.Any advise would be greatlly appreciated.

I tried to create a script but even though I double click it and it runs properly, it does not seem to kick in when users log in or when the machine is turned on. Also is there an easy way to create an msi? If you have the enterprise version of the software (easily determined by the presence of an "admin" folder in the root directory structure), you can run setup /admin and create an msp file. Put the msp file in the updates directory and run setup (from a logon script or similar); the setup program will now follow whatever settings you put in the msp file.If you don't have an enterprise version (you get what you pay for); you have to install it manually on every computer (or do something different like AppV). With all respect, that simply does not work for 2010 - installing the MSI simply is not supported.

You HAVE to either make your own around it, or - the "official" version - use a logon script to run the install. MS really did not do a good job here.� TomTom Jun 3 '10 at 3:14 Well, turn it like you want - the user explicitely asks for exactly NOT what you provide.

He does not want to run the logon script. I personally think MS dropped the ball with office setup - no MSI to just publish.� TomTom Jun 3 '10 at 4:19 I agree MS dropped the ball, but you're suggested solution is the exact same as mine.

I just gave the 2 cent summary of the MS article you linked. Should I downvote you as well? Also, the question doesn't say anything about not using a login script.� Chris S Jun 3 '10 at 4:25 Sorry, you are "done" - MS does not support MSI installation but pushes people to online script, as you found out.

An "EASY" way does not exist - you can take WIX, write your own cusom action and push out the exchange install in it, but this is not an easy way (especially the possible rollback scenario).I sugest geting the (official) logon script working. The script at https://technet.microsoft.com/en-us/library/ff602181.aspx works fine for me - note that "double click" is not the same as starting via GPO (where it runs with elevated priviledges). I have had good luck using a starup script to install Office with Group Policy.

I usually create a seperate OU called "Software Install OU" just to install software and then after that move the computer to appropriate OU.1) Configure the "Software Install OU" GPO as follows: Computer ConfigurationPoliciesScriptsStartup. Create a file and name it something like office2010install.cmd.

The contentents should look something like this.path to office2010sharesetup.exe /config path to config file, this depends on type of office install Standard.WW, ProProPlus.WW, or Enterprise.WWconfig.xml /adminfile path to Updates folderoffice2010.msp Copy this file to the the "Software Install OU"2) Use the Office Customization Tool to create a Custom Office Install file (MSP) name it office2010.msp.

Place it in the Updates folder in your Office 2010 Install Share. At very minimum put in your product key, accept the Lic. Agreement, and Display level to None.3) Customize your config.xml.

This depends on which type of Office you want to install. Need the following information in your office 2010 msi installer it in the appropriate folder such as Standard.WW, ProProPlus.WW, or Enterprise.WWTest your work.

You can always just run the office2010install.cmd locally on a computer to make sure this works. Then move on to testing the OU install. TechnologyLife / ArtsCulture / RecreationScienceOther� Stack Overflow� Server Fault� Super User� Web Applications� Ask Ubuntu� Webmasters� Game Development� TeX - LaTeX� Programmers� Unix & Linux� Ask Different (Apple)� WordPress Development� Geographic Information Systems� Electrical Engineering� Android Enthusiasts� Information Security� Database Administrators� Drupal Answers� SharePoint� User Experience� Mathematica� Salesforce� ExpressionEngine� Answers� Cryptography� Code Review� Magento� Signal Processing� Raspberry Pi� Programming Puzzles & Code Golf�more (7)� Photography� Science Fiction & Fantasy� Graphic Design� Movies & TV� Music: Practice & Theory� Seasoned Advice (cooking)� Home Improvement� Personal Finance & Money� Academia�more (8)� English Language & Usage� Skeptics� Mi Yodeya (Judaism)� Travel� Christianity� English Language Learners� Japanese Language� Arqade (gaming)� Bicycles� Role-playing GamesIf you are dissatisfied with Microsoft Office Click-to-Run editions of Microsoft Office 2010 Home and Student or Microsoft Office 2010 Home and Business or if your problem is one of the known issues for Office 2010 Click-to-Run, it might be better for you to use the MSI-based edition of Microsoft Office.For more information about Office Click-to-Run, see Office 2010 Click-to-Run: Introduction or Learn more about Office 2010 Click-to-Run.

Switch from Office 2010 Click-to-Run to MSI-based Office 2010The license is the same. You do not need a new Product Key. If you have any questions, contact Microsoft Support.�Save all work, and then close all programs.�In Control Panel, open Programs and Features to see a list of installed programs.�Click Microsoft Office Click-To-Run 2010, and then click Uninstall.�To remove Microsoft Office Click-to-Run, click Yes.�Go to the Microsoft Office alternative fulfillment page.�Click My account.�Click Download, and then click Advanced options.�Follow the instructions.�To install the MSI-based Microsoft Office 2010 edition, run SingleImage.exe.�When prompted, type your Product Key to continue.Share Related Questions� uninstall software� Linux Agent Issue after v5.0 Upgrade� Help Desk Question� wuauclt.exe using 90% of CPU� User Portal� Inventory vs Asset� Help Desk Email� Date format to use in filters Related Links� Exchange email relaying� Scripting Ninjas� K1000 Management Appliance Home Page� K1000 Management Appliance Documentation� K1000 Management Appliance Support� K1000 Management Appliance Product Page� IT certification gives federal job seekers an edge� K1000 UserVoice Feedback Forum Related Posts� KACE Launches AppDeploy Live� KACE Extends Leadership in Systems Management Appliances with Significant KBOX 1000 Series Upgrade� KACE Takes The Sting Out of 2007 Daylight Saving Time Changes� KBOX Systems Management Appliances Updated With Solaris Support, New Security Policies and Easier Agent Deployment� Education Market Manages Networks with KACE� New KBOX Appliances Bring Enterprise-Grade, Cross Platform IT Automation to Mid-Market� KACE Launches New Help Desk Module For Upgraded KBOX IT Management Applicance� Managing Dell Servers with the Dell KACE K1000 and Dell Open Manage We recently acquired Microsoft Office 2010 and to my surprise it does not bring an MSI to deploy it in Active Directory with.

So I have been looking at other options but nothing seems to be working for me so far. My last option is to generate a ZAP file, but I don't think this is the best solution and a lot of website advise against it.So far I've tried deploying it with the user's logon script but unfortunately users can't install software unless they are administrators so that did not work. Running it as admin did not work either.Does anyone have any ideas?Thanks in advance and thanks for the awesome community! I too was caught off guard by the lack of msi files.

But Cole has already provided you with the link you need to get the silent deployment configured. It uses xml files to change the setup which is a bit nicer than mst's. I have not tried this with�Office 2010 but i have used this technique to create my own MSI files as the active directory deployment tool is my preferred method of deployment, i just make desired app work!https://dennisbareis.com/makemsi.htmhope that helps sometimes configuring answer files for silent installation can be annoying as the syntax has to be correct and seen as my quad core pc took 30 mins to install office 2010 you dont want to be making too many mistakesWe use an MSI packaging software where you take a snapshop of a hard drive.

install and preconfigure personal preference settings then take another snapshop. the software then automatically creates an msi of all the system changes.Wininstall LEhttps://technet.microsoft.com/en-us/library/bb742609.aspxwith this mSI you can deploy through AD GPO or script Paul6790: Yes this certainly was one of my possible solutions, but I wondered if the installation had to be the same for everyone.

for example, if I install Publisher but I need some users to NOT have publisher, will the MSI not care about those intricacies even though it has a snapshot of the whole suit installed in that one "clean system"?Just wondering.MSI is undeniably the best way to go. You have to wonder why in the name of god would microsoft not include an MSI for office, I mean, it goes against all logic. im not quite sure how your hardware specs�are or your licensing but if you have plenty of HDD space and your license supports�it�for the sake of a couple 100MB it is worth having the full suite installed.

it would then save you the task of having to installed modules when your users require it good question im not quite sure. i would imagine so�because the office setup creates files in the document and settings folder for xp and from vista they have changed it to users so�i would probably do�and msi for each OS.�maybe try an xp capture on a win 7 test rig see what happens. I ended up deploying via a zap file.

Not the most elegant solution but I had to keep going with this project. I would have liked to do it through wpkg but unfortunately the service would not start in my computer. After spending, a long long time trying to troubleshoot the problem I decided to go with the .zap solution, after all our network is not really that big, only 60 something users.Thanks for all your input. VirtualizationOne of our new clients has some real old software running on a Windows XP machine.

We want to virtualize it, and slap windows 7 on the workstation so that it can still be used, and then the XP machine will act more as a server. How can we do this?� Store homeDevices�Microsoft Surface�PCs & tablets�Xbox�Virtual reality�Accessories�Windows phone�Microsoft BandSoftware�Office�Windows�Additional softwareApps�All apps�Windows apps�Windows phone appsGames�Xbox One games�Xbox 360 games�PC games�Windows games�Windows phone gamesEntertainment�All Entertainment�Movies & TV�MusicBusiness & Education�Business Store�Education Store�DeveloperSale�SaleFind a store Gift cards� Software & services�Windows�Office�Free downloads & security�Internet Explorer�Microsoft Edge�Skype�OneNote�OneDrive�Microsoft Health�MSN�Bing�Microsoft Groove�Microsoft Movies & TVDevices & Xbox�All Microsoft devices�Microsoft Surface�All Windows PCs & tablets�PC accessories�Xbox & games�Microsoft Band�Microsoft Lumia�All Windows phones�Microsoft HoloLensFor business�Cloud Platform�Microsoft Azure�Microsoft Dynamics�Windows for business�Office for business�Skype for business�Surface for business�Enterprise solutions�Small business solutions�Find a solutions provider�Volume LicensingFor developers & IT pros�Develop Windows apps�Microsoft Azure�MSDN�TechNet�Visual StudioFor students & educators�Office for students�OneNote in classroom�Shop PCs & tablets perfect for students�Microsoft in Education�Support The redistributable contains the PIAs for the following products:� Microsoft Access 2010� Microsoft Excel 2010� Microsoft InfoPath 2010� Microsoft Outlook 2010� Microsoft PowerPoint 2010� Microsoft Project 2010� Microsoft Publisher 2010� Microsoft SharePoint Designer 2010� Microsoft Visio 2010� Microsoft Word 2010The redistributable package also contains additional PIAs that are associated with many of these products.� System Requirements Supported Operating SystemWindows 2000 Service Pack 4, Windows Server 2003, Windows XP Service Pack 2Microsoft Windows XP, Microsoft Windows Vista, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows 7� The following is also required:� Microsoft .NET Framework 2.0 or higher� Install Instructions To install the Office 2010 Primary Interop Assemblies, click the Download button, then click Save and select a location for PIARedist.exe on your computer.

Run the executable to extract the O2010pia.msi file. Use one of the following installation methods to install O2010pia.msi:� Double-click the O2010pia.msi file� Execute msiexec.exe /i O2010pia.msi, or� Wrap the O2010pia.msi file in another setup package through Visual Studio or other Windows Installer aware setup editor.

Please note that the Office 2010 Primary Interop Assemblies setup does not support the /a or /j options for MsiExec. Brasil (Portugues) Ceska�republika (Cestina) Deutschland (Deutsch) Espana (Espanol) France (Francais) Indonesia (Bahasa) Italia (Italiano) Romania (Romana) Turkiye (Turkce) ������ (�������) ????? (?????) ??????? ??????? ???????? (???????) ??? (???) ???? (???) ??????? (??) ?? (??) ?? (???) We system administrators�have been bitching for years at 3rd party developers for not providing deployable MSI packages for their applications, and now Microsoft does the same for their flagship product.

What gives? Why did this happen? Is there anyspecial reason, or was it just to up the sales of SCCM/SCE?And I don't want to hear a thing about those half-baked methods of using batch scripts or similar kludges to "deploy" Office. That's not deployment! That's just automating manual installations with no benefits that IntelliMirror provides - manageability,repairability and uninstallability via GPO.You owe us atleast a technical explanation of why it isn't possible to use IntelliMirror for O2k10, if not an enablement of the functionality in the next service pack. Hello,With Office 2007, the setup architecture of Office changed considerably.

Office 2007 and 2010 have multiple MSI files that install Language specific and Language neutral components of the suite, and setup.exe calls the MSI files in a certain sequence toensure that all the components install properly. Setup exe also does other functions, such as creating the Local installation source (mandatory for Office 2007 and 2010) and applying updates and customization patches during the setup process.As you know GPO deployments use the Windows Installer and simple MSI files to perform installations, and does not have the added functionality that setup.exe provides.

In Office 2007, deploying the ProWW.msi (or another main product MSI) would make a callback to setup.exe and use that to install Office.

This process is not very efficient and severely limits customizability of the installation (you could only modify 4 options via config.xml, instead of the granular level of customization that CustomizationPatches provide.

Office 2007 and above does not use Transforms anymore to customize installations and that is the only method GPOs accept for customization). This is the reason we recommend a deployment tool such as SCCM to install Office 2007 and 2010. TheComputer startup script method athttps://technet.microsoft.com/en-us/library/ff602181.aspx�has been provided for customers who do not have any deployment tools and still want a way to deploy Office without user intervention.Hope this helps.Tarak Chakraborty�- MSFTOffice Deployment Team Blog: https://blogs.technet.com/b/odsupport/ Hello,With Office 2007, the setup architecture of Office changed considerably.

Office 2007 and 2010 have multiple MSI files that install Language specific and Language neutral components of the suite, and setup.exe calls the MSI files in a certain sequence toensure that all the components install properly. Setup exe also does other functions, such as creating the Local installation source (mandatory for Office 2007 and 2010) and applying updates and customization patches during the setup process.As you know GPO deployments use the Windows Installer and simple MSI files to perform installations, and does not have the added functionality that setup.exe provides.

In Office 2007, deploying the ProWW.msi (or another main product MSI) would make a callback to setup.exe and use that to install Office.

This process is not very efficient and severely limits customizability office 2010 msi installer the installation (you could only modify 4 options via config.xml, instead of the granular level of customization that CustomizationPatches provide. Office 2007 and above does not use Transforms anymore to customize installations and that is the only method GPOs accept for customization). This is the reason we recommend a deployment tool such as SCCM to install Office 2007 and 2010.

TheComputer startup script method athttps://technet.microsoft.com/en-us/library/ff602181.aspx�has been provided for customers who do not have any deployment tools and still want a way to deploy Office without user intervention.Hope this helps.Tarak Chakraborty�- MSFTOffice Deployment Team Blog: https://blogs.technet.com/b/odsupport/ Im not sure exactly how you justify your comments regarding Group Policy deployment being limiting in any fashion.

Its Microsoft that removed the functionality we used to have and that made me and many of my colleagues unhappy.With Office 2003, one could download the ORK (Office Resource Kit) which came with the customization wizard that produced a transform file (MST) that customized a 2003 group policy install perfectly.No scripts, no 3rd party deployment software, no programming skills nothing.Microsoft removed that, made the setup /admin function to produce an MSP instead of the MST like before, and now we are all hosed since Microsoft also didnt extend Active Directory Group Policy to support MSP's from Office 2007/2010.Shame Training� Expert-led, virtual classes� Training Catalog� Class Locator� Microsoft Virtual Academy� Free Windows Server 2012 courses� Free Windows 8 courses� SQL Server training� Microsoft Official Courses On-Demand Applies to: Office 2010Topic Last Modified: 2011-09-10You can use Microsoft System Center Configuration Manager 2007 to deploy Microsoft Office 2010 msi installer 2010 in a medium- to large-sized organization.

This article contains detailed technical guidance on the necessary processes and procedures.System Center Configuration Manager 2007 is the solution to comprehensively assess, deploy, and update the servers, clients, and devices across physical, virtual, distributed, and mobile environments.

This article contains detailed technical guidance for specifically deploying Office 2010.Although this article describes the test network environment used for helping to describe the process of deploying Office 2010 by using Configuration Manager 2007, it does not provide information about how to set up the test network infrastructure, such as the Active Directory directory service, Microsoft SQL Server, and System Center Configuration Manager 2007.

For resources on how to set up the test infrastructure, see Resources for deploying the infrastructure later in this article.In this article:�Overview of the deployment process�Deploying Office 2010 in a test environment�Resources for deploying the infrastructure Once you have the supporting infrastructure in place for Configuration Manager 2007, the process for deploying the Office Professional Plus 2010 involves creating and defining five primary areas:�Collections�Packages�Programs�Distribution points�AdvertisementsCollections Collections are groups of Configuration Manager 2007 resources, such as users, user groups, or computers, against which a software deployment is targeted.

For more information about collections, see Collections Overview (https://go.microsoft.com/fwlink/p/?LinkId=145870).Packages A package is the set of installation source files that Configuration Manager 2007 manages and distributes for software deployment. Some of the information that is included within the package is the distribution points and programs. For more information about packages, see About Packages (https://go.microsoft.com/fwlink/p/?LinkId=145871).Programs Programs are part of the package configuration in Configuration Manager 2007.

They contain any command-line switches and additional parameters to be run from the designated package source files, such as Setup.exe. For more information about programs, see About Programs (https://go.microsoft.com/fwlink/p/?LinkId=145872).Distribution points Distribution points are Configuration Manager 2007 site systems that store designated packages for deployment to Configuration Manager 2007 clients.

When the Configuration Manager 2007 client receives and processes a relevant advertisement, the client then contacts a distribution point to download the package and start the installation process. For more information about distribution points, see About Distribution Points (https://go.microsoft.com/fwlink/p/?LinkId=145873).Advertisements Advertisements tie packages and programs together with collections, which enables administrators to target software deployment of specific or customized applications to collections of computers or users.

An advertisement specifies a package and program, and the collection to which it will be advertised or deployed. For more information about advertisements, see About Advertisements (https://go.microsoft.com/fwlink/p/?LinkId=145875). This section provides an illustration and description of the test network environment for the Configuration Manager 2007 infrastructure.

It also includes procedural steps for deploying Microsoft Office Professional Plus 2010 by using Configuration Manager 2007. The test network environment for this article is shown in the following illustration.All of the servers (A, B, and C) are running Windows Server 2008 and are members of the same domain (CPANDL.COM), including the client computers (D), which are running Windows�7 Professional. The applications and roles that each server is running, and the fully qualified domain name (FQDN) for each client computer, are listed as follows:A�-�Active Directory, DNS, DHCP B�-�Microsoft SQL Server 2008 C�-�Configuration Manager 2007 SP2 (management point, distribution point) D�-�Windows�7 Professional, Configuration Manager 2007 client NoteIn this simple test network environment, the site server is performing multiple site system roles (such as management point and distribution point) simultaneously.

However, we do not recommend this configuration for production sites that have large numbers of resources. In this example deployment scenario, detailed information is provided to deploy Office Professional Plus 2010 in the previously defined Configuration Manager 2007 test environment.

By follow� Technologies� App Development� Cloud� Web� Data� Gaming� Internet of Things� Downloads� Visual Studio� MSDN subscription access� SDKs� Trial software� Free downloads� Office resources� SharePoint Server 2013 resources� SQL Server 2014 Express resources� Windows Server 2012 resources� Programs� MSDN subscriptions� Overview� Benefits� Administrators� Students� Microsoft Imagine� Microsoft Student Partners� ISV� Startups� TechRewards� Events� Community� Magazine� Forums� Blogs� Tech Advisors� Channel 9� Documentation� APIs and reference� Dev centers� Retired content� Samples Deploying a Visual Studio 2010 Tools for Office Solution UsingWindows InstallerSummary: Learn how to deploy a Microsoft Visual Studio Tools for the Office system 2010 add-in or document-level solution using a Visual Studio 2010 setup project to create a Windows Installer package that targets the 2007Microsoft Office system or Microsoft Office 2010.Wouter van Vugt, Code CounselTed Pattison, Ted Pattison GroupThis article was updated by Microsoft with permission from the original authors.Applies to: Visual Studio 2010 Tools for Office, 2007 Microsoft Office system,Microsoft Office 2010, Visual Studio 2010.Download: https://code.msdn.microsoft.com/VSTO2010MSIContents� Overview� Deployment Methods� Deploying Office solutions that target the Visual Studio 2010 Tools for Office runtime� Download Samples Provided with this Article� Creating a Basic Installer� Conclusion� Additional Resources� About the AuthorsOverviewYou can develop a Visual Studio 2010 Tools for Office solution for the 2007 Microsoft Office system or MicrosoftOffice 2010, and deploy the solution by using a Visual Studio 2010 Setup project to create a Windows Installerpackage.

The discussion includes steps for deploying a simple Office add-in.For a discussion about how to deploy a solution built with Visual Studio Tools for Office 3.0, see Deploying a VisualStudio Tools for the Office System 3.0 Solution for the 2007 Microsoft Office System Using Windows Installer (Part1 of 2) and Deploying a Visual Studio Tools for the Office System 3.0 Solution for the 2007 Microsoft Office SystemUsing Windows Installer (Part 2 of 2).

Deployment MethodsYou can use ClickOnce to create and install self-updating applications with minimal user interaction. This has anautomated mechanism for easily distributing updates to your application.

However, ClickOnce is not capable ofdeploying components that require administrative privilege such as machine level add-ins.For solutions that require administrative privilege you can use Windows Installer to deploy a Visual Studio Tools forOffice customization.

Windows Installer allows you to configure the deployment in great detail, but this doesrequire more effort to configure correctly. You lose the simple ease of deploying using ClickOnce technology andadvantages such as automated updates, but you receive benefits of configurability.For an overview of how to deploy a Visual Studio Tools for the Office 2010 solution using ClickOnce, see DeployingSolutions for the 2007 Office System with ClickOnce Using Visual Studio 2008 Office 2010 msi installer.

Deploying Office solutions that target the Visual Studio 2010 Tools for Office runtimeBoth ClickOnce and Windows Installer packages need to perform the same rudimentary tasks when installing anOffice solution.� Install prerequisite components on the user computer.� Deploy the solution specific components.� For add-ins, create registry entries.� Trust the solution to allow it to execute.Required Prerequisite Components on the Target ComputerTo run Visual Studio 2010 Tools for Office solutions, the following software must be available on the user computer.� The 2007 Microsoft Office system or Microsoft Office 2010.� The Microsoft .NET FrameworkVisual Studio Tools for the Office system 2010 can work with the Microsoft .NET Framework 3.5 orMicrosoft .NET Framework 4.� The Microsoft Visual Studio 2010 Tools for Office Runtime.Visual Studio 2010 Tools for Office Runtime provides a runtime environment that manages add-insand document-level solutions.� The primary interop assemblies for the 2007 Microsoft Office system or Microsoft Office 2010.� Any utilities assemblies referenced by projects that target the .NET Framework 4.Solution Specific ComponentsThe installer package must install the following components to the user computer.� The Microsoft Office document, if you create a document-level solution.� The customization assembly and any assemblies it requires.� Additional components such as configuration files.� The application manifest (.manifest).� The deployment manifest (.vsto).Registry Entries for Add-insAdd-ins require a set of registry entries for the Microsoft Office application to locate the add-in.

You should createthe registry entries as part of the deployment process. For more information about registry entries pertaining to aVisual Studio Tools for Office add-in, see Registry Entries for Application-Level Add-Ins. When