Microsoft Office 2007 Silent Install Executable

Hello Microsoft Community, i've recently done a cleaninstall of my PC (no DVD drive). Unfortunately i forgot to backup the Microsoft Office Enterprise 2007 exe which i've downloaded from Digital River Content a few years ago. I tried to redownload it but found out that all the download servers from Digital River Content were taken down by Microsoft. Does anyone know where i can get the setup.exe? Or do i have to buy an external DVD-drive just to install Office again. I don't want to waste money on something which will probably be used once. Thanks Best regards D.Vu.

Dec 16, 2017 Security. Let's face it. Software has holes. And hackers love to exploit them. New vulnerabilities appear almost daily. If you have software - we all do.

I have already created my Silent Office 2007 installation. I just came across a language pack for my native language(greek) and i am trying to install that silently too. I actually only want the Proofing Tools. 1) Direct Method (based on info found on the MS Resource center) Copy paste the language files on the installation source directory. No overwrites occur(except 2-3 files which are essentially exactly the same). If i run setup normally(no switches etc) i get the message on the screenshot attached and continue the Installation normally and everything is good. However, when i create an *.MSP file to make the installation silent, i still get prompted to choose and until i click next the installation pauses.

So i can't figure out a way to get rid of that message. 2) Indirect Method Install Office 2007 normally with my already created installation which has been tested and works great, and then apply the language pack.

However, there is no way to customize the installation the same way as office is, not even make it silent. I copied some files from the office 2007 to enable the /admin command but that does't work either. 3) Alternative Method I tried to somehow add the proofing tools to the original installation, by copying the appropriate files and editing.xml but that didn't work either. Setup said there were no applications to install and didn't even start the process. Any ideas?: ) Edited December 15, 2007 by BabisSougias. I mean the Update folder from office 2007, the one you drop all update file in and then they are automatically installed during installation. You know, the new method microsoft thinks it's really good, but in reality takes more space and more time.

Wait, unless i am missing something. I need to copy some file from the language pack to the installation point right? Then i edit the xml as you said, and then i use the AutoIt script? Edit: As i see on the script, keystrokes are send to click next for the program to begin.

I didn't know you could do that. If you can do it there is an easier way to make the installation. As i already mentioned if you copy paste all Language pack files on the source of your silent installation point and then run setup.exe /admin then you have the ability to choose stuff from both packs at once! I was able to do that without needing to run a second installer, i just needed a way to get that 'Next' clicked. So what script do i need to press 'next'? Edited December 15, 2007 by BabisSougias.

Check my edited post. Also here is a screeshot for that: This is the main point of the installation which has new options once you copy paste everything. I think you can do the same thing and not have to run a second installer, just a small script to press Alt+N at the right time. Also, if you do that, then the updates will launch after everything is installed and will also update the proofing tools(the main service pack 1 contains the fixes for languange packs as well). Edited December 15, 2007 by BabisSougias. Ok, so to clarify because i might have confused you.

I copy paste all language pack files to the root directory of my installation(See left side of the screenshot on post directly above). Setup realises that, and offers the options shown on the screenshot on the top post. It also changes what options you have when you click to install the main program! Therefore you are able to install everything at once, but the only problem is that the message prompting you to choose what to install(top post screenshot) will always occur. A script that just clicks next at the right time is all that is needed. At least i think so:/ I understand what your script does, but i think there is a better way for you too: ). Edited December 15, 2007 by BabisSougias.

Ok, so to clarify because i might have confused you. I copy paste all language pack files to the root directory of my installation(See left side of the screenshot on post directly above). Setup realises that, and offers the options shown on the screenshot on the top post. It also changes what options you have when you click to install the main program! Therefore you are able to install everything at once, but the only problem is that the message prompting you to choose what to install(top post screenshot) will always occur.

Mounting File Systems Under Linux Academy. A script that just clicks next at the right time is all that is needed. At least i think so:/ I understand what your script does, but i think there is a better way for you too: ).

In this case you can try this script. With these commands i add english-us and make them the language the Shell will use and i also add greek. You would probably only need the first line since you only deal with english. With the same command you add any language you want.

Then the installation is unattended. Meaning you just create the.msp file with the /admin command, you choose from options that also include everything the language pack has and you just run setup like if you didn't have any language pack in the first place. That way you don't need autoIT script.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see. HotPatching Not applicable Removal Information This update cannot be removed. File Information See Registry Key Verification Not applicable Office Features The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see.

HotPatching Not applicable Removal Information This update cannot be removed. File Information See Registry Key Verification Not applicable Deployment Information Installing the Update You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 3.1 or later version be installed on the system. To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites: • • For more information about the terminology that appears in this bulletin, such as hotfix, see. This security update supports the following setup switches. Supported Security Update Installation Switches Switch Description /? Or /help Displays usage dialog. /passive Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.

/quiet Specifies quiet mode, or suppresses prompts, when files are being extracted. /norestart Suppresses restarting the system if the update requires a restart. /forcerestart Automatically restarts the system after applying the update, regardless of whether the update requires the restart.

/extract Extracts the files without installing them. You are prompted for a target folder. /extract: Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or.exe file.

/lang: Forces the use of a specific language, when the update package supports that language. /log: Enables logging, by both Vnox and Installer, during the update installation. Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see.

Verifying that the Update Has Been Applied • Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information. • File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. • Click Start and then enter an update file name in the Start Search box. • When the file appears under Programs, right-click the file name and click Properties. • On the General tab, compare the file size with the file information tables provided in the bulletin KB article.

Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. • You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied.

Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. • Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. Office 2010 (all 32-bit editions) Reference Table The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs None Deployment Installing without user intervention mscomctlocx2010-kb2597986-fullfile-x86-glb.exe /passive Installing without restarting mscomctlocx2010-kb2597986-fullfile-x86-glb.exe /norestart Update log file Not applicable Further information For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.

Restart Requirement Restart required? In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section. Restart Requirement Restart required? This update may require a restart. HotPatching Not applicable Removal Information This update cannot be removed.

File Information See Registry Key Verification HKEY_LOCAL_MACHINE Software Microsoft Updates VFP8 KB2708940 'Installed' = dword:1 Deployment Information Installing the Update You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and Deployment Tools and Guidance subsection. This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit the following Microsoft website: • For more information about the terminology that appears in this bulletin, such as hotfix, see.

This security update supports the following setup switches. Supported Security Update Installation Switches Switch Description /? Or /h or /help Display usage dialog box. Setup Mode /q[n b r f] Sets user interface level n - No UI b - Basic UI r - Reduced UI f - Full UI /quiet Same as /q /passive Same as /qb Install Options /extract [directory] Extract the package to the specified directory. /uninstall or /u Uninstall this update. /addsource or /as Specifies the source path of the product msi.

This option may be used when installing the update results in a prompt to insert the installation source media for the product. For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.

Restart Requirement Restart required? This update may require a restart.

HotPatching Not applicable Removal Information This update cannot be removed. File Information See Registry Key Verification HKEY_LOCAL_MACHINE Software Microsoft Updates VFP9 KB2708941 'Installed' = dword:1 Deployment Information Installing the Update You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and Deployment Tools and Guidance subsection. This security update requires that Windows Installer 2.0 or later be installed on the system.

All supported versions of Windows include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit the following Microsoft website: • For more information about the terminology that appears in this bulletin, such as hotfix, see.

This security update supports the following setup switches. Supported Security Update Installation Switches Switch Description /? Or /h or /help Display usage dialog box. Setup Mode /q[n b r f] Sets user interface level n - No UI b - Basic UI r - Reduced UI f - Full UI /quiet Same as /q /passive Same as /qb Install Options /extract [directory] Extract the package to the specified directory.

/uninstall or /u Uninstall this update. /addsource or /as Specifies the source path of the product msi. This option may be used when installing the update results in a prompt to insert the installation source media for the product.