Deploying ManicTime with preconfigured settings

You can only deploy ManicTime with preconfigured settings if you are using Windows authentication (Windows users)

Settings will mostly contain the location of ManicTime Server, so that the client knows where to send the data. This way there is no need to tweak every ManicTime installation.

You can then change ManicTime client settings in Administration, Client settings.

To deploy ManicTime to multiple machines you need ManicTimeSetup.msi file, which you can get on our download page. Then you need to create configuration file (ManicTimeTrackerSettings.json), which needs to be in the same folder as ManicTimeSetup.msi.

The easiest way to create ManicTimeTrackerSettings.json is to use your ManicTime server installation. Visit the server with the browser, then go to Administration section and click Create deployment file menu option (you need to be an admin on the server).

On the Create deployment file page, make sure that url to the server is correct. This must be an Url which will be accessible from the machines where ManicTime tracker will run. Copy the generated file in the same folder as ManicTimeSetup.msi.

When ManicTimeSetup.msi is executed, it will check for this file and apply any settings you defined.
You can put the ManicTimeSetup.msi and ManicTimeTrackerSettings.json to some folder on a shared drive and install it from there, or you can use Active directory to automatically push the installation to specific clients.

When more than one user is using the same computer

If more than one user is using the same computer, also copy this file in the same folder as ManicTimeSetup.msi and ManicTimeTrackerSettings.json

http://cdn.manictime.com/setup/custom/ManicTimeSetup.ini

This will ensure that ManicTime will run for all users.

Testing if settings work ok

On one machine you can double click on ManicTimeSetup.msi (ManicTimeTrackerSettings.json should be in the same folder) to install it. Once it is installed, it should work according to your settings and automatically send data to the server.
When it works ok, you can use Active directory to deploy it on other machines.

Using Active directory to deploy ManicTime clients

First installation


Put ManicTimeSetup.msi and ManicTimeTrackerSettings.json files on a shared folder. Then:

  1. Run Group Policy Management (gpmc.msc)
  2. Right-click on domain and select Create a GPO in this domain, and Link it here...
  3. Enter ManicTime and click Ok
  4. Select newly created group policy object
  5. On the right pane in the Security Filtering section select users you wish to assign ManicTime to
  6. Right-click on newly created group policy object and seled Edit...
  7. Open User Configuration, Policies, Software Settings
  8. Right-click on Software installation, select New, Package...
  9. Select ManicTimeSetup.msi - it should be on a network drive than can be accessed by all users
  10. Select Advanced and click Ok
  11. Select Deployment tab, select Assigned radio button and check Install this application at logon

Next time a user turns on his computer and logs in, ManicTime should be installed.

Upgrading to new ManicTime Desktop version


First, remove the current installation:
  1. Run Group Policy Management (gpmc.msc)
  2. Software installation -> right click ManicTime -> All Tasks -> Remove -> Allow users to continue to use the software
  3. Follow the steps for first installation


Deploy changed ManicTimeTrackerSettings.json file, without deploying new version

  1. Run Group Policy Management (gpmc.msc)
  2. Right-click on group policy object and select Edit...
  3. Open User Configuration, Preferences, Windows Settings, Files
  4. Right-click on Files, select New, File...
  5. Select Action "Replace"
  6. Select source file location for ManicTimeTrackerSettings.json - it should be on a network drive than can be accessed by all users
  7. Select destination file "c:\Program Files (x86)\ManicTime\ManicTimeTrackerSettings.json" - this path is for default manictime installation on 64-bit systems
  8. Select Common tab, check "Run in logged-on user's security context"
  9. Click OK


On the client you can issue this command for changes to take affect immediately.
gpupdate /force

You can also wait an hour or so and the file will be deployed automatically.

Feedback and Knowledge Base