System Center 2012 Configuration Manager has many great built-in requirement rules that will help you to get the right deployment type installed for the current environment. For most of my applications the built-in rules can get the job done, but some times we need to create our own Global Conditions, to fit the requirement rules for an application/Deployment Type. One example could be a 3rd. party add-on for Microsoft Office, where you need to install a Deployment Type that matches the architecture of Microsoft Office. All clients with a 32-bit OS will always have the 32-bit version of Office installed,…
Browsing: Microsoft Office
Earlier this year Microsoft released an update to USMT 4.0, adding support for Office 2010 and a few other minor updates: The XML rules included in the default Migapp.xml file are updated to include new rules that support migrating Office 2010 application settings. Changes that resolve an issue that creates many temporary files, that does not correctly remove the temporary files in a hard-link migration, and that causes poor LoadState performance. An issue that prevents migration in certain time zones is corrected. You can download the update from Here.
The 2007 Microsoft Office suite Service Pack 1 delivers important customer-requested stability and performance improvements, while incorporating further enhancements to user security. This service pack also includes all of the updates released for the 2007 Office suite prior to December of 2007. You can get a more complete description of SP1, including a list of issues that were fixed, in the Microsoft Knowledge Base article 936982: Description of the 2007 Microsoft Office suite Service Pack 1. Service Pack 1 will install even if a publicly available update has already been installed on your computer. SP1 also includes stability improvements developed…