I. Creating the Office 2010 MSP file for silent installation

  1. Insert the Office 2010 DVD into a system to build the MSP file on
  2. Copy the installation files to the desired directory on the build system                                           
  3. Download the Office 2010 Admin Template files: http://www.microsoft.com/en-us/download/details.aspx?id=18968
  4. Launch the Appropriate admin template file for the version you are installing                          
  5. Extract the Office 2010 Admin files to the folder where the Office files are located                      
  6. Initiate the Office Customization tool with the command below                                                     
  7. Select the desired version you are going to install                                                    
  8. Configure the Office install in the manner for which you would like it installed
  9. On the Licensing and user interface section, make sure to select the option to accept the terms in the License Agreement and change the display level to basic or none. The full display level will allow the end user to view/alter the install
  10. After the configuration has been completed and the MSP file has been saved, copy the MSP file to the Office Installation Updates folder                                      
  11. Like any deployment, you want to test your install before try to deploy it
    1. Run setup.exe – Since we put the MSP in the updates folder, we don’t have to call it when we launch setup.exe and it will automatically be called                                                                                                                                                                          NOTE: You will notice that even if you chose the None option for the display level, a momentary office install window will still appear.  This window is not able to be suppressed and any complaints regarding this needs to be directed to Microsoft as KACE has no control over it.                            
    2. When the install has been configured successfully, the files can be zipped up. For simplicity sake, use the following process for zipping the files:
      1. Navigate to the root of the install files since this will be the directory where the setup.exe file is located
      2. Select all files                                                                                                                            
      3. Right click and send to compressed/zip file                                                                                            
      4. A new zip file will appear and can be named as desired                                                    
      5. If this is the first system to have Office 2010 installed on it, you will want to force an inventory from the K1 so a record will be generated in the Software Inventory
      6. If this is the same system that is going to test the deployment from the K1, uninstall the office installation at this time

 

II. Building the Managed Install on the K1000

  1. Locate the listing for Office 2010 in your Software inventory (Inventory>Software Tab – I searched for 2010 and that greatly narrowed my results)                                                                                                                        
  2. Click the Software title to access the Software detail page                                                                          
  3. Select the Operating systems that are going to receive the Office install                                                 
  4. Locate and click the Browse button under the Associated Files section to upload the Desired zip file                  
  5. Navigate the File Upload selection window to the location where the Office 2010 zip file is located at                
  6. Click Save to upload the file and due to the size of the zip file, this will take a few minutes                                        
  7. Click the Distribution category. Using the Choose Action drop-down menu and select the option to Add New Item 
    1. On the Managed Software Installation Edit Detail page, select Office 2010 from the Software drop-down menu
    2. Since we are having to use a zip file to perform this install, Select to Configure Manually
    3. Since we put our MSP file in the Updates folder of our Office Build, all we need to do is call Setup.exe and our MSP will be called during the install without any special switches.    

      NOTE: At least during testing, I advise to not check the Delete Downloaded Files option in case the files are needed on the test system for troubleshooting the deployment. As soon as the MI is functioning as desired, this option can be used to keep from consuming too much disk space with large installs.

    4. Select the test system that will be used for testing                                                     
    5. Set the desired Deployment order, Max attempts, Deployment Window, and set any Pre/Post install message options and click Save
  8. Click into the new Managed Install and confirm that settings are set as desired. If all is well, change the Managed Action to Execute anytime (next available) and click Save                                              

III. Testing The New Managed Install

  1. Enable debug on the test computer using the following article: How to enable Debug
  2. Force an Inventory update on the test computer from Inventory>Computers Tab
  3. Monitor the test computer for installation.  Watching Task Manager is helpful to see when a fully silent install completes.  The Process that needs to be watched will be named Microsoft Setup Bootstrapper. Watching the C:\ProgramData\Dell\KACE\Downloads folder can also be helpful so that the end user can see the Folder created with the Software Item ID number and to see if the zip file was copied over.  Once the download has completed and the agent has validated the HASH, the install files will be extracted to the directory
  4. If the install doesn’t proceed, review the agent logs for any failure message(s) and correct the failure(s).  If the end user isn’t able to determine where the failure is from reading the logs, manually execute the install from command prompt using psexec.exe –s to test the install in a similar means as the agent will run it.

Comments

  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • This content is currently hidden from public view.
    Reason: Member is not approved yet
    For more information, visit our FAQ's.
  • Brilliant article, many thanks. Is there a switch I can add that will stop the end user PC from rebooting?
    Andy
Please log in to comment