METAmessage Server and Domain Requirements Hardware 1Ghz Pentium processor or higher 512MB RAM. (1 GB recommended) 2GB free hard disk space. Network Interface Card connected to a Microsoft Domain. Minimum Display Resolution > 800x600. Supported Operating System Software The system on which you install the server must not be a primary or backup domain controller. You may install the METAmessage server using any of the following operating systems: Windows NT 4 with Service Pack 5 or later and ADSI Windows 2000 Server or Professional Windows XP Professional Windows 2003 Server Note: If you plan to use METAmessage print functionality on Windows 2003 or Windows XP, you should perform the following steps to enable the Kernel Mode Printer Driver installation Note: Do not install METAmessage on a PDC/BDC
Set Up a Domain User Account for the METAmessage Service METAmessage uses a domain user account to log on as an NT service. 1) Set up a domain user account for the METAmessage service and add the account to the Local Administrators group of the target server computer. 2) If using BES 4.0 you should set the following rights for the METAmessage domain user account: Log on locally Act as part of the operating system In addition, add the METAmessage domain user account to the Local Admins group on the BES machine. 3) If you plan to provide network printing capability, the METAmessage domain user account must have print permissions for any network printers that will be accessed by end users. 4) If using BES 3.6 give this domain user account read permissions to the BES administrator mailbox. Third Party Applications Any Anti-Virus software must be configured to not scan METAmessage folders. Internet Explorer 5 or later. -Installed as the METAmessage Domain User Office 2000 or later * (full suite with all filters and converters run from the local Hard Disk <Not the Office Default>). -Installed as the METAmessage Domain User. Adobe Acrobat Writer 4.0 or later (full version with Distiller is recommended for the broadest conversion ability of PDF files). -Installed as the METAmessage Domain User. Lotus SmartSuite (if you plan to support reading or printing of Lotus SmartSuite files) Microsoft Project (if you plan to support reading or printing of Microsoft Project files) Microsoft Visio (if you plan to support printing of Microsoft Visio files)
Configure Third-party Applications The server uses third-party applications to convert file attachments from their native formats into a format friendly for a wireless email device. To configure third-party applications: 1) Check that the applications are accessible to the METAmessage domain user account. This is the case if the METAmessage domain user account installs the applications or if the METAmessage domain user account can open the applications. 2) As the METAmessage domain user account, start all third-party applications and close all start-up or first use configuration dialogs. Select any Do not show this dialog again options and permanently hide or turn off any Office Assistants. 3) Check that all aspects of the Office suite are installed locally and set to Run all from my computer, not from a network or CD. This setting is not the default Office 2000/XP/2003 installation setting. Note: Outlook should not be present if you are installing the server on the same computer as a BES. Note: Office XP Speech Recognition components must not be installed on the same computer as the server. Important Note: Outlook 2000 SP3 and higher/xp Professional/Outlook 2003 require special configuration described in http://www.onsettechnology.com/download/outlook Security Settings.pdf. 4) If you are using Microsoft Exchange, set Outlook to work in Corporate or Workgroup mode and configure at least one mailbox that uses the Exchange service while logged on as the METAmessage domain user account. Third-party applications need not be open while the server is operating.
Configure HTTP To take advantage of METAmessage server s HTTP capabilities utilizing the BlackBerry Mobile Data System (MDS), installation for the METAmessage IIS Web Link on an IIS Web server is required. The METAmessage client on a BlackBerry handheld sends a HTTP based request via MDS to a METAmessage.asp page installed on the IIS Web server. The.asp file intercepts the request and dispatches it to the METAmessage server. The METAmessage server then processes the request. The setup program will create a Web folder with the METAmessage.asp pages. Note: Mobile Data Service must be enabled on the BlackBerry Enterprise Server (BES). To create the Web folder: Install the IIS Web Link software on a Windows 2000 or higher server running IIS. This server may run the BES or METAmessage or it may be a standalone IIS server. 1. Stop the World Wide Web Publishing and METAmessage services, if running, and close the METAmessage console. 2. From the METAmessage CD or download files, run MM_IIS_setup.exe. The MM IIS setup creates a shared folder and by default is called: METAmessage\METAmessage Transport By default the shared name given to the folder is: METAmessage IIS All client request files that are received via HTTP are placed in this folder. The METAmessage server then takes the files from this folder for handling. The folder created by the MM IIS setup program will be referenced in the handheld clients Settings. For example, if the IIS Web Link is installed in the default folder Inetpub\wwwroot\MMIIS, the URL path in the handheld Settings will be http://<ip address of IIS server>/mmiis. Note: If the IIS Web Link is installed on Windows 2003, perform steps 3 to 6, otherwise continue to step 7. 3 Register the ASP.NET IIS by using the registration tool which is located under: C:\WINDOWS\Microsoft.NET\Framework\v#.#.## ##\ The tool name is aspnet_regiis.exe and you should run it using the -i parameter. For example: C:\WINDOWS\Microsoft.NET\Framework\v1.1.43 22\aspnet_regiis.exe i 4. Open IIS Manager, expand the master server node (Servername node), and then select the Web service extensions node.
5. In the right pane of the IIS Manager, right-click the Active Server Pages and set its status to Allowed. 6. In the right pane of IIS Manager, right-click the ASP.NET v#.#.####. (For example: ASP.NET v1.1.4322) and set its status to Allowed. 7. Restart the World Wide Web Publishing service. Enable Printer driver installation If you plan to use METAmessage print functionality on Windows 2003 or Windows XP, you should perform the following steps to enable the Kernel Mode Printer Driver installation: 1) From the Start menu, select Run. 2 In the Run dialog box Open field, enter MMC and click OK. 3) From the Console menu, select Add/Remove snap-in and click Add... 4) In the Add Standalone Snap-In dialog box, highlight Group Policy Object Editor and click Add. 5) In the Select Group Policy Object dialog box, click Finish. 6) In the Add Standalone Snap-In dialog box click Close. 7) In the Add/Remove Snap-In dialog box click OK. 8 )In the new Console Root/Local Computer Policy window, select Local Computer Policy, Computer Configuration, Administrative Templates and Printers. 9) Disable Disallow installation of printersusing Kernel-mode drivers. 10) Close MMC