The effect is the package or installer won’t run as it never completes verification, making it impossible to install. This is a strange issue that can cause some alarm, because it can happen with both third party packages and installers, as well as updates and packages that come directly from Apple. I finally found the installer command. To install a package, type: sudo installer -pkg Desktop/Java1.4.1.pkg -target / In most cases, -target will be the root of your boot volume (/), but you may also specify /Volumes/OtherDrive. Also note that the installer will not prompt you if the update requires a restart.
The process of installing TMSM client on a single computer is similar to the installation process for other Macintosh software. During the installation, you may be prompted to allow connections to icorepluginMgr, which is used to register the client to the server. Allow this connection when prompted.
Do the following:. Get the client installation package (tmsminstall.mpkg.zip) from the TMSM server by doing any of the following:. Log on to the OSCE Plug-in Manager TMSM web console, go to Agents Agent Setup Files and click the link under Client Installation File.
The same page contains the link for Client Uninstallation File, which can be used to remove the client program from a Macintosh computer. Go to TMSMHTML ActiveUpdate ClientInstall and look for the tmsminstall.mpkg.zip file.
Launch the tmsminstall.mpkg file. When the installation notification appears, click Continue.
On the Introduction screen, click Continue to proceed. Read the reminders and click Continue. On the Installation Type screen, click Install. Enter your Name and Password to begin the installation process. Once the installation is completed, click Close. The client automatically registers to the server where the client installation package was obtained.
The client also updates for the first time. After the installation, check the following items to make sure that Trend Micro Security for Mac is properly installed:. The Trend Micro Security client icon shows on the menu bar of the Macintosh computer. The Trend Micro Security client files are found under the client installation folder.
The client appears on the web console's client tree. To access the client tree, click Client Management on the main menu. Run an initial update and scan by clicking Update Now and Scan Now. This step is recommended to begin protecting your computer. If the client cannot connect to the server, it downloads directly from the Trend Micro ActiveUpdate (AU) server.
Internet connection is required to connect to the ActiveUpdate server. Also, you need to run a manual update if it cannot connect to the server. This allows TMSM to get all the latest updates. The process of installing TMSM client on several computers can be simplified using Apple Remote Desktop. Do the following:. Check for and uninstall any security software on the Macintosh computers.
Get the client installation package (tmsminstall.mpkg.zip) from the TMSM server by doing any of the following:. Log on to the OSCE Plug-in Manager TMSM web console, go to Agents Agent Setup Files and click the link under Client Installation File. The same page contains the link to the Client Uninstallation File, which can be used to remove the client program from a Macintosh computer. Go to TMSMHTML ActiveUpdate ClientInstall and look for the file tmsminstall.mpkg.zip. Copy and then launch the package on the Macintosh computer with Apple Remote Desktop.
Launching the package unarchives the tmsminstall.mpkg file. The files on the package may become corrupted if users launch the package using archiving tools that is not built-in on the Mac. Instruct users to launch the package using built-in archiving tools, such as Archive Utility. Open the Apple Remote Desktop on the Macintosh computer.
Select the computers where you want to install the TMSM client and then click Install. On the Install Package screen, drag the installation package or click plus sign ( +) to locate the installation package. Click Save to automatically run the installation task on the new Macintosh computers that connect to the network.
You could do it all in one package built from Composer. Basically, get the latest volume license installer version to ensure you're not installing something really old like 14.0.0. Drop that package. Along with the current 14.4.8 updater into a folder in tmp/ called something like 'OfficeInstall' Create your choices.xml file according to the instructions shown on the OfficeforMac site and also drop that into the same folder in tmp/ Then create your Composer Source by dragging those 3 items into Composer. Now create a postinstall script that uses command line installer to first install the 14.3 full installer mpkg and also use the choices.xml file to customize the installation, and then run the 14.4.8 updater installer from that same path. All of this would be in one postinstall script. The total installation time will likely take longer than just a Composer capture to DMG might, but in the end you'll have a much cleaner installation.
Making it into an actual.pkg installer will also mean it can be used outside of the Casper Suite, as opposed to a.dmg. As for uninstallation, I would go the scripted route. The same OfficeforMac site has a really good script for uninstalling Office 2011 that I've used dozens of times during tests and it has always worked flawlessly. However, as Robert Hammen mentions, all of this really depends on how comfortable you are with making that choices.xml file and a postinstall script to utilize it. I use Composer only because the resulting PKG installs faster, then creating a single bundled installer.
I've created a single installer using Packages that first installs Office 14 SP3 and then 14.4.x updater, but it takes longer time for it to install then a pkg made in composer. Here's what has worked for us since we've been deploying Office 2011.
Setup a computer with a clean install of Mac OS X. Log in as a Admin account; not necessary to be root. Open Composer, select New Package - Normal Snapshot.
Name it: MicrosoftOffice2011-14.4.8 Install Office 2011 SP 3 using the install mpkg from Microsoft Complete the Office Assistance, but bogus info since we will delete the Users folder later on Check for updates via Help menu or download directly from Microsoft and install. Open Lync and and check for updates - for some reason it's not included when you update the Office suite.
Quit all Office apps. Within Composer, click 'Create Package Source' to take the final snap shot Delete the following files/folders /User/xxxxusername /Library/Application Support/.blahxxxxxx. (it's a long random character file name.) /Library/Preferences/.blahxxxxxx. (it's a long random character file name.) For both /Applications/Microsoft Office 2011 and /Applications/Microsoft Lync.app, set the owner to 'root' and the group to 'wheel'. And click the gear to 'Apply Owner and Group to' for both. Click the Build as PKG.
As you can see, I've done nothing to customize Office or avoid the Office setup assistant for our users. I have a second package that will install our custom template documents. Not a Casper user, but I'll take a swing.
The first thing to remember when playing with Installer Choices is that 'installer' will react to the software that's already installed on the target disk. Make sure you're doing this testing on a computer without the software of interest installed (e.g. Your startup disk with Office already installed) otherwise you may get weird results due to installer (properly) reacting to what's already there.
The proper installer switch (now) to determine available choices via 'installer' is no longer 'showChoicesXML' as mentioned, it's 'showChoiceChangesXML' (see 'man installer'). The Office for Mac Help page is centered around an older version of InstallerChoices that simulated faux 'clicks' in Installer.app-the newer format (de)selects specific choices in the pkg. To see the available options that are available with the newer format: installer -showChoiceChangesXML -pkg /Volumes/Microsoft Office 2011/Office Installer.mpkg -target / /officechoices.plist This outputs a plist-formatted list of choices and three attributes around them:. 'visible': Whether or not the choice is visible (e.g. Listed) in the GUI Installer.app. 'enabled': Whether or not the GUI Installer.app allows the state of the choice to be changed (i.e. Unchecked if it's checked, checked if it's unchecked).
'selected': Whether or not the choice will be installed The only attribute you're trying to really modify is 'selected' (everything else is Installer.app GUI trimmings), but the other two attributes are important since you really want to determine the intent of the pkg developer. For example, if the pkg developer doesn't make a choice 'visible' in Installer.app it's a pretty good bet that the developer doesn't want (and won't support) that Installer Choice being disabled. So let's trim down the giant plist above to just the choices: installer -showChoiceChangesXML -pkg /Volumes/Microsoft Office 2011/Office Installer.mpkg -target / grep -A1 choiceIdentifier grep -v choiceIdentifier sort uniq Which outputs in part: appsupport automator brazilian catalan communicator czech danish dcc dock Note your output may be slightly different, due to Microsoft swapping Communicator for Lync and other various changes to the Office 2011 installer.
Take a look at the various choices output by the above command-I'm going to guess that by following your nose. you'll be able to find the choice name that you want. Since you haven't specified what you're trying to remove, I'll choose 'communicator' for this discussion. Go look at the 'officechoices.plist' document made above and search for 'communcator'-there is the following snippet of XML: attributeSetting choiceAttribute visible choiceIdentifier communicator attributeSetting choiceAttribute enabled choiceIdentifier communicator attributeSetting 1 choiceAttribute selected choiceIdentifier communicator So the 'communicator' choice is 'visible' (=true) in Installer.app, it can be changed ('enabled'=true), and it's set to be installed (in this case by default) since it is 'selected'=1. Excellent- the pkg developer intentionally allows the user to change the state of this choice. You indicate in the choice changes file the options you'd like changed in the pkg, whether selecting or deselecting them (in this case you're deselecting them). Add as many dicts to the array as needed, however make sure you're acting against the actual options in your pkg (as mentioned, older Office 2011 installers include Communicator, while newer Office 2011 installers include Lync).
Regarding file naming, as long as the ChoiceChanges file is a valid plist, it can be named with a.plist extension, a.xml extension, any extension, or none at all. When an office 2011 dmg is created via Composer, do i have to remove any user files prior to creating the.dmg? I installed office, used the customization option and weeded out lync, outlook etc., after it finished installing I ran Word and went through the prompts (no to auto updates, no to improvement program.). Then I clicked composer to do the second snapshot.
![Apples Apples](http://spyrestudios.com/wp-content/uploads/mac-dmg/dmg-24.jpg)
After this second snapshot, and prior to creating the dmg, should any files be removed? I want it to FUT, FEU to avoid users getting those prompts the first time they run word, excel or whatever. I created the.dmg and deployed it to test computers and it works fine, but i'm just curious if i had to remove any files prior???
That's taking an axe to do the job that should be accomplished with a surgical knife. What I mean is that you are literally copying all preferences without any regarding to what preferences are actually being stored in those plist files.
Find out what preferences and settings exactly you want and where those preferences are stored in the plist. Use Composer to do a before and after snapshot if you must to determine where the plist are stored each time you change a setting in Word or Excel and so on. Then create a plist with those preferences you want and use a tool like MCXtoProfile to create config profiles to manage those preferences. I'll provide this to get you started but you should really look at what I mentioned and avoid creating snapshots like that. Do the handwork now and learn the minutia of every little thing that's changing when you set a setting so that you don't have to kill full preferences for users. The problem with taking snapshots of a full plist is that you are literally copying the entire plist file (all preferences) over to each user.
What happens if there is hardcoded path in the plist path that other users would not have access to? What if it's a setting that you didn't really mean to set? These are some of the issues that can come up with that approach: you end up copying preferences that you may not have intended to copy. It may work in most cases, but it only takes one situation for where it does not work and suddenly you're wondering where things went wrong. For example, in the case of Office 2011 if you literally copied the preferences as they are after having 'configured' Office to your liking, you have literally hardcoded the first and last name values for each user. Seems unimportant, right? But did you know that Microsoft uses that information so that applications can track who makes changes to documents (this is helpful for example if you've ever worked in Word and reviewed documents or make use of SharePoint)?
If your environment makes use of that future, you most definitely do not want to have that value hardcoded with something generic such as MYCOMPANYNAME. Or as another example, lets say you set the AutoRecovery folder to /Users/jsmith/random/path/ for one of the Office applications.
However, a new user (jdoe) logs into the computer, and they do not have access to /Users/jsmith/random/path/. That's a bit problematic. Now, imagine if jsmith doesn't even exist on each computer. I'm not sure where Office would try to create a recovery file, but I definitely don't want to find out in a worst case situation that the Auto Recovery feature was never working to begin with. By finding out that specific preference you want to change there are a few benefits: -you learn how the specific preference being changed in the plist file -you can now create a new plist specifically for the preferences you want to set -you can try to convert it into a configuration profile to manage using the method apple is trying to get everyone to use The commands I gave you change specific preferences and nothing more. However you probably want to change the location where the defaults command is writing to otherwise the command as is will write to /Library/Preferences which you may not want if there are other preferences already there and you are looking to make a config profile out of a plist.
![Installer Installer](/uploads/1/2/5/4/125464467/374233569.png)
Learning how to make configuration profiles is rather simple. is a free tool by to convert MCX or PLISTs into configuration profiles. And Casper also supports creating custom configuration profiles as well from plist files (Computers tab - Configuration Profiles - New - Custom Settings - Configure). Hopefully this makes sense.