Deploying the 2007 Office system by using System Center Configuration Manager


Hello, my name is Ross and I’m one of the technical writers for the Office Resource Kit. I’m posting a draft copy of this article in order to receive your (customer) feedback before the article is published in the 2007 Office Resource Kit on Microsoft TechNet, located here: http://technet.microsoft.com/en-us/library/cc303401.aspx.

I would greatly appreciate your input. For example, is the information adequate? Do you like the layout? What improvements would you suggest? Thank-you for taking the time to read this article and (hopefully)  provide feedback.

—-

Deploying the 2007 Office system by using System Center Configuration Manager

January 2009 – Draft Copy

 

 

Summary

This article provides detailed technical guidance on the processes and procedures when using Microsoft System Center Configuration Manager 2007 to deploy the 2007 Microsoft Office system in a medium to large enterprise corporate environment. This article includes the following sections:

·         Overview

·         Introduction to the deployment process

·         Deploying the 2007 Office system in a test environment

·         Resources for deploying the infrastructure

 


 

Overview

Microsoft System Center Configuration Manager 2007 is the solution to comprehensively assess, deploy, and update your servers, clients, and devices across physical, virtual, distributed, and mobile environments. This article provides detailed technical guidance for specifically deploying the 2007 Microsoft Office system.

Although this article illustrates the test network environment used for helping to describe the process of deploying the 2007 Office system by using System Center Configuration Manager 2007, it does not provide information about how to set up the test network infrastructure, such as the Active Directory directory service, Microsoft SQL Server, and System Center Configuration Manager. However, it does provide links for setting up a similar network infrastructure. This information is located in the last section of this article, “Resources for deploying the infrastructure.”

Audience

The target audience for this article is IT professionals. These IT professionals could include network managers, consultants, and IT managers who work for or with medium to large enterprises.

Prerequisites

Prior knowledge and experience will help users understand and apply the information in this article, particularly experience in the following areas:

·         Microsoft Systems Management Server (SMS) 2003 or System Center Configuration Manager 2007

·         Office Customization Tool (OCT)

·         2007 Microsoft Office system, Microsoft Office 2003, or Microsoft Office XP

Introduction to the deployment process

Once you have your supporting infrastructure in place for System Center Configuration Manager, the process for deploying the 2007 Office system involves creating and defining five primary areas:

·         Collections

·         Packages

·         Distribution points

·         Programs

·         Advertisements

Collections   Collections are groups of System Center Configuration Manager resources, such as users, user groups, or computers, against which a software deployment is targeted. For additional overview information about collections, see “Collections Overview” located at the following link: http://technet.microsoft.com/en-us/library/bb680321.aspx.

Packages   A package is the set of installation source files that System Center Configuration Manager manages and distributes for software deployment. Some of the information included within the package is the distribution points and programs. For additional overview information about packages, see “About Packages” located at the following link: http://technet.microsoft.com/en-us/library/bb680855.aspx.

Distribution points   Distribution points are System Center Configuration Manager site systems that store designated packages for deployment to System Center Configuration Manager clients. When the System Center Configuration Manager client receives and processes a relevant advertisement, the client then contacts a distribution point to download the package and start the installation process. For additional overview information about distribution points, see “About Distribution Points” located at the following link: http://technet.microsoft.com/en-us/library/bb680614.aspx.

Programs   Programs are part of the package configuration in System Center Configuration Manager, and most importantly, define the setup program that must be run. A program can also include any command-line switches and additional parameters that are required to install and customize the package. For additional overview information about programs, see “About Programs” located at the following link: http://technet.microsoft.com/en-us/library/bb632775.aspx.

Advertisements   Advertisements tie packages and programs together with collections, enabling administrators to target software deployment of specific or customized applications to collections of computers or users. An advertisement specifies a package and program, and the collection to which it will be advertised or deployed. For additional overview information about advertisements, see “About Advertisements” located at the following link: http://technet.microsoft.com/en-us/library/bb694110.aspx.

Deploying the 2007 Office system in a test environment

This section provides a diagram and description of the test network environment for the System Center Configuration Manager infrastructure. It also includes procedural information of the steps for deploying 2007 Microsoft Office Enterprise by using System Center Configuration Manager.

Network environment

The test network environment for this article is shown in the following illustration.

 SCCM_Network_Diagram


All of the servers (A, B, and C) are running Windows Server 2008 and are members of the same domain (CPANDL.COM), including the client computers (D), which are running Windows Vista Enterprise. The applications and roles that each server is running, and the fully qualified domain name (FQDN) for each client computer, are listed as follows:

A.      Active Directory, DNS, DHCP <DC.CPANDL.COM>

B.      SQL Server 2008 <SQLSRV.CPANDL.COM>

C.      System Center Configuration Manager 2007 R2 (Management Point, Distribution Point) <SCCM.CPANDL.COM>

D.      Windows Vista Enterprise, System Center Configuration Manager client <WVC01.CPANDL.COM>

Although in this simple test network environment the site server is performing multiple site system roles (management point and distribution point) simultaneously, this configuration is not recommended for production sites that have large numbers of resources.

Procedural steps for deploying the 2007 Office system by using System Center Configuration Manager

In this example, deployment scenario detailed information is provided for deploying 2007 Office Enterprise in the previously defined System Center Configuration Manager test environment. By following these steps, you can use System Center Configuration Manager to deploy a silent installation of the 2007 Office system, where the users do not interact with the installation process.

In this example, the first step is to create a customization file for the silent installation of the 2007 Office system.

Create a Setup customization file for the 2007 Office system

In the 2007 Office system, Setup controls the entire installation, including processes that Windows Installer handled in previous Office versions. Customizing the default behavior of Setup allows you to control the process. In this example, you customize the installation for a silent installation of the 2007 Office system.

The Office Customization Tool (OCT) is used to create a Setup customization file (MSP file). Setup applies this file when Office is installed on the computers.

To customize Office Setup, you use the command line setup.exe /admin to start the Office Customization Tool. In this example, using System Center Configuration Manager to deploy the 2007 Office system, at a command prompt you run setup.exe /admin from the package source directory, \SCCMOffice2007Enterprise.

To ensure that the 2007 Office system is silently installed, you need to modify and configure the settings as follows:

On the Licensing and user interface dialog box, set the Display Level to None, which will then enable the Suppress modal check box. Verify that the Completion notice and No Cancel options are not selected. Enter a valid 25-character volume license key in the Product Key box located under Licensing and user interface. Select the I accept the terms in the License Agreement check box.

Save and name the newly created MSP file and place it in the Updates folder for the 2007 Office system on the computer that contains the package source directory, which in this example is \SCCMOffice2007EnterpriseUpdatesCustomFileOffice2007SilentInstall.MSP.

For additional information about how to customize the default behavior of Setup for the 2007 Office system, see “Customize Setup before installing the 2007 Office system” located at the following link: http://technet.microsoft.com/en-us/library/cc179121.aspx.

Create a collection

This section provides the details for using direct membership rules to create a collection in System Center Configuration Manager. This allows for selecting the computer resources of the targeted computers.

For additional information about the membership rules, including both query and direct, see “About Membership Rules” located at the following link: http://technet.microsoft.com/en-us/library/bb680821.aspx.

To create a collection, in the Configuration Manager Console, navigate to System Center Configuration Manager / Site Database / Computer Management.

Right-click Collections, and then click New Collection. On the General dialog box of the New Collection Wizard, enter a name for the collection. In this example, it is named “Target-Computers”.

On the Membership Rules dialog box, click the computer icon, which opens the Create Direct Membership Rule Wizard. Click Next.

On the Search for Resources dialog box, click the Resource class drop-down menu and select System Resource. Then, click the Attribute name drop-down menu and select Name. In the Value field enter %, and then click Next.

On the Collection Limiting dialog box, click the Browse button, select All Windows Workstation or Professional Systems, and then click Next.

On the Select Resources dialog box, select the check box for each of the targeted computer resources. In this example, TestComputer01 and TestComputer02 were selected. Click Next, and then on the Finished dialog box, click Finish. On the Membership Rules dialog box of the New Collection Wizard, click Next.

On the Advertisements dialog box, for now, do not assign an advertisement because it is not yet created. Click Next. On the Security dialog box, accept the defaults, click Next, and then click Close.

The next step is to create a source directory for the package.

For more information about collections, see “Collections in Configuration Manager” located at the following link: http://technet.microsoft.com/en-us/library/bb693730.aspx.

Create a package source directory

The package source folder contains all the files and subdirectories needed to run the programs in a package. In this example, the source directory is \SCCMOffice2007Enterprise, which contains a copy of the 2007 Office Enterprise installation CD. However, to reduce the size of the package file created by System Center Configuration Manager, the additional files that are not needed (such as other languages and programs within the Office Suite that will not be deployed) have been removed from \SCCMOffice2007Enterprise. In this example, only English is deployed; therefore, the program directories that do not end with “en-us” have been removed.

For more information about multiple language deployments, see “Customize and deploy multiple language versions of the 2007 Office system” located at the following link: http://technet.microsoft.com/en-us/library/dd162397.aspx.

For more information about package source directories, see “How to Set Up a Package Source Directory” located at the following link: http://technet.microsoft.com/en-us/library/bb633067.aspx.


Comments (23)

  1. RossC says:

    Hi Alex, you can use the setup property, SETUP_REBOOT, with the value of, Never, to avoid the forced reboot at the end of the installation. This can be done by using the Office Configuration Tool (OCT) or the config.xml file to customize the setup process. For more information please reference the articles under the following topic, Setup reference for Office 2010, located here: http://tnstage.redmond.corp.microsoft.com/en-us/library/cc179099(office.14).aspx

  2. Anonymous says:

    Feed: The Configuration Manager Support Team Blog Over on the Office Resource Kit blog it looks like

  3. RossC says:

    Hi Safdar, here are some troubleshooting steps from a previous post to the updated version of this article.

    Also, the final version of this article has been posted to TechNet, located here: http://technet.microsoft.com/en-us/library/dd630737.aspx

    Here are some troubleshooting steps to hopefully help isolate the problem.

    1) Make sure you are using a volume license – requisite for silent install

    2) On the targeted client computer(s) in the WindowsTemp directory there should be a log file (if setup.exe started) for the attempted installation of Office. It would be named: SetupExe(20090310xxxxxxxxx).log – where year, month, and day are the first 8 digits within the enclosed parenthesis. If you are not seeing a .log file for Office setup then the troubleshooting should be within SCCM, which contains multiple log files for troubleshooting.

    3) If you do see the SetupExe(xxxxxxxxxxxxxxxxx).log then open the file to see if there are any errors indicating why setup did not complete.

    4) One possible reason would be if you are testing in a lab environment without internet access and there are update files from the Office DVD source in the Updates folder which require access for validation.

    5) Another possible reason is if you import the "EnterpriseWW.msi" file when creating a program for SCCM but are actually installing Office Professional Plus (ProPlus), which was referenced when you created the .msp file using setup /admin.

    6) Finally, as a troubleshooting step you can try creating a new .msp file with only one product (such as MS Word) from the Office 2007 Suite. This is done when using setup /admin (using the OCT). You can select which products to install under Features | Set feature installation states.

  4. RossC says:

    Hi Stopspamjunk, it is possible that you are using a different version of Office 2007 – instead of the Enterprise version used as an example throughout this article (http://technet.microsoft.com/en-us/library/dd630737.aspx).
    For example, if you have Microsoft Office Professional Plus 2007 then the file would be proplusww.msi. Here are some links that may be of further assistance:

    How to determine which version of a 2007 Office product is installed –
    http://support.microsoft.com/kb/928116

    Run Setup from the local installation source to install the 2007 Office system –

    http://technet.microsoft.com/en-us/library/cc179070.aspx

    If needed, there is always the option of contacting Microsoft’s Technical Support –

    http://support.microsoft.com/common/international.aspx?RDPATH=dm;en-us;select&target=assistance

  5. RossC says:

    Andy, thank-you for your feedback. Here are some troubleshooting steps:

    1) Try setting Display Level to Basic – instead of None. This will allow you to see if there are any messages (install related or error) that appear during the install.

    2) If SCCM timed out because of network bandwidth issues then you can try precaching the Office files to the local hard drive before the install from SCCM.

    3) I’ve included some links below with additional troubleshooting information that also may be of assistance.

    If these additional troubleshooting do not help isolate and resolve the issue please either post back here or send feedback to "feedork@microsoft.com". I will then continue to assist.

    http://social.technet.microsoft.com/forums/en-US/configmgrswdist/thread/d1170085-2707-41a4-8753-68b51f9cee17/

    http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/5d015073-10c3-4ea0-9eea-79d34a353f3e/

    http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/026f7559-a5a0-460c-947b-12560ec599cb/

  6. RossC says:

    Hi Safdar, I’m glad to hear you were able to do a silent install of Office 2007 using SCCM. Here are some references that may assist you in deploying an OS using SCCM:

    TechNet Webcast: Deploying Operating Systems with System Center Configuration Manager 2007 –

    http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032352696&CountryCode=US

    The Configuration Manager Support Team Blog –
    http://blogs.technet.com/configurationmgr/default.aspx

  7. RossC says:

    TBailey, thank-you for your feedback. I’m pleased to hear that this information was helpful.

  8. Anonymous says:

    enterpriseww.msi is missing from my computer

    I didn’t want outlook but everytime I click on anyones link to do an email it always tries to open outlook instead of yahoo.com or telling me the email address.

    Since I removed outlook from my system those clicks causes my computer to go wakoo in that it keeps opening new tabs with error and I literally have to force reboot my computer to stop it.

    Then I learned that my computer is missing enterpriseww.msi could this be the problem and if so how do I put that in my computer?

  9. RossC says:

    Hi Safdar, did the log file provide any error messages? Also, you can look in the Windows Event Viewer under the log files there – seeing if there are any errors that correspond to the time stamps in the log file in the WindowsTemp directory.

    For more information about the updates folder see the "Updates Folder" section in the following link:

    http://technet.microsoft.com/en-us/library/cc178995.aspx.

    The reason I suggested trying one application only, such as Word, is to try and isolate whether one of the other applications is causing the problem. For example, another customer found the problem to be related to Access. Here’s a quote from the previous
    post: "…I figured out why it was failing. In my OCT file, I configured ACCESS as "Installed on 1st use", but it required "Visual Basic for Applications", which needed user intervention.  That’s why the Setup.exe was hanging in the process.  I reconfigured
    the program to "Allow users to interact with this program", re-deployed the package, ran the advertisement, saw what the problem and fixed it."

    If needed, there is always the option of contacting Microsoft’s Technical Support –

    http://support.microsoft.com/common/international.aspx?RDPATH=dm;en-us;select&target=assistance

  10. Anonymous says:

    Feed: The Configuration Manager Support Team Blog Posted on: Monday, February 09, 2009 6:38 PM Author

  11. RossC says:

    Kju, thank-you for your feedback. I’m pleased to hear that this information was helpful.

  12. Anonymous says:

    Over on the Office Resource Kit blog it looks like Ross posted the latest draft of the article describing

  13. Anonymous says:

    Feed: The Configuration Manager Support Team Blog Over on the Office Resource Kit blog it looks like

  14. RossC says:

    Today(02/26/09)an updated copy of this article was posted on the Office Resource Kit Blog. Please see:

    "Updated – Deploying the 2007 Office system by using System Center Configuration Manager". Thank-you again for all of your feedback.

  15. Sandy Wood says:

    We struggled with this one for weeks to get a silent install using SCCM. We couldn’t get the Licensing and user interface,Suppress modal, or Completion notice UIs to work with just a .msp alone. We found that the only way to run it silently in SCCM was to create a custom config.xml file and that did the trick. Our command-line looks like this:

    setup.exe /config proplus.wwconfig_silent.xml /adminfile BasicInstall_1_Silent.msp

  16. Andy says:

    I have read through and tested your procedure, but I still seem to be having problems with the deployment.  It seems my install hangs, setup.exe is running but nothing happens.  after the 2 hour run time limit is reached, it ends and gives an error 10070, Program failed (run time exceeded). Is there soemthing I am missing?  I followed as best I can to fit my SCCM system.

  17. Kju says:

    Hi all,

    Ross thanks, your post very informative.

    Sandy Wood  thankkksss :)) your solution 100% works

  18. TBailey says:

    I just followed this step-by-step, and it worked great.

    Took a little over an hour to push out to 3 clients on a virtual test network.

    Thanks!

  19. Safdar Rizvi says:

    I have read through and tested your procedure, but I still seem to be having problems with the deployment.  It seems my install hangs, setup.exe is running but nothing happens.  after the 2 hour run time limit is reached, it ends and gives an error 10070, Program failed (run time exceeded). Is there soemthing I am missing?  I followed as best I can to fit my SCCM system.

    I have tried everything and yet no luck. I was able to deploy adobe with no problem. I am testing office 2007 deployment in our lab.

  20. Safdar Rizvi says:

    Sorry for getting back so late, I was out for 2 days. Here is the situation.

    We do have volume license.

    I do see On the targeted client computer(s) in the WindowsTemp directory there should be a log file (if setup.exe started) for the attempted installation of Office

    We definetly do not have internet access, because we are in test lab and i am not sure about this step.

    I did import EnterpriseWW.msi file and installing enterprise version.

    I did not try to install MS Word only.

    If i say allow user to interact with program then installation works and enterprise version gets installed on client computer, but user do have to choose enterprise version and then click contiue to finish installation.

    Please let me know what else i can try to do silent install.

  21. Safdar Rizvi says:

    I used our production version of office 2007 installation and was able to deploy. I will do other troubleshooting later on.

    Now i was test deploying operating system. First step is to install WDS and when i go to add and remove component i do not see WDS option and do not why? I am using Windows 2003 R2 SP1. Can you help me on that please? In meanwhile, i will do more research.

    I already have Windows AIK installed and Deployment toolkit.

    Thank you,

    Safdar Rizvi

  22. alex says:

    Hi,

    The procedure works perfect! 10x

    I have a scenario and i nedd help with it!

    I want to deploy outlook’07 with sccm in my organization where i have only outlook’03.

    I don’t want to close outlook’03 during install(upgrade) and i don’t want to restart the machines after the setup finishes.

    I’ve tested the silent install and the setup works fine with outlook’03 opened, but after setup finishes i get a big force restart, and i want to avoid that.

    Thanks!