Office 2. 01. 6 installation – 4sysops. Before deploying Office 2. In this article, I’ll cover how to customize the Windows Installer–based version of Office 2. Office 2. 01. 3. I’ll also describe some of the settings you may want to consider for your install. HP Reinvent. World Partner Forum showcases digital transformation and the future of Print, Personal Systems and Everything as a Service. View press kit. Kyle Beckman works as a systems administrator in Atlanta, GA supporting Office 3. He has 1. 7+ years of systems administration experience. Latest posts by Kyle Beckman (see all)If you’re deploying Microsoft Office 2. MSP file using the Office Customization Toolkit (OCT) for OS deployment and use automated software deployment solutions such as System Center Configuration Manager. Customize the install ^To begin, you’ll need a copy of the Microsoft Office 2. InformationWeek.com: News, analysis and research for business technology professionals, plus peer-to-peer knowledge sharing. Engage with our community. On the Notification Server virtual machine, open the Altiris Console. Click the Tasktab. In the left pane, select Software Management> Patch Management> Manage.ISO image (Windows Installer version, not the App- V version), as well as the Office Customization Toolkit (which also includes the Office 2. Administrative Templates). Extract both the ISO and the contents of the ADMX/OCT download. For my lab environment, I have a software file share on a file server, and I’ve created separate x. Office_2. 01. 6 folder to store both installers. The network share and file permissions are configured so that Domain Computers have Read access and IT users have Full Control, but your permissions may vary based on your environment and software installation solution. Copy the “admin” folder from the Office Customization Tool download into the folder where you’ve saved the Office 2. In this tutorial, we’ll be using the x. When you’re prompted, overwrite the files that are in the destination folder. Copying the updated admin folder to the Office 2. Next, you’ll need to open a command prompt and run setup. Office Customization Tool. When the OCT opens, leave the default Create a new Setup customization file for the following product option selected and click OK. Creating a new Setup customization file for Office 2. There are three main areas that you’ll definitely want to customize for your organization’s Office 2. Setup section. Start by setting your organization name in the Install Location and Organization Name section. Next, go to the Licensing and User Interface section. Most organizations with a licensing agreement will probably leave the default Use KMS client key option, but you can set a MAK key here if necessary. Select the I accept the terms in the License Agreement check box so that end users won’t see the license agreement when Office is installed. Last, set the display level to None and select the Suppress modal and No cancel check boxes. Leave the Completion notice check box cleared. These options will give you a silent installation without a final confirmation. Setting the product key, license agreement, and display level for Office 2. Next, go to the Remove Previous Installations section. Here you can choose which previous versions of Office applications are uninstalled when Office 2. I’ve had some unexpected results in the past when using the Default Setup behavior. So, I usually configure all of the applications to be removed unless I need to leave certain applications installed on the client system. Removing previous Office installations when installing Office 2. Once you’re done with your customization, click File and then Save and save your MSP file to the same network share where you’ve saved the Office 2. I usually like to put it in the root of the same folder as the installer. Install the customized Office 2. To install Office 2. MSP file, you’ll need to run setup. Your command should end up looking something like this. Office_2. 01. 6\x. Office_2. 01. 6\x. Office_2. 01. 6. MSP1\\fileserver\software\Office_2. Office_2. 01. 6\x. Office_2. 01. 6. MSPInstalling Office 2. MSP file. Remove Office 2. Depending on which components of Office 2. Office 2. 01. 3 completely. To do this, you’ll need the setup. Office 2. 01. 3. Create a new text file called Silent. Uninstall. Config. Office_2. 01. 3\Pro. Plus. WW\ folder with the following text (if the file already exists, make the following edits to the file). Configuration Product="Pro. Plus">. < Display Level="none" Completion. Notice="no" Suppress. Modal="yes" Accept. Eula="yes" />. < /Configuration> < Configuration Product="Pro. Plus"> < Display Level="none"Completion. Notice="no"Suppress. Modal="yes"Accept. Eula="yes"/> < /Configuration> Running the following command will remove the remnants of Office 2. Office_2. 01. 3\setup. Pro. Plus /config \\fileserver\software\Office_2. Pro. Plus. WW\Silent. Uninstall. Config. Office_2. 01. 3\setup. Pro. Plus/config\\fileserver\software\Office_2. Pro. Plus. WW\Silent. Uninstall. Config. Additional customization options to consider ^In addition to the settings I’ve already covered, you can also pre- configure a number of user settings when Office is installed on a computer. These settings are included in the Group Policy ADMX files, but they can be useful if you don’t want to manage Office with Group Policy or if you need a pre- configured build for non- managed systems. There are quite a few settings in Features > Modify User Settings, but following are a few you might want to consider for your installation. Modify User Settings section in the Office 2. Office Customization Tool. Application. Sub- Section. Setting Name. Notes. Microsoft Office 2. Privacy > Trust Center. Disable Opt- in Wizard on first run. When set to Enabled, suppresses a dialog end users don’t need to see. Microsoft Office 2. Privacy > Trust Center. Enable Customer Experience Improvement Program. Enables/disables Customer Experience Program; some organizations don’t want their PCs participating. Microsoft Office 2. Privacy > Trust Center. Send Office Feedback. Allows/prevents end users from sending feedback to Microsoft about Office; some organizations don’t want their PCs participating. Microsoft Office 2. Privacy > Trust Center. Allow including screenshot with Office Feedback. Allows/prevents PC from sending screenshots with Office Feedback. Microsoft Office 2. Services > Fax. Disable Internet Fax feature. Disables Internet Faxing in Office apps. Microsoft Office 2. Miscellaneous. Show One. Drive Sign In. Shows/removes option to sign into One. Drive. Microsoft Office 2. Miscellaneous. Control Blogging. Prevents end users from using Office apps to post to blogging platforms. Microsoft Office 2. Miscellaneous. Block signing into Office. Blocks/allows signing into Office (consumer) and Office 3. Org ID only only allows Office 3. One. Drive consumer access. Microsoft Office 2. First Run. Disable First Run movie. When set to Enabled, suppresses a dialog end users don’t need to see. Microsoft Office 2. First Run. Disable Office First Run on application boot. When set to Enabled, suppresses a dialog end users don’t need to see. Win the monthly 4sysops member prize for IT pros Users who have LIKED this post: Related Posts. SCCM and Group Policy update rings make updates easier. Place a workstation out of service remotely with Power.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |