Difference between revisions of "MailStore Client Deployment"

[unchecked revision][checked revision]
 
(34 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Using a software distribution system, MailStore Client can be distributed among the users' computers automatically. To be able to do so, the distribution system must be able to execute MailStore Client's setup program without requiring any input or confirmations.
+
{{GPO Preamble|Client}}
  
Please note: Administrators can find a brief description of deployment without using group policies in chapter MailStore and Active Directory, section Deploying MailStore Client.
 
 
= Using Group Policies =
 
 
== Installation ==
 
== Installation ==
In addition to being installed manually, MailStore Client can also be distributed to all user computers using Active Directory. Once the distribution process is set up successfully, MailStore Client will be installed automatically when the user logs on. This process runs in the background and requires no action on part of the user. Immediately after the distribution, the user can start and use MailStore Client as usual. A shortcut icon on the desktop is created automatically.
+
{{GPO Installation|Client}}
  
Example: Setting up distribution in Windows Server 2003
+
{{GPO Distribution|2019|Client}}
  
* Download MailStore Client in .msi format from the MailStore website http://www.mailstore.com/de/mailstore-server-download.aspx
+
<div class="msnote">'''Please note:''' To avoid problems when installing software using group policies, the following settings should be applied via group policy for computer objects which represent the Windows clients of MailStore users:
* Save MailStore Client in a directory on the server that is released and accessible to all users of the domain. 
+
* ''Computer Configuration > Administrative Templates > System > Scripts > Run logon scripts synchronously''
* Open the Group Policy Management Console. If this is not available, download the installation routine under http://www.mailstore.com/?gpmc.
+
* ''Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon''
* Install the console.
+
</div>
* Open the group policy management console of the Windows server
 
* Right-click on the administrative folder Group Policy Objects, select New and create a new group policy object called MailStore Deployment. 
 
*: [[File:Tech_client_01.png|center]]
 
* Highlight the new object and click on Edit. Expand User Configuration and Software Settings and right-click on Software installation. Select New and Package...
 
*: [[File:tech_client_02.png|center]]
 
* Select an MSI package. Please keep in mind that the path for the file must be entered in UNC notation (e.g. \\Server\Setup\MailStoreClientsetup...) and that the users of the domain have to have read-access to this directory share.
 
* In the following dialog window, select Advanced and click OK.
 
*: [[File:Tech_client_03.png|center]]
 
* On the next screen, please select the settings as shown below:
 
*: [[File:Tech_client_04.png|center]]
 
* Click on OK to confirm all settings. The group policy should look similar to the one shown below:
 
*: [[File:Tech_client_05.png|center|520px]]
 
* Close the group policy editor. The group policy is now configured and can be linked to the corresponding user objects. Linking is done using organizational units (OU).
 
* Highlight the organizational unit (OU) which contains the desired user objects, right-click on the OU (DE_Viersen in the example below) and select the option Link an Existing GPO. In the dialog window Select GPO, highlight MailStore Deployment and click on OK.
 
*: [[File:Tech_client_06.png|center|520px]]
 
* The group policy is now available and becomes active the next time users log on to the Windows client.
 
  
 
== Updating ==
 
== Updating ==
With group policies, the MailStore Client software on the user machines can be updated automatically. This becomes necessary if MailStore Server is updated because the server can only be accessed by clients with the same software version. To edit an existing MailStore deployment group policy so that an automatic update of the clients can be performed, please proceed as follows:
 
 
* Open the existing group policy MailStore Deployment. Create a new package and select the updated MailStore Client MSI file. In the following dialog window, select Advanced and click on OK. Please select the settings as shown below:
 
*: [[File:Tech_client_07.png|center]]
 
* In the Updates tab, click on Add and select the software to be updated. Choose the settings as shown below and click on OK and confirm by clicking on OK again.
 
*: [[File:Tech_client_08.png|center|520px]]
 
* The group policy should look similar to the one in the following graphic:
 
*: [[File:Tech_client_09.png|center|520px]]
 
  
MailStore Client will be updated the next time users log on to their Windows workstations.
+
The MailStore Client MSI installs basically only a loader that actually loads the latest MailStore Client components from the MailStore Server. In case this loader needs to be updated itself, group policies can do the update automatically on the MailStore user computers. To edit an existing ''MailStore Client Deployment'' group policy so that an automatic update of the clients can be performed, please proceed as follows:
  
To avoid complications when installing software using group policies, the following settings for the MailStore Deployment group policy should be adjusted as well:
+
{{GPO Update|2019|Client}}
  
* Computer Configuration/Administrative Templates/System/Scripts\Run logon scripts synchronously [activated]
+
The MailStore Client loader will be updated upon the next login of the users on their Windows workstations.
* User Configuration/Administrative Templates/System/Logon\Always wait for the network at computer startup and logon [activated]
 
  
 
== Configuration ==
 
== Configuration ==
{{:Installation_of_Group_Policy_Template}}
 
 
= Without using Group Policies =
 
== Installation ==
 
The silent installation of MailStore Client requires the regular setup program, which can be downloaded from the MailStore website. The request for the silent installation is made to the command line. For example:
 
  
  MailStoreClientSetup.exe /SP- /SILENT /SUPPRESSMSGBOXES /LOG="log.txt" /NOCANCEL
+
{{GPO Templates|2019|Client}}
  
The command line used in this example will execute a setup which does not require any input or confirmations yet displays the current status of the installation on the screen. To hide the installation progress, simply exchange /SILENT with /VERYSILENT:
+
{{GPO Configuration|2019|Client}}
  
  MailStoreClientSetup.exe /SP- /VERYSILENT /SUPPRESSMSGBOXES /LOG="log.txt" /NOCANCEL
+
== Uninstalling ==
  
 +
{{GPO Uninstalling|Client}}
  
 
[[de:MailStore Client Deployment]]
 
[[de:MailStore Client Deployment]]
 +
[[en:MailStore Client Deployment]]

Latest revision as of 11:36, 28 June 2022

A MailStore Server installation includes the MailStore Client as a Windows Installer package (MSI) that can be installed on client machines using software distribution. You can either find the MSI package via the link on your desktop Install MailStore Client on other Computers or in the Setup-<version> folder of your MailStore Server installation folder.

This article describes the distribution and configuration of MailStore Client through Active Directory group policies.

Installation

To distribute the MailStore Client via Active Directory you have to copy its MSI package to a share on your server that is accessible to all domain users. After the distribution has been set up the MailStore Client will be installed automatically upon the next user login. This process is transparent to users and needs no interaction on their behalf.

Set up the software distribution as follows:

  • Open the Group Policy Management Console on your domain controller.
  • Right-click on the administrative folder Group Policy Objects
  • Select New and create a new group policy object called MailStore Client Deployment.
    GPO Client 2019 01.png
  • Right-click on the new GPO and select Edit....
  • Expand User Configuration > Policies > Software Settings.
  • Right-click on Software installation.
  • Select New and Package....
  • Select the above mentioned MSI package. Please note that the path for the file must be entered in UNC notation (e.g. \\Server\Setup\MailStoreSetup...) and that domain users need to have read-access to this share.
  • In the following dialog window, select Advanced and click OK.
    GPO Client 2019 02.png
  • On the next screen, please set the options on the Deployment tab as shown below:
    GPO Client 2019 03.png
  • Click on OK to confirm all settings.
  • The group policy should look similar to the one shown below:
    GPO Client 2019 04.png
  • Close the group policy editor.

The group policy is now configured and can be linked to the corresponding user objects. Linking is done using organizational units (OU).

  • Highlight the organizational unit (OU) which contains the desired user objects, right-click on the OU (Seattle in the example below) and select the option Link an Existing GPO....
  • In the dialog window Select GPO, highlight MailStore Client Deployment and click on OK.
    GPO Client 2019 05.png
  • Through the organizational unit the group policy is now linked to the user objects contained therein. It will become active the next time users log on to the Windows clients.
Please note: To avoid problems when installing software using group policies, the following settings should be applied via group policy for computer objects which represent the Windows clients of MailStore users:
  • Computer Configuration > Administrative Templates > System > Scripts > Run logon scripts synchronously
  • Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon

Updating

The MailStore Client MSI installs basically only a loader that actually loads the latest MailStore Client components from the MailStore Server. In case this loader needs to be updated itself, group policies can do the update automatically on the MailStore user computers. To edit an existing MailStore Client Deployment group policy so that an automatic update of the clients can be performed, please proceed as follows:

  • Open the Group Policy Management Console on your domain controller.
  • Navigate to the administrative folder Group Policy Objects.
  • Right-click on the existing MailStore Client Deployment GPO and select Edit....
  • Expand User Configuration > Policies > Software Settings.
  • Right-click on Software installation.
  • Select New and Package....
  • Select the updated MailStore Client MSI package. Please note that the path for the file must be entered in UNC notation (e.g. \\Server\Setup\MailStoreSetup...) and that domain users need to have read-access to this share.
  • In the following dialog window, select Advanced and click OK.
    GPO Client 2019 02.png
  • On the next screen, please set the options on the Deployment tab as shown below:
    GPO Client 2019 03.png
  • On the Upgrades tab, a list of upgradeable packages is shown. Select the option Required upgrade for existing packages.
    GPO Client 2019 06.png
  • Click on OK to confirm all settings.
  • The group policy should look similar to the one shown below:
    GPO Client 2019 07.png

The MailStore Client loader will be updated upon the next login of the users on their Windows workstations.

Configuration

If Mailstore Server is used within an Active Directory infrastructure, the MailStore Client and the MailStore Outlook Add-in can be configured using group policies. Settings that are configured through group policies supersede local settings and cannot be changed by users.

For this purpose, group policy templates are available as ADMX files (for Windows 7 SP1 and Windows Server 2008 R2 or higher).

Installing the ADMX Template

Group policy templates can either be managed locally on an administrative workstation or centrally in the domain. Please refer to Microsoft Technet for further details.

Installation of the ADMX Templates in the Local Store

  • Download the ADMX templates to your administrative workstation.
  • Unzip the package to %systemroot%, retaining its folder structure.

Installation of the ADMX Templates in the Central Store

Please note: Use this method only, if you are already using a central store for group policies, else group policies stored in the local store are not accessible anymore.
  • Download the ADMX templates to your domain controller.
  • In the SYSVOL folder, unzip the package to domain\policies, retaining its folder structure (default: %systemroot%\sysvol\domain\policies).

To verify the installation and for further configuration, please proceed as follows:

  • Open the Group Policy Management Console.
  • Right-click on the administrative folder Group Policy Objects.
  • Select New and create a new group policy object called MailStore Client Settings.
  • Right-click on the new GPO and select Edit....
  • Expand User Configuration > Policies > Administrative Templates.
  • If the templates have been installed correctly, an entry MailStore and sub-entries MailStore Client and MailStore Outlook-Add-in exist.
    GPO Client 2019 12.png


Configuring Policy Settings

  • Open the Group Policy Management Console.
  • Right-click on the administrative folder Group Policy Objects.
  • Right-click on the existing group policy object called MailStore Client Settings and select Edit....
  • Expand User Configuration > Policies > Administrative Templates > MailStore > MailStore Client.
    GPO Client 2019 08.png
  • These settings supported by the current MailStore Client are available:
    • Authentication
      Sets the authentication method to either Standard Authentication or Windows Authentication. When the authentication method is set to Windows Authentication then the Server Name also must be set
    • Language
      Sets the display language of the MailStore Client. Select System language to have the MailStore Client use the language of a client's operating system.
    • Remember Password
      This setting stores a user's password, once entered, locally on the client, provided that the authentication method has been set to Standard Authentication as well.
    • Server Name
      If this parameter is provided, the MailStore Client always connects to this server. If the authentication method has also been set to Windows Authentication, the login to MailStore Server occurs directly without any user interaction (Single Sign On). If the MailStore Client access has been configured to a port different from the default (8460), this parameter has to be provided as Server Name:Port.


Applying Policy Settings

To apply these settings to users, the group policy has to be linked to the corresponding user objects. Linking is done using organizational units (OU).

  • Highlight the organizational unit (OU) which contains the desired user objects, right-click on the OU (Seattle in the example below) and select the option Link an Existing GPO....
  • In the dialog window Select GPO, highlight MailStore Client Settings and click on OK.
    GPO Client 2019 09.png
  • Through the organizational unit the group policy is now linked to the user objects contained therein. The settings will become active the next time users log on to the Windows clients.


Uninstalling

Just like the distribution, the uninstalling of software packages can be done using group policies. Please proceed as follows:

  • Open the Group Policy Management Console on your domain controller.
  • Navigate to the administrative folder Group Policy Objects.
  • Right-click on the existing MailStore Client Deployment GPO and select Edit....
  • Expand User Configuration > Policies > Software Settings > Software installation.
  • Right-click on the package to be uninstalled and select All Tasks > Remove...
  • In the following dialog window, select Immediately uninstall the software from users and computers and click OK.
  • Close all open windows and exit the group policy editor.

The MailStore Client will be uninstalled upon the next login of the users on their Windows workstations.