AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
These options are typical for many customers who deploy Office in an enterprise environment. In addition, the installation operation will be silent, with a related verbose log file created in the %temp% directory. The following is a simplified example of a custom config.xml file, which can be used with volume license source files for Office 2010 Professional Plus to automate the process of inputting an Office MAK product key and activating the product at install time. If that fails for whatever reason (i.e., proxy issues, user rights, Internet connectivity issues, etc.), another attempt will not be made and Office users will later be prompted to activate Office 2010. NOTE: Adding the AUTO_ACTIVATE property to an install will trigger an attempt to activate only once. This blog post will expand on that a bit and explain how to perform the same actions using an MSP file created with the Office Customization Tool (OCT). In a previous Office Deployment Support Team Blog post, we explained how to automatically activate Office 2010 by using a customized config.xml file and setting element/property, AUTO_ACTIVATE.
0 Comments
Read More
Leave a Reply. |