Office 2010/2013/2016 supports integration of Updates by placing the MSP files in the Updates folder of the installation medium.
The challenge is more in getting all the update files. Fortunate there are a few great community users that have created WHDownloader for downloading these files and they also maintain the list of applicable updates for Office 2010 and Office 2013 and 2016
Download the Updates
- 1. Run WHDownloader.
- 2. Click the button in the upper left to download all latest update lists.
- 3. Select the Office 2016 version.
- 4. Configure a Download Target folder.
- 5. Select all General Updates and Hotfixes for downloading. Tip, right click and Select All.
- 6. Let it download, this can take some time…
Saving a lot of time
There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. Each Office Deployment Tool works only with that specific version of Office. You can download them from the Microsoft Download Center by using the following links:
<Add SourcePath=”d:\2016\” OfficeClientEdition=”32″ Branch=”Current”>
<Language ID=”en-us” />
<Language ID=”nl-nl” />
<Language ID=”en-us” />
<Language ID=”nl-nl” />
<!– <Updates Enabled=”TRUE” Branch=”Current” /> –>
<Display Level=”Full” AcceptEULA=”TRUE” />
<Logging Name=”OfficeSetup.txt” Path=”%temp%” />
<Property Name=”AUTOACTIVATE” Value=”1″ />
D:\2016\setup.exe /download d:\2016\configuration.xml
Install / Configure Office 365 (2016)
D:\2016\setup.exe /configure d:\2016\configuration.xml
A recent update for Windows may cause Outlook to crash.
The update that causes this is KB3097877 and it appears to be limited to only some Windows 7 installations when downloading online images for a HTML message. The version of Outlook that you are using doesn’t seem to matter and other applications may also be affected.
Thanks to Howto-Outlook
About two weeks October 13, 2015 this is the final day of mainstream support for Outlook 2010.
This is especially relevant to Exchange Online users as the system requirements for Office 365 state that it is designed to work with “any version of Microsoft Office in mainstream support”. While Microsoft does not actively block you from connecting to Office 365 with legacy versions or client applications, the text around older versions includes phrases like “does not recommend”, “limited support” and “quality of user experience will diminish over time”.
Exchange 2013 and Outlook 2007 is a interrested thing
Outlook 2007 SP3 is supported with with April 2014 Public Update KB 2863811
For you as a System or Exchange administrator or Consultant you might consider some things before migrating to Exchange 2013.
You can’t share your calendar in Outlook 2007
When you use Microsoft Office Outlook 2007 to share your calendar, you receive the following error message:
Error while preparing to send sharing message.
Also, if you try to check the permissions on the calendar, you may receive the following error message:
An error occurred when setting schedule permissions.
Solotion Microsoft: Using OWA
It works for share the calendar and you can set editor calendar permissies. All other permissions are not availible
Add-MailboxFolderPermission –identity (username+’:\calendar’) –user testuser –Accessrights PublishingEditor
Upgrade your Outlook Client to 2010 or 2013
Service Pack 1 for Microsoft Office 2013 (KB2817430) 32-Bit Edition
No info yet!
I’ve recently installed Office Web Apps 2013. The installation is straight forward and documented on Technet . However, there was on tricky issue. KB2592525 is a prerequisite and the PS New-OfficeWebAppsFarm cmdlet checks if the KB2592525 is installed. I was installing on a Windows Server 2008 R2 SP1 with all the actual patches. But KB2592525 was not installed and the KB2592525 installer refused to install on this machine. One way to get around this issue is to force the update using pkgmgr.
- Download KB2592525 to folder on your system
- Create a new folder called “files”
- Extract the MSU: expand Windows6.1-KB2592525-x64.msu –F:* .\install
- go to files
- Install using Pkgmgr: pkgmgr.exe /n:c:\install\Windows6.1-KB2592525-x64.xml
That’s it, and the New-OfficeWebAppsFarm cmdlet will accept this workaround.
When you want to deploy Office 2013 with MDT 2012 you must first create a MSP File and saved in Updates Folder:
How to: Create custom configurations of Office 2013.
1. Copy de Office 2013 install to the Applications folder
2. Create a application:
2. Change the Command Line
Change Quiet install Command: setup.exe /adminfile \\servername\deploymentshare$\Applications\Microsoft Office 2013 NL x86\Updates\setup.msp
4. Change the Task Sequence:
5. Final Deployment
Volume license editions of Office 2013 client products require activation. This download enables IT administrators to set up a Key Management Service (KMS) or configure a domain for Active Directory-Based activation. Either of these volume activation methods can locally activate all Office 2013 clients connected to an organization’s network.
If you want to activate volume license editions of Office 2013, Visio 2013, or Project 2013 with a KMS host or Active Directory-Based activation, you need to first install Office 2013 Volume License Pack. When an Office 2013 volume edition client is installed, it will automatically attempt to activate via either Active Directory by using its existing domain pairing or a DNS-discoverable KMS host on your organization network. To set up Active Directory-Based activation, you must be running Windows Server 2012, Windows 8, or newer.
All volume editions of Office 2013 client products are pre-installed with a Generic Volume License Key (GVLK) key, which supports automatic activation for both KMS and Active Directory-Based Activation, so you will not need to install a product key.
This download contains an executable file that will extract and install KMS host license files. These license files are required for the KMS host service to recognize Office 2013 KMS host keys. On Windows Server 2012 and volume license editions of Windows 8, you can use your same KMS host key to set up Active Directory-Based activation.
Supported operating systems: Windows 7, Windows 8, Windows Server 2008 R2, Windows Server 2012
- KMS Host: Windows Server 2008 R2, Windows 7 (volume editions), Windows Server 2012, or Windows 8.
- Active Directory-Based Activation
- Set-up and Configuration: Windows Server 2012, Windows 8 or newer.
- Domain controller: Active Directory Domain Services with the Windows Server 2012 schema installed.
Instructions:Microsoft Office 2013 Volume License Pack
- You need to perform this step only if you’re setting up a KMS host on Windows Server 2008 R2 or Windows 7 (volume editions). Download and run the update contained in the KB article below. This update enables your Windows Server 2008 R2 or Windows 7-based KMS host to successfully activate Office 2013 clients that are running on Windows 8 or Windows Server 2012:
- Download and run the executable file on this page on a supported operating system.
- Enter your Office 2013 KMS host key when prompted.
- Activate the product key online.
- If setting up a KMS host, open port 1688 to allow the KMS host service through the firewall:
- Open Control Panel and click on the Windows Firewall icon.
- Click the “Allow a program through Windows Firewall” link.
- Click the Change Settings button.
- Check the box for Key Management Service.
- To learn more about configuring your KMS host with slmgr.vbs, see the TechNet documentation found on this page.
This download includes Group Policy Administrative Template (ADMX/ADML) and Office Customization Tool (OPAX/OPAL) files for Microsoft Office 2013.
This download includes Group Policy Administrative Template files and Office Customization Tool files for use with Office 2013 applications. It also includes an \Admin folder with an Office Customization Tool, and ADMX and ADML versions of Office 2013 system Administrative Template files. For administrative template files, you may use the combination of ADMX and language-specific ADML files on computers running at least Windows Vista or Windows Server 2008.
For the latest information about policy settings, please refer to the Microsoft Excel 2013 workbook, Office2013GroupPolicyAndOCTSettings_Reference.xls