For this, you’ll need a postflight script. The last piece is telling the installers to run. Once created, drag the noquit.xml file into the Additional Resources section of your Iceberg project. This should hopefully tell Office 2011 to not quit your browsers: Drag them into the Additional Resources section of your Iceberg project.Ĭreate the following choices.xml file and save it as noquit.xml. Select your Office 2011 and applicable Office 2011 update installer packages. In this case, I’m naming the project Microsoft Office 2011 SP2 14.2.2 That will open the project with the installation privileges automatically set to root. Since we’ll need to run this installer with root privileges, I recommend setting the project type to Darwin: Package. Volume-licensed Office 2011 SP 2 installer As an added bonus, I should be able to include the latest Office updates and thus be able to deploy a fully up-to-date Office 2011 SP 2 installer. Fortunately, after mulling it over for a bit, I realized that I had already solved this problem. I didn’t want to repackage with Composer, as I’m generally a believer in using the standard installer whenever possible. When I tried putting Microsoft’s unmodified Office 2011 SP 2 installer into Self Service and then installing it, the policy was failing. I’ve been working on getting Office 2011 SP 2 added to my work’s Casper Self Service, but I was hitting a problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |