Line 12: |
Line 12: |
| | | |
| == Instructions == | | == Instructions == |
− | *1.) Install Thunderbird:
| + | === Install Thunderbird:=== |
− | **2.) Log into a client computer as “admin”.
| + | # Log into a client computer as “admin”. |
− | **3.) Download and install Thunderbird to a local folder that is writable by all users. This example uses “c:\Applications\Thunderbird”
| + | # Download and install Thunderbird to a local folder that is writable by all users. This example uses “c:\Applications\Thunderbird” |
− | **4.) Start Thunderbird and configure it using the “admin” email account (Using IMAPS or POPS, SMTPS and the full external SME server name is recommended so this configuration will work outside the network). Do not subscribe to IMAP folders or save your password at this time.
| + | # Start Thunderbird and configure it using the “admin” email account (Using IMAPS or POPS, SMTPS and the full external SME server name is recommended so this configuration will work outside the network). Do not subscribe to IMAP folders or save your password at this time. |
− | **5.) Install and configure any Thunderbird Extensions. Note: This method will replace any instance of "admin" with the user's login. Do not use any other name than "admin" in settings where you want the user's information to appear. For example in Thunderbird the user's name should be "admin" and not "SME Administrator". User's can change these configurations later if desired.
| + | # Install and configure any Thunderbird Extensions. Note: This method will replace any instance of "admin" with the user's login. Do not use any other name than "admin" in settings where you want the user's information to appear. For example in Thunderbird the user's name should be "admin" and not "SME Administrator". User's can change these configurations later if desired. |
− | **6.) Configure any shared address books and calendars (using https addresses to keep the user’s credentials secure).
| + | # Configure any shared address books and calendars (using https addresses to keep the user’s credentials secure). |
− | *2.) Setup SME server:
| + | ===Setup SME server:=== |
− | **1.) Create and ibay with Write access “admin” and read access “everyone”.
| + | ====Create and ibay ==== |
− | **2.) Applications:
| + | * give Write access “admin” and read access “everyone”. |
− | ***1.) Copy the local install folder (“c:\Applications”) of to this new share (“\\<server>\<share>\Applications”).
| + | ====Applications:==== |
− | **3.) Installs:
| + | # Copy the local install folder (“c:\Applications”) of to this new share (“\\<server>\<share>\Applications”). |
− | ***1.) Create a “Installs” folder on the server share (“\\<server>\<share>\Installs”).
| + | ====Installs:==== |
− | ***2.) Create a folder for your desktop shortcuts (“\\<server>\<share>\Installs\Desktop Shortcuts”).
| + | # Create a “Installs” folder on the server share (“\\<server>\<share>\Installs”). |
− | ***3.) Copy the Thunderbird Desktop Shortcut to the server shortcuts folder.
| + | # Create a folder for your desktop shortcuts (“\\<server>\<share>\Installs\Desktop Shortcuts”). |
− | ***4.) Copy “C:\Documents and Settings\admin\Application Data\Thunderbird” to this new folder. There will now be a folder “\\<server>\<share>\Installs\Thunderbird”. Note: the “Application Data” folder is a hidden folder.
| + | # Copy the Thunderbird Desktop Shortcut to the server shortcuts folder. |
− | ***5.) Uninstall Thunderbird from the client computer.
| + | # Copy “C:\Documents and Settings\admin\Application Data\Thunderbird” to this new folder. There will now be a folder “\\<server>\<share>\Installs\Thunderbird”. Note: the “Application Data” folder is a hidden folder. |
− | **4.) Utilities:
| + | # Uninstall Thunderbird from the client computer. |
− | ***1.) Create a “Utilities” folder on the server share (“\\<server>\<share>\Utilities”).
| + | ====Utilities:==== |
− | ***2.) Search the internet and download “munge.exe” (part of the MS Windows XP Resource Kit) and place it in your “Utilities” folder.
| + | # Create a “Utilities” folder on the server share (“\\<server>\<share>\Utilities”). |
− | *3.) Create an Install Thunderbird batch file:
| + | # Search the internet and download “munge.exe” (part of the MS Windows XP Resource Kit) and place it in your “Utilities” folder. |
− | **1.) Create a batch file in the “Utilities” folder (“\\<server>\<share>\Utilities\Thunderbird_Install.bat”).
| + | ===Create an Install Thunderbird batch file:=== |
− | **2.) Edit this file with notepad and add the following (make sure to enter your data where there are "<>"):
| + | # Create a batch file in the “Utilities” folder (“\\<server>\<share>\Utilities\Thunderbird_Install.bat”). |
| + | # Edit this file with notepad and add the following (make sure to enter your data where there are "<>"): |
| | | |
| title DO NOT CLOSE THIS WINDOW! - Installing Thunderbird | | title DO NOT CLOSE THIS WINDOW! - Installing Thunderbird |
Line 101: |
Line 102: |
| | | |
| | | |
− | *4.) Modify the netlogin.bat file on the SME server to call the Thunderbird install batch file just created and redirect the output to a log file either locally or on the server.
| + | ===Modify the netlogin.bat=== |
| + | Modify the netlogin.bat file on the SME server to call the Thunderbird install batch file just created and redirect the output to a log file either locally or on the server. |
| | | |
| call "\\<server>\<share>\Utilities\Thunderbird_Install.bat" >"c:\Applications\Thunderbird_Install-%username%.log" 2>&1 | | call "\\<server>\<share>\Utilities\Thunderbird_Install.bat" >"c:\Applications\Thunderbird_Install-%username%.log" 2>&1 |
Line 110: |
Line 112: |
| Here are some comments on my experiences: | | Here are some comments on my experiences: |
| | | |
− | *Funambol in General
| + | ===Funambol in General=== |
− | **Pros:
| + | *Pros: |
− | ***Fast.
| + | **Fast. |
− | ***True synchronization of data records and not global file copy.
| + | **True synchronization of data records and not global file copy. |
− | **Cons:
| + | *Cons: |
− | ***Unstable? Often duplicates records. Server time out error renders client permanently "un-syncable".
| + | **Unstable? Often duplicates records. Server time out error renders client permanently "un-syncable". |
− | ***Configuration stored in Windows Registry. Different Funambol settings for each Thunderbird profile not possible.
| + | **Configuration stored in Windows Registry. Different Funambol settings for each Thunderbird profile not possible. |
− | ***Only a single address book and calendar can be synced.
| + | **Only a single address book and calendar can be synced. |
− | ***Windows only.
| + | **Windows only. |
− | ***Plug-in needs to be rewritten to be more "compliant" to the Thunderbird methodology.
| + | **Plug-in needs to be rewritten to be more "compliant" to the Thunderbird methodology. |
| | | |
− | *Funambol with eGroupware 1.4
| + | ===Funambol with eGroupware 1.4=== |
− | **Pros:
| + | *Pros: |
− | ***Syncs with webmail.
| + | **Syncs with webmail. |
− | **Cons:
| + | *Cons: |
− | ***Must have PHP 5 installed.
| + | **Must have PHP 5 installed. |
− | ***Users must login to eGroupware at least once to create their account.
| + | **Users must login to eGroupware at least once to create their account. |
− | ***Complicated install with SME 7.
| + | **Complicated install with SME 7. |
| | | |
− | *Funambol with Horde 3.3
| + | ===Funambol with Horde 3.3=== |
− | **Pros:
| + | *Pros: |
− | ***Syncs with webmail.
| + | **Syncs with webmail. |
− | **Cons:
| + | *Cons: |
− | ***Users must first create a contact in Horde before they are able to see the synchronized entries in Horde (Horde bug?).
| + | **Users must first create a contact in Horde before they are able to see the synchronized entries in Horde (Horde bug?). |
| | | |
− | *SyncKolab
| + | ===SyncKolab=== |
− | **Pros:
| + | *Pros: |
− | ***Reliable to date.
| + | **Reliable to date. |
− | ***True synchronization of data records and not global file copy.
| + | **True synchronization of data records and not global file copy. |
− | ***Can have several shared address books and calendars.
| + | **Can have several shared address books and calendars. |
− | **Cons:
| + | *Cons: |
− | ***Slow.
| + | **Slow. |
− | ***Data store is in an IMAP folder that users have direct access to.
| + | **Data store is in an IMAP folder that users have direct access to. |
− | ***Somewhat complicated setup.
| + | **Somewhat complicated setup. |
− | ***Dovecot IMAP does not support ACLs or shared IMAP folders. Group shares must be on another account.
| + | **Dovecot IMAP does not support ACLs or shared IMAP folders. Group shares must be on another account. |
| | | |
− | *Groupdav with eGroupware 1.6
| + | ===Groupdav with eGroupware 1.6=== |
− | **Pros:
| + | *Pros: |
− | ***Reliable.
| + | **Reliable. |
− | ***True synchronization of data records and not global file copy (I believe).
| + | **True synchronization of data records and not global file copy (I believe). |
− | ***Can have several shared address books and calendars.
| + | **Can have several shared address books and calendars. |
− | ***Simple client setup.
| + | **Simple client setup. |
− | **Cons:
| + | *Cons: |
− | ***Slow.
| + | **Slow. |
− | ***Requires PHP 5 and Mysql 5. Not supported on SME 7.
| + | **Requires PHP 5 and Mysql 5. Not supported on SME 7. |
| | | |
− | *WebDAV
| + | ===WebDAV=== |
− | **Pros:
| + | *Pros: |
− | ***Reliable.
| + | **Reliable. |
− | ***Can have several shared calendars.
| + | **Can have several shared calendars. |
− | ***Good for sharing a group calendar read only.
| + | **Good for sharing a group calendar read only. |
− | **Cons:
| + | *Cons: |
− | ***Slow.
| + | **Slow. |
− | ***Full ics file sync not individual events.
| + | **Full ics file sync not individual events. |
− | ***Can only share calendars.
| + | **Can only share calendars. |
− | ***Need DAV contrib installed.
| + | **Need DAV contrib installed. |
| | | |
| | | |