SCOoffice Server 4.1.0Ga Maintenance Pack 4a
Release and Installation Notes

The SCOoffice Server Maintenance Pack 4a contains important fixes for SCOoffice Server Release 4.1.0Ga and should be applied at your next maintenance period. Be sure to install this maintenance pack before submitting problem reports to SCO Support.

These Release and Installation Notes contain critical information that you need to know before and after installing SCOoffice Server Maintenance Pack 4a. Please familiarize yourself with the information that is relevant to your system, then install the Maintenance Pack according to the instructions in this document.

These Release and Installation Notes cover the following topics:

  • About Maintenance Packs
  • Before installing the Maintenance Pack
  • Installing the Maintenance Pack
  • Removing the Maintenance Pack
  • Bugs Fixed by the Maintenance Pack
  • Maintenance Pack notes
  • Limitations

About Maintenance Packs

A Maintenance Pack (MP) is a collection of security updates and fixes for reported problems. Maintenance Packs are cumulative, so only the latest one needs to be installed.

Maintenance Packs are made available periodically and can be downloaded and installed in accordance with the terms of your maintenance agreement. Current maintenance is free for all SCOoffice Server 4.1 customers, but SCO reserves the right to introduce an annual maintenance and upgrade fee in the future. SCOoffice Server Maintenance Packs are available for download from the SCO Support Services Download web page at:
 
         http://www.sco.com/support/download.html

Before Installing the Maintenance Pack

  • Maintenance Pack 4a can only be installed on SCOoffice Server 4.1.0Ga systems.

  • Maintenance Pack 4a supersedes the following updates. Do not install any of the updates listed here after installing Maintenance Pack 4a.

    • Maintenance Pack 1 for SCOoffice Server 4.1.
    • Maintenance Pack 2 for SCOoffice Server 4.1.
    • Maintenance Pack 2a for SCOoffice Server 4.1.
    • Maintenance Pack 3 for SCOoffice Server 4.1.
    • Maintenance Pack 4 for SCOoffice Server 4.1.
    • ERG712894 - SCOoffice Server 4.1 WebClient fix for 8-bit characters
    • ERG712733 - French translation issues
    • ERG712815 - Portuguese issues with SCOoffice connector and Webclient
    • ERG712833 - PST Migration does not include entries other than mail
    • ERG712813 - Fix SCOoffice WebClient custom_links
    • ERG712832 - SCOoffice Autocomplete for WebClient

  • If Maintenance Pack 4 is installed, it should be removed before Maintenance Pack 4a is installed.

  • Maintenance Pack 4a can be installed if earlier Maintenance Packs (1, 2a or 3) are already installed. If an earlier Maintenance Pack is installed, only files and fixes new in Maintenance Pack 4a will be installed. If an earlier Maintenance Pack is not installed, all files and fixes will be installed.

  • Back up the data on your system and verify the integrity of the backup.

  • If the SCOoffice Server 4.1.0 Connector 3.0.7-1129174 Supplement is installed, remove it before installing Maintenance Pack 4a.  Connector 3.0.7-1129174 is beta software and has a hardcoded expiration date.

  • If an earlier Maintenance Pack is installed, the following does not apply. If an earlier Maintenance Pack is NOT installed, then to install Maintenance Pack 4a SCOoffice Server must be running in single server mode. Systems that are master or slave servers in a distributed configuration or that are set to use Active Directory for authentication (adauth mode) must be re-configured to single server mode before you can install the Maintenance Pack. After the Maintenance Pack is successfully installed, you can switch back to master, slave, or adauth mode.

    • To confirm the state of a server and, if necessary, re-configure the system to single server mode:

    1.      Ensure that all users are logged off the system before making any configuration changes.


    2.      Log into the SCOoffice Server GUI as the admin user.


    3.      Click on Configuration then Distributed Mail in the navigation bar on the left side of the page.


    4.      Locate where the hostname of your server is displayed followed by the ``Type'' drop down selection list.


        1. If the server is set to ``Master'' or ``Slave'', note current configuration settings on this page then change the setting to ``Single'' and click on the Set button.

        2. If the server is set to ``Single'' AND ``Active Directory Authentication'' is set to ``On'', note the current configuration settings on this page then click on the Switch to Single Mode button.

        3. If the server is set to ``Single'' and ``Active Directory Authentication'' is set to ``Off'', the system is already configured for single server mode.

    Once you've confirmed that the server is in single server mode, it is safe to install the Maintenance Pack.

  • Maintenance Pack 4a should either be installed while the server is in maintenance mode, or in multi-user mode after stopping the SCOoffice Server processes by entering the following command as root:
     
             /etc/init.d/insightserver stop
     
    The Maintenance Pack installation may update kernel tuning, which requires the kernel to be re-linked. Reboot the server after Maintenance Pack 4a is successfully installed to ensure that all SCOoffice Server processes are restarted.

  • Maintenance Pack 4a replaces the configuration file:
     
             /opt/insight/icc/groupware/conf/custom.inc.php
     
    If you have customized any values in this file you will need to edit the file after the Maintenance Pack is installed to set your customized values again. A copy of your pre-Maintenance Pack custom.inc.php file will be saved in the following location:
     
             /var/opt/K/SCO/oms/OMS410MP4A.oms410.SCO.oms/patch_backup/opt/insight/icc/groupware/conf/custom.inc.php

  • Maintenance Pack 4a may be safely removed and re-installed.

  • Maintenance Pack 4a does not change the SCOoffice Server 4.1.0Ga product version number.

Installing the Maintenance Pack

To install SCOoffice Server Maintenance Pack 4a from media images that you download manually:

  1. Log in as root.

  2. Download the Maintenance Pack from either the SCO web site or using FTP.

         - to use the web site, go to the SCO Support Services Download web page:

                   http://www.sco.com/support/update/download/release.php?rid=156

         - to use FTP, for the MP4a Cover Letter see:

                   ftp://ftp.sco.com/pub/office/410/mp/office410mp4a/office410mp4a.ltr

         - and for the Maintenance Pack 4a archive see:

                   ftp://ftp.sco.com/pub/office/410/mp/office410mp4a/office410mp4a_vol.tar

  3. Download the office410mp4a_vol.tar file to an empty directory, such as /tmp/office410mp4a. After the download is complete, change to the directory containing the office410mp4a_vol.tar file and run the following to extract the media image files:

         tar xvf office410mp4a_vol.tar

  4. Start the Software Manager by double-clicking on its icon on the desktop, or by entering the following at the command-line prompt:

         scoadmin software

  5. From the Software menu, select Install New.

  6. When prompted for the host (machine), select the current host and then click on Continue.

  7. Select Media Images as the Media Device then click on Continue. (You may need to scroll down before you see the Media Images option.)

  8. Enter the absolute pathname for the directory that contains the Maintenance Pack 4a media images. For example:

         /tmp/office410mp4a

  9. Click on OK.

  10. In the Install Selection window, make sure that the Maintenance Pack is highlighted then click on Install.

  11. When the installation is complete, click on OK. The Software Manager lists Maintenance Pack 4a among the installed software.

  12. Exit the Software Manager by selecting the Host menu, then Exit.

  13. Reboot the machine. (If the Software Manager relinks the kernel, you must reboot before the new kernel takes effect.)

Removing the Maintenance Pack

If an earlier Maintenance Pack is installed, this note does not apply. If an earlier Maintenance Pack is NOT installed, then this Maintenance Pack cannot be removed from SCOoffice Server systems that are configured as master or slave servers, or from servers that are configured to use Active Directory Authentication (adauth mode). Before attempting to remove the Maintenance Pack, verify that SCOoffice Server is in single server mode. See ``Before Installing the Maintenance Pack'' for instructions on verifying and, if necessary, reconfiguring the server mode.

  1. Log in as root.

  2. Start the Software Manager by double-clicking its icon on the desktop, or by entering the following at the command-line prompt:

         scoadmin software

  3. Select the Maintenance Pack in the list of installed software.

  4. From the Software menu, select Remove Software. In the confirmation window, verify that you selected the correct software, then click on Remove.

  5. A window displays, showing you a list of software that will stop functioning after the Maintenance Pack is removed. Click on Continue.

  6. When the Removal complete window appears, click on OK and exit the Software Manager by selecting Exit from the Host menu.

CRITICAL UPDATE for SMP systems

An issue with the socket driver on multi-processor systems has been identified which can prevent Postfix from delivering mail. This manifests as a very large number of messages in Postfix mailq with a very slow rate of delivery due to transport unavailability.

You may see messages in the /var/adm/syslog file similar to this:

   Feb 15 15:08:24 myserver postfix/qmgr[572]: 3870022948: to=<deagan@mycompany.com>, 
   relay=none, delay=1953, status=deferred (transport is unavailable)

A corrected socket driver is available in Maintenance Pack 4 or later for SCO OpenServer 5.0.7 (this is a different update than Maintenance Pack 4 or 4a for SCOoffice Server).

Please contact your Support representative or visit http://support.sco.com.

Bugs Fixed by the Maintenance Pack

Included from Maintenance Pack 1

530115

-

Can't use same alias name in multiple virtual domains.

530186

-

Some localization issues due to improper UTF8 encoding have been resolved.

530191

-

Defining ``send only local mail'' or ``receive only local mail'' doesn't work properly. Removed drop down selection menus. Implement ``send only local mail'' and ``receive only local mail'' at the bottom of the User account page.

530192

-

The documentation doesn't match with current GUI for setting ``local mail only''.

530193

-

Outlook doesn't recognize special folder types such as Calendar or Contacts.

530195

-

Contact Items folder type translation missing from the WebClient.

530197

-

Days translation missing - admin->Tools->taskplanner (German).

530199

-

Problems creating/deleting/renaming folders in WebClient for Spanish.

530200

-

Can't login to WebClient or the GUI when the server is configured for Active Directory authentication.

530201

-

Exchange Migration creates an extra top level directory.

530202

-

Migration now migrates mail folders and Calendar and Contacts folders.

530223

-

Migration from server running SCOoffice Server 2.0 fails with error when importing mail folders.

530235

-

The Amavisd startup script fails to start/stop AMaViS correctly.

530258

-

The DNS Section of the Getting Started Guide needs updating.

530260

-

The /opt/insight/etc/rc scripts fail to stop/restart the services correctly.

530263

-

Restoring an SCOoffice Server 4.1 LDAP backup on fresh system fails.

530263

-

Restore of LDAP backup results in errors on master/slave configuration.

530264

-

Button missing from master/slave page in GUI for Internet Explorer

530265

-

The Administrators Guide for Exchange migration needs updating.

530272

-

Migrating users from a server running SCOoffice Server 2.0 doesn't copy email to the server running SCOoffice Server 4.1.

530275

-

In statistic web page: ``Warning: rsort() expects parameter 1 to be array''.

530285

-

Modifying a user's first name results in the user being deleted from LDAP.

530307

-

Modifying ``send only local mail'' or ``receive only local mail'' for a user can cause user login to be deleted.

530341

-

Get an error when adding a user with ``send only local mail'' or ``receive only local mail'' selected.

530342

-

Backups run by Cron show file permission errors in log files.

530354

-

Freshclam reports that ClamAV is out of date and must be updated immediately. ClamAV has been updated to version 0.85

530368

-

The backup of the server configuration doesn't include all settings.

530369

-

Internal mail marked as spam (amavis whitelist via ldap). Fixed mmdftailor file. Be sure all virtual domains are specified in the Postfix mydestinations parameter and all Domains are resolvable using DNS.

530413

-

The WebClient resets browser character encoding.

530417

-

The ``availability'' image in the WebClient does not display in Spanish.

530423

-

Moving a user to another domain fails - user is deleted

530428

-

The insightserver-setup.sh script points to wrong place in the install.log message.

530446

-

When migrating users from a server running SCOoffice Server 2.0 to server running SCOoffice Server 4.1 the users don't get imported properly.

530447

-

Complete restore of mail server loses additional IP addresses in the GUI.

530480

-

The URL http://hostname/msg now works to open the WebClient.

530535

-

Osr5 update pack 3 causes Statistics to error.

530544

-

If /var/log directory exist, files/directories under this show up in Logging within GUI.

530565

-

Need address auto-complete in the WebClient.

530584

-

The WebClient is slow to load Calendar folders with a large number of appointments.

530598

-

Reoccurring appointment doesn't work.

530602

-

Can't accept/reject meeting requests via WebClient using Outlook 2003 in Spanish.

530630

-

Massive performance loss using WebClient after multiple days of uptime (high kernel CPU time).

530720

-

Amavis crontab not being setup properly, syntax error.

530721

-

Home directories incorrect for SCOoffice Server 4.1 service accounts such as postfix.

530892

-

Readpst files to import larger Outlook PST files - core dumps.

530895

-

In ADauth mode: WebClient fails to open Calendar - proftpd still looking at ldap.

Included from Maintenance Pack 2 and 2a

531060

-

sv_SV message catalog is supposed to be sv_SE (Swedish)

531373

-

Migrated users are not put at top level rather than into their Domain

531523

-

PST file migration uploads are not deleted

531530

-

Accepted meetings are not posted in Calendar

531537

-

Portuguese, WebClient Calendar folder name wrong, can't create events

531538

-

Portuguese, WebClient months/days in English

531539

-

Portuguese, Outlook Sent Items folder name wrong, can't save items

531540

-

Portuguese, can't save Notes in WebClient

531541

-

Portuguese, no spam folder, no Trash icon

531542

-

Can't migrate organizations from Exchange

531549

-

Fix support for custom_links file

531564

-

Large PST file import fails

531565

-

Readpst core dumps when processing corrupt PST files

531566

-

Mail migrated from Exchange 2k has corrupted From: and To: addresses

531567

-

Can not migrate users in an Exchange Organization

531939

-

WebClient Contact distribution lists not usable in Outlook via Connector

531940

-

WebClient doesn't handle apostrophe characters correctly in folder names

532232

-

Setting text for a rejection filter inserts characters ``&AA0ACg-'' into text every eight words.

erg712733

-

French translation issues

erg712815

-

Portuguese issues with SCOoffice connector and Webclient

erg712833

-

PST Migration does not include entries other than mail

erg712813

-

Fix SCOoffice WebClient custom_links

erg712832

-

SCOoffice Autocomplete for WebClient

 

-

saslauthd security update

 

-

Mime boundaries no longer visible in mail migrated from Exchange

 

-

Migration tool now supports migrating mail, Calendar and Contacts folders.

 

-

The WebClient Calendar navigation link (top right hand corner) is not localized.

 

-

Spanish - fixed folder names for ``Deleted Items''.

 

-

Portuguese Webclient - Editar la response aceptee changed to Editar resposta aceita.

 

-

Portuguese WebClient - fix encoding issues in meeting accept dialog.

 

-

WebClient - Calendar navigation bar (top right) was not localized.

 

-

Portuguese WebClient - The Portuguese word for March has been corrected.

 

-

Shared Calendar entries do not display correctly, fixed encoding issues.

 

-

After accepting a meeting request the meeting displays characters incorrectly.

 

-

User Preferences homepage in GUI is not completely translated.

 

-

Contacts can't be deleted

 

-

Spanish - the translation for Subject is “Asunto”.

 

-

Contacts created in OUtlook cause error in the WebClient.

 

-

When you accept a meeting in the Webclient, the subject is in another language.

 

-

``Sticky Note'' not translated in WebClient.

 

-

The days and month of the year are always in English - Webclient.

 

-

Portuguese WebClient - When you create a task, Subject and Complete are not translated.

 

-

WebClient, Start, End and Occurrences not translated in reoccurring meetings.

 

-

Change ``Registros para deste mes'' to ``Registros para este męs'' in WebClient month view.

 

-

Need a command line utility to import PST files.

 

-

Need to retain message seen flag (read/unread) when migrating messages.

 

-

Message migration creates rtf attachments for all messages. Content needs to be put in the body of the message.

 

-

WebClient - the message body in the Sent Items folder is not visible.

 

-

Can't migrate users in Exchange organizations.

 

-

WebClient Autocomplete needs to include matches from the Global Address Book

 

-

WebClient Autocomplete needs to sort matches

 

-

Missing WebClient localized strings for "Accepted" and "Declined"

 

-

WebClient fails to properly send attachments

Included from Maintenance Pack 3

532711

-

reminder pop-ups are not working or result in an error message

532834

-

GUI allows Exchange migration in AD auth mode but should prevent it

532836

-

8bit chars in body lost when replying to a message

532799

-

Portuguese webclient (w/mp2) losing special characters when replying

532837

-

8bit chars in reminder are corrupted

532874

-

The global disclaimer filter is truncating messages with a . (dot) on a line by itself

532731

-

new config.php fixes problem of urlencoded strings in the xml file being copied into the service config files

532875

-

cyrus stop does not stop active imapd and pop3d connections. cyrus start should perform a recover

532838

-

cyrus checkpoint period should be 30 not 5 in cyrus.conf

532731

-

changed capitalization on Portuguese "Items *" folders so the second word is lowercase to match the connector

532883

-

ClamAV has been updated to version 0.87

532964

-

Running the cyrus reconstruct from the GUI assigns incorrect ownership

533040

-

SECURITY SCOoffice ClamAV updated to ClamAV 0.87

 

-

Mon now logs to /var/adm/user instead of the console.

Included from Maintenance Pack 4

532922

-

Security update for PCRE Quantifier Values Integer Overflow Vulnerability (libpcre)

533040

-

Update to ClamAV 0.87.1

526936

-

Add –i argument to both invocations of $SENDMAIL in the /opt/insight/etc/postfix/disclaimer.sh file.  Prevents truncation of messages/attachments.

 

-

First release of SCO Office Connector 3.0.7 and Address Book 2.5 for Microsoft Outlook

 

-

Single-click installation/update of the Connector and Address Book.

 

-

New transparent licensing for the Connector and Address Book.

 

-

New Connector 3 Users Guide.

531738

-

New remime tool for repairing messages.

 

-

Corrected folder name capitalization in the Portuguese message catalogs to resolve duplicate folder issues in the WebClient

New for Maintenance Pack 4a

 

-

Corrected ClamAV installation to avoid failure after upgrading from SCOoffice 4.1.0Ga or MP1, and to enable the latest ClamAV security fixes after upgrading from MP2a.

 

-

Stop and restart Postfix, if running, to avoid mail delivery problems after upgrading.

 

Maintenance Pack Notes

This release of Maintenance Pack 4a contains Connector 3 and supporting software.  It includes:

 

Single-click installation and configuration.  This tool will perform a new installation or upgrade from Connector 2.5  and earlier builds of Connector 3.0.x. The SCO office Address Book  will also be installed/upgraded and the users email account and  Address Book will be automatically configured.


Automatic server based licensing.  No additional licenses or licensing tasks are necessary.  The Connector and Address Book query the mail server for a valid  SCO Office Server license. If the mail server is licensed the Connector and Address Book will also be licensed.


A tool (remime) for correcting html messages that have been incorrectly (MIME) typed as text/plain by Connector 2.5.  Connector 2.5 can mis-type html message content  when synchronizing the message from the local PST file on the client to the IMAP folder on the server. Thus a correctly formatted message resides in the PST file and an incorrectly formatted copy of  the message resides on the server. Since Outlook displays messages from the local PST file the mis-typing is not immediately apparent.  When such messages are viewed directly from the server using the WebClient or Connector 3 the <html> tags are displayed at ordinary text without formatting.

 

After installing Maintenance Pack 4a on the server your Windows Outlook users may want to upgrade their Connector software to this latest version. The following describes the steps to take to upgrade to Connector 3.

 

 

High Level Summary for upgrading to Connector 3:

 

This is a summary of the overall steps to take to install/upgrade the Connector software for Outlook on the Windows client systems. Detailed descriptions for each of these steps is covered below.

 

If users of the SCO Office Server are using or have ever used Connector 2.5 run the remime utility on the server to correct mis-typed html message content.


Have the users install/upgrade to Connector 3 using the Single-click (Client Configuration link) in the User Preferences Manager web based GUI:

     https://<mail_server_hostname>

After all users have installed or upgraded to Connector 3 run the remime utility one last time.

 

 

Running the REMIME Tool:

 

Note: IT IS STRONGLY RECOMMENDED THAT A BACKUP OF THE CYRUS IMAP SERVER BE PERFORMED IMMEDIATELY BEFORE AND AFTER RUNNING REMIME.

 

If the users of the SCO Office server are using or have ever used Connector 2.5 with Outlook consider using the remime tool to scan for and correct any html message content that may have

been mis-typed as text/plain.

 

The remime tool repairs messages by scanning the message content and rebuilding any mis-typed parts with the correct Content-Type.  The tool operates directly on the files in the IMAP mail folders which are located in /opt/insight/var/spool/imap.

 

A copy of the original message will be created for all messages that are modified. These are denoted by the file extension ".backup".  Since IMAP stores messages as a number followed by a ".", such as 1., a backup of this message would be 1..backup. In this case you could return to the original message by copying "1..backup" to "1.".  Be sure the message retains the proper ownership of cyrus and group mail.

 

The remime tool must be run by the root user on the server. It will shutdown the mail server while it is running so care should be taken to schedule an appropriate time when uses are not likely to need access to the mail server. The remime utility runs swiftly but processing can take an extended period of time on mail servers with a very large amount of stored data.

 

If most of the users of the SCO Office Server have or are using Connector 2.5 run the remime utility with the following options to scan and repair all folders:

 

    /opt/insight/bin/remime -v -a

 

If only a small number of users are or have used Connector 2.5 it may be more efficient to run the remime utility to scan and repair each of the users mailboxes rather than on all users mailboxes. This can be done by using the following arguments:

 

    /opt/insight/bin/remime -v -l <email_login_username>

 

If this approach is chosen all folders under the "Shared Folders" area should also be scanned. This can be accomplished using these arguments:

 

    /opt/insight/bin/remime -v -p

 

 

Final Remime:

 

After all users have upgraded to Connector 3 and imported their INBOX folder (if necessary) run the remime script one last time using the guidelines discussed above.

 

 

Using Single-Click to Install Connector 3 and the Address Book:

 

Please refer to the SCO Office Connector 3.0.7 Users Guide for additional information. This guide is accessed using your web browser. Simply go to the login page for the SCO Office Server GUI or WebClient and click the 'Help' button. Click on the link for

 

The login page is here: http://<mail_server_hostname>

 

Note: In order to install the Connector software on the Windows workstation the user must have 'administrator' privileges.

 

1. Login to the Windows workstation as yourself.

 

2. Close Outlook if it is running.

 

3. Verify that Outlook is not running using the Windows Task Manager.

   - Start the Task Manager by holding down the 'ctrl' and 'alt' keys and press the 'delete' key.

   - Click on the 'Process' tab in the Windows Tasks Manager.

   - Look for the process "OUTLOOK.EXE" in the process list.  If it exists, click on it to select it then click the 'End process' button to kill it.

   - Close the Task Manager window.

 

4. Log into the SCO Office Server User Preferences Manager web page using your email login username. The URL for this page is

 

   https://<mail-server-hostname>

 

5. Click on 'Preferences' in the navigation bar on the left hand side then click 'Client Configuration'.

 

6. Near the top of the page that is next to display you will see a box with some text and two buttons labelled Outlook and Outlook Express. Click the button labelled 'Outlook'.

 

7. Click the 'Download' link at the top of the next page. In the subsequent File Download dialogue click on 'Open' or 'Run'. You may also be prompted with additional security warning dialogues.   Choose the responses that will allow the Connector 3 installer to be downloaded and 'Run' on your computer.

 

8. Once past the security prompts the Connector 3 installer will be downloaded to your computer as C:\icsetup.exe. A configuration file will also be created as C:\icsetup.ini. Once this is complete the icsetup.exe will be automatically run with icsetup.ini as input to the installation:

 

   C:\icsetup.exe /y C:\icsetup.ini /silent

 

  The installer will remove any older version of the Connector and Address Book. The new Connector and Address Book software will be installed and a profile named  'SCOoffice Mail Connector 3.0' will be created. Your email account and address book will be configured automatically up in this profile.

 

   If a profile of the name 'SCOoffice Mail Connector 3.0' already exists the installation will retain this profile and attempt to use the existing email account and address book configuration.

 

9. When the installation and configuration is complete a pop-up dialog box will be displayed to notify the user of completion.

 

10. Start Outlook and choose the 'SCOoffice Mail Connector 3.0' profile when prompted.

 

11. Users of Connector 2.5 who did not have their INBOX folder synchronized with the server (the default) may need to import the INBOX folder from their old PST file into the new

    Connector 3 INBOX folder on the server.

 

    With POP3 accounts the messages are removed from the server by default when popped to the client for reading. This leaves the bulk of the users INBOX folder in the PST file on the client.

 

    Since Connector 3 reads INBOX directly from the server the INBOX in the PST file may need to be imported back to the INBOX folder on the server.

 

    Use the Outlook File->Import feature to import the INBOX folder of the Connector 2.5 PST file. Be sure to mark the check box that says 'Replace duplicates with items imported'.

 

Microlite BackupEdge

  • Versions of BackupEdge prior to 2.01.04 will not recognize SCO Office Maintenance Pack 4a. Update to BackupEdge 2.01.04 prior to installing Maintenance Pack 4a. Failure to do so may prevent BackupEdge from performing a successful system backup.

Active Directory Authentication

  • When using Active Directory authentication, the WebClient Access Control does not work. Users who are not granted access to use the WebClient will still be able to log into the WebClient.

PST File Migration

  • The PST file migration tool has been enhanced to migrate Calendar and Contacts folders as well as Mail folders.

  • Migrated messages are now placed into the proper folder locations rather than under a separate folder hierarchy. For example, messages migrated from a Sent Items folder will be placed into Sent Items.

  • PST files can be imported from the command line using a new tool. See examples 1 and 2 below for usage information.

  • The ``seen'' flag for each message can be migrated in some circumstances. The ``seen'' flag indicates if the message has been read by the user.

    1. The message seen flag will be retained if the user logs into the User Preferences GUI as themselves and uses the migration wizard to import their PST file. If the Admin user logs into the GUI and uses the migration wizard to import the PST file the ``seen'' flag will not be migrated.

    2. If the PST file is imported using the command line tool the seen flag will be retained if the user login and password are used as arguments to the migrate.php program. If, instead, a destination mailbox is specified the seen flag will not be migrated.

Example 1:

This is an example of importing a PST file using the command line import tool. The ``seen'' flag is not retained.

The email account login is ``smith'' and the PST file to import is /tmp/engineering.pst. This will import the contents of the PST file into the top level of the mailbox for ``smith''. If an additional folder name such as user/smith/engineering_mail is specified the PST contents would be imported into the ``engineering_mail'' folder for ``smith''. This method does NOT retain the message ``seen'' flag because we are specifying a specific import destination. 

    login: root
    password: <root password>
    # LD_LIBRARY_PATH=/opt/insight/lib;export LD_LIBRARY_PATH
    # cd /opt/insight/htdocs/is4web
    # /opt/insight/bin/php  module/run.php  module/migrate.php \
          /tmp/engineering.pst  user/smith

Example 2:

This example uses the command line tool to import a PST file into the mailbox for a named user and is indicated by providing the users mail account login and password. Because the users login and password are provided the ``seen'' flag can be migrated. 

    login: root
    password: <root password>
    # LD_LIBRARY_PATH=/opt/insight/lib;export LD_LIBRARY_PATH
    # cd /opt/insight/htdocs/is4web
    # /opt/insight/bin/php  module/run.php  module/migrate.php \
          /tmp/engineering.pst  /  <login> <login password> 

Exchange Migration

  • The Exchange migration tool in the Administrative Interface has been enhanced to migrate Exchange 2000 Organizations. The Organizations will be created as SCOoffice Groups within the appropriate Domain. The migrated mail users will be placed into the proper Domain or Group. Mail folders as well as Calendar and Contacts folders will be migrated to the SCOoffice Server.

  • IMPORTANT: When migrating from an Exchange 2000 server the Administrator DN that is entered to bind to the Exchange Active Directory has changed. It is no longer possible to enter the default of ``Administrator''. The full DN of the Administrator's account in Active Directory must be specified.

Example of migrating users from Exchange 2000:

The hostname of the example Exchange server is mail.mycompany.com. The default container or Domain for the mail users on this server is ``workgroup''.

In step 2 of the migration process enter the following into the input fields:

Administrator DN: cn=administrator,cn=users,dc=workgroup,dc=mycompany,dc=com Administrative password: <administrator password> Confirm password: <administrator password> LDAP Suffix: cn=users,dc=workgroup,dc=mycompany,dc=com

If the above method does not work for your Exchange 2000 server you can find the LDAP Suffix and Administrator DN by opening a shell on the SCOoffice Server, login as root and run the following command using mail.mycompany.com as the example Exchange server:
 
     /opt/insight/bin/ldapsearch -x -h mail.mycompany.com -p 3268 \
     -b "dc=mycompany,dc=com" "(objectclass=domain)" o dn | grep dn:

The output from the command will look something like the following:
 
     dn: DC=WORKGROUP,DC=mycompany,DC=com

For each ``dn:'' prepend ``cn=users'' to construct the LDAP Suffix as in:
 
     cn=users,dc=WORKGROUP,dc=mycompany,dc=com

To construct the Administrator DN prepend ``cn=administrator'' to the LDAP Suffix as in:
 
     cn=administrator,cn=users,dc=WORKGROUP,dc=mycompany,dc=com

With the correct information entered into the fields for Step 2, click Next. A page of users will be displayed with a checkbox next to each one. This is step 3. Select the CN entry for each user to be migrated. The ``Administrator'' user will not be migrated so it does not need to be selected. Continue on with the migration process as documented in the Administrators Guide.

  • Migrating users from an Exchange Organizations is accomplished in the same manner as described immediately above with one difference. The LDAP Suffix will change to include the name of the Organization.

An example using our mail.mycompany.com server:

If the Exchange Organization is ``marketing'' then enter the following in step 2 of the migration process:

Administrator DN: cn=administrator,cn=users,dc=workgroup,dc=mycompany,dc=com
Administrative password: <administrator password>
Confirm password: <administrator password>
LDAP Suffix: ou=marketing,dc=workgroup,dc=mycompany,dc=com

Having entered this information for step 2 click next. The next page, step 3, will display the Organization and users to migrate. Select the CN entry for each user to be migrated. It is not necessary to select the OU entry for the Organization.

Here is an example of such entries:

    OU=marketing,DC=WORKGROUP,DC=mycompany,DC=com
    CN=Wendell Blick,OU=marketing,DC=WORKGROUP,DC=mycompany,DC=com

If the name of the Exchange Organization is unknown it can be found by running the following ldapsearch command. Note that to lookup the Exchange Organizations ldapsearch must bind to the Exchange Active Directory server using the Exchange Administrator DN (the -D argument) and password (the -w argument):

    /opt/insight/bin/ldapsearch -x -p 3268 -h mail.mycompany.com 
    -D "cn=administrator,cn=users,dc=workgroup,dc=mycompany,dc=com" -w admin
    -b "dc=mycompany,dc=com" "objectclass=organizationalUnit" o dn

The output from this command will look something like this:

# Domain Controllers, workgroup,mycompany.com
dn: OU=Domain Controllers,DC=WORKGROUP,DC=mycompany,DC=com
 
# marketing, WORKGROUP.pdev.sco.com
dn: OU=marketing,DC=WORKGROUP,DC=mycompany,DC=com

Ignoring all Domain Controller entries we find that we have one Exchange Organization that is entered as the LDAP Suffix in step 2 of the Exchange migration process:

OU=marketing,DC=WORKGROUP,DC=mycompany,DC=com

WebClient Autocomplete

An autocomplete feature has been added to the WebClient. The autocomplete feature assists the user when entering recipient email addresses. Autocomplete searches the Contacts folders, any shared Contacts folders, and the Global Address Book and presents possible address completions at each keystroke. The up and down arrow keys are used to select the address from the completion list and the Return key will enter the selected address into the form. The autocomplete feature is off by default and is enabled in the WebClient preferences page.

WebClient default user settings file

The file /opt/insight/icc/groupware/conf/usersettings.inc allows the administrator to set default preferences for the WebClient users. The preferences that can be set are listed in the file. For example, the autocomplete feature can be enabled by default for all users. Settings made by the user in the WebClient Preferences page override the settings in the usersettings.inc file.

Before modifying this file please make a backup and take care not to damage the php syntax of this file.

    <?
        // mail options
        $refreshTree_opt = 300;     // refresh folder list every n seconds
        $storeSent_opt = 'on';      // save a copy of sent messages
        $autoComplete_opt = 'off';  // enable/disable autocomplete
 
        // calendar options
        $starthour_opt = 8;
        $startminute_opt = 0;
        $startampm_opt = "AM";
        $endhour_opt = 6;
        $endminute_opt = 0;
        $endampm_opt = "PM";
        $day_start = '0700';       
        $day_end = '2000';
 
        $calendar_view_opt = 'day'; // default calendar view, day/week/month
        $week_start_opt = 'Sunday'; // day calendar week starts 
   ?>

Limitations

·      MS Contact Manager is not compatible.

·      On some manual installations, Outlook crashes when configuring the address book, but a subsequent restart of outlook has the address book configured correctly.

·      Multiple accounts in the same profile are not fully supported. Always add other email accounts after the SCOoffice Server account is configured.

·      PDA synchronization is limited. Additional support will be provided in subsequent releases.

·      The Outlook 2003 folder Groups feature is not supported.

·      Outlook stationary is not supported.

·      Slashes in folder names are not allowed.

·      GIMP is not compatible due to a DLL conflict.

·      Connector 3 will not connect to the SCOoffice Server when used with the Chinese-language version of Outlook.

·      Character encoding of Russian/Cyrillic characters cannot be used in  meeting invitations.

 

Copyright (C) 2006 The SCO Group, Inc. All rights reserved.

13 April 2006