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.
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”.
This blog was viewed about 110,000 times in 2012. If it were a concert at the Barclays Center, it would take about 6 sold-out performances for that many people to see it. In 2012, there were 88 new posts, growing the total archive of this blog to 485 posts. The busiest day of the year was March 13th with 616 views. The most popular post that day was Exchange 2010 Opening multiple shared calendars & additional mailboxes.
These are the posts that got the most views in 2012. You can see all of the year’s most-viewed posts in your Site Stats.
Microsoft Deployment Toolkit (MDT) 2012 Update 1 is the newest version of MDT, a Solution Accelerator for operating system and application deployment. MDT 2012 Update 1 supports deployment of Windows 8, Windows 7, Office 2010 and 365, Windows Server 2012, and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.
Some of the key changes in MDT 2012 Update 1 are:
Added support for Windows 8 and Windows Server 2012.
Support for System Center 2012 Configuration Manager SP1 CTP: Added support in MDT for deploying Windows 8 and Windows Server 2012 with Configuration Manager 2012 SP1 CTP, while supporting all new Configuration Manager functionality (offline BitLocker, UEFI, and Assessment and Deployment Kit).
Support for DaRT 8 Beta: Updated MDT to support DaRT 8 for Windows 8 deployments, while continuing to support DaRT 7 for Windows 7 deployments. Added DaRT support for Configuration Manager scenarios.
New “Build Your Own Pages” User-Driven Installation (UDI) feature: Enhanced the UDI wizard and designer to enable IT pros to design their own wizard pages with little effort.
New System Center 2012 – Orchestrator support: Provided the ability to add steps into an OS deployment task sequence to execute Orchestrator runbooks as part of the deployment process.
Other improvements: Added support for Windows PowerShell 3.0, reworked Roles and Features installation logic for Windows 8, improved “boot from VHD” deployment scenarios, and added support for Configuration Manager monitoring.
The VMware View created a funny video to celebrate the release of View 5.
Check out the Video
VMware Party Rock Parody
And off Course the New features in View 5:
PCoIP WAN performance optimization – Improvements on PCoIP protocol performance in low-bandwidth WAN environments. Users who connect to their desktops over an external WAN have enhanced desktop experience.
PCoIP Build-to-Lossless – PCoIP now provides the ability to turn off Build-to-Lossless. This is the feature that puts PCoIP in parity with ICA when the discussion is around bandwidth consumption. Build-to-Lossless is ON by default and included in the PCoIP protocol within VMware View. I have prepared another post specifically to discuss this feature along with other important changes to the display protocol.
VMware Client Side Caching – VMware View Client (Windows Only) now implements a client side image caching to store portions of the display that were previously transmitted. Image caching reduces the amount of data that is retransmitted and improve user experience. This cache can be managed and it’s size can be modified. I have prepared an article specifically to address this feature.
Support for 3D graphics on vSphere 5.0 – This feature provides View desktops with vGPU graphics enablement available on vSphere 5.0 platforms (hardware version 8). View users can take advantage of desktop graphics enhancements provided by AERO (such as peek, shake, and Flip 3D) and the 3D capabilities of Windows Office 2010 (such as picture editing, slide transitions and animations, presentation-to-video conversion, video embedding, editing, and 3D rotations). Include here: Support for DirectX9 and OpenGL 2.1
View Persona Management – The View Persona Management feature manages user profiles in a secure and centralized environment. (User profiles include user data and settings, application data and settings, and Windows registry settings configured by user applications.) View Persona Management allows IT organizations to simplify and automate the capture and management of a user’s persona while providing a rich user experience. View Persona Management offers the following benefits:
Provides a user profile that is independent of the virtual desktop. When a user logs into any desktop, the same profile appears.
Lets you configure and manage personas entirely within View. You do not have to configure Windows roaming profiles.
Expands functionality and improves performance compared to Windows roaming profiles.
Minimizes login impact by downloading only the files that Windows requires, such as user registry files. Other files are copied to the local desktop when the user or an application opens them from the local profile folder.
Copies recent changes in the local profile to a remote profile repository at configurable intervals, typically once every few minutes.
Client certificate checking for Windows Clients – You can configure remote Windows clients to require certificate verification. Users without valid certificates are denied access to View Connection Server. Alternatively, you can use a Warn But Allow mode that supports self-signed server certificates and lets users connect to View Connection Server with certificates that have expired or are not yet valid. You can also set a No Security mode that lets users connect without certificate checking.
Support for vSphere 5.0 and hardware v8 – Remote View desktops can be hardware v8 virtual machines. Hardware v8 is not supported for desktops that run in local mode.
The Microsoft Assessment and Planning Toolkit (MAP) is an agentless, automated, multi-product planning and assessment tool for quicker and easier desktop and server migrations. MAP provides detailed readiness assessment reports and executive proposals with extensive hardware and software information, and actionable recommendations to help organizations accelerate their IT infrastructure planning process, and gather more detail on assets that reside within their current environment. MAP also provides server utilization data for Hyper-V server virtualization planning; identifying server placements, and performing virtualization candidate assessments, including ROI analysis for server consolidation with Hyper-V.
MAP helps make the following IT planning projects faster and easier:
Migration to Windows 7, Windows Server 2008 R2, and Microsoft Office 2010
Migration to Windows 7 compatible versions of Internet Explorer
Migration to cloud-based services
Server virtualization with Hyper-V
SQL Server consolidation and migration to SQL Server 2008 R2
Assessment of current software usage and client access history for simplified software asset management
PC security assessment and migration to Microsoft Forefront Client Security
You can use MAP to inventory the following technologies:
Microsoft has released a new version of MDT 2010 named Update 1.
It’s a great tool im loving it.
For System Center Configuration Manager 2007 users:
New “User Driven Installation” deployment method. An easy-to-use UDI Wizard allows users to initiate and customize an OS deployment on their PCs that’s tailored to their individual needs.
Support for Configuration Manager R3 “Prestaged Media.” For those deploying Windows 7 and Office 2010 along with new PCs, a custom OS image can easily be loaded in the factory and then customized once deployed.
For Lite Touch Installation:
Support for Office 2010. Easily configure Office 2010 installation and deployment settings through the Deployment Workbench and integration with the Office Customization Tool.
Improved driver importing. All drivers are inspected during the import process to accurately determine what platforms they really support, avoiding common inaccuracies that can cause deployment issues.
Bug Fixes and small improvements
LTI Wizard performance improvement. The LTI Wizard now takes less time to initialize and shows up faster.
Issue in validating connection to the server fixed. In a few scenarios, MDT 2010 used to report the error message, "A connection to the distribution share could not be made" when a task sequence is run. The Microsoft Support article, “Error message when you use MDT 2010: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed,’” at http://support.microsoft.com/kb/977566 describes this issue in detail. This issue has been fixed in MDT 2010 Update 1.
Support for installing Windows 7 roles and features. MDT 2010 Update 1 adds support for installation of Windows 7 operating system roles and features.
Looping issue with x64 custom Windows images fixed. In MDT 2010, ZTI–System Center Configuration Manager deployments could get into an infinite loop when deploying an x64 Windows image captured by LTI. This issue has been fixed in MDT 2010 Update 1
Error handling improvements in MDT task sequence templates. In MDT 2010, task sequences appear to finish successfully even when they really failed. These issues are fixed in MDT 2010 Update 1.
I Like Office 2010. For me it is the best Office version i ever worked with. MDT 2010 it’s great tool that Microsoft created. Now i will talk about how you deploy Office 2010 with Multilanguage packs with MDT 2010.
Step 1: Download the Office 2010 English version booth will be in x86 & x64
Step 2. Download the Office 2010 (language) Multilanguage iso only available from the Microsoft Volume Licensing site. Both in x86 en x64.
Step 4. Extract the Office 2010 (language) Multilanguage iso with 7zip in the same application folder witch you created in Step 3.
Step 5. When you open MDT 2010 management console and you go to the Office 2010 Application that you added in step 3. You wil see that MDT sees more the one language. In my case it was en-us and nl-nl. The Screenshot is from the older MDT 2010 you MDT sees Office 2010 as Office 2007. MDT 2010 beta 1 supports Office 2010. I found till now no issues deploying Office 2010.
Step 6. Check the languages that you want. Check the Screenshot how i did it.
Step 7. Deploy the a Windows XP or Windows 7 client with Office 2010 Multilanguage versions.
Step 8. You can check with Microsoft Office 2010 Language Preferences or the languages that you configured are installed.
Step 9. Use Group Policy to set the language settings for users
Download the Office 2010 policy template files to your computer. You will find them HERE
Make a new GPO named Office 2010 languages settings it is a user policy.
Under User Configuration in the console tree, right-click Administrative Templates.
Click Add/Remove Templates, and then click Add.
In the Policy Templates dialog box, click the template that you want to add, and then click Open.
After you add the Office 2010 templates, click Close.
Open the Group Policy object (GPO) for which you want to set policy.
Double-click User Configuration and expand the tree under Administrative Templates.
Locate language-related policies in the Microsoft Office 2010 \ Language Settings node.
Select the languages that you want to use for each setting.