This document provides information about updates to the Microsoft Office 2010 Group Policy and Office Customization Tool settings. It describes new and removed settings, how to install the updated administrative template files, and files included in the download package. The download package contains updated ADM, ADMX, and ADML files for Group Policy settings, as well as updated OPAX and OPAL files and other files for the Office Customization Tool. It is important to install the updated files to apply any new or changed settings for Office 2010.
This document provides hardware and software requirements for installing Microsoft SharePoint Server 2010 in different environments. It outlines minimum requirements such as having a 64-bit processor with at least 4GB RAM, 80GB hard disk space, and Windows Server 2008 R2 or SQL Server 2008. It also lists prerequisite software that must be installed, including .NET Framework 3.5 SP1, SQL Server Native Client, and Windows Identity Foundation. Optional software like SQL Server 2008 R2 is recommended for working with PowerPivot workbooks. The Microsoft SharePoint Products Preparation Tool can help automate installation of prerequisites.
This document provides information about Microsoft's standards support documentation for Word, Excel, and PowerPoint. It includes links to download the documentation in PDF or ZIP format. It notes some issues with viewing the documentation, such as hyperlinks between documents not working unless the PDFs are in the same directory. It also provides links to forums for discussing the documentation, standards implementation, and interoperability scenarios.
This document provides a walkthrough guide for Microsoft SharePoint 2010. It begins with an introduction to SharePoint 2010 and its key capabilities such as sites, communities, content, search, insights, and composite applications. The document then outlines seven walkthroughs that demonstrate how to access and use various SharePoint 2010 features through a fictional manufacturing company example. The walkthroughs cover configuring and customizing team sites, using social and collaboration features, managing content and metadata, utilizing business intelligence tools, and building customized solutions. The goal is to highlight the major functional areas of SharePoint 2010 and how they can help meet everyday business needs when combined.
Whitepaper Sharepoint Operations Checklist - Mark van Lunenburg, Daniel McPhe...Wilco Turnhout
This document provides guidance on operations management and monitoring for a SharePoint Server 2010 environment. It discusses the Microsoft Operations Framework (MOF) and how it can be applied. It also provides best practices around capacity management, change management, monitoring tools, daily/weekly/monthly tasks, and checklists. Monitoring options covered include diagnostic logging, health data collection, SharePoint Health Analyzer, web analytics, and using Microsoft Operations Manager.
Configure Intranet and Team Sites with SharePoint Server 2013Vinh Nguyen
This document provides step-by-step instructions for configuring intranet and team sites on a SharePoint Server 2013 three-tier farm test lab. It describes setting up the farm, creating web applications for the intranet and team sites, and provisioning site collections for departments and teams. The configuration separates content using four web applications with different application pools and content databases. It also configures DNS entries and sets database capacity limits. Following the steps would result in a test environment for evaluating SharePoint's intranet and team site capabilities.
This document discusses how to configure document management in Dynamics AX, including creating document types, document data sources, and using the Office add-in to create Word templates. It provides steps to create a document type for notes and files, configure forms to use specific document types, and create a document data source using a predefined query to populate Word templates for debt collection letters.
This document provides hardware and software requirements for installing Microsoft SharePoint Server 2010 in different environments. It outlines minimum requirements such as having a 64-bit processor with at least 4GB RAM, 80GB hard disk space, and Windows Server 2008 R2 or SQL Server 2008. It also lists prerequisite software that must be installed, including .NET Framework 3.5 SP1, SQL Server Native Client, and Windows Identity Foundation. Optional software like SQL Server 2008 R2 is recommended for working with PowerPivot workbooks. The Microsoft SharePoint Products Preparation Tool can help automate installation of prerequisites.
This document provides information about Microsoft's standards support documentation for Word, Excel, and PowerPoint. It includes links to download the documentation in PDF or ZIP format. It notes some issues with viewing the documentation, such as hyperlinks between documents not working unless the PDFs are in the same directory. It also provides links to forums for discussing the documentation, standards implementation, and interoperability scenarios.
This document provides a walkthrough guide for Microsoft SharePoint 2010. It begins with an introduction to SharePoint 2010 and its key capabilities such as sites, communities, content, search, insights, and composite applications. The document then outlines seven walkthroughs that demonstrate how to access and use various SharePoint 2010 features through a fictional manufacturing company example. The walkthroughs cover configuring and customizing team sites, using social and collaboration features, managing content and metadata, utilizing business intelligence tools, and building customized solutions. The goal is to highlight the major functional areas of SharePoint 2010 and how they can help meet everyday business needs when combined.
Whitepaper Sharepoint Operations Checklist - Mark van Lunenburg, Daniel McPhe...Wilco Turnhout
This document provides guidance on operations management and monitoring for a SharePoint Server 2010 environment. It discusses the Microsoft Operations Framework (MOF) and how it can be applied. It also provides best practices around capacity management, change management, monitoring tools, daily/weekly/monthly tasks, and checklists. Monitoring options covered include diagnostic logging, health data collection, SharePoint Health Analyzer, web analytics, and using Microsoft Operations Manager.
Configure Intranet and Team Sites with SharePoint Server 2013Vinh Nguyen
This document provides step-by-step instructions for configuring intranet and team sites on a SharePoint Server 2013 three-tier farm test lab. It describes setting up the farm, creating web applications for the intranet and team sites, and provisioning site collections for departments and teams. The configuration separates content using four web applications with different application pools and content databases. It also configures DNS entries and sets database capacity limits. Following the steps would result in a test environment for evaluating SharePoint's intranet and team site capabilities.
This document discusses how to configure document management in Dynamics AX, including creating document types, document data sources, and using the Office add-in to create Word templates. It provides steps to create a document type for notes and files, configure forms to use specific document types, and create a document data source using a predefined query to populate Word templates for debt collection letters.
Microsoft India - SharePoint Business Productivity at its Best FactsheetMicrosoft Private Cloud
As information work evolves in response to external trends and technological innovations, the tools for information work must evolve as well. Microsoft Office, as the primary vehicle by which people experience Business Productivity Infrastructure (BPI) capabilities, continues to expand to support the changing requirements of businesses and information workers around collaboration, mobility and secure access to business data, while providing value, simplicity and integration throughout the BPI stack.
How Microsoft Office Add-ins Simplify Daily Routine and Prevent Costly MistakesBrimit
Take a closer look at how Office add-ins improve productivity, what mundane tasks can be eliminated, what types of add-ins exist, and how to start using them
https://www.brimit.com/blog/how-microsoft-office-add-ins-simplify-daily-routine-and-prevent-costly-mistakes
The document provides steps for demonstrations of document storage, management, collaboration and information sharing features in Windows SharePoint Services 3.0. It includes steps to edit documents, create and add documents to libraries, add content types, and view document version histories. The demonstrations are intended to explore key capabilities like document management, collaboration and information management/communication provided by the Windows SharePoint platform.
The document discusses the new features and development tools in SharePoint 2010, including the new Visual Studio 2010 SharePoint tools, improvements to SharePoint Designer, and the addition of PowerShell support to replace STSADM.EXE for administration and scripting. A demo is provided of the new SharePoint tools in Visual Studio 2010 and improvements in the SharePoint Designer interface.
This document summarizes an advanced SharePoint features training session facilitated by Ivor Davies. The agenda covers working with SharePoint lists and forms using InfoPath 2010, as well as Excel Services, Visio Services, slide libraries, picture libraries, surveys, and SharePoint workspaces. The document provides an overview of these features and how they can be used to enable collaboration within teams. Examples of existing forms in use are also listed. Resources for further learning about InfoPath and SharePoint are included.
This software is a third party tool to backup & export Office365 Mailboxes to Outlook PST and to restore i.e. import the Outlook PST data to the Ofice 365 user account.
This document specifies the binary file format for Microsoft PowerPoint file versions 97 through 2007. It includes documentation of over 100 file records related to slides, presentations, images, animations, comments and other elements. The file format uses OLE 2 compound files, which allow a hierarchical system of storages and streams within a single file.
This document provides an overview of TCP/IP fundamentals and its implementation in Microsoft Windows operating systems. It discusses the history and standards process behind TCP/IP, the protocol architecture including layers and key protocols like IP, TCP and UDP. It also covers topics like IPv4 and IPv6, address resolution, neighbor discovery, and the tools and configuration options available in Windows for working with TCP/IP.
Office 365 Q & A about Microsoft Teams Access,OneDrive, O365 Groups, Shared C...Learning SharePoint
1) The document provides guidance on managing file access in MS Teams, permissions for Office 365 groups, syncing SharePoint files, and sharing calendars from Office 365.
2) By default, files uploaded to MS Teams channels are accessible to all members but owners can restrict access at the channel folder level in SharePoint.
3) Any Office 365 user can create groups by default but an organization can designate a security group to control group creation.
4) SharePoint files can be synced to OneDrive and bulk data uploaded by copying files to the synced SharePoint library folder.
5) Shared calendars from Office 365 will sync to mobile devices using the Outlook mobile app if both users are in the same
This document summarizes the implementation and features of a content management system developed as a final year project. The system allows users to register and log in. It has two databases (Version A and B) that contain iris images. Registered users can view each other's profiles and system administrators can manage content by adding, editing, or deleting subjects and pages. The system was created using PHP, MySQL, Dreamweaver and Fireworks to provide user registration, login, content editing and a public website.
Next level of SharePoint Training for Team Site Owners and Portal Content Managers.
Includes: Online Forms with InfoPath 2010, Excel Services, Visio Services, Site Actions Menu items
Microsoft India - Evaluation Guide for SharePoint Server 2010 WhitepaperMicrosoft Private Cloud
The document provides an overview of new features in Microsoft SharePoint Server 2010 for IT professionals, including improved administration, a scalable services architecture, and more flexible deployment options. It discusses system requirements, installation, upgrading from Microsoft Office SharePoint Server 2007, and key areas like governance, high availability, and administration using Windows PowerShell.
I created this knowledge base database for ICT Central to fill a gap in the retention and access of issue cause and resolution across the corporate SA Health department in 2008
This document provides an introduction to using Microsoft Word 2007, including how to launch Word, work with the user interface, create and save documents, edit text, format text and paragraphs, view and print documents, and access help. It describes the main components of the Word 2007 interface and how to perform basic tasks in Word like opening, saving, editing, formatting and printing a document.
Microsoft Word is a word processing program developed by Microsoft that was first released in 1983. It allows users to type documents that can be shared electronically and read on different platforms. Word is widely used and files can be opened by most users through the Word program itself or free viewers. It has evolved over time to support different operating systems and includes features like spell check and formatting tools.
Deployment guide for Microsoft Office 2010 for IT professionals.Компания Робот Икс
This book contains information about how to install, configure, and upgrade to Microsoft Office 2010. The audience for this book includes IT generalists, IT operations, help desk and deployment staff, IT messaging administrators, consultants, and other IT professionals.
This document provides guidance on planning security for sites and content in Microsoft Windows SharePoint Services 3.0. It discusses the available default permission levels and security groups, and helps determine if any custom groups or permission levels need to be created. Worksheets are also included to aid in deciding which security groups and administrators to use for various permission levels and administration roles.
Robin Meure Daniel McPherson - zevenseas - rapid circle - implementing gove...Wilco Turnhout
This document provides guidance on implementing governance controls in SharePoint 2010 to maintain consistency and control while empowering users. It discusses controls at the farm, web application, and site collection levels including managing service accounts, diagnostic logging, backup procedures, content types, security policies, and more. The goal is to realize the benefits of user empowerment in SharePoint while still enforcing appropriate centralized governance.
The document provides deployment instructions for Microsoft Office 2013. It discusses planning volume activation using Key Management Service (KMS) or Multiple Activation Key (MAK). It also covers activating through Active Directory-Based activation or using the Volume Activation Management Tool. The document provides details on configuring KMS hosts and clients, and customizing Office 2013 installations using the Office Customization Tool and Config.xml file.
The document provides deployment instructions for Microsoft Office 2013. It discusses planning volume activation using Key Management Service (KMS) or Multiple Activation Key (MAK). It also covers activating through Active Directory-Based activation or using the Volume Activation Management Tool. The document provides details on configuring KMS hosts and clients, and customizing Office 2013 installations using the Office Customization Tool and Config.xml file.
1) The user creates a Document Workspace called SPP in Alfresco Share to manage documents. They add a document called local.docx to the workspace.
2) The user edits local.docx by checking it out from the workspace, making changes, and checking it back in. They also view the version history and restore an earlier version.
3) Additional features explored include adding a new folder called "Research" and uploading a document to it. The user closes local.docx to conclude managing documents in the SPP workspace.
This document provides a roadmap to content for Microsoft Windows SharePoint Services 3.0 organized by audience and stage of the IT lifecycle. It outlines content portals for information workers, IT professionals, and developers on Microsoft sites. It also lists community and blog sites with additional shared content for all users of SharePoint Products and Technologies.
Microsoft India - SharePoint Business Productivity at its Best FactsheetMicrosoft Private Cloud
As information work evolves in response to external trends and technological innovations, the tools for information work must evolve as well. Microsoft Office, as the primary vehicle by which people experience Business Productivity Infrastructure (BPI) capabilities, continues to expand to support the changing requirements of businesses and information workers around collaboration, mobility and secure access to business data, while providing value, simplicity and integration throughout the BPI stack.
How Microsoft Office Add-ins Simplify Daily Routine and Prevent Costly MistakesBrimit
Take a closer look at how Office add-ins improve productivity, what mundane tasks can be eliminated, what types of add-ins exist, and how to start using them
https://www.brimit.com/blog/how-microsoft-office-add-ins-simplify-daily-routine-and-prevent-costly-mistakes
The document provides steps for demonstrations of document storage, management, collaboration and information sharing features in Windows SharePoint Services 3.0. It includes steps to edit documents, create and add documents to libraries, add content types, and view document version histories. The demonstrations are intended to explore key capabilities like document management, collaboration and information management/communication provided by the Windows SharePoint platform.
The document discusses the new features and development tools in SharePoint 2010, including the new Visual Studio 2010 SharePoint tools, improvements to SharePoint Designer, and the addition of PowerShell support to replace STSADM.EXE for administration and scripting. A demo is provided of the new SharePoint tools in Visual Studio 2010 and improvements in the SharePoint Designer interface.
This document summarizes an advanced SharePoint features training session facilitated by Ivor Davies. The agenda covers working with SharePoint lists and forms using InfoPath 2010, as well as Excel Services, Visio Services, slide libraries, picture libraries, surveys, and SharePoint workspaces. The document provides an overview of these features and how they can be used to enable collaboration within teams. Examples of existing forms in use are also listed. Resources for further learning about InfoPath and SharePoint are included.
This software is a third party tool to backup & export Office365 Mailboxes to Outlook PST and to restore i.e. import the Outlook PST data to the Ofice 365 user account.
This document specifies the binary file format for Microsoft PowerPoint file versions 97 through 2007. It includes documentation of over 100 file records related to slides, presentations, images, animations, comments and other elements. The file format uses OLE 2 compound files, which allow a hierarchical system of storages and streams within a single file.
This document provides an overview of TCP/IP fundamentals and its implementation in Microsoft Windows operating systems. It discusses the history and standards process behind TCP/IP, the protocol architecture including layers and key protocols like IP, TCP and UDP. It also covers topics like IPv4 and IPv6, address resolution, neighbor discovery, and the tools and configuration options available in Windows for working with TCP/IP.
Office 365 Q & A about Microsoft Teams Access,OneDrive, O365 Groups, Shared C...Learning SharePoint
1) The document provides guidance on managing file access in MS Teams, permissions for Office 365 groups, syncing SharePoint files, and sharing calendars from Office 365.
2) By default, files uploaded to MS Teams channels are accessible to all members but owners can restrict access at the channel folder level in SharePoint.
3) Any Office 365 user can create groups by default but an organization can designate a security group to control group creation.
4) SharePoint files can be synced to OneDrive and bulk data uploaded by copying files to the synced SharePoint library folder.
5) Shared calendars from Office 365 will sync to mobile devices using the Outlook mobile app if both users are in the same
This document summarizes the implementation and features of a content management system developed as a final year project. The system allows users to register and log in. It has two databases (Version A and B) that contain iris images. Registered users can view each other's profiles and system administrators can manage content by adding, editing, or deleting subjects and pages. The system was created using PHP, MySQL, Dreamweaver and Fireworks to provide user registration, login, content editing and a public website.
Next level of SharePoint Training for Team Site Owners and Portal Content Managers.
Includes: Online Forms with InfoPath 2010, Excel Services, Visio Services, Site Actions Menu items
Microsoft India - Evaluation Guide for SharePoint Server 2010 WhitepaperMicrosoft Private Cloud
The document provides an overview of new features in Microsoft SharePoint Server 2010 for IT professionals, including improved administration, a scalable services architecture, and more flexible deployment options. It discusses system requirements, installation, upgrading from Microsoft Office SharePoint Server 2007, and key areas like governance, high availability, and administration using Windows PowerShell.
I created this knowledge base database for ICT Central to fill a gap in the retention and access of issue cause and resolution across the corporate SA Health department in 2008
This document provides an introduction to using Microsoft Word 2007, including how to launch Word, work with the user interface, create and save documents, edit text, format text and paragraphs, view and print documents, and access help. It describes the main components of the Word 2007 interface and how to perform basic tasks in Word like opening, saving, editing, formatting and printing a document.
Microsoft Word is a word processing program developed by Microsoft that was first released in 1983. It allows users to type documents that can be shared electronically and read on different platforms. Word is widely used and files can be opened by most users through the Word program itself or free viewers. It has evolved over time to support different operating systems and includes features like spell check and formatting tools.
Deployment guide for Microsoft Office 2010 for IT professionals.Компания Робот Икс
This book contains information about how to install, configure, and upgrade to Microsoft Office 2010. The audience for this book includes IT generalists, IT operations, help desk and deployment staff, IT messaging administrators, consultants, and other IT professionals.
This document provides guidance on planning security for sites and content in Microsoft Windows SharePoint Services 3.0. It discusses the available default permission levels and security groups, and helps determine if any custom groups or permission levels need to be created. Worksheets are also included to aid in deciding which security groups and administrators to use for various permission levels and administration roles.
Robin Meure Daniel McPherson - zevenseas - rapid circle - implementing gove...Wilco Turnhout
This document provides guidance on implementing governance controls in SharePoint 2010 to maintain consistency and control while empowering users. It discusses controls at the farm, web application, and site collection levels including managing service accounts, diagnostic logging, backup procedures, content types, security policies, and more. The goal is to realize the benefits of user empowerment in SharePoint while still enforcing appropriate centralized governance.
The document provides deployment instructions for Microsoft Office 2013. It discusses planning volume activation using Key Management Service (KMS) or Multiple Activation Key (MAK). It also covers activating through Active Directory-Based activation or using the Volume Activation Management Tool. The document provides details on configuring KMS hosts and clients, and customizing Office 2013 installations using the Office Customization Tool and Config.xml file.
The document provides deployment instructions for Microsoft Office 2013. It discusses planning volume activation using Key Management Service (KMS) or Multiple Activation Key (MAK). It also covers activating through Active Directory-Based activation or using the Volume Activation Management Tool. The document provides details on configuring KMS hosts and clients, and customizing Office 2013 installations using the Office Customization Tool and Config.xml file.
1) The user creates a Document Workspace called SPP in Alfresco Share to manage documents. They add a document called local.docx to the workspace.
2) The user edits local.docx by checking it out from the workspace, making changes, and checking it back in. They also view the version history and restore an earlier version.
3) Additional features explored include adding a new folder called "Research" and uploading a document to it. The user closes local.docx to conclude managing documents in the SPP workspace.
This document provides a roadmap to content for Microsoft Windows SharePoint Services 3.0 organized by audience and stage of the IT lifecycle. It outlines content portals for information workers, IT professionals, and developers on Microsoft sites. It also lists community and blog sites with additional shared content for all users of SharePoint Products and Technologies.
This document provides an overview and guide for evaluating Microsoft Office SharePoint Server 2007. It describes the goals and features of Office SharePoint Server 2007, including improved management of content, accelerated business processes, centralized access to information, and sharing of business information within and outside an organization. The guide also lists top benefits such as a consistent user experience, boosted employee productivity, comprehensive content control, repurposing of content, access to structured and unstructured information, connecting people to information and expertise, accelerated business processes, sharing of business data while protecting sensitive information, and presenting business-critical information in one central location. It aims to provide readers with an understanding of Office SharePoint Server 2007 to help effectively evaluate the product.
This paper shows how Microsoft® Office, Microsoft SharePoint®, Microsoft Exchange, and Microsoft Office Communications Server contribute to the powerful architectural design of the Microsoft Business Productivity Infrastructure (BPI). The BPI stack approach suggests that only by thinking at a capability level (for example, “What do users want to do?‖), and then adding the right aspects of capability in each place (client, server, and services), can we create desktop applications that also deliver rich server and services capabilities to information workers.
This document provides guidance on developing an effective governance plan for implementing Microsoft SharePoint Server 2010. It discusses keys to an effective plan such as defining roles and responsibilities, establishing guiding principles, and creating policies and standards for content management and design. The document uses a fictional company, Contoso, to illustrate examples of framing decisions, governance team members, and an outline for a governance plan.
Microsoft Access 2010 provides easier access to tools to build and manage databases faster. It features a customizable ribbon interface, pre-built templates, and allows publishing databases to Microsoft SharePoint for sharing. New capabilities like web databases, navigation forms, and conditional formatting are added to enhance usability and leverage data across browsers and devices. The product guide outlines the key new and improved features in Access 2010 to help users maximize their information.
This document provides a summary of what's new in Microsoft SharePoint 2013. It explores improvements in areas such as authentication, Business Connectivity Services, eDiscovery, support for mobile devices, records management, business intelligence, social computing, and more. The document is intended to help application specialists, line-of-business specialists, and IT administrators understand the updates and new features in SharePoint 2013.
SharePoint 2013 includes improvements to claims-based authentication that enable new server-to-
server and app authentication scenarios. Key changes include easier migration to claims-based
authentication, caching of login tokens in the Distributed Cache Service, improved logging for
troubleshooting authentication issues, and extensions to OAuth to support server-to-server
authentication between SharePoint and other services like Exchange and Lync.
See Also
App authentication
SharePoint 2013 also extends OAuth to implement an app authentication protocol that enables apps to
authenticate and request access to SharePoint resources on behalf of a signed-in user. SharePoint 2013
includes a dedicated app security token service (STS) that issues app identity tokens to apps.
This document provides instructions for managing content from within Microsoft Office using Alfresco Community Edition 3.3. It describes how to:
1. Create a Document Workspace called SPP in Word that connects to documents stored in an Alfresco repository.
2. Edit a document in the SPP Document Workspace by checking it out, making changes, and checking it back in. It also describes how to view previous versions and restore a document to a previous version.
3. Add additional content to the SPP Document Workspace by creating a "Research" folder and uploading a document to that folder.
The document then continues with instructions for collaborating with colleagues on a document in the SPP Workspace
This document provides instructions for managing content from within Microsoft Office using Alfresco Community Edition 3.3. It describes how to:
1. Create a Document Workspace called SPP in Word that stores documents in Alfresco Share. This allows managing documents without entering the Share interface.
2. Edit a document stored in the SPP Document Workspace by checking it out, making changes, and checking it back in once complete. Version history is maintained.
3. Collaborate on documents with colleagues by customizing the SPP site, managing members and permissions, and working with local and site-stored document copies.
This document provides instructions for managing content from within Microsoft Office using Alfresco Community Edition 3.3. It describes how to:
1. Create a Document Workspace called SPP in Word that stores documents in Alfresco Share. This allows managing documents without entering the Share interface.
2. Edit a document stored in the SPP Document Workspace by checking it out, making changes, and checking it back in once complete. Version history is maintained.
3. Collaborate on documents with colleagues by customizing the SPP site, managing members and permissions, and working with local and site-stored document copies.
This document provides instructions for managing content from within Microsoft Office using Alfresco Community Edition 3.3. It describes how to:
1. Create a Document Workspace called SPP in Word that connects to documents stored in an Alfresco repository.
2. Edit a document in the SPP Document Workspace by checking it out, making changes, and checking it back in. It also describes how to view previous versions and restore a document to a previous version.
3. Add additional content to the SPP Document Workspace by creating a "Research" folder and uploading a document to that folder.
The document then continues with instructions for collaborating with colleagues on a document in the SPP Workspace
This document provides instructions for managing content from within Microsoft Office using Alfresco Community Edition 3.3. It describes how to:
1. Create a Document Workspace called SPP in Word that connects to documents stored in an Alfresco repository.
2. Edit a document in the SPP Document Workspace by checking it out, making changes, and checking it back in. It also describes how to view previous versions and restore a document to a previous version.
3. Add additional content to the SPP Document Workspace by creating a "Research" folder and uploading a document to that folder.
The document then continues with instructions for collaborating with colleagues on a document in the SPP Workspace
This document provides instructions for managing content from within Microsoft Office using Alfresco Community Edition 3.3. It describes how to:
1. Create a Document Workspace called SPP in Word that stores documents in Alfresco Share. This allows managing documents without entering the Share interface.
2. Edit a document stored in the SPP Document Workspace by checking it out, making changes, and checking it back in once complete. Version history is maintained.
3. Collaborate on documents with colleagues by customizing the SPP site, managing members and permissions, and working with local and site-stored document copies.
This document provides instructions for managing content from within Microsoft Office using Alfresco Community Edition 3.3. It describes how to:
1. Create a Document Workspace called SPP in Word that stores documents in Alfresco Share. This allows managing documents without entering the Share interface.
2. Edit a document stored in the SPP Document Workspace by checking it out, making changes, and checking it back in once complete. Version history is maintained.
3. Collaborate on documents with colleagues by customizing the SPP site, managing members and permissions, and working with local and site-stored document copies.
4. Additional features covered include adding folders and content to the site document
Similar to Руководство по эксплуатации для Microsoft Office 2010 (для ИТ-специалистов) (20)
Microsoft sql server analysis services multidimensional performance and opera...Компания Робот Икс
This document provides a summary of a book that consolidates two previously published guides on building and operating high-performance Analysis Services cubes in Microsoft SQL Server. The book is intended for BI developers and operations specialists. It covers proven techniques for designing cubes that process and query faster, as well as how to optimize cubes in a production environment. The book is organized into two parts - the first focuses on building scalable cubes, and the second focuses on running cubes in production.
This document discusses support for hard disks up to 8 TB in capacity and support for cloud or hybrid configurations. It also notes that the information is current as of 2012 and that Microsoft cannot guarantee the accuracy of information provided after the date of the presentation.
This QuickStart is for users new to PowerPivot or tabular model projects
authored in SQL Server Data Tools. It is meant to give you a quick and easy introduction
on how you can use Data Analysis Expressions (DAX) to solve a number of basic data
modeling and analytical problems.
Microsoft SQL Server always on solutions guide for high availability and dis...Компания Робот Икс
This document discusses how SQL Server AlwaysOn solutions in SQL Server 2012 can be used to provide high availability and disaster recovery capabilities. It describes the different layers of protection provided, including infrastructure availability with Windows Server Failover Clustering, SQL Server instance level protection with AlwaysOn Failover Cluster Instances, and database availability with AlwaysOn Availability Groups. The paper also touches on concepts like planned vs unplanned downtime, recovery time objectives, and recovery point objectives that are important considerations for high availability and disaster recovery planning.
This document discusses support for hard disks up to 8 TB in capacity and support for cloud or hybrid configurations. It also notes that the information is current as of 2012 and that Microsoft cannot guarantee the accuracy of information provided after the date of the presentation.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Programming Foundation Models with DSPy - Meetup Slides
Руководство по эксплуатации для Microsoft Office 2010 (для ИТ-специалистов)
1. For IT professionals: Operations guide for
Microsoft Office 2010
Microsoft Corporation
Published: September 2010
Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com)
Abstract
This book contains information about how to manage and maintain an installation of Microsoft Office
2010. The audience for this book includes IT generalists, IT operations, help desk and deployment staff,
IT messaging administrators, consultants, and other IT professionals.
The content in this book is a copy of selected content in the Office 2010 Resource Kit technical library
(http://go.microsoft.com/fwlink/?LinkId=181453) as of the publication date. For the most current content,
see the technical library on the Web.
3. iii
Contents
Getting help........................................................................................................................................ iv
Maintaining and updating Office 2010.................................................................................................1
Available updates for Office 2010 .......................................................................................................2
Office 2010 Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool .....3
Overview of new and removed Group Policy and OCT settings.........................................................3
Group Policy settings location.............................................................................................................3
New administrative templates.......................................................................................................4
OCT settings and availability ........................................................................................................4
Preventing conflicts with earlier versions of Group Policy settings.....................................................4
Installing the settings...........................................................................................................................5
Files included in this download ...........................................................................................................5
Apply updates for Office 2010...........................................................................................................10
Uninstall Outlook 2010 and install a previous version ......................................................................11
Overview ...........................................................................................................................................11
Effect on Outlook settings...........................................................................................................11
Effect on .pst files .......................................................................................................................12
Uninstall Outlook 2010 by using the OCT.........................................................................................12
Install a previous version of Outlook .................................................................................................12
Add or remove languages after deploying Office 2010.....................................................................13
Overview ...........................................................................................................................................13
Before you begin ...............................................................................................................................14
Modify an existing installation ...........................................................................................................14
Deploy language packs.....................................................................................................................16
Remove language packs...................................................................................................................17
Identify installed languages...............................................................................................................18
Manage users' configurations for Office 2010...................................................................................20
Change users' configurations after installing Office 2010.................................................................21
Overview ...........................................................................................................................................21
Customize an existing Office installation ..........................................................................................22
How customization works..................................................................................................................22
Applying Setup customization .msp files to existing installations...............................................23
Setup customization patch sequencing......................................................................................23
4. iv
Getting help
Every effort has been made to ensure the accuracy of this book. This content is also available online in
the Office System TechNet Library, so if you run into problems you can check for updates at:
http://technet.microsoft.com/office
If you do not find your answer in our online content, you can send an e-mail message to the Microsoft
Office System and Servers content team at:
itspdocs@microsoft.com
If your question is about Microsoft Office products, and not about the content of this book, please
search the Microsoft Help and Support Center or the Microsoft Knowledge Base at:
http://support.microsoft.com
5. 1
Maintaining and updating Office 2010
This section provides information about how to apply updates and how to manage user configurations
after you install Microsoft Office 2010.
In this section:
Article Description
Available updates for Office 2010 Provides information about the updated that are
available for Office 2010.
Apply updates for Office 2010 Provides information about how to apply updates
to Office 2010.
Manage users' configurations for Office 2010 Provides information about how to make changes
to an existing installation of Office 2010
6. 2
Available updates for Office 2010
This section describes the available updates for Microsoft Office 2010.
In this section:
Article Description
Office 2010 Administrative Template files (ADM,
ADMX, ADML) and Office Customization Tool
Contains information about the new and updated
Microsoft Office 2010 Group Policy and Office
Customization Tool (OCT) settings that are
included in the download package for Office 2010
Administrative Template files (ADM, ADMX,
ADML) and Office Customization Tool
(http://go.microsoft.com/fwlink/?LinkId=189316).
7. 3
Office 2010 Administrative Template files (ADM,
ADMX, ADML) and Office Customization Tool
This article contains information about the new and updated Microsoft Office 2010 Group Policy and
Office Customization Tool (OCT) settings that are included in the download package for Office 2010
Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool
(http://go.microsoft.com/fwlink/?LinkId=189316).
In this article:
Overview of new and removed Group Policy and OCT settings
Group Policy settings location
Preventing conflicts with earlier versions of Group Policy settings
Installing the settings
Files included in this download
Overview of new and removed Group Policy and OCT
settings
The download package for Office 2010 Administrative Template files (ADM, ADMX, ADML) and Office
Customization Tool (http://go.microsoft.com/fwlink/?LinkId=189316) includes an Admin folder that
contains the Office Customization Tool (OCT) and OCT files, and ADMX and ADML versions of the
Office 2010 Administrative Template files for Windows Vista and Windows Server 2008 or later versions
of Windows.
Also included in the Office 2010 Administrative Template files (ADM, ADMX, ADML) and Office
Customization Tool download page (http://go.microsoft.com/fwlink/?LinkId=189316) is an updated
Microsoft Excel 2010 workbook, Office2010GroupPolicyAndOCTSettings_Reference.xls which is
available in the Files to download section of the download page. This workbook provides the latest
information about all Office 2010 Group Policy settings and OCT settings, and also includes the new,
deleted, and non-versioned specific settings for both Group Policy and OCT.
Group Policy settings location
To obtain information about the policy settings that are currently in effect for the Group Policy object
(GPO) linked to the domain or organizational unit that contains a given computer or user, you can use
Group Policy Results in Group Policy Management Console. To access Group Policy Results data for
a user or computer, you must have Read Group Policy Results data permission on the domain or
organizational unit that contains the user or computer, or you must be a member of the Administrators
group on the targeted local computer.
8. 4
Unless otherwise noted, you will find local Group Policy settings under the User
Configuration/Administrative Templates node of the Group Policy Object Editor and OCT settings on
the Modify user settings page of the OCT.
For information about Group Policy Management Console, see Group Policy overview for Office 2010
(http://technet.microsoft.com/library/c8cec707-2afa-4964-b0f8-611e4709bd79(Office.14).aspx)and
Enforce settings by using Group Policy in Office 2010 (http://technet.microsoft.com/library/873a5392-
1b1a-47a1-a863-1f29ef116d0e(Office.14).aspx) . For more information about how to report by using
Group Policy Results, see “Using Group Policy Results to determine Resultant Set of Policy” in Group
Policy Planning and Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=182208)
(http://go.microsoft.com/fwlink/?LinkId=182208).
New administrative templates
New administrative templates are available for Microsoft SharePoint Workspace 2010, a new Office
2010 application. The templates available for this application are spw14.adm, spw14.admx, and
spw14.adml for Group Policy.
To review the new policy settings, see Group Policy settings reference for Microsoft Office 2010
(http://go.microsoft.com/fwlink/?LinkId=189156).
OCT settings and availability
The OCT settings have two new files extensions: .opax is the standard file name extension, and .opal is
the language-specific extension for the OCT settings.
New OCT files are available for SharePoint Workspace 2010, a new Office 2010 application. The OCT
files available for this application are spw.opax, and spw.opal for the OCT.
Preventing conflicts with earlier versions of Group
Policy settings
This section applies only to Group Policy, and not the OCT.
Policy setting information for Office 2010 is stored in version-specific locations in the Windows registry,
as shown in the following table.
Type of setting 2010 subkey
User-specific policy settings HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice14.0
Computer-specific policy
settings
HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftOffice14.0
Similarly, policy setting information for the 2007 Office system is stored in version-specific locations in
the Windows registry, as shown in the following table.
Note:
9. 5
Type of setting 2007 subkey
User-specific policy settings HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice12.0
Computer-specific policy
settings
HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftOffice12.0
There are several policy settings for Office 2010 that are not stored in one of the version-specific
registry subkeys. For these policy settings, if you had previously configured the 2007 Office system (or
earlier) versions, you must set those policy settings to their Not Configured state before you remove
the previous Office 2010 ADM or ADMX files and load the Office 2010 ADM or ADMX files. This
removes the registry key information for the policy setting from the registry. This occurs because if an
.adm or .admx file is removed, the settings that correspond to the .adm or .admx file do not appear in
Group Policy Object Editor. However, the policy settings that are configured from the .adm or .admx file
remain in the Registry.pol file and continue to apply to the appropriate target client or user.
Installing the settings
For information about how to install and load the Group Policy settings, see Enforce settings by using
Group Policy in Office 2010 (http://technet.microsoft.com/library/873a5392-1b1a-47a1-a863-
1f29ef116d0e(Office.14).aspx).
To update the OCT, replace the /Admin folder in your Office 2010 installation files or installation image
with the new /Admin folder that is included in the download package.
Files included in this download
The download package for the Office 2010 Administrative Template files (ADM, ADMX, ADML) and
Office Customization Tool (http://go.microsoft.com/fwlink/?LinkId=189316) contains the following folders
and files:
Office2010GroupPolicyAndOCTSettings.xls
For the latest information about policy settings, please refer to the updated Microsoft Excel
2010 workbook, Office2010GroupPolicyAndOCTSettings_Reference.xls which is available in
the Files to download section of the Office 2010 Administrative Template files (ADM, ADMX,
ADML) and Office Customization Tool download page
(http://go.microsoft.com/fwlink/?LinkId=189316). The updated workbook,
Office2010GroupPolicyAndOCTSettings_Reference.xls, contains settings changes that were
made after the download package was built.
AdminTemplates.exe
ADMX: The ADMX folder contains XML-based versions (.admx or .adml files) of the
Administrative Template files for Windows Vista and Windows Server 2008 or later versions of
Windows. Administrative Template files in Windows Server 2008 and Windows Vista or later versions of
Windows are divided into ADMX (language-neutral) and ADML (language-specific) files. By default, the
%systemroot%PolicyDefinitions folder on a local computer stores all ADMX files. ADML files are stored
Important:
10. 6
in language-specific folders under the %systemroot%PolicyDefinitions folder. Each language subfolder
contains the .adml files for that language; for example, the English language ADML files would be
stored in the %systemroot%PolicyDefinitionsen-us folder. Languages included are Chinese Simplified
(People’s Republic of China), Chinese (Hong Kong SAR), English, French, German, Italian, Japanese,
Korean, and Spanish. The files that are stored in the ADMX folder are as follows:
access14.admx
excel14.admx
inf14.admx
office14.admx
onent14.admx
outlk14.admx
ppt14.admx
proj14.admx
pub14.admx
spd14.admx
spw14.admx
visio14.admx
word14.admx
de-de: Contains the German language version of the .adml files.
en-us: Contains the English language version of the .adml files.
access14.adml
excel14.adml
inf14.adml
office14.adml
onent14.adml
outlk14.adml
ppt14.adml
proj14.adml
pub14.adml
spd14.adml
spw14.adml
visio14.adml
word14.adml
es-es: Contains the Spanish language version of the .adml files.
fr-fr: Contains the French language version of the .adml files.
it-it: Contains the Italian language version of the .adml files.
ja-jp: Contains the Japanese language version of the .adml files.
ko-kr: Contains the Korean language version of the .adml files.
11. 7
zh-cn: Contains the Chinese Simplified (People's Republic of China) language version of the
.adml files.
zh-tw: Contains the Chinese (Hong Kong SAR) language version of the .adml files.
ADM: Contains the updated .adm files. Each of the language subfolders contains the .adm files
for that language. For example, the en-us subfolder contains the English-US version of the .adm files.
Languages included are Chinese Simplified (People’s Republic of China), Chinese (Hong Kong SAR),
English, French, German, Italian, Japanese, Korean, and Spanish.
de-de: Contains the German language version of the .adm files.
en-us
access14.adm
excel14.adm
inf14.adm
office14.adm
onent14.adm
outlk14.adm
ppt14.adm
proj14.adm
pub14.adm
spd14.adm
spw14.adml
visio14.adm
word14.adm
es-es: Contains the Spanish language version of the .adm files.
fr-fr: Contains the French language version of the .adm files.
it-it: Contains the Italian language version of the .adm files.
ja-jp: Contains the Japanese language version of the .adm files.
ko-kr: Contains the Korean language version of the .adm files.
zh-cn: Contains the Chinese Simplified (People's Republic of China) language version of the
.adm files.
zh-tw: Contains the Chinese (Hong Kong SAR) language version of the .adm files.
Admin: Contains the updated OPAX files, oct.dll, and octca.dll files. These files contain all
previous hotfix updates that affected the OCT. Each of the language subfolders contains the .opal files
for that language, the Office Customization Help file (OCT.chm), and octres.dll files. For example, the
en-us subfolder contains the English-US version of these files. Languages included are Chinese
Simplified (People’s Republic of China), Chinese (Hong Kong SAR), English, French, German, Italian,
Japanese, Korean, and Spanish.
oct.dll
octca.dll
de-de: Contains the German language version of the files in the en-us subfolder.
12. 8
en-us: Contains the .opal files, oct.chm Help file, and octres.dll files.
access14.opal
excel14.opal
inf14.opal
office14.opal
onent14.opal
outlk14.opal
ppt14.opal
proj14.opal
pub14.opal
spd14.opal
spw14.opal
visio14.opal
word14.opal
oct.chm Help file
octres.dll
es-es: Contains the Spanish language version of the .opal, oct.chm, and octres.dll files.
fr-fr: Contains the French language version of the .opal, oct.chm, and octres.dll files.
it-it: Contains the Italian language version of the .opal, oct.chm, and octres.dll files.
ja-jp: Contains the Japanese language version of the .opal, oct.chm, and octres.dll files.
ko-kr: Contains the Korean language version of the .opal, oct.chm, and octres.dll files.
zh-cn: Contains the Chinese Simplified (People's Republic of China) language version of the
.opal, oct.chm, and octres.dll files.
zh-tw: Contains the Chinese (Hong Kong SAR) language version of the .opal, oct.chm, and
octres.dll files.
For information about how to use the ADM files, see Group Policy overview for Office 2010
(http://technet.microsoft.com/library/c8cec707-2afa-4964-b0f8-611e4709bd79(Office.14).aspx) and
Enforce settings by using Group Policy in Office 2010 (http://technet.microsoft.com/library/873a5392-
1b1a-47a1-a863-1f29ef116d0e(Office.14).aspx).
For information about how to use ADMX files for Windows Vista, see Managing Group Policy ADMX
Files Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=75124).
For information about how to use the Office Customization Tool, see Office Customization Tool in Office
2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-24a66a531bb5(Office.14).aspx).
See Also
Group Policy overview for Office 2010 (http://technet.microsoft.com/library/c8cec707-2afa-4964-b0f8-
611e4709bd79(Office.14).aspx)
Enforce settings by using Group Policy in Office 2010 (http://technet.microsoft.com/library/873a5392-
1b1a-47a1-a863-1f29ef116d0e(Office.14).aspx)
13. 9
Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-
24a66a531bb5(Office.14).aspx)
Planning for Group Policy in Office 2010 (http://technet.microsoft.com/library/83ff7b6a-6ad5-4abb-8edf-
e97824e14af9(Office.14).aspx)
14. 10
Apply updates for Office 2010
This section describes how to apply updates to Microsoft Office 2010.
In this section:
Article Description
Uninstall Outlook 2010 and install a previous
version
Describes how to remove Microsoft Outlook 2010,
reinstall the previous version of Outlook, and then
re-create the user Outlook profiles.
Add or remove languages after deploying Office
2010
Describes how to add and remove language packs
for an existing Office 2010 installation and also
how to identify installed languages.
15. 11
Uninstall Outlook 2010 and install a previous
version
In some circumstances, you might need to restore a group of users to a previous installation of
Microsoft Outlook after an upgrade to Microsoft Outlook 2010. To do this, you remove Outlook 2010,
and then reinstall the previous version of Outlook. You must also re-create the users' Outlook profiles.
This article is for Outlook administrators. To learn more about how to uninstall Outlook 2010 on
your computer, see Install or remove individual Office program or components
(http://go.microsoft.com/fwlink/?LinkId=81274).
In this article:
Overview
Uninstall Outlook 2010 by using the OCT
Install a previous version of Outlook
Overview
If you installed Outlook 2010 by using the Office Customization Tool (OCT), you remove Outlook by
using the OCT. In the OCT, you select Office 2010 from the list of options and set the feature
installation state to Not Available to uninstall it. For more information about the OCT, see Customize
Office 2010 (http://technet.microsoft.com/library/a33e64b0-46a5-45e5-b76f-
3add595af8de(Office.14).aspx).
If you installed Outlook 2010 from a stand-alone product CD, you must run Setup with the /uninstall
command-line option on each computer to uninstall Outlook. For more information, see Setup
command-line options for Office 2010 (http://technet.microsoft.com/library/0f489f42-4c01-41d1-8b52-
3a2a2da8f731(Office.14).aspx).
Because of the changes in Outlook 2010 that allow for multiple Microsoft Exchange Server e-mail
accounts, user profiles that are upgraded to Outlook 2010 will not work if you uninstall Outlook 2010,
reinstall a previous version of Outlook like Office Outlook 2007, and then attempt to start Outlook by
using the same user profile. You must configure and deploy new profiles for users when you reinstall a
previous version of Outlook.
Effect on Outlook settings
Settings that you specify in Outlook 2010 are not retained when you revert to a previous installation of
Outlook. Outlook settings will revert to default values or will be set as they were before you installed
Outlook 2010 (depending on the setting).
Rules are saved in the Outlook store and are not affected by uninstalling and reinstalling Outlook.
Note:
16. 12
Effect on .pst files
Outlook personal data files (.pst) are not affected by installing or uninstalling Outlook 2010.
If users have Unicode .pst files and are reinstalling an earlier version of Outlook that does not support
Unicode .pst files, they can copy the information into an Outlook 97–2002 Personal Folders file. To do
this, create a data file in the older Outlook 97–2002 Personal Folders file format. Then import items into
that file from the Unicode data file. There is no automatic procedure to convert files from one format to
the other.
Uninstall Outlook 2010 by using the OCT
1. To start the OCT, from the root of the network installation point, run the following command:
serversharesetup.exe /admin
2. To edit an existing Setup customization file (.msp), in the Select Product dialog box, click
Open an existing Setup customization file. Or to create a new customization file, select the
Office suite that you want to customize, and then click OK.
3. In the navigation pane, select Set feature installation states.
4. In the center pane, expand the Microsoft Office tree, and then right-click Microsoft Outlook.
5. Select the installation option Not Available. To prevent users from reinstalling Outlook, select
Hidden and Locked. The application name is displayed as [H] [L] Microsoft Outlook.
6. After you have finished all the customizations, save the Setup customization file (.msp), and
then exit the OCT.
7. Deploy and apply the Setup customization file (.msp) to users' computers.
Install a previous version of Outlook
When you have removed Outlook 2010, reinstall the previous version of Outlook. As part of the
installation, configure new profiles for users. For example, set options for Office Outlook 2007 by using
the OCT or for Office Outlook 2003 or earlier versions by using the Custom Installation Wizard. Or, you
can configure new profiles by distributing an Outlook profile (.prf) file.
See Also
Change users' configurations after installing Office 2010
Customize Outlook profiles by using an Outlook Profile (PRF) file
(http://technet.microsoft.com/library/71b4efb2-539a-49eb-935e-3222aed9f6a2(Office.14).aspx)
Configure feature installation states for Office 2010 (http://technet.microsoft.com/library/5e377afe-3c09-
447d-82b9-06400fbf1138(Office.14).aspx)
To remove Outlook 2010 by using the Office Customization Tool
17. 13
Add or remove languages after deploying Office
2010
This article describes how to add and remove language packs for an existing Microsoft Office 2010
installation and also how to identify installed languages.
In this article:
Overview
Before you begin
Modify an existing installation
Deploy language packs
Remove language packs
Identify installed languages
Overview
Although the most frequently deployed languages for Office 2010 are released at the same time as the
product, many other Office 2010 Language Packs are released over time. The Office 2010 Multi-
Language Pack, which includes all available language packs, is not released until after all the individual
language packs are released. However, if you upgrade your multilingual organization to Office 2010
before all the language packs are released, you can add or remove languages later. The Office 2010
Multi-Language Pack and Office 2010 Proofing Tools Kit CDs for Office 2010 will be available for
purchase in major retail stores and via their Web sites, and also through Microsoft volume licensing
programs.
There are two methods that you can use to add languages after deploying Office 2010:
Modify an existing installation. With this recommended method, a language is treated as another
feature to add to a deployment of Office 2010. This method involves modifying the Config.xml file to
add the appropriate language and rerunning Setup.exe. This method installs only the necessary
language parts for the products installed on the user's computer. For example, if you add Japanese
to an installation of Microsoft Office Professional 2010, the Microsoft Visio 2010 resources for
Japanese are not installed. However, if the computer has both Office Professional 2010 and Visio
2010 installed on it, you would have to add the Japanese resources for each product through two
separate operations.
Deploy Language Packs as separate products. With this method, there must be at least one Office
2010 product installed on the computer. This method involves running Setup.exe for the Office
2010 Language Pack that you want to install so that the full Language Pack is installed to the
computer. This method is appropriate for adding languages after a deployment of Office 2010
where you do not know which set of products Office 2010 are installed on users' computers.
18. 14
Before you begin
It is important to determine which languages will be used at the beginning of your deployment. If you
change users' configurations after the initial deployment and include additional languages as part of
your customizations, you must first copy all the Office 2010 Language Packs you want to deploy to the
network installation point that contains the Office product files. For example, servershareOffice14. A
static list of the products contained in the installation source is built only during the initial creation of a
customization .msp file. If you later add more languages to the installation source, the existing .msp file
is not updated to reflect this change. Addressing this issue involves the following steps:
1. Create a new customization file by using the Office Customization Tool (OCT).
2. Import your existing customization .msp file by using the File | Import command in the OCT.
3. Make any additional customizations that you need and then save the .msp file.
4. After you update the installation source with additional languages, deploy the new .msp file to
users.
Failure to create and deploy a new .msp file might result in unexpected behavior, because the changes
to an existing customization .msp file will not apply to the languages that were added. If you do not
create a new .msp file and import the existing .msp file into that file, your deployment may test correctly
in your lab, but users might not see the new language in their Office 2010 applications, or they might
see only a subset of the language features. For more information, see To import a customization .msp
file to add languages to an existing installation (http://technet.microsoft.com/library/6bd88342-4f3a-
4535-a570-475d251ef9da.aspx#BKMK_ImportMSO_AddLanguage) in the article Import an Office 2010
Setup customization file (http://technet.microsoft.com/library/6bd88342-4f3a-4535-a570-
475d251ef9da(Office.14).aspx) and Change users' configurations after installing Office 2010.
For information about how to create a network installation point with multiple languages, see Customize
language setup and settings for Office 2010 (http://technet.microsoft.com/library/1c423975-1848-4060-
999c-cafcadf3047d(Office.14).aspx).
For a complete list of language tags, see Language identifiers and OptionState Id values in Office 2010
(http://technet.microsoft.com/library/f5fee727-df49-4ef7-b073-dd6c08dfecfa(Office.14).aspx).
Modify an existing installation
The recommended method for adding languages to an existing installation of Office 2010 is to run
Setup again and modify the existing Office installation. Because you are only modifying the original
installation, no new entry appears in Add or Remove Programs in Control Panel.
You cannot replace the language of the shell user interface (Shell UI) that was installed during the initial
installation. The Shell UI includes core elements of Office that register with the operating system, such
as file name extensions, Tool Tips, and right-click menu items.
When you update a multilanguage installation, you can specify that the new language matches the user
locale set on the local computer. For example, if your organization includes both English-speaking and
Russian-speaking users, you might first deploy English to everyone. Later, when the Russian language
pack becomes available, you can add the following line to Config.xml:
<AddLanguage Id="match" />
19. 15
In this case, Setup installs Russian language elements on any computer that has the user locale set to
Russian. Users with an English user locale are not affected.
1. Copy the files and folders in the new language packs from the source media to the original
network installation point. When you are prompted to overwrite Setup files, click No.
Each language pack includes language-specific elements for every product in the Office 2010.
However, Setup installs language-specific elements only for the Office product that you are
updating.
2. In the core product folder for the product that you are updating, locate the Config.xml file.
For example, if you are adding languages to an installation of Microsoft Office Professional Plus
2010, find the Config.xml file in the ProPlus.WW folder.
3. Open Config.xml in a text editor, such as Notepad.
4. Find the <AddLanguage> element. Uncomment the line by deleting the opening <!-- and closing
--> tags.
5. Set the value of the Id attribute to the language tag that corresponds to the language that you
want to install. You can specify more than one language by including additional <AddLanguage>
elements and attributes.
For example, to add the Russian language version, the line should resemble this:
<AddLanguage Id="ru-ru" />
6. If you add more than one language in Config.xml, you must specify one language as the
language for the Shell UI. For example:
<AddLanguage Id="ru-ru" ShellTransform="yes" />
<AddLanguage Id="en-us" />
You must specify a ShellUI language, even though Setup does not change the ShellUI
language that was set for the initial installation.
7. Save the Config.xml file. Run Setup.exe and specify the path of your modified Config.xml file.
You must use a full qualified path. For example: servershareOffice14setup.exe /config
servershareOffice14ProPlus.WWConfig.xml
where Office14 is the root of the network installation point.
Because Setup also recognizes language packs as separate products, make sure that you
specify the Config.xml file for the Office product that you are updating, and not the language
pack.
To deploy these languages for new Office 2010 installations, see Specify which languages to install
(http://technet.microsoft.com/library/1c423975-1848-4060-999c-
cafcadf3047d.aspx#BKMK_SpecifyLanguagesToInstall) in the article Customize language setup and
settings for Office 2010 (http://technet.microsoft.com/library/1c423975-1848-4060-999c-
cafcadf3047d(Office.14).aspx) and import existing customization .msp files into a new customization
.msp file. A static list of the products contained in the installation source is built only during the initial
creation of a customization file. If you later add more languages to the installation source, the existing
customization file is not updated to reflect this change. For more information, see To import a
To deploy additional languages after Office is installed
20. 16
customization .msp file to add languages to an existing installation
(http://technet.microsoft.com/library/6bd88342-4f3a-4535-a570-
475d251ef9da.aspx#BKMK_ImportMSO_AddLanguage) in the article Import an Office 2010 Setup
customization file (http://technet.microsoft.com/library/6bd88342-4f3a-4535-a570-
475d251ef9da(Office.14).aspx).
Deploy language packs
If you deployed multiple Office 2010 products in your organization and you must add more language
support, you can deploy language packs as separate products. In this case, Setup installs language-
specific elements for every product in Office 2010. No matter which products users have installed,
users can access the additional language versions.
For this deployment method to work, there must be at least one Office 2010 product installed on the
computer that you are deploying to.
When you deploy language packs separately, you must consider the amount of disk space that is
required on users' computers. Language pack requirements range from 800MB to 1.5 GB of hard disk
space that is needed.
Language-specific elements for Microsoft Project 2010 and Microsoft Visio 2010 are installed
separately. In each language pack, the core product folder for Project 2010 is PMUI.ll-cc. The core
product folder for Visio 2010 is VisMUI.ll-cc.
1. Copy all the files and folders in the new language pack from the source media to a location on
the network. If you are using an Office 2010 Multi-Language Pack, you can copy just the files
and folders for the languages that you want to install. When you are prompted to overwrite
Setup files, click No.
2. In the core product folder for the language pack that you are installing, locate the Config.xml
file.
For example, if you are installing the Russian language pack, find the Config.xml file in the
OMUI.ru-ru folder.
3. Run the language pack Setup from the root of the network installation point for the Office 2010
Multi-Language Pack or Office 2010 Language Pack, and specify the path of the Config.xml file
on the command line. For example:
servershareOffice14LPSetup.exe /ConfigservershareOffice14LPRUOMUI.ru-
ruConfig.xml
where Office14LP is the root of the network installation point for the language packs and RU is
the language folder name.
Complete the previous steps for each language that you want to install.
To deploy these languages for new Office 2010 installations, see Specify which languages to install
(http://technet.microsoft.com/library/1c423975-1848-4060-999c-
cafcadf3047d.aspx#BKMK_SpecifyLanguagesToInstall) in the article Customize language setup and
settings for Office 2010 (http://technet.microsoft.com/library/1c423975-1848-4060-999c-
To deploy language packs
21. 17
cafcadf3047d(Office.14).aspx) and import existing customization .msp files into a new customization
.msp file. A static list of the products contained in the installation source is built only during the initial
creation of a customization file. If you later add more languages to the installation source, the existing
customization file is not updated to reflect this change. For more information, see To import a
customization .msp file to add languages to an existing installation
(http://technet.microsoft.com/library/6bd88342-4f3a-4535-a570-
475d251ef9da.aspx#BKMK_ImportMSO_AddLanguage) in the article Import an Office 2010 Setup
customization file (http://technet.microsoft.com/library/6bd88342-4f3a-4535-a570-
475d251ef9da(Office.14).aspx).
Remove language packs
If the Office 2010 Language Packs were deployed as separate products, the Language Packs can be
removed by using Windows Add or Remove Programs.
If the Office 2010 Language Packs were deployed with Office 2010 and not as separate products, the
procedure to remove them resembles the deployment of the Language Packs. Instead of using the
<AddLanguage> tag, use the <RemoveLanguage> tag. See the procedure that follows for the specific steps.
You must follow these steps for each language that you want to remove.
1. If the language was deployed with the Office product (not as a separate product), locate the
Config.xml file in the core product folder for the product that you are updating.
For example, if you are removing languages from an installation of Office Professional Plus
2010, find the Config.xml file in the ProPlus.WW folder.
2. Open Config.xml in a text editor, such as Notepad.
3. Find the <Display> element. Uncomment the line by deleting the opening <!-- and closing -->
tags.
4. Set the value of the Level to “basic” or “none”, CompletionNotice to “yes”, SuppressModal to
“yes”, and AcceptEula to “yes”.
The line should resemble this:
<Display Level="basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes"
/>
5. Find the <AddLanguage> element. If it is in the file, comment out the line by adding opening <!--
and closing --> tags around the element.
The line should resemble this:
<!-- <AddLanguage Id="ru-ru" /> -->
6. Add the <RemoveLanguage> element.
7. Set the value of the Id attribute to the language tag that corresponds to the language that you
want to remove.
For example, to remove the Russian language version, the line should resemble this:
<RemoveLanguage Id="ru-ru" />
To remove language packs
22. 18
8. Save the Config.xml file.
9. If you edited the Config.xml file in the core product folder, run Setup.exe and specify the path of
your modified Config.xml file.
You must use a fully qualified path. For example:
servershareOffice14Setup.exe /ConfigservershareOffice14ProPlus.WWConfig.xml
where Office14 is the root of the network installation point.
servershareOffice14LPSetup.exe /ConfigservershareOffice14LPRUOMUI.ru-
ruConfig.xml
where Office14LP is the root of the network installation point for the language packs and RU is
the language folder name.
You must complete the previous steps for each language that you want to remove.
Identify installed languages
In the registry, you can view a list of languages installed for the Office 2010 either during the initial
installation or during a separate installation of a language pack.
Although all applications in the Office 2010 use a shared set of registry data to determine their UI
language, they do not necessarily all appear in the same UI language. Applications in Office 2010
usually appear with the UI language indicated in the UILanguage value of this registry key. But there
are circumstances where this might not be the case. For example, some deployments might have
Microsoft Word 2010 and Microsoft Excel 2010 installed in French, but another Office 2010 application
installed in a different language. In this case, the other application will look at the UIFallback list in this
registry key, and use the first language that works with its installed configuration.
1. Open the registry.
2. Expand the registry key
HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonLanguageResourcesE
nabledLanguages.
3. The LCID for the language is displayed. To identify the language, see Language identifiers and
OptionState Id values in Office 2010 (http://technet.microsoft.com/library/f5fee727-df49-4ef7-
b073-dd6c08dfecfa(Office.14).aspx).
4. To view the UI language, view the following registry key values and refer to Language
identifiers and OptionState Id values in Office 2010
(http://technet.microsoft.com/library/f5fee727-df49-4ef7-b073-dd6c08dfecfa(Office.14).aspx).
HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonLanguageReso
urcesHelpLanguage
HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonLanguageReso
To identify installed languages
23. 19
urcesUILanguage
5. To view the fallback languages, view the registry key value for
HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonLanguageResourcesUI
Fallback. To identify the language, see Language identifiers and OptionState Id values in
Office 2010 (http://technet.microsoft.com/library/f5fee727-df49-4ef7-b073-
dd6c08dfecfa(Office.14).aspx).
See Also
Import an Office 2010 Setup customization file (http://technet.microsoft.com/library/6bd88342-4f3a-
4535-a570-475d251ef9da(Office.14).aspx)
Change users' configurations after installing Office 2010
Language identifiers and OptionState Id values in Office 2010
(http://technet.microsoft.com/library/f5fee727-df49-4ef7-b073-dd6c08dfecfa(Office.14).aspx)
Customize language setup and settings for Office 2010 (http://technet.microsoft.com/library/1c423975-
1848-4060-999c-cafcadf3047d(Office.14).aspx)
Plan for multilanguage deployment of Office 2010 (http://technet.microsoft.com/library/f458a0cb-a3a5-
4d4a-9f98-a4a81a17ee3a(Office.14).aspx)
24. 20
Manage users' configurations for Office 2010
This section describes how to manage users’ configurations in Microsoft Office 2010.
In this section:
Article Description
Change users' configurations after installing Office
2010
Provides information about how to make changes
to an existing installation of Office 2010.
25. 21
Change users' configurations after installing
Office 2010
This article provides information about how to make changes to an existing installation of Microsoft
Office 2010.
In this article:
Overview
Customize an existing Office installation
How customization works
Overview
After you install Office 2010 on users' computers, you can make changes to the installation by using the
same tool that you used to customize the installation originally. By running the Office Customization
Tool (OCT) and creating or modifying a Setup customization file (.msp file), you can customize the
Office installation. For example, you can add or remove features, modify user settings, or add or
remove files or registry entries.
In Office 2010, two architecture-specific versions of the OCT are available: one for 32-bit Office 2010
and one for 64-bit Office 2010. The 64-bit version of the OCT supports 64-bit client editions of Office
2010, and provides the same user interface, capabilities, and configurable settings as the 32-bit
version. You use the same command to run the 32-bit or 64-bit version of the OCT. For instance, if you
want to run the 32-bit OCT, run the setup.exe /admin command line from the x86 (32-bit) folder as
shown in the following example: servershareOffice14x86setup.exe /admin. To run the 64-bit
OCT, run the setup.exe /admin command line from the x64 (64-bit) folder. For more information about
64-bit Office 2010, see 64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-
bb6c-4636-811e-24f6939548d1(Office.14).aspx). For more information about the OCT, see Office
Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-
24a66a531bb5(Office.14).aspx).
If you have created an initial Setup customization file (.msp file) for an Office 2010 product (for
example, Microsoft Office Professional Plus 2010) and you later want to modify the installation
to add language packs, you can do so by using the Import feature in the OCT. In such cases,
you first add the language packs to the network installation point that contains the Office
product source files. Then, you run the OCT from the root of the network installation point and
create a new Setup customization file for the same product, and import the original
customization .msp file that you created previously for Office Professional Plus 2010. For more
information, see To import a customization .msp file to add languages to an existing installation
(http://technet.microsoft.com/library/6bd88342-4f3a-4535-a570-
475d251ef9da.aspx#BKMK_ImportMSO_AddLanguage)in Import an Office 2010 Setup
customization file (http://technet.microsoft.com/library/6bd88342-4f3a-4535-a570-
475d251ef9da(Office.14).aspx). For information about the network installation point, see Create
Note:
26. 22
a network installation point for Office 2010 (http://technet.microsoft.com/library/72c9ae03-1342-
4524-8242-1524fbd068a5(Office.14).aspx).
Customize an existing Office installation
Use the following procedure to customize an existing installation of Office 2010.
1. From the root of the network installation point that contains the source files, run the following
command line to start the OCT: serversharesetup.exe /admin
2. In the Select Product dialog box, select the product that you want to customize, and then click
OK.
3. In the left pane, select an area of customization, click the option that you want to customize,
and then customize the installation in the right pane.
For example, to remove Microsoft Access 2010 from the installation, locate Features in the left
pane, and then click Set feature installation states. In the right pane, expand Microsoft
Office, right-click Microsoft Office Access, and select Not Available.
4. On the File menu, click Save As after you finish customizing the installation.
5. Specify a unique name for the customization file with an .msp file name extension, and then
click Save.
6. Deploy and apply the Setup customization file (.msp) to users' computers. For more
information, see Applying Setup customization .msp files to existing installations.
If you decide later that you want to make additional changes to an existing installation, you can use the
OCT to create a new maintenance customization .msp file. For example, you might want to modify
existing feature installation states.
As a best practice for modifying existing feature installation states on an existing installation of Office
2010, we recommend that you create a new Setup customization .msp file to make only the changes
that you want to implement. To avoid unexpected results, you must specify only the changes that you
want to make. For example, to create a Setup customization .msp file to add the Access feature after
an initial installation, start the OCT and create a new customization .msp file for the product. In the left
pane of the OCT, locate Features, and then click Set feature installation states. In the right pane,
expand Microsoft Office, right-click Microsoft Office Access, and then select Run from My
Computer. On the File menu, click Save As, and specify a path and file name for the .msp
customization file.
How customization works
Because the Setup customization file that is created by the OCT is a Windows Installer package (.msp),
you can apply the file to users' computers as you would apply a software update. The Office installation
is modified by using the customizations defined in the .msp file. The following sections describe how to
deploy customization .msp files to existing Office installations and show customization patch
sequencing.
To customize the installation
27. 23
Applying Setup customization .msp files to existing installations
To apply the Setup customization (.msp) file to existing installations, you must apply the .msp file
directly to the user's computer. You cannot apply the customization file to existing installations by
placing the .msp file in the Updates folder and running Setup again on the user's computer, or by
running Setup with the customization file specified in the command line.
For example, users can apply the Setup customization .msp file by double-clicking the .msp file or by
running msiexec with the /p option, at a command prompt as shown in the following example:
msiexec.exe /p serversharecustom.msp
For information about Windows Installer command-line options, see Windows Installer Command-Line
Options (http://go.microsoft.com/fwlink/?LinkId=162945).
You can also use a deployment management program, such as Microsoft System Center Configuration
Manager 2010, to deploy Setup customization files. For more information, see the System Center
Configuration Manager TechCenter (http://go.microsoft.com/fwlink/?LinkID=162933) Web site
(http://go.microsoft.com/fwlink/?LinkID=162933).
Although you can use Windows Server Update Services (WSUS) to deploy software updates, you
cannot use WSUS to deploy Setup customization .msp files.
Setup customization patch sequencing
Every time that you save a customization .msp file in the OCT, the tool updates the customization file’s
patch sequencing number with the current computer date and time stamp and generates a new patch
globally unique identifier (GUID). The OCT .msp files are applied chronologically according to their time
stamps.
To show the sequencing behavior, assume that you created the following .msp maintenance files:
1. An OCT .msp file that is named uninstall-access.msp, in which you set Microsoft Office Access to
Not Available. This file is saved first, so it has a lower patch sequence number and an older date
and time stamp. This .msp file is sequenced first and Access is set to Not Available on users'
computers.
2. An OCT .msp file that is named install-access.msp, in which you set Microsoft Office Access to
Run all from My Computer. This file is saved last, so it has a higher patch sequence number and
a newer date and time stamp. This .msp file is sequenced later than the first OCT .msp file,
uninstall-access.msp. Therefore, Access is set to Run all from My Computer on users' computers.
See Also
Office Customization Tool in Office 2010 (http://technet.microsoft.com/library/8faae8a0-a12c-4f7b-839c-
24a66a531bb5(Office.14).aspx)
64-bit editions of Office 2010 (http://technet.microsoft.com/library/faab55b2-bb6c-4636-811e-
24f6939548d1(Office.14).aspx)
Setup architecture overview for Office 2010 (http://technet.microsoft.com/library/f022a92a-2c32-44b7-
996d-09e671a41e9c(Office.14).aspx)
Import an Office 2010 Setup customization file (http://technet.microsoft.com/library/6bd88342-4f3a-
4535-a570-475d251ef9da(Office.14).aspx)