Deploying SMARTReporter:
This guide should help you getting SMARTReporter deployed in your organization.
When installing SMARTReporter on a large number of Macs there are usually these requirements (though yours may differ substantially):
	• automatic installation on multiple Macs without manual work
	• have SMARTReporter not interact with the local user sitting in front of the Machine in any way, but just silently check for problems and contact the admin if a problem is detected

The way deployment is usually done requires two steps:
	1.) Configure SMARTReporter on one test machine in the desired way.
	2.) Push out the preconfigured installation to all the clients


1.) Configuring SMARTReporter:
1.1.) Visible Preferences:
You can set many important options using the normal SMARTReporter preferences window. You'll probably want to enable only notifications through e-mail and disable the local notifications to the user and set SMARTReporter not to be displayed in the dock or menubar. 
1.1.1.) Automatic Updates:
You might want to disable automatic updates using the Dock menus because this would require cooperation of the local user. Please ensure to regularly push out the latest version as they may contain important bug fixes.
1.1.2.) Activation:
Activating your eSellerate bought SMARTReporter copy on the test machine writes the serial number to the preferences file. Since the serial number is the same for every mac (if you bought enough copies at once or have a unlimited license) pushing this preferences file to the target macs will automatically have the activation work. The only thing left to do here is to make sure you use the hidden key (see section 1.2) to disable popping up a dialogue that the activation succeeded.
1.1.3.) E-mail:
You'll probably want to enable problem notification by email so you get informed whenever a problem occurs on any Mac. You'll probably NOT want to use email delivery through Mail.app because it depends on a properly configured local Mail.app installation and can be unreliable. The most relibable way to send email notifications is using the new (and default) option to send through our provided server (3.0.5). This has no dependencies except a working internet connection. We do not collect any information from the mails sent through our server, except when delivery fails so that the email can be retransmitted. If you can't use this option for some reason you can try the custom settings. Sending using "custom settings" has its own caveats because it uses the local keychain (and not the preferences file) for secure storage of the password (starting with version 2.5.3). Therefore you can't configure e-mail delivery on the test machine and expect it to work after deploying to other machines. You'll either need to make sure that the keychain is properly configured (to contain the password and let SMARRTReporter access it without warning) but this may be difficult to do remotely and automatically. The other option is to use a hidden option, see the next section.
1.2) Hidden Options:
SMARTReporter (3.0.4) contains hidden options to ease deployment. All keys should be written to SMARTReporter's normal preferences file, i.e. ~/Library/Preferences/com.corecode.SMARTReporter.plist
1.2.0.) Silent activation (1/2):
Set the key "esellerateActivateWithoutPrompt" to "1" to make SMARTReporter perform activation if necessary without asking for confirmation beforehand. Important: if the activation fails for some reason there will still be local interaction with dialogues!
1.2.1.) Silent activation  (2/2):
Set the key "SilentActivation" to "1" to make SMARTReporter not pop up a dialogue that the activation succeeded. Important: if the activation fails for some reason there will still be local interaction with dialogues!
1.2.2.) E-mail:
If you want to use "custom settings" email delivery you can set the key "DontUseTheKeychain" to "1" and the key "EmailPassword" to the actual password to use. This will make SMARTReporter use this password for email sending instead of using the keychain.

2.) Pushing the installation:
The only thing left to do is to push out SMARTReporter and the pre-configured preferences file to the target machines (using your preferred deployment tool) and make sure it gets launched 
• once now, to activate the copies with the serial number. please check that the activation succeeded
• and then every time any user logs in. your deployment software should contain options to do that, if not you can contact us for help. the built-in autostart function of SMARTReporter is not good enough for this purpose since it has to be manually activated on the target machine and only works for the user accounts it has been activated on.


Summary:
Deploying SMARTReporter should be easy if you are aware of the caveats and know the hidden options to make your life easier. If your use-case is a bit different or you need help please just contact us and we will work out everything with you.