Back

Silent Network Installation of Office 2010 and Lync

Configure a silent installation of Office 2010 and Office 365 Office ProfessionalNote To create the source files from the Compressed Sing...

4 min read
Published on Jul 12, 2011
Silent Network Installation of Office 2010 and Lync

Configure a silent installation of Office 2010 (and Office 365 Office Professional)

Note – To create the source files from the Compressed, Single MicrosoftOffice.exe file that is downloaded in Office 365, you must extract using the procedure documentedĀ Customizing the Office Professional Plus deployment.

You can configure a silent installation of Microsoft Office 2010 by using the Config.xml file. The Config.xml file is used to configure installation tasks and is usedĀ onlyĀ when you run Setup. It is not installed or cached on users’ computers. You can edit the Config.xml file to customize an installation.

By default, the Config.xml file that is stored in the core product folder,Ā core_product_folder_name.WW, directs Setup to install that product. For example, if ProPlus.WW is the folder name, the Config.xml file in the ProPlus.WW folder installs Microsoft Office Professional Plus 2010.

Modify the Config.xml file to configure a silent installation

To configure aĀ silent installationĀ (unattended installation) of an Office 2010 product that requires no user interaction, modify the Config.xml file for the product that you are installing and set theĀ DisplayĀ element’sĀ LevelĀ attribute to**ā€œnoneā€**Ā (Display Level=ā€œnoneā€), and then save the Config.xml file, as shown in the following procedure. TheDisplayĀ element specifies the level of user interface that Setup displays to users.

To specify silent installation options in Config.xml

  1. Open the Config.xml file for the Office product (such as Office Professional Plus 2010) that you are installing by using a text editor tool, such as Notepad.
  2. Locate the line that contains theĀ DisplayĀ element, as shown in the following example:
<!--Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> -->

NaN. Modify theĀ DisplayĀ element entry with the silent options that you want to use. Make sure that you remove the comment delimiters, ā€<!ā€”ā€ and ā€ā€”ā€. For example, use the following syntax:

Display Level=ā€œnoneā€ CompletionNotice=ā€œnoā€ SuppressModal=ā€œyesā€ AcceptEula=ā€œyesā€

These options will direct Setup to run silently, prevent prompting users to enter information, and prevent the installation from waiting for any user interaction. For more information about the syntax and Config.xml, seeDisplayĀ element inĀ Config.xml file in Office 20101.

NaN. Save the Config.xml file.

Make sure that no Office applications are running when you install Office 2010. For example, to install Office Professional Plus 2010 after you modify the Config.xml file to specify silent installation options, use the following command:

serversharesetup.exe /config servershareProPlus.WWconfig.xml

Where:

servershareĀ is the path of the Office Professional Plus 2010 source files.

/configĀ is a Setup command-line option that specifies the location of the Config.xml file. SeeĀ Setup command-line options for Office 20102.

servershareProPlus.WWconfig.xmlĀ is the location of your modified Config.xml file for Office Professional Plus 2010.

Note:

If you use the Config.xml file to set silent installation options as in the previous example, you will also want to use the Office Customization Tool (OCT) to create a Setup customization file (.msp file) to configure additional installation customizations. For example, you can use the OCT to specify previous versions of Microsoft Office applications to keep or remove. You can also set feature installation states by using the OCT to change the default way in which Office features are installed. For a complete description of the areas that you can configure by using the OCT, seeĀ Office Customization Tool in Office 20103. The OCT is available with Volume Licensing editions of Office 2010 (and the 2007 Office system). To determine whether your Office 2010 installation is a Volume Licensing edition, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a Volume Licensing edition. If the Admin folder does not exist, the disk is a retail edition.You can also set silent installation options by using the OCT. For more information, see theĀ Licensing and user interface4Ā section inĀ Office Customization Tool in Office 20103. (TheĀ LevelĀ attribute of theĀ DisplayĀ element in the Config.xml file is equivalent to theĀ Display LevelĀ option in the OCT). In enterprise deployments, we recommend that you set theĀ Display LevelĀ toĀ NoneĀ if using the OCT to ensure that Setup runs silently, to prevent prompting users to enter information, and to prevent the installation from waiting for any user interaction, including when files are being used. Setting theĀ Display LevelĀ toĀ NoneĀ assumes that theĀ Suppress modalĀ andĀ Completion noticeoptions are silenced and that theĀ I accept the terms in the License AgreementĀ check box is selected. As noted previously, administrators must also make sure that no Office applications are running during an installation of Office 2010.

Read the whole article @Ā http://technet.microsoft.com/en-us/library/gg998766.aspx#section4

PS -Ā For Lync: ā€œLyncSetup.exe /Install /Silentā€ will perform a silent install.

Need more help? Learn how ourĀ Managed ServiceĀ &Ā Cloud ConsultingĀ services can help your business.

This post has matured and its content may no longer be relevant beyond historical reference. To see the most current information on a given topic, click on the associated category or tag.

Related Posts

Critical Data Backup in Azure | Identify & Protect What Matters

Identifying Critical Data and Applications for Backup in Azure

Learn how to identify and prioritize your critical data and applications for backup in Azure to reduce risk, ensure business continuity, and meet compliance requirements.

Oct 3, 2025
5 min read
Microsoft 365 Backup Compliance | Key Risks & Best Practices

Compliance Considerations When Backing Up Microsoft 365 Data

Ensure your Microsoft 365 backups meet compliance requirements for CMMC, NIST 800-171, and other regulations. Learn key considerations to avoid violations.

Oct 3, 2025
6 min read
Azure Backup Needs Assessment | Plan Your Cloud Data Protection

Assessing Your Organization's Backup Needs for Azure Workloads

Learn how to assess your backup needs for Azure workloads, from compliance and recovery objectives to choosing the right tools for data protection and resilience.

Sep 26, 2025
6 min read
CUI Compliance and the Role of MSPs

Overview of CUI Compliance and the Role of MSPs

Explore the essentials of CUI compliance and how MSPs support DFARS, NIST 800-171, and ITAR requirements through secure IT services and expert guidance.

Sep 26, 2025
7 min read
Evaluating Data Retention Policies for Microsoft 365 and Azure

Evaluating Data Retention Policies for Microsoft 365 and Azure

Learn how to evaluate and manage data retention policies in Microsoft 365 and Azure to meet compliance, security, and operational needs.

Sep 26, 2025
6 min read
How MSPs Help Meet CUI Compliance Requirements

How MSPs Help Organizations Meet CUI Compliance Requirements

Learn how MSPs help organizations meet CUI compliance by offering expertise, secure environments, and ongoing support for DFARS and NIST 800-171 standards.

Sep 26, 2025
7 min read

Ready to Secure and Defend Your Data
So Your Business Can Thrive?

Fill out the form to see how we can protect your data and help your business grow.

Loading...
Secure. Defend. Thrive.

Let's start a conversation

Discover more about Agile IT's range of services by reaching out.

Don’t want to wait for us to get back to you?

Schedule a Free Consultation

Location

Agile IT Headquarters
4660 La Jolla Village Drive #100
San Diego, CA 92122