https://wiki.zimbra.com/api.php?action=feedcontributions&user=Jhurley&feedformat=atomZimbra :: Tech Center - User contributions [en]2024-03-19T09:48:39ZUser contributionsMediaWiki 1.39.0https://wiki.zimbra.com/index.php?title=Zimbra_Releases/8.8.15/P38&diff=69515Zimbra Releases/8.8.15/P382023-03-08T18:58:38Z<p>Jhurley: /* Zimbra Collaboration Joule 8.8.15 Patch 38 GA Release */</p>
<hr />
<div>= Zimbra Collaboration Joule 8.8.15 Patch 38 GA Release =<br />
<br />
<div class="col-md-9"><br />
Check out the '''[[#Security Fixes|Security Fixes]]''', '''[[#What's New|What's New]]''', and '''[[#Known Issues|Known Issues]]''' for this version of Zimbra Collaboration.<br />
Please refer to the '''[[#Patch Installation|Patch Installation]]''' section for Patch Installation instructions.<br />
As always, you are encouraged to tell us what you think in the Forums or open a support ticket to report issues.<br />
{{ReleaseNote-note}}<br />
<div><br />
<br />
<br />
<div style="padding:1%; color:#008000;font-size:19px;" ><br />
'''NOTICE: MTA Patch version'''<br />
<br />
As part of this patch, we are releasing the updated ClamAV and its related packages which are installed only on MTA nodes. Since this patch will not get installed on other nodes (e.g. Mailbox, LDAP), it will continue to display the previously installed patch versions as '''Patch 8.8.15_P37'''.<br />
<br />
If patch 36 or older are currently installed on your server, please ensure you review [https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P37 Patch 37] release notes to obtain all updates on all components. <br />
<br />
</div><br />
<br/><br />
<br />
= Security Fixes =<br />
{|class="wikitable" style="border: solid #ffffff; padding: 20px;"<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|Summary<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|CVE-ID<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|CVSS Score<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|Zimbra Rating<br />
|-<br />
|style="border: solid #ffffff;"| The ClamAV package has been upgraded to version 0.105.2 to fix multiple vulnerabilities<br />
|style="border: solid #ffffff; text-align: center;"|[https://nvd.nist.gov/vuln/detail/CVE-2023-20032 CVE-2023-20032] [https://nvd.nist.gov/vuln/detail/CVE-2023-20052 CVE-2023-20052]<br />
|style="border: solid #ffffff; text-align: center;"| TBD <br />
|style="border: solid #ffffff; text-align: center;"| Critical<br />
|}<br />
<br />
''' Note: Additional configuration for further hardening your Zimbra setup can be found on the [https://support.zimbra.com Zimbra Support Portal]. It is recommended that all customers consider these additional steps. If someone had applied this configuration previously, then after upgrading to this patch, they will have to re-apply the same configuration. '''<br />
<br />
= What's New =<br />
<br />
== Package Upgrade ==<br />
<div style="padding:1%; color:#f68b1f;font-size:20px;" ><br />
* ClamAV package has been upgraded from 0.105.1-2 to version 0.105.2<br />
</div><br />
<br/><br />
<br />
= Known Issues =<br />
* While deploying zimlets, if the following error is encountered, please refer to the '''[https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/patch_installation Patch Installation]''' section to install the '''zimbra-common-core-jar, zimbra-common-core-libs, zimbra-mbox-store-libs''' packages in a particular order and re-deploy the zimlets. <br />
/opt/zimbra/bin/zmjava: line 59: /bin/java: No such file or directory<br />
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/appender/ConsoleAppender$Target<br />
at com.zimbra.cs.localconfig.LocalConfigCLI.main(LocalConfigCLI.java:353)<br />
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target<br />
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)<br />
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)<br />
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)<br />
... 1 more<br />
<br />
* From Joule-Patch-32 onwards, customers using SSO will need to update <code>zimbraVirtualHostName</code> attribute for the domains. Please refer to the '''[[#Changes required for SSO setup before patch upgrade| instructions]]''' to update the attribute.<br />
<br />
* With JDK 17, weaker Kerberos encryption types like 3DES and RC4 have now been disabled by default. This can cause SPNEGO auth to fail if described encryption types are being used. We recommend using stronger encryption types like AES256.<br />
To get SPNEGO auth working with weak encryption types, weak encryption can be enabled by setting the '''allow_weak_crypto''' property to true in the krb5.conf configuration file. Please follow below instructions:<br />
<br />
1. In '''/opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults]''' section, set '''allow_weak_crypto = true'''<br />
<br />
2. Restart mailboxd service:<br />
su - zimbra<br />
zmmailboxdctl restart<br />
<br />
<br />
= Packages =<br />
The package lineup for this release is:<br />
<br />
FOSS:<br />
'''PackageName''' -> '''Version'''<br />
zimbra-mta-patch -> 8.8.15.1677488961.p38-1<br />
zimbra-mta-components -> 1.0.19-1zimbra8.8b1<br />
zimbra-clamav -> 0.105.2-1zimbra8.8b3<br />
<br />
<br />
=Patch Installation=<br />
<br />
Please refer to the steps below to install Joule 8.8.15 Patch 38 on [[#Redhat|Redhat]] and [[#Ubuntu|Ubuntu]] platforms:<br />
<br />
<span class="h2">Before Installing the Patch, consider the following:</span><br />
* Patches are cumulative.<br />
* A full backup should be performed before any patch is applied. There is no automated roll-back.<br />
* Switch to <code>zimbra</code> user before using ZCS CLI commands.<br />
* '''Important!''' You cannot revert to the previous ZCS release after you upgrade to the patch.<br />
* '''Important Note for ZCS Setup with Local ZCS repository:''' Customers who have set up local ZCS repository should first update the local repository by following instructions in [https://wiki.zimbra.com/wiki/Zimbra_Collaboration_repository#Keep_the_local_Repository_up_to_date wiki]<br />
<br />
<br />
==Redhat==<br />
<br />
<br />
'''Install/Upgrade <code>zimbra-mta-patch</code> on MTA node'''<br />
* As <code>root</code>, install the package:<br />
yum install zimbra-mta-patch<br />
* Restart <code>ZCS</code> as <code>zimbra</code> user:<br />
su - zimbra<br />
zmcontrol restart<br />
<br />
<br />
== Ubuntu ==<br />
<br />
<br />
'''Install/Upgrade <code>zimbra-mta-patch</code> on MTA node'''<br />
* As <code>root</code>, install package<br />
apt-get install zimbra-mta-patch<br />
* Restart <code>ZCS</code> as <code>zimbra</code> user:<br />
su - zimbra<br />
zmcontrol restart<br />
<br />
= Quick note: Open Source repo =<br />
The steps to download, build, and see our code via Github can be found here:<br />
[https://github.com/Zimbra/zm-build https://github.com/Zimbra/zm-build]</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zimbra_Releases/9.0.0/P31&diff=69514Zimbra Releases/9.0.0/P312023-03-08T18:57:32Z<p>Jhurley: /* Zimbra Collaboration Kepler 9.0.0 Patch 31 GA Release */</p>
<hr />
<div>= Zimbra Collaboration Kepler 9.0.0 Patch 31 GA Release =<br />
Check out the '''[[#Security Fixes|Security Fixes]]''', '''[[#What's New|What's New]]''', and '''[[#Known Issues|Known Issues]]''' for this version of Zimbra Collaboration.<br />
Please refer to the '''[[#Patch Installation|Patch Installation]]''' page for Patch Installation instructions.<br />
As always, you are encouraged to tell us what you think in the Forums or open a support ticket to report issues<br />
<div style="padding:1%; color:#008000;font-size:19px;" ><br />
'''NOTICE: MTA Patch version'''<br />
<br />
As part of this patch, we are releasing the updated ClamAV and its related packages which are installed only on MTA nodes. Since this patch will not get installed on other nodes (e.g. Mailbox, LDAP), it will continue to display the previously installed patch versions as '''Patch 9.0.0_P31'''.<br />
<br />
If patch 29 or older are currently installed on your server, please ensure you review [https://wiki.zimbra.com/wiki/Zimbra_Releases/9.0.0/P30 Patch 30] release notes to obtain all updates on all components. <br />
<br />
</div><br />
<br />
= Security Fixes =<br />
{|class="wikitable" style="border: solid #ffffff; padding: 20px;"<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|Summary<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|CVE-ID<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|CVSS Score<br />
!style="background-color:#f15922; color: white; border: solid #ffffff;"|Zimbra Rating<br />
|-<br />
|style="border: solid #ffffff;"| The ClamAV package has been upgraded to version 0.105.2 to fix multiple vulnerabilities<br />
|style="border: solid #ffffff; text-align: center;"|[https://nvd.nist.gov/vuln/detail/CVE-2023-20032 CVE-2023-20032] [https://nvd.nist.gov/vuln/detail/CVE-2023-20052 CVE-2023-20052]<br />
|style="border: solid #ffffff; text-align: center;"| TBD <br />
|style="border: solid #ffffff; text-align: center;"| Critical<br />
|}<br />
<br />
''' Note: Additional configuration for further hardening your Zimbra setup can be found on the [https://support.zimbra.com Zimbra Support Portal]. It is recommended that all customers consider these additional steps. If someone had applied this configuration previously, then after upgrading to this patch, they will have to re-apply the same configuration. '''<br />
<br />
= What's New =<br />
<br />
== Package Upgrade ==<br />
<br/><br />
<div style="padding:1%; color:#f68b1f;font-size:20px;" ><br />
* ClamAV package has been upgraded from 0.105.1-2 to version 0.105.2<br />
</div><br />
<br/><br />
= Known Issues =<br />
* While deploying zimlets, if the following error is encountered, please refer to the '''[https://wiki.zimbra.com/wiki/Zimbra_Releases/9.0.0/patch_installation Patch Installation]''' page to install the '''zimbra-common-core-jar, zimbra-common-core-libs, zimbra-mbox-store-libs''' packages in a particular order and re-deploy the zimlets. <br />
/opt/zimbra/bin/zmjava: line 59: /bin/java: No such file or directory<br />
Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/logging/log4j/core/appender/ConsoleAppender$Target<br />
at com.zimbra.cs.localconfig.LocalConfigCLI.main(LocalConfigCLI.java:353)<br />
Caused by: java.lang.ClassNotFoundException: org.apache.logging.log4j.core.appender.ConsoleAppender$Target<br />
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)<br />
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)<br />
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)<br />
... 1 more<br />
<br />
* From Kepler-Patch-25 onwards, customers using SSO will need to update <code>zimbraVirtualHostName</code> attribute for the domains. Please refer to the '''[[#Changes required for SSO setup before patch upgrade| instructions]]''' to update the attribute.<br />
<br />
* With JDK 17, weaker Kerberos encryption types like 3DES and RC4 have now been disabled by default. This can cause SPNEGO auth to fail if described encryption types are being used. We recommend using stronger encryption types like AES256.<br />
To get SPNEGO auth working with weak encryption types, weak encryption can be enabled by setting the '''allow_weak_crypto''' property to true in the krb5.conf configuration file. Please follow below instructions:<br />
<br />
1. In '''/opt/zimbra/jetty_base/etc/krb5.ini.in -> [libdefaults]''' section, set '''allow_weak_crypto = true'''<br />
<br />
2. Restart mailboxd service:<br />
su - zimbra<br />
zmmailboxdctl restart<br />
<br />
<br />
= Packages =<br />
The package lineup for this release is:<br />
<br />
zimbra-mta-patch -> 9.0.0.1677489008.p31-1<br />
zimbra-mta-components -> 1.0.19-1zimbra8.8b1<br />
zimbra-clamav -> 0.105.2-1zimbra8.8b3<br />
<br />
<br />
=Patch Installation=<br />
<br />
Please refer to the steps below to install Kepler 9.0.0 Patch 31 on [[#Redhat|Redhat]] and [[#Ubuntu|Ubuntu]] platforms:<br />
<br />
<span class="h2">Before Installing the Patch, consider the following:</span><br />
* Patches are cumulative.<br />
* A full backup should be performed before any patch is applied. There is no automated roll-back.<br />
* Switch to <code>zimbra</code> user before using ZCS CLI commands.<br />
* '''Important!''' You cannot revert to the previous ZCS release after you upgrade to the patch.<br />
* '''Important Note for ZCS Setup with Local ZCS repository:''' Customers who have set up local ZCS repository should first update the local repository by following instructions in [https://wiki.zimbra.com/wiki/Zimbra_Collaboration_repository#Keep_the_local_Repository_up_to_date wiki]<br />
<br />
<br />
==Redhat==<br />
<br />
<br />
'''Install/Upgrade <code>zimbra-mta-patch</code> on MTA node'''<br />
* As <code>root</code>, install the package:<br />
yum install zimbra-mta-patch<br />
* Restart <code>ZCS</code> as <code>zimbra</code> user:<br />
su - zimbra<br />
zmcontrol restart<br />
<br />
<br />
== Ubuntu ==<br />
<br />
<br />
'''Install/Upgrade <code>zimbra-mta-patch</code> on MTA node'''<br />
* As <code>root</code>, install package<br />
apt-get install zimbra-mta-patch<br />
* Restart <code>ZCS</code> as <code>zimbra</code> user:<br />
su - zimbra<br />
zmcontrol restart</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=GPO_Deployment&diff=68837GPO Deployment2022-03-11T21:51:47Z<p>Jhurley: Created page with "= Deploying ZCO Connector Using GPO = {{KB|{{ZC}}|{{ZCO 8.8.15}}|{{ZCO 9.0.0}}|}} {{WIP}} The Zimbra Connector is configured to support multiple languages and when installin..."</p>
<hr />
<div>= Deploying ZCO Connector Using GPO =<br />
{{KB|{{ZC}}|{{ZCO 8.8.15}}|{{ZCO 9.0.0}}|}}<br />
<br />
{{WIP}}<br />
<br />
The Zimbra Connector is configured to support multiple languages and when installing using GPO, there is no method to flag the appropriate language. Because of this, the msi file language needs to be manually set before the GPD rollout. <br />
<br />
Note: If the rollout occurs without setting the language, the installation will default to Arabic since it is the first language listed in the languages list.<br />
<br />
<br />
To Update the ZCO msi file, you will need to: <br />
<br />
* Download Windows SDK and install the MSI tool.<br />
* Download the latest ZCO connector.<br />
* Modify MSI language<br />
<br />
<br><br />
Steps: <br />
<br><br />
<br><br />
1) Download the Windows SDK at https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/ <br />
<br><br />
<br><br />
a. Select the "DOWNLOAD THE INSTALLER" button from the portal. <br />
b. Run the 'winsdksetup.exe'<br />
c) Select the download path<br />
d) Uncheck everything except MSI Tools and download.<br />
<br><br />
<br><br />
[[File:MSI_Tool.png|800px]]<br />
<br><br />
<br><br />
2) Install Orca-x86_en-us.msi by opening window Explorer going to the download path and double clicking Orca-x86_en-us.<br />
<br />
3) Launch Orca Tool by locating Orca within the start list [[File:ORCA.png|100px]] <br />
<br />
4) Downloading the latest ZCO connector at https://www.zimbra.com/downloads/zimbra-connector-for-outlook/ <br />
<br />
5) Open the connector MSI within Orca by selecting File => Open and selecting the ZCO msg installer.<br />
<br />
6) Setting the language by select View => Summary Information and removing all languages other than your preferred language.<br />
<br><br />
<br><br />
[[File:languages.png|450px]]<br />
<br><br />
<br><br />
The following are supported Language and codes:<br />
<br><br />
<br><br />
{| width=40% border=1<br />
! bgcolor="#0087c3"| Language Code<br />
! bgcolor="#0087c3"| Locate<br />
|-<br />
|1033<br />
|English - United States<br />
|-<br />
|1030<br />
|Danish<br />
|-<br />
|1031<br />
|German - Germany<br />
|-<br />
|3082<br />
|Spanish - Spain (Modern Sort)<br />
|-<br />
|1036<br />
|French - France<br />
|-<br />
|1040<br />
|Italian - Italy<br />
|-<br />
| 1041<br />
| Japanese<br />
|-<br />
| 1043<br />
| Dutch - Netherlands<br />
|-<br />
| 1046<br />
| Portuguese - Brazil<br />
|-<br />
| 1049<br />
| Russian<br />
|-<br />
| 1053<br />
| Swedish - Sweden<br />
|-<br />
| 1025 <br />
| Arabic - Saudi Arabia<br />
|-<br />
| 1081<br />
| Hindi<br />
|-<br />
| 1042<br />
| Korean<br />
|- <br />
| 1045<br />
| Polish<br />
|-<br />
| 1055<br />
| Turkish<br />
|-<br />
| 2052<br />
| Chinese - People's Republic of China<br />
|-<br />
| 3076<br />
| Chinese - Hong Kong SAR<br />
|-<br />
| 1028<br />
| Chinese - Taiwan<br />
|-<br />
| 1038<br />
| Hungarian<br />
|-<br />
| 1048<br />
| Romanian - Romania<br />
|-<br />
| 1058<br />
| Ukrainian<br />
|-<br />
| 1054<br />
| Thai<br />
|-<br />
| 2070<br />
| Portuguese - Portugal<br />
|-<br />
| 1086<br />
| Malay - Malaysia<br />
|-<br />
| 1060<br />
| Slovenian<br />
|-<br />
| 1037<br />
| Hebrew<br />
|-<br />
| 1057<br />
| Indonesian<br />
|-<br />
| 1027<br />
| Catalan<br />
|-<br />
| 1044<br />
| Norwegian (Bokmål)<br />
|-<br />
| 1066<br />
| Vietnamese<br />
|-<br />
|}<br />
<br><br />
<br><br />
7) Save<br />
<br />
Note: The file been modified and will contain an unknown publisher.<br />
<br />
<br />
Once the timezone has been updated, it is time to deploy the ZCO connector. There are a number of approaches that can be used, Zimbra has verified the follow options. <br />
<br />
<br />
https://docs.microsoft.com/en-us/archive/blogs/grouppolicy/group-policy-in-windows-server-2012-using-remote-gpupdate<br />
<br />
https://activedirectorypro.com/update-group-policy-remote-computers/</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Languages.png&diff=68836File:Languages.png2022-03-11T21:33:13Z<p>Jhurley: For ZCO, GPO deployment wiki</p>
<hr />
<div>For ZCO, GPO deployment wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:ORCA.png&diff=68835File:ORCA.png2022-03-11T21:28:58Z<p>Jhurley: For ZCO CPO Deployment Wiki</p>
<hr />
<div>For ZCO CPO Deployment Wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:MSI_Tool.png&diff=68834File:MSI Tool.png2022-03-11T21:24:01Z<p>Jhurley: For ZCO GPO Deployment wiki</p>
<hr />
<div>For ZCO GPO Deployment wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Log-in_to_adminUI_hangs_after_upgrade_to_zcs_8.6&diff=68757Log-in to adminUI hangs after upgrade to zcs 8.62022-02-04T02:08:55Z<p>Jhurley: </p>
<hr />
<div>{{Archive}}<br />
=== Problem: ===<br />
<br />
After upgrade to zcs 8.6.0, the log-in hangs indefinitely. <br />
<br />
<br />
<br />
=== Troubleshooting: ===<br />
<br />
<br />
==== Prerequisites: ====<br />
<br />
a). Make sure the networking is configured correctly<br />
<br />
b). Check DNS configuration<br />
<br />
<br />
==== Web console ====<br />
<br />
Open Firefox, click on the '''menu''' icon (''top right corner''), select the "Developer" icon > '''Web Console'''. It has couple of tabs listed at the top, but we will be only paying attention to the "Console" and "Network" tabs. As the web console is open, we try to log-in to the AdminUI. In the "Console" tab, there are couple of lines, as the last one is the '''following error''': <br />
<br />
<pre style="color: green">TypeError: this._mbsList.loadEffectiveRights is not a function Zimlets-nodev_all.js.zgz.js:30684</pre><br />
<br />
When clicking on the "Network" tab, we see that the trace stops at the '''"GetAllServersRequest"'''. In fact, there are couple of the same requests (in this case 4) made, one after another. Based on the above error, we can see the problem is with a zimlet installed on the machine. <br />
<br />
After comparing the zimlets from a default machine we see that there are some non-default zimlets on the problematic machine, probably manually installed or left there from previous old zcs installations. <br />
<br />
The next thing that was observed was that the order of the default zimlets was different from the default one. Regrouping (''zmzimletctl setPriority {zimlet} {priority}'') did not fix the problem. <br />
<br />
Lastly, we disabled all non-default zimlets, which fixed the problem. When this was done, we enabled one by one all of them, to see which one was causing the problem. It was <pre style="color: red">com_zimbra_xmbxsearch</pre> That zimlet is too old and it's not compatible with zcs 8.6. <br />
<br />
<br />
==== Logging ====<br />
<br />
Here are excerpts from /opt/zimbra/log/mailbox.log file, showing us the logging for the problem.<br />
<br />
2015-01-27 10:55:27,539 INFO [qtp509886383-20:https://10.0.0.1:7071/service/admin/soap/GetAdminConsoleUICompRequest] [name=<br />
user@example.com.de;mid=1;ip=10.0.0.1;ua=ZimbraWebClient - FF35 (Win);] soap - GetAdminConsoleUICompRequest elapsed=18<br />
2015-01-27 10:55:27,720 DEBUG [qtp509886383-19:https://10.0.0.1:7071/service/admin/soap/GetAdminSavedSearchesRequest] [] mis<br />
c - Servlet (contextPath=/service active=0), Jetty pool (threads=10, idle=3, busy=7, room=243)<br />
2015-01-27 10:55:27,722 INFO [qtp509886383-19:https://10.0.0.1:7071/service/admin/soap/GetAdminSavedSearchesRequest] [name=<br />
user@example.com.de;mid=1;ip=10.0.0.1;ua=ZimbraWebClient - FF35 (Win);] misc - delegated access: doc=GetAdminSavedSearches, aut<br />
henticated account=user@example.com.de, target account=user@example.com.de<br />
2015-01-27 10:55:27,728 INFO [qtp509886383-19:https://10.0.0.1:7071/service/admin/soap/GetAdminSavedSearchesRequest] [name=<br />
user@example.com.de;mid=1;ip=10.0.0.1;ua=ZimbraWebClient - FF35 (Win);] soap - GetAdminSavedSearchesRequest elapsed=6<br />
2015-01-27 10:55:27,757 DEBUG [qtp509886383-18:https://10.0.0.1:7071/service/admin/soap/GetAllServersRequest] [] misc - Serv<br />
let (contextPath=/service active=0), Jetty pool (threads=10, idle=3, busy=7, room=243)<br />
<br />
<br />
==== Conclusion: ====<br />
<br />
Make sure all zimlets are up-to date and are supported by the zcs version.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=LHammonds-Notes&diff=68756LHammonds-Notes2022-02-04T02:08:19Z<p>Jhurley: </p>
<hr />
<div>{{Archive}}<br />
Eh, not much to say. I am evaluating various alternatives to MS Exchange and this is one of them. <br />
<br />
I am documenting my experience evaluating Zimbra here: [http://www.zimbra.com/forums/installation/52399-my-notes-installing-zimbra-7-1-2-ubuntu-10-04-a.html My Notes for Installing Zimbra 7.1.2 on Ubuntu 10.04]<br />
<br />
[[User:LHammonds|LHammonds]] 12:59, 29 September 2011 (PDT)<br />
----<br />
Actually, we decided to go with Zimbra so now I am documenting the conversion here: [http://www.zimbra.com/forums/installation/56367-my-notes-installing-zimbra-ose-ubuntu-server-10-04-lts.html My Notes for Installing Zimbra OSE on Ubuntu Server 10.04 LTS]<br />
<br />
[[User:LHammonds|LHammonds]] 20:21, 26 April 2012 (PDT)<br />
----</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Security/Collab&diff=68755Security/Collab2022-02-04T02:07:46Z<p>Jhurley: </p>
<hr />
<div>{{Archive}}{{BC|Security Center}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
= Security Pointers and Tidbits =<br />
<br />
The main jumping point for security is the [[Security Center]].<br />
<br />
== Release Specific Settings ==<br />
* [[Security/Collab/86|ZCS 8.6 security settings]]<br />
* [[Security/Collab/87|ZCS 8.7 security settings]]<br />
* [[Security/Collab/88|ZCS 8.8 security settings]]<br />
<br />
= Odds and Ends =<br />
Here are a few questions that come up from time to time...<br />
<br />
=== An OS Patch/Bug/Vulnerability was announced, is Zimbra affected? ===<br />
Best practice dictates that you '''always stay up to date with vendor provided OS patches'''. Also, be sure to follow OS recommended best practices when applying patches (e.g. restarting affected services, tools like '''needs-restarting''', '''needrestart''' and '''checkrestart''' may be helpful when trying to understand which processes are using files that were replaced by a patch). When in doubt about the status of a system after a patch, go ahead and '''reboot''' to ensure the patches take effect.<br />
<br />
=== Cookie ZM_TEST cookie is missing the '''HttpOnly''' attribute, is this a problem? ===<br />
The ZM_TEST cookie in ZCS is used solely to determine if cookies are enabled a the browser. There are no privileges associated with that cookie. As such, there is no inherent risk with not having an '''HttpOnly''' attribute on this cookie.<br />
<br />
=== Cookies JSESSIONID and ZM_AUTH_TOKEN are missing the '''Secure''' attribute, why? ===<br />
Typically this is an indication of one of the following (ref: [https://bugzilla.zimbra.com/show_bug.cgi?id=91298 bug 91298]):<br />
* a configuration problem - '''zimbraReverseProxySSLToUpstreamEnabled''' has been set to '''FALSE''' instead of '''TRUE'''<br />
* a site that is performing SSL/TLS offloading - consider adding the '''Secure''' attribute via the device that is performing the offloading<br />
<br />
=== JSESSIONID is sometimes exposed in a URL, is that a problem? ===<br />
Generally speaking, the fact that this occurs is related to the server not yet being sure about the client supporting/allowing cookies. In ZCS, the use of JSESSIONID is limited to some client state management (ref: [https://bugzilla.zimbra.com/show_bug.cgi?id=30319 bug 30319] and [https://bugzilla.zimbra.com/show_bug.cgi?id=71982 bug 71982]). As such, there is no security risk associated with authentication or authorization by having JSESSIONID in a URL. <br />
<br />
=== Can you explain the relationship between the <u>UNIX user/group</u> '''zimbra''' and '''root'''? ===<br />
Historically the '''zimbra''' UNIX account and group has been treated as ''trusted'' from the UNIX process perspective. It is important to note that this goes against many common trust models, where accounts that provide network services would be considered ''untrusted''. With that in mind, if one has access to <u>UNIX user/group</u> '''zimbra''', then one has that ability to obtain '''root''' privilege. While there are ''explicit'' abilities identified via ''sudoers'' (ref: [[Sudoers]]), there are also ''implicit'' abilities due to limitations of the tools currently being used and the weak trust model.<br />
<br />
Please be aware that there is potential for user/group '''zimbra''' to escalate to '''root''' privileges via ''nginx'' (ref: https://trac.nginx.org/nginx/ticket/376) as well as other utilities allowed in the ''sudoers'' configuration. This is not an ideal situation and will likely change over time, but that is the status quo within the product.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Rhel5_to_rhel6_upgrade_options&diff=68754Rhel5 to rhel6 upgrade options2022-02-04T02:07:03Z<p>Jhurley: </p>
<hr />
<div>{{Archive}}<br />
<br />
Zimbra ZCS version 8 and beyond will no longer be supported on Red Hat Enterprise Linux v.5. <br />
<br />
[http://bugzilla.zimbra.com/show_bug.cgi?id=75191 Click to See Our RFE Bug Requesting Further Support for RHEL5]<br />
<br />
This has caused many Zimbra customers to consider upgrading to the supported RHEL6. <br />
<br />
Unfortunately, Red Hat does not support in-place upgrades from RHEL5 to RHEL6, and recommends a fresh install. Such an upgrade is possible, however, they are not recommended by Red Hat and result in such issues as unresponsive GUI login windows and other, possibly unknown defects. <br />
<br />
[https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-upgrade-x86.html Red Hat Upgrade Guide and Disclaimer]<br />
<br />
<br />
Therefore, we have been working with our customers on a number of possible routes to migrating a current RHEL5 ZCS instance to a new RHEL6 server. <br />
<br />
'''CAUTION- When testing, make sure the new Zimbra Server cannot contact the old server over the network. The test installer can make unwanted changes to the production server's LDAP, requiring an emergency LDAP restore from backups. Use a VLAN or subnet to keep them separate while testing!'''<br />
<br />
<br />
'''First Method- Add New Servers To Replace ZCS Services And Use "zmmboxmove"'''<br />
<br />
[http://wiki.zimbra.com/wiki/Zmmailboxmove zmmboxmove]<br />
<br />
This option would be to add servers to your ZCS environment with the intention of "turning off" the ZCS services on the old servers.<br />
<br />
*Add a ZCS LDAP slave running the OS and ZCS version you want. Promote the new ldap slave to become the ldap master and later decommission the older one.<br />
<br />
[http://wiki.zimbra.com/wiki/LDAP#LDAP_replication Configure LDAP replication]<br />
<br />
[http://wiki.zimbra.com/wiki/Promoting_Replica_to_LDAP_Master How to Promote an LDAP Replica]<br />
*Add new mta servers running the OS and ZCS version you want. Decommission older boxes once done.<br />
<br />
*Add new mailstores running the OS and ZCS version you want. Use the zmmboxmove command to move all the accounts to the new mailstores. Decommission the older mailstores once this is done.<br />
<br />
You will need to use the new "zmdedupe' tool in ZCS 8 to address an issue with links that cause the mailstore to grow to a much larger size, see this bug for more detail:<br />
<br />
[https://bugzilla.zimbra.com/show_bug.cgi?id=77597 "zmdedupe"]<br />
<br />
See here for AJ Cody's notes and a list of bugs to review for using zmmboxmove:<br />
<br />
[http://wiki.zimbra.com/wiki/Ajcody-Notes-OS-Upgrade-And-ZCS-Options#Add_New_Servers_To_Replace_ZCS_Services_And_Use_zmmboxmove_-_Necessary_For_RHEL_4.2F5_to_RHEL6 "zmmboxmove" Issues]<br />
<br />
Here is a bit more on the process, it's a bit dated but still applies:<br />
[http://wiki.zimbra.com/wiki/Preferred_Method_of_Moving_Users_To_New_Machine_(zmmailboxmove_-_Network_Edition_Only) Zmmailboxmove Method]<br />
<br />
<br />
'''Disaster Recovery Method'''<br />
<br />
[http://wiki.zimbra.com/wiki/Network_Edition_Disaster_Recovery DR Wiki Page]<br />
<br />
In this method, you would close access to the Zimbra server with a firewall rule or similar, and make a full backup. Then, copy this backup to the new server and import it using the disaster recovery wiki to guide you. The result would be a duplicate of the first server. <br />
<br />
This route has the fewest steps and has a good chance of success the first try. However, it is also very slow and requires the most downtime (possibly a day or more). <br />
<br />
<br />
'''A Modified "rsync" Method'''<br />
<br />
Similar to the methods mentioned [http://wiki.zimbra.com/wiki/Platform_and_OS_Independent_ZCS_to_ZCS_Migration_Using_Rsync here]:<br />
<br />
In this method, however, we do not use rsync to copy all of the Zimbra files (/opt/zimbra). We have found that using these methods between RHEL5 and RHEL6 results in (currently) unknown failures due to Perl and other library incompatibilities. Therefore, a finer-grained approach is needed to copy, export and re-import only the necessary files and database information. This method has the most steps, but offers a short downtime as you can perform the initial rsyncs while the old server is still running. <br />
<br />
[http://wiki.zimbra.com/wiki/Modified_Rsync_Migration Modified Rsync Method]<br />
<br />
'''PLEASE NOTE- We cannot guarantee that any of these methods will work exactly as described. You should ALWAYS test these first in a lab or VM environment before using in production.'''<br />
<br />
<br />
<br />
If you have feedback on any of these methods, please contact me at lshaughnessy@zimbra.com and let me know what you discover.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Enable_IM_on_ZCS_5.0&diff=68752Enable IM on ZCS 5.02022-02-04T01:57:38Z<p>Jhurley: </p>
<hr />
<div>{{Archive}}__NOINDEX__{{Article Infobox|{{admin}}||{{ZCS 5.0}}|}}IM is disabled by default in ZCS 5.0. In order to enable IM, please follow the following steps:<br />
<br />
<pre><br />
zmprov -l -v mcf zimbraXMPPEnabled TRUE<br />
zmprov -v mc default zimbraFeatureIMEnabled TRUE<br />
zmprov -v mc default zimbraFeatureInstantNotify TRUE<br />
zmcontrol stop<br />
zmcontrol start<br />
</pre><br />
<br />
<br />
<br />
{{Article Footer|ZCS 5.0|1/11/2008}}<br />
<br />
[[Category:Configuration]]<br />
[[Category:ZCS 5.0]]</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Recreating_a_Self-Signed_SSL_Certificate_in_ZCS_4.5_%26_5.0&diff=68751Recreating a Self-Signed SSL Certificate in ZCS 4.5 & 5.02022-02-04T01:55:17Z<p>Jhurley: </p>
<hr />
<div>{{Archive}} __NOINDEX__<br />
This article contains information on recreating a self-signed SSL certificate. <br />
<br />
'''''Important:''' If you are using ZCS 5.0 or later, see [[Administration Console and CLI Certificate Tools]]. <br />
<br />
'''''Important:''' If you are working with a commercial certificate, do not use this page.''<br />
<br />
=ZCS Version=<br />
'''If you are using ZCS 5.0.x, this article is not recommended. See [[Administration Console and CLI Certificate Tools]] instead.'''<br />
<br />
This article contains information for recreating a certificate using the command line interface in both ZCS 4.5.x and 5.0.x. In deployments of 5.0.x and later, this process does not need to be done via the CLI. Using the Administration Console Certificates Tools will simplify this process, and generally eliminates any issues or errors encountered by using the CLI. If you choose to recreate your SSL certificate manually instead of using the Administration Console Certificate Tools, please read all instructions with particular attention to version specific sections and notes before attempting to recreate a self-signed SSL certificate.<br />
<br />
=Why Recreate My Certificates?=<br />
<br />
Your certificates are expired and need to be recreated if you see an error like this when you run zmprov.<br />
<br />
[] ERROR: java.security.cert.CertificateExpiredException: NotAfter: Sun Oct 08 00:38:45 EDT 2006<br />
ERROR: zclient.IO_ERROR (invoke java.security.cert.CertificateException: Untrusted Server Certificate Chain, server: localhost) <br />
(cause: javax.net.ssl.SSLHandshakeException java.security.cert.CertificateException: Untrusted Server Certificate Chain)<br />
<br />
=Instructions for Recreating a Self-Signed SSL Certificate= <br />
<br />
==Back up existing certificates==<br />
<br />
* This backs up the default certificates created by zmcreateca and zmcreatecert:<br />
tar cf /tmp/zimbra-ssl-bak.tar /opt/zimbra/ssl/<br />
<br />
* This backs up the server's working certificate files:<br />
tar cf /tmp/zimbra-certs.tar /opt/zimbra/conf/ca/ \<br />
/opt/zimbra/conf/*.crt \<br />
/opt/zimbra/conf/*.key \<br />
/opt/zimbra/conf/*.pem \<br />
/opt/zimbra/tomcat/conf/keystore \<br />
/opt/zimbra/java/jre/lib/security/cacerts<br />
<br />
''Error in instructions: Tar for 5.0 doesnt capture the keys in jetty for 5.0+''<br />
<br />
==Delete and re-create SSL Directory (as root)==<br />
su -<br />
rm -rf /opt/zimbra/ssl<br />
mkdir /opt/zimbra/ssl<br />
chown zimbra:zimbra /opt/zimbra/ssl<br />
<br />
==Give the zimbra user write access to the cacerts keystore (4.5 only)==<br />
If you are running ZCS 4.5, give the zimbra user write access to the cacerts keystore. If you are running ZCS 5.0.x, skip this step.<br />
<br />
* On linux the java cacerts file is a part of the ZCS installation.<br />
chown zimbra:zimbra /opt/zimbra/java/jre/lib/security/cacerts<br />
chmod 644 /opt/zimbra/java/jre/lib/security/cacerts<br />
* On Mac OS X the java cacerts file is a part of the system's java installation. Either run the "keytool -delete ..." command in the next section as root or give write access to the zimbra user.<br />
chown zimbra:zimbra /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/lib/security/cacerts<br />
chmod u+w /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/lib/security/cacerts<br />
<br />
==Remove the self-signed root certificate from the cacerts keystore (as zimbra)==<br />
* Mac OS X<br />
keytool -delete -alias my_ca -keystore /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/lib/security/cacerts -storepass changeit<br><br />
* Linux<br />
keytool -delete -alias my_ca -keystore /opt/zimbra/java/jre/lib/security/cacerts -storepass changeit<br />
<br />
==Delete the server cert from the mailboxd keystore (as zimbra)==<br />
<br />
* For ZCS upto 4.5.x (tomcat)<br />
su - zimbra<br />
keytool -delete -alias tomcat -keystore /opt/zimbra/tomcat/conf/keystore -storepass zimbra<br />
<br />
* For ZCS 5.0+ (mailboxd/jetty)<br />
su - zimbra<br />
keytool -delete -alias jetty -keystore /opt/zimbra/mailboxd/etc/keystore -storepass zimbra<br />
<br />
* Storepass is normally stored in localconfig<br />
su - zimbra<br />
zmlocalconfig -s -m nokey tomcat_keystore_password<br />
<br />
or for 5.0 (jetty)<br />
su - zimbra<br />
zmlocalconfig -s -m nokey mailboxd_keystore_password<br />
<br />
==Perform optional configuration==<br />
* If you want to change the duration of the certificate from the default (365 days), modify the "default_days" entry in the file /opt/zimbra/conf/zmssl.cnf.in<br />
<br />
''Workaround: zmssl.cnf.in default_days is ingnored. Currently you will need to edit zmcreateca and zmcreatecert:'' Bug is http://bugzilla.zimbra.com/show_bug.cgi?id=12228<br />
<br />
* If you want the common name show up in the CA rather than 'Zimbra Collaboration Suite' because you have several zimbra servers. Please Note: I probably have unnecessary steps in this section here, but this is what I did to get it working for me.<br />
vi /opt/zimbra/conf/zmssl.cnf.in<br />
[change section to appear as below]<br />
0.organizationName = Zimbra<br />
0.organizationName_default = Zimbra<br />
# we can do this but it is not needed normally :-)<br />
#1.organizationName = Second Organization Name (eg, company)<br />
#1.organizationName_default = World Wide Web Pty Ltd<br />
organizationalUnitName = Zimbra<br />
organizationalUnitName_default = Zimbra<br />
commonName = <put your hostname here -- @@HOSTNAME@@ doesn't seem to work><br />
commonName_max = 64<br />
commonName_default = <put your hostname here -- @@HOSTNAME@@ doesn't seem to work><br />
<br />
==Create the CA certificate (as zimbra)==<br />
* for 4.*<br />
zmcreateca<br />
<br />
* for 5.* (as root)<br />
/opt/zimbra/bin/zmcertmgr createca -new<br />
<br />
* (OPTIONAL) If you did the Optional step to make the CN the hostname for the CA, the output should be like the following:<br />
...<br />
Signature ok<br />
subject=/C=US/ST=N/A/L=N/A/O=Zimbra/OU=Zimbra/CN=<your hostname><br />
Getting Private key<br />
unable to write 'random state'<br />
<br />
==Install server ca files==<br />
* After creating the ca, it appears that zmcreateca doesn't copy the new ca.key and ca.pem to /opt/zimbra/conf/ca, so do it manually (as zimbra, 4.*):<br />
cp /opt/zimbra/ssl/ssl/ca/ca.key /opt/zimbra/conf/ca/ca.key<br />
cp /opt/zimbra/ssl/ssl/ca/ca.pem /opt/zimbra/conf/ca/ca.pem<br />
<br />
* 5.* (as root)<br />
/opt/zimbra/bin/zmcertmgr deployca -localonly<br />
<br />
==Create the server certificate (as zimbra)==<br />
* 4.*<br />
zmcreatecert<br />
<br />
* 5.* (as root)<br />
/opt/zimbra/bin/zmcertmgr createcrt self -new<br />
# Optional<br />
/opt/zimbra/bin/zmcertmgr verifycrt self<br />
<br />
''Error in instructions: There IS NO '''createcrt''' in zmcertmgr in 5.0.1_GA_1902:<br />
Usage: <br />
bin/zmcertmgr -help<br />
bin/zmcertmgr createca [-new]<br />
bin/zmcertmgr deployca<br />
bin/zmcertmgr createcsr <self|comm> [-new] [subject] [-subjectAltNames "host1,host2"]<br />
bin/zmcertmgr deploycrt <self> [-new] [validation_days]<br />
bin/zmcertmgr deploycrt <comm> [certfile] [ca_chain_file]<br />
bin/zmcertmgr viewcsr <self|comm> [csr_file]<br />
bin/zmcertmgr viewdeployedcrt [all|ldap|mta|proxy|mailboxd]<br />
bin/zmcertmgr viewstagedcrt <self|comm> [certfile]<br />
bin/zmcertmgr verifycrt <self|comm> [priv_key] [certfile]<br />
bin/zmcertmgr verifycrtchain <ca_file> <certfile><br />
bin/zmcertmgr migrate<br />
<br />
''Confirmed, version 5.0.2_GA_1975 doesnt have it either. Can do it by hand instead with openssl, but you'll have to manually enter your cert sign request info,<br />
and get the COMMON NAME (CN) correct or you'll have problems (createcrt outputs in its usage what your CN is, or you can check /opt/zimbra/conf/zmssl.cnf.in):<br />
#<br />
# as root manually generate new keys '''DO NOT PASTE ALL 3 LINES AT A TIME INTO CLI, DO ONE BY ONE''' input in 2nd step required from console<br />
cd /opt/zimbra/ssl/zimbra/server<br />
#<br />
openssl genrsa -out server.key 2048<br />
openssl req -new -key server.key -out server.csr<br />
openssl x509 -req -days 365 -in server.csr -CA ../ca/ca.pem -CAkey ../ca/ca.key -CAcreateserial -out server.crt<br />
#<br />
openssl genrsa -out mailboxd.key 2048<br />
openssl req -new -key mailboxd.key -out mailboxd.csr<br />
openssl x509 -req -days 365 -in mailboxd.csr -CA ../ca/ca.pem -CAkey ../ca/ca.key -CAcreateserial -out mailboxd.crt<br />
#<br />
# some options in x509 certs mentioned in zmssl.cnf but not included here yet... seems to WFM... -mathx<br />
''<br />
<br />
If you wish to have several names on the certificate, supply them as arguments<br />
<br />
zmcreatecert mail.mydomain.com webmail.mydomain.com webmail.yourdomain.com<br />
<br />
==Install the server certificate files (as zimbra)==<br />
* For Tomcat (ZCS upto 4.5.x)<br />
zmcertinstall mailbox /opt/zimbra/ssl/ssl/server/tomcat.crt<br />
zmcertinstall mta /opt/zimbra/ssl/ssl/server/server.crt /opt/zimbra/ssl/ssl/server/server.key<br />
<br />
* For Mailboxd (ZCS < 5.0.3)<br />
zmcertinstall mailbox /opt/zimbra/ssl/ssl/server/mailboxd.crt<br />
zmcertinstall mta /opt/zimbra/ssl/ssl/server/server.crt /opt/zimbra/ssl/ssl/server/server.key<br />
<br />
''(Error: is no zmcertinstall in ZCS 5.0.2_GA_1975, just skip to deploycrt below)''<br />
<br />
* To update CA cert stored in LDAP (as zimbra, 4.x):<br />
''zmprov -l mcf zimbraCertAuthorityKeySelfSigned "`cat /opt/zimbra/ssl/ssl/ca/ca.key`"''<br />
''zmprov -l mcf zimbraCertAuthorityCertSelfSigned "`cat /opt/zimbra/ssl/ssl/ca/ca.pem`"''<br />
<br />
* 5.x (as root)<br />
/opt/zimbra/bin/zmcertmgr deploycrt self<br />
<br />
* You can see your updated certs in LDAP now and compare them to contents of /opt/zimbra/ssl/ssl/ca (as zimbra)<br />
zmprov -l gcf zimbraCertAuthorityKeySelfSigned <br />
zmprov -l gcf zimbraCertAuthorityCertSelfSigned<br />
<br />
==Restart zimbra services==<br />
* It may be necessary to restart the Zimbra servers for the changes to take effect (as zimbra).<br />
zmcontrol stop<br />
zmcontrol start<br />
<br />
=Troubleshooting=<br />
<br />
'''Note about 'unable to write random state':'''<br />
<br />
This is a "harmless" warning that openssl has no random number seed file. The [http://www.openssl.org/support/faq.html#USER1 full] [http://www.openssl.org/support/faq.html#USER2 story] is available from openssl.org.<br />
<br />
'''Permission denied (publickey,gssapi-with-mic)'''<br />
<br />
http://www.ncsa.uiuc.edu/UserInfo/Resources/Software/ssh/openssh_3.8.html<br />
<br />
{{Article Footer|ZCS 4.5.x & 5.0.x|2/23/2006}}<br />
<br />
[[Category:SSL/TLS]]<br />
[[Category:Troubleshooting Certificates]]<br />
[[Category:Certificates]]<br />
[[Category:ZCS 4.5]]<br />
[[Category:ZCS 5.0]]<br />
[http://www.ssmatrix.com Cheap SSL Certificates]</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=About_Creating_ZCS_Themes&diff=68750About Creating ZCS Themes2022-02-04T01:53:14Z<p>Jhurley: </p>
<hr />
<div>{{Archive}}<br />
<br />
'''''For information about ZCS 5.0 Themes, see the [http://files.zimbra.com/docs/skins/index.html ZWC 5.0 Themes]''<br />
'''<br />
<br />
You can create a theme as simply as setting two colors and their variants, or you make heavy modifications to the "chrome" or outlines of the user interface with extensive use of images. Information is provided about the details of how the theming mechanism works to enable you to create more advanced themes. <br />
<br />
Note that while the theming mechanism is very flexible, we recommend in the 4.x version of ZCS that you limit yourself to just changing colors and fonts. While there is nothing preventing you from making more advanced themes, we cannot guarantee that these themes will survive upgrades to the framework as we are planning some changes in the near future that will shift some things around. So if you don't mind having to possibly go back to the drawing board at some time in the future, go ahead and play around all you like. <br />
<br />
[[Customizing Themes and Adding Zimbra Powered Logo - Open Source Edition]].<br />
<br />
[[Creating_Themes_Long_Version]]<br />
<br />
If you have any questions or themes you want to share with the world, feel free to post them on the [http://www.zimbra.com/forums/ Zimbra Forums].<br />
<br />
[[Category:Themes]]</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zimbra_Support_Portal_User_Guide&diff=68492Zimbra Support Portal User Guide2021-10-21T17:06:20Z<p>Jhurley: /* HOME PAGE */</p>
<hr />
<div>= Default Ports Used by Zimbra =<br />
{{KB|{{ZC}}|}}<br />
{{WIP}}<br />
<br />
= Zimbra Support Portal =<br />
<br />
The Zimbra Support portal is build to provide a friendly and up to date user experience. To access the Support portal you will need an active support contract, a username and password. To obtain access please contact your Account representative or email Zimbra Support and we will verify your account and send a welcome email containing your username. <br />
<br />
Once you receive your username, you will need to reset your password. <br />
To do this, go to https://support.zimbra.com<br />
<br />
<br />
<center>[[File:Main_Login_Page.png |900px]] </center><br />
<br />
<br />
Select Forgot your password link within the login page and enter your Username. <br />
<br />
<center>[[File:Password_Reset.png |300px]]</center><br />
<br />
When successful and email will be sent to your contact email address containing a link to the reset password page. <br />
<br />
<center>[[File:Reset_Password_Email.png |600px]] </center><br />
<br />
If you do not receive an email it could be caused by:<br />
<br />
*Incorrect username. <br />
* Message was flagged as spam.<br />
* A different email address is listed as your primary email address.<br />
<br />
<br />
Select the link will open the reset password page:<br />
<br />
<center>[[File:Reset_Password_Page.png|250px]] </center><br />
<br />
If the reset password link within the email sends you back to the reset password URL, then the URL embedded within the email was modified during delivery. Customers who have experienced this issue had security protections that re-write embedded URL's from external senders and will need to white list https://support.zimbra.com. If whitelisting is not an option, please contact Support and we can work with you on an alternative solution.<br />
<br />
<br />
==HOME PAGE==<br />
<br />
Once logged in, you will be presented the Home page which contains latest postings from the Support team.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zimbra_Support_Portal_User_Guide&diff=68491Zimbra Support Portal User Guide2021-10-21T03:46:56Z<p>Jhurley: /* Zimbra Support Portal */</p>
<hr />
<div>= Default Ports Used by Zimbra =<br />
{{KB|{{ZC}}|}}<br />
{{WIP}}<br />
<br />
= Zimbra Support Portal =<br />
<br />
The Zimbra Support portal is build to provide a friendly and up to date user experience. To access the Support portal you will need an active support contract, a username and password. To obtain access please contact your Account representative or email Zimbra Support and we will verify your account and send a welcome email containing your username. <br />
<br />
Once you receive your username, you will need to reset your password. <br />
To do this, go to https://support.zimbra.com<br />
<br />
<br />
<center>[[File:Main_Login_Page.png |900px]] </center><br />
<br />
<br />
Select Forgot your password link within the login page and enter your Username. <br />
<br />
<center>[[File:Password_Reset.png |300px]]</center><br />
<br />
When successful and email will be sent to your contact email address containing a link to the reset password page. <br />
<br />
<center>[[File:Reset_Password_Email.png |600px]] </center><br />
<br />
If you do not receive an email it could be caused by:<br />
<br />
*Incorrect username. <br />
* Message was flagged as spam.<br />
* A different email address is listed as your primary email address.<br />
<br />
<br />
Select the link will open the reset password page:<br />
<br />
<center>[[File:Reset_Password_Page.png|250px]] </center><br />
<br />
If the reset password link within the email sends you back to the reset password URL, then the URL embedded within the email was modified during delivery. Customers who have experienced this issue had security protections that re-write embedded URL's from external senders and will need to white list https://support.zimbra.com. If whitelisting is not an option, please contact Support and we can work with you on an alternative solution.<br />
<br />
<br />
==HOME PAGE==<br />
<br />
Once logged in, the support portal provides a great deal of information</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zimbra_Support_Portal_User_Guide&diff=68490Zimbra Support Portal User Guide2021-10-21T03:40:46Z<p>Jhurley: /* Zimbra Support Portal */</p>
<hr />
<div>= Default Ports Used by Zimbra =<br />
{{KB|{{ZC}}|}}<br />
{{WIP}}<br />
<br />
== Zimbra Support Portal ==<br />
<br />
The Zimbra Support portal is build to provide a friendly and up to date user experience. To access the Support portal you will need an active support contract, a username and password. To obtain access please contact your Account representative or email Zimbra Support and we will verify your account and send a welcome email containing your username. <br />
<br />
Once you receive your username, you will need to reset your password. <br />
To do this, go to https://support.zimbra.com<br />
<br />
<br />
<center>[[File:Main_Login_Page.png |900px]] </center><br />
<br />
<br />
Select Forgot your password link within the login page and enter your Username. <br />
<br />
<center>[[File:Password_Reset.png |300px]]</center><br />
<br />
When successful and email will be sent to your contact email address containing a link to the reset password page. <br />
<br />
<center>[[File:Reset_Password_Email.png |600px]] </center><br />
<br />
If you do not receive an email it could be caused by:<br />
<br />
*Incorrect username. <br />
* Message was flagged as spam.<br />
* A different email address is listed as your primary email address.<br />
<br />
<br />
Select the link will open the reset password page:<br />
<br />
<center>[[File:Reset_Password_Page.png|250px]] </center><br />
<br />
If the reset password link within the email sends you back to the reset password URL, then the URL embedded within the email was modified during delivery. Customers who have experienced this issue had security protections that re-write embedded URL's from external senders and will need to white list https://support.zimbra.com. If whitelisting is not an option, please contact Support and we can work with you on an alternative solution.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Reset_Password_Page.png&diff=68489File:Reset Password Page.png2021-10-21T03:13:14Z<p>Jhurley: Zimbra Support Portal User Guide</p>
<hr />
<div>Zimbra Support Portal User Guide</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Reset_Password_Email.png&diff=68488File:Reset Password Email.png2021-10-21T03:10:55Z<p>Jhurley: Zimbra Support Portal User Guide</p>
<hr />
<div>Zimbra Support Portal User Guide</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Password_Reset.png&diff=68487File:Password Reset.png2021-10-21T03:09:51Z<p>Jhurley: Zimbra Support portal user guide</p>
<hr />
<div>Zimbra Support portal user guide</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Main_Login_Page.png&diff=68486File:Main Login Page.png2021-10-21T02:55:28Z<p>Jhurley: Support Portal Image</p>
<hr />
<div>Support Portal Image</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zimbra_Support_Portal_User_Guide&diff=68485Zimbra Support Portal User Guide2021-10-21T02:26:15Z<p>Jhurley: Created page with "= Default Ports Used by Zimbra = {{KB|{{ZC}}|}} {{WIP}} == Zimbra Support Portal == The Zimbra Support portal is build to provide a friendly and up to date user experience...."</p>
<hr />
<div>= Default Ports Used by Zimbra =<br />
{{KB|{{ZC}}|}}<br />
{{WIP}}<br />
<br />
== Zimbra Support Portal ==<br />
<br />
The Zimbra Support portal is build to provide a friendly and up to date user experience. To access the Support portal you will need an active support contract, a username and password. To obtain access please contact your Account representative or email Zimbra Support and we will verify your account and send a welcome email containing your username. <br />
<br />
Once you receive you user name, you will need to reset your password. To do this, go to https://support.zimbra.com<br />
<br />
<Login page></div>Jhurleyhttps://wiki.zimbra.com/index.php?title=CBPolicyd_with_Zimbra_MySQL&diff=68201CBPolicyd with Zimbra MySQL2021-06-11T20:59:36Z<p>Jhurley: /* Setting up CBPolicyd with Zimbra MySQL */</p>
<hr />
<div>__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
<br />
=Setting up CBPolicyd with Zimbra MySQL=<br />
{{KB|{{ZC}}|{{ZCS 9.0}}|{{ZCS 8.8}}|}}<br />
<br />
<br />
<br />
Execute the following steps on MTA Node to setup CBPolicyd with Zimbra MySQL.<br />
<br />
'''Note''': These steps do not support multi-MTA setups and if more than one MTA exist in an environment, these steps must be done on each MTA. <br />
<br />
* Clone the repo (as root) :<br />
$ git clone https://github.com/Zimbra/zm-core-utils.git<br />
<br />
* Go to <code>zm-core-utils/src/bin/</code> directory and execute the '''cbpolicyd.sh''' script:<br />
$ bash cbpolicyd.sh<br />
<br />
* Obtain password for <code>ad-policyd_db</code> user using below command:<br />
$ grep Pass /opt/zimbra/conf/cbpolicyd.conf.in<br />
<br />
* Login to MySQL database to change or review your polices using mysql client as <code>ad-policyd_db</code> user.<br />
$ su - zimbra<br />
$ /opt/zimbra/bin/mysql policyd_db -u ad-policyd_db -p <br />
<br />
SELECT * FROM quotas_limits;<br />
<br />
* Following will be the output:<br />
+----+----------+-----------------------+--------------+---------+----------+<br />
| ID | QuotasID | Type | CounterLimit | Comment | Disabled | <br />
+----+----------+-----------------------+--------------+---------+----------+<br />
| 1 | 1 | MessageCount | 10 | NULL | 0 |<br />
| 2 | 1 | MessageCumulativeSize | 8000 | NULL | 0 |<br />
| 3 | 2 | MessageCount | 12 | NULL | 0 |<br />
| 4 | 3 | MessageCount | 100 | NULL | 0 |<br />
| 5 | 4 | MessageCount | 125 | NULL | 0 |<br />
+----+----------+-----------------------+--------------+---------+----------+<br />
<br />
* CBPolicyd has been installed successfully. Following are the details of the policy:<br />
** Rate limit any sender from sending more than 100 emails every 60 seconds. Messages beyond this limit are deferred.<br />
** Rate limit any @domain from receiving more than 125 emails in a 60 second period. Messages beyond this rate are rejected.<br />
<br />
* For testing purpose, we can set the following policy:<br />
** 2 emails every 60 seconds. Messages beyond this limit are deferred.<br />
** 2 emails in a 60 second period. Messages beyond this rate are rejected.<br />
<br />
* As <code>ad-policyd_db</code> user, login to the MySQL database and execute the following commands for updating '''quotas_limits''' table to set the above mentioned policies:<br />
$ /opt/zimbra/bin/mysql policyd_db<br />
UPDATE quotas_limits SET CounterLimit = 2 WHERE ID = 4;<br />
UPDATE quotas_limits SET CounterLimit = 2 WHERE ID = 5;<br />
<br />
* To make the configuration effective, execute these commands as <code>zimbra</code> user:<br />
$ su - zimbra<br />
$ zmprov ms `zmhostname` +zimbraServiceEnabled cbpolicyd<br />
$ zmprov ms `zmhostname` zimbraCBPolicydQuotasEnabled TRUE <br />
<br />
* Restart services:<br />
$ zmmtactl restart<br />
$ zmcbpolicydctl start<br />
<br />
'''Note:'''<br />
<br>The installed policy is a basic template to get started.<br><br />
In many cases you will want to set the `Period` column in `quotas` table to 600 or 3600 and set `CounterLimit` to around 100 for all records of type `MessageCount` in `quotas_limits` table.<br><br />
It is recommended to monitor the users e-mailing behavior prior to installing cbpolicyd. Be prepared to alter the limits after installing in case your users send more email than expected.<br />
<br />
==Testing the CBPolicyd configuration==<br />
<br />
* Login to Zimbra Modern Web App.<br />
* Send 2 emails within 60 seconds.<br />
* You will see an error message in UI:<br />
''You are sending too many emails, contact helpdesk.''<br />
* Similar message will also get logged in <code>/var/log/zimbra.log</code> and <code>/opt/zimbra/log/cbpolicyd.log</code><br />
<br />
===Tested versions===<br />
* Centos 7: 9.0.0_P14<br />
* Centos 8: 8.8.15_P21<br />
* Ubuntu 16: 9.0.0_P14 <br />
* Ubuntu 18: 8.8.15_P21</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Full_Setting_window.png&diff=68031File:Full Setting window.png2021-03-11T23:45:37Z<p>Jhurley: for ZCO_unable_to_send_from_another_account wiki</p>
<hr />
<div>for ZCO_unable_to_send_from_another_account wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Setting_window_modern.png&diff=68030File:Setting window modern.png2021-03-11T22:51:55Z<p>Jhurley: for ZCO_unable_to_send_from_another_account wiki</p>
<hr />
<div>for ZCO_unable_to_send_from_another_account wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Modern_Setting_2.png&diff=68029File:Modern Setting 2.png2021-03-11T22:13:47Z<p>Jhurley: for ZCO_unable_to_send_from_another_account wiki</p>
<hr />
<div>for ZCO_unable_to_send_from_another_account wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Setting_modern.png&diff=68028File:Setting modern.png2021-03-11T22:11:36Z<p>Jhurley: for ZCO_unable_to_send_from_another_account wiki</p>
<hr />
<div>for ZCO_unable_to_send_from_another_account wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Ajax_Account_page.png&diff=68027File:Ajax Account page.png2021-03-11T22:04:24Z<p>Jhurley: forZCO_unable_to_send_from_another_account wiki</p>
<hr />
<div>forZCO_unable_to_send_from_another_account wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:ZWC_add_persona.png&diff=68026File:ZWC add persona.png2021-03-11T21:57:49Z<p>Jhurley: for ZCO_unable_to_send_from_another_account wiki</p>
<hr />
<div>for ZCO_unable_to_send_from_another_account wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:SendFrom.png&diff=68025File:SendFrom.png2021-03-11T21:44:41Z<p>Jhurley: for ZCO_unable_to_send_from_another_account wiki</p>
<hr />
<div>for ZCO_unable_to_send_from_another_account wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Modify_new_persoan_.png&diff=68024File:Modify new persoan .png2021-03-10T19:05:54Z<p>Jhurley: for ZCO_unable_to_send_from_another_account</p>
<hr />
<div>for ZCO_unable_to_send_from_another_account</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:Add_Persona.png&diff=68023File:Add Persona.png2021-03-10T19:02:24Z<p>Jhurley: For ZCO_unable_to_send_from_another_account</p>
<hr />
<div>For ZCO_unable_to_send_from_another_account</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:ZCOPersonabutton.png&diff=68020File:ZCOPersonabutton.png2021-03-05T20:20:23Z<p>Jhurley: ZCO Unable to Send As or from Send on the Behalf wiki</p>
<hr />
<div>ZCO Unable to Send As or from Send on the Behalf wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68019Zco partial sync2021-03-05T17:59:56Z<p>Jhurley: /* ZCO Outlook Partial Sync */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Partial Account Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent the profile from running into known performance and profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
[[File:ZCOSyncOption.png |300px]]<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<br />
[[File:ZCOStartPurge.png |300px]]<br />
<br />
<br />
During a purge, the ''Start Purge'' button will show as ''Pause Purge'' which will stop the purge at its current status.<br />
<br />
<br />
[[File:ZCOPausePurge.png |300px]]<br />
<br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purged outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' A User can disable purge by selecting Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<br />
[[File:ZCOhoverover.png |300px]]<br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry. <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68018Zco partial sync2021-03-05T17:57:42Z<p>Jhurley: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent the profile from running into known performance and profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
[[File:ZCOSyncOption.png |300px]]<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<br />
[[File:ZCOStartPurge.png |300px]]<br />
<br />
<br />
During a purge, the ''Start Purge'' button will show as ''Pause Purge'' which will stop the purge at its current status.<br />
<br />
<br />
[[File:ZCOPausePurge.png |300px]]<br />
<br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purged outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' A User can disable purge by selecting Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<br />
[[File:ZCOhoverover.png |300px]]<br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry. <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68017Zco partial sync2021-03-05T17:55:06Z<p>Jhurley: /* Understanding and Managing Partial Sync */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent the profile from running into known performance and profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
[[File:ZCOSyncOption.png |300px]]<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<br />
[[File:ZCOStartPurge.png |300px]]<br />
<br />
<br />
During a purge, the ''Start Purge'' button will show as ''Pause Purge'' which will stop the purge at its current status.<br />
<br />
<br />
[[File:ZCOPausePurge.png |300px]]<br />
<br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purged outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' A User can disable purge by selecting Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<br />
[[File:ZCOhoverover.png |300px]]<br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry. <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68016Zco partial sync2021-03-04T21:04:42Z<p>Jhurley: /* ZCO Outlook Partial Sync */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent the profile from running into known performance and profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
[[File:ZCOSyncOption.png |300px]]<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<br />
[[File:ZCOStartPurge.png |300px]]<br />
<br />
<br />
During a purge, the ''Start Purge'' button will show as ''Pause Purge'' which will stop the purge at its current status.<br />
<br />
<br />
[[File:ZCOPausePurge.png |300px]]<br />
<br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' A User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<br />
[[File:ZCOhoverover.png |300px]]<br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry. <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68015Zco partial sync2021-03-04T20:43:03Z<p>Jhurley: /* Understanding and Managing Partial Sync */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
[[File:ZCOSyncOption.png |300px]]<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<br />
[[File:ZCOStartPurge.png |300px]]<br />
<br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<br />
[[File:ZCOPausePurge.png |300px]]<br />
<br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<br />
[[File:ZCOhoverover.png |300px]]<br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:ZCOhoverover.png&diff=68014File:ZCOhoverover.png2021-03-04T20:21:19Z<p>Jhurley: ZCO Partial Sync wiki</p>
<hr />
<div>ZCO Partial Sync wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:ZCOPausePurge.png&diff=68013File:ZCOPausePurge.png2021-03-04T19:41:25Z<p>Jhurley: ZC Partial Sync wiki</p>
<hr />
<div>ZC Partial Sync wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:ZCOStartPurge.png&diff=68012File:ZCOStartPurge.png2021-03-04T19:36:59Z<p>Jhurley: ZCO Partial Sync wiki</p>
<hr />
<div>ZCO Partial Sync wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68011Zco partial sync2021-03-04T19:31:09Z<p>Jhurley: /* Existing profiles */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
[[File:ZCOSyncOption.png |300px]]<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68010Zco partial sync2021-03-04T19:30:57Z<p>Jhurley: /* Existing profiles */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
[[File:ZCOSyncOption.png |350px]]<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=File:ZCOSyncOption.png&diff=68009File:ZCOSyncOption.png2021-03-04T19:26:30Z<p>Jhurley: Used within the ZCO Partial Sync wiki</p>
<hr />
<div>Used within the ZCO Partial Sync wiki</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68008Zco partial sync2021-03-04T19:24:19Z<p>Jhurley: /* Existing profiles */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select the Zimbra Ribbon, Advanced option then modify the Synchronization Options settings. There are two options: <br />
<br />
* ''Purge Calendar Items Older than:'' Removes all appointments older than configured date. <br />
* ''Purge Mail and Task Items older than:'' Removes all messages and tasks older than the configured date. <br />
<br />
<br />
<screenshot><br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68007Zco partial sync2021-03-04T19:23:01Z<p>Jhurley: /* New profiles */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without editing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select Zimbra Ribbon, Advanced then modify the Synchronization Options settings. There are four options: <br />
<br />
* Purge Calendar Items Older than: Removes all appointments older than configured date. <br />
* Purge Mail and Task Items older than: Removes all messages and tasks older than the configured date. <br />
<br />
<br />
<screenshot><br />
<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68006Zco partial sync2021-03-04T19:21:40Z<p>Jhurley: /* How do you implement Partial Sync? */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enable within an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without accessing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select Zimbra Ribbon, Advanced then modify the Synchronization Options settings. There are four options: <br />
<br />
* Purge Calendar Items Older than: Removes all appointments older than configured date. <br />
* Purge Mail and Task Items older than: Removes all messages and tasks older than the configured date. <br />
<br />
<br />
<screenshot><br />
<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68005Zco partial sync2021-03-04T19:20:04Z<p>Jhurley: /* Why was Partial Sync added? */</p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the pst 50 GB file size limit. With Zimbra Connector providing partial sync within Outlook, this allows users to access their most recent data within the Outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enabling in an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without accessing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select Zimbra Ribbon, Advanced then modify the Synchronization Options settings. There are four options: <br />
<br />
* Purge Calendar Items Older than: Removes all appointments older than configured date. <br />
* Purge Mail and Task Items older than: Removes all messages and tasks older than the configured date. <br />
<br />
<br />
<screenshot><br />
<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68004Zco partial sync2021-03-04T19:17:44Z<p>Jhurley: </p>
<hr />
<div>{{BC|Certified}}<br />
__FORCETOC__<br />
<div class="col-md-12 ibox-content"><br />
=ZCO Outlook Partial Sync=<br />
{{KB|{{ZC}}|{{ZCO 9.0}}|}}<br />
{{WIP}}<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the PST 50 GB file size limit. With Zimbra Connector providing partial sync, allows users to access their most recent data within the outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enabling in an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without accessing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select Zimbra Ribbon, Advanced then modify the Synchronization Options settings. There are four options: <br />
<br />
* Purge Calendar Items Older than: Removes all appointments older than configured date. <br />
* Purge Mail and Task Items older than: Removes all messages and tasks older than the configured date. <br />
<br />
<br />
<screenshot><br />
<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68003Zco partial sync2021-03-04T19:14:10Z<p>Jhurley: /* New profiles */</p>
<hr />
<div>==ZCO Outlook Partial Sync Customization==<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the PST 50 GB file size limit. With Zimbra Connector providing partial sync, allows users to access their most recent data within the outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enabling in an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without accessing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select Zimbra Ribbon, Advanced then modify the Synchronization Options settings. There are four options: <br />
<br />
* Purge Calendar Items Older than: Removes all appointments older than configured date. <br />
* Purge Mail and Task Items older than: Removes all messages and tasks older than the configured date. <br />
<br />
<br />
<screenshot><br />
<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurleyhttps://wiki.zimbra.com/index.php?title=Zco_partial_sync&diff=68002Zco partial sync2021-03-04T18:53:03Z<p>Jhurley: /* Understanding and Managing Partial Sync */</p>
<hr />
<div>==ZCO Outlook Partial Sync Customization==<br />
<br />
ZCO now supports partial account sync that allows users with large accounts the ability to sync a defined number of days worth of messages, Tasks, and calendars to prevent them from running into known profile size limitations. <br />
<br />
====Why was Partial Sync added?====<br />
<br />
Partial account sync was added because within today’s business environment, it's common for power users to have large mail accounts that can cause Outlook performance issues due to profile size, Outlook version, hardware configuration, and system load. Also, many profiles can now exceed the PST 50 GB file size limit. With Zimbra Connector providing partial sync, allows users to access their most recent data within the outlook client but still provides the user the ability to store and obtain older data from the Zimbra Web client.<br />
<br />
====How do you implement Partial Sync?====<br />
<br />
There are two ways to implement ZCO partial sync, create a new profile or enabling in an existing profile. The following is an outline of how to configure, enable, and how ZCO partial sync works.<br />
<br />
==New profiles==<br />
<br />
In a default installation, ZCO partial sync is set to disable and the full account will be synced. It is recommended to create a ZmCustomizeMsi.js file to enable and configure an initial sync limit. This will prevent the excessive load and actions of the full account syncing, then having the retention setting purge the unwanted data. The user or admin can also enable these attributes within the registry at:<br />
<br />
Computer\HKEY USER\SOFTWARE\Zimbra\CalCutoffDays < N > DWORD<br />
Computer\HKEY USER\SOFTWARE\Zimbra\MsgCutoffDays < N > DWORD<br />
<br />
Where <N> is the last number of days that will be synced, the default setting is 0. <br />
<br />
''Please note'', this setting is configured during the initial sync of the account. If the configuration isn't set correctly and the initial sync is started, the profile will need to be recreated to recognize the new initial sync requirements. This method can also be used to set the value without accessing the registry. This is because the initial sync and partial sync configuration uses the same registry attributes and is a global configuration. If the user creates a profile using the steps below within the existing profile then purge and creates a new profile, the new profile will inherit the new initial sync attributes.<br />
<br />
For steps on how to create a ZCO customized installer, please see the Customizing the Installer section within the Zimbra Connector for Microsoft Outlook: Admin Guide.<br />
<br />
==Existing profiles==<br />
<br />
For existing profiles, users can enable the feature by logging into the profile within Outlook, select Zimbra Ribbon, Advanced then modify the Synchronization Options settings. There are four options: <br />
<br />
* Purge Calendar Items Older than: Removes all appointments older than configured date. <br />
* Purge Mail and Task Items older than: Removes all messages and tasks older than the configured date. <br />
<br />
<br />
<screenshot><br />
<br />
<br />
==Understanding and Managing Partial Sync==<br />
<br />
When messages are removed from the profile, they are not automatically deleted. The Partial Sync process will move targeted data to a subfolder within trash called Zimbra Trash. This is how the system identifies which data needs to be purged at the server-side vs the client only. Data will stay within the Zimbra Trash folder until the user initiates a ''Start Purge'' or Outlook deletes the Zimbra Trash folder from Trash. If the Zimbra Trash folder is deleted, the folder will be recreated during the next retention run. <br />
<br />
Users can initiate the purge by selecting ''Start Purge'' within the purge section of the Zimbra ribbon. <br />
<br />
<Screenshot> <br />
<br />
During a purge, the Start Purge button will show as Pause Purge which will stop the purge at its current status.<br />
<br />
<Screenshot> <br />
<br />
''Calendaring:'' All Calendars excluding active reoccurring appointments will be purge outside of the configured purge window. Active reoccurring and all modified instances of an appointment will reside in the calendar until the end date of the reoccurring appointment surpasses the purge date. Increased profile size can be caused by reoccurring appointments where an organizer is modifying instances of a reoccurring appointment with no end date and the appointment has been in existence for years. For reoccurring appointments that do not have an end date and occur daily or weekly, Zimbra recommends setting a defined end date that represents your business cycle, like yearly. Then create a new reoccurring appointment for the next business cycle. <br />
<br />
''Disable Purge;'' User can disable purge by select Zimbra Ribbon, Advanced then updating Purge Calendar Items Older than and Purge Mail and Task Items older than to 0. This will require a restart of Outlook and once disabled, the Purge button will be grayed out.<br />
<br />
''Purge Count:'' To obtain the number of purged items since the last restart of Outlook, hover the mouse over the Start/Pause Purge button. A display will appear with total items purged since the last restart. <br />
<br />
<<Screenshot>><br />
<br />
<br />
"Idle Profiles:" When accounts are inactive for an extended period of time like due to vacations, at the initial restart, the profiles will sync new data that occurred during the idle time. If the idle days exceed the retention days, new messages could be moved to the Zimbra Trash folder. If the user does not want this to occur, then they need to change the sync day value to 0 or a number of days greater than new messages or pause the purge. Also if the profile is idle for an extended time, the user could get a warning message to rebuild the profile.<br />
<br />
ZCO partial sync does not remove the data from the server, only the local profile. Once the message is purge from the local profile, the user can view the message within the Zimbra web client. There is no method to resync purge data.<br />
<br />
ZCO partial sync only applies to primary account data. Mounted data from shared profiles or local profiles will not be managed by this process and can affect the performance of Outlook.<br />
<br />
ZCO partial sync is disabled in a default installation and will need to be enabled by creating a custom installer or updating the registry <br />
<br />
Upgrading ZCO will retain the existing configuration.</div>Jhurley