This article will describe the installation and configuration of Exchange Connector for Service Manager 2012.
Exchange 2. 01. 3 and 2. This guide shows the steps necessary to configure a newly installed Exchange 2. POPcon or POPcon PRO (or from the internet directly) and for sending out emails to the internet. Basically you need to perform these simple steps: Add your own internet domain to the “Accepted Domains” list. Configure a Send Connector for outgoing emails. Configure the Default Frontend Receive Connector for incoming emails (from POPcon) without Authentication. Assign email addresses to users. Install and configure POPcon to download POP3 emails(Optional) Make sure you know it first when the Exchange server is down(Optional) Check out the Change. Sender Exchange Send- as Outlook Add- in. ![]() Add your own internet domain to the “Accepted Domains” list. In contrast with previous versions of Exchange (2. MMC application to manage the server. Everything is done with the new Exchange Control Panel (ECP) and the Exchange Management Shell (EMS). Open the Internet browser and go to the following address: https: //exchange. It will redirect us to the login screen in order to authenticate before accessing the ECP. Once you have entered your credentials, the ECP window appears: As we've already mentioned, all of the management operations happen here. The first step to configure our server is to add our Internet domain to the "Accepted Domains" list. To do so, go to the Mail Flow option (on the left pane) and select “Accepted Domains” in the menu bar above. There should be a default setting, usually the internal domain name (here servolutions. Now, add a new accepted domain by clicking on the "+" icon: Now, a pop- up window opens. Add the Internet domain that we want our server to accept. In the "Name" field enter a descriptive name for our rule (In this case, "Domain name for the Internet" is the name that I've chosen). In the Accepted domain field enter the name of your Internet domain name (in this case, servolutions. Mark the "Authoritative domain" option and once done, click the SAVE button in the lower part of the window. This setting indicates that this Exchange server will accept e- mails directed to the "servolutions. The Authoritative domain option is to indicate that this server will be the one that processes all of the e- mails sent to the servolutions. Configure a send connector for outgoing emails. The send connector is used to pipe outgoing emails from Exchange via your providers SMTP relay server to the internet. In Exchange 2. 01. Hub Transport” role that existed in Exchange 2. Mailbox server role. So now, all you have to do is click on the Send Connectors menu option. Here, we add a new send connector by clicking on the "+" icon. A new window will open. In the "Name" field enter a descriptive name for the connector (I've named it "Send Internet Mail"), select the Internet option and click in next. In most cases your Exchange server will be on a normal internet connection with a dynamic IP address and you should use the webspace provider's SMTP relay server to send out internet through. This ensures our emails are not flagged as spam by the receiving end since it originate from a public IP address. So in Exchange terms we will use a relay “Smart host” to send e- mail. For this option please select "Route mail through smart hosts" and in the next field add the smart host's address (FQDN). Once finished, click on Save. The configuration will look like the image shown below. Click Next. In the next window we will enter the authentication data for the SMTP relay server / smart host. Every commercial relay server requires authentication to keep spammers from abusing them. Choose "Basic authentication" and enter your provider's SMTP server username and password. Note that if you have multiple logins for the server it is not important which one you use. It will not affect the email sender name, this log in is purely used to allow you to send email through the relay server. Click on the Next button. The next screen asks for the send connector e- mail routing rules. Here we can instruct our Exchange server to use a different e- mail server (smart host) to send e- mails depending on the domain we send to. This is seldom useful and does not allow different smart hosts depending on the sender domain. If you want that please check out our Multi. Sendcon, the multi- domain send connector for Exchange. In our case only one server is required, so in the next screen we should put an asterisk "*" in the "Domain" field. The asterisk means that e- mail to any other domain outside our organization will be routed through this external smart host. Click on the Next button. Another window will appear. In this screen we can indicate in which Exchange server this rule will apply. In this case, it applies to our one Exchange server. To set this rule, click on the “+” button and the next window (below) will appear. Here we select the server that this rule will apply. As we have one Exchange server only, we select it here and then click on the "add- > " button, so it should look like this: Once finished just click on the OK button and it'll return to the previous window with the changes made. Once we are satisfied with the changes, click on finish. And now we're finished with our outgoing e- mail rule. But one more change should be applied to make it complete: The maximum outgoing message size is set to 1. MB by default. This is how to change it: Please click the pencil icon to review and edit our changes: Change the maximum message size for outgoing emails to a value that is more convenient here and save the changes clicking on the Save button. With this done, we’re finished with the outgoing mail configuration. Now we’re ready to take a look at the e- mail receiving configuration. Configure the "Default Frontend" receive connector for incoming email. POPcon uses SMTP to forward emails to Exchange. For this to work we need to have a Receive Connector configured on the Exchange 2. MB by default and can cause many problems) and we need to add the anonymous user to the permission group in order to allow POPcon to transfer email into the Exchange server. Important: You also need to make sure to not install the Windows "Simple Mail Transfer Protocol" service. This service could block the Exchange SMTP transport from actually answering the SMTP IP port (2. Emails to loop back to the internet if installed. Check Administrative tools, Services and disable this service in case it is installed. Back to the Exchange configuration: In order to configure the incoming mail rules, open the Exchange Control Panel, go to the "Mail Flow" option located on the left pane and in the right pane, click on "Receive Connectors". The screen will look like the one pictured below. Select the "Default Frontend" connector and click the pencil icon to change the settings. In the General option we need to change the "“Maximum receive message size" from the default 1. MB to 1. 00. MB, so larger E- Mails don't get stuck between POPcon and the Exchange Server. If you want you can later limit the maximum message size in the Exchange general options or even for an individual user in their mailbox options and cause Exchange to return undeliverable messages if the email is too large. Check the image below: Once finished, click on the save button. Now go to the Security option. Make sure to mark the checkbox which says "Anonymous users" (inside the red square in the image below). Anonymous users are all email senders from outside your organiation, so this check mark allows email senders from outside to deliver email into Exchange. Check the "Anonymous users" checkbox and click on the save button. Now, go to the Scoping option. Make sure to the Exchange server's real IP address, like in the image below. Also make sure that the "Network adapter bindings" option shows the server's IP address or "All available IPv. You can change the FQDN field to reflect the mail server’s fully qualified hostname or you can leave it as it is. That option is not important for POPcon. Click on the save button. Oracle Connector for Outlook. Oracle Connector for Outlook is a calendaring and messaging service provider that extends and improves Outlook's functionality with real- time calendaring, advanced group and resource scheduling capabilities and unified messaging functionality by providing one central Inbox for your e- mail, voice mail and fax messages. A key advantage to using Oracle Connector for Outlook is that you can continue to use the familiar Outlook interface on your desktop while accessing Oracle's calendar server and e- mail server instead of Microsoft Exchange Server. The Oracle Calendar server stores all users' calendars together in a single database. Each time you look at another user's free/busy time, you are viewing up- to- the- minute information about their schedules, including unconfirmed meetings. Similarly, each time you open a meeting in your Calendar folder, you are getting the latest version directly from Oracle's calendar server, instead of opening a copy of an e- mail describing a meeting that may have been moved or changed without your knowledge. Calendaring with Microsoft Exchange Server, by contrast, is message- based: all meetings are created, stored, forwarded and retrieved as e- mail messages. There are a number of limitations with this method. For example, between the time you create the meeting and the time your co- worker accepts it, nobody else can know when that meeting exists by looking at your co- worker's calendar. In fact, nobody else can tell that the meeting exists at all, because it doesn't exist in your co- worker's Calendar folder until he or she accepts it. Installation instructions. This section contains the following topics. System requirements. Table 2- 1 Oracle Connector for Outlook System Requirements. Requirement. Value. Operating system. Windows NT 4. 0. Windows 9. Windows 2. 00. 0Windows XP Professional SP2. Administrative privileges are required to install Oracle Connector for Outlook on Windows NT, 2. XP. Disk space. Free disk space equivalent to the approximate size of the user's IMAP4 mailbox. RAMRefer to the RAM requirements of your Microsoft Outlook client. Outlook. Outlook 9. Outlook 2. 00. 0Outlook 2. Outlook 2. 00. 3Note: Native Language version or Multilingual User Interface Pack (MUI) is required for non- English version localization (see supported languages)Calendar server. Oracle Calendar server 5. Oracle Calendar server 9. Oracle Calendar functionality)E- mail servers. SMTP server for outgoing mail included with Oracle Connector for Outlook. Oracle IMAP4 Server 9. Other e- mail servers whose implementations are based upon the open standards of SMTP and the IMAP4 reference implementations Cyrus and University of Washington. Conduits for PDA synchronization. Pocket. Mirror 2. Pocket. Journal. Desktop To Go 2. Desktop To Go 2. 5. Outlook 2. 00. 2 only)PSIWIN 2. Active. Sync 3. 0, 3. Note: Oracle Collaboration Suite Release 2 Patch Set 1 (9. Active. Sync versions up to 3. Hot. Sync Manager 4. Windows XP only)Devices. The following devices have been certified with Oracle Connector for Outlook. Similar devices may work but the end- user experience may vary. Pocket PCCompaq i. PAQ Pocket PC 2. 00. Model 3. 87. 0Compaq i. PAQ Pocket PC 2. 00. Model 3. 97. 0HP i. PAQ Pocket PC 2. 00. Model h 1. 94. 5Palm. Palm III (3. Com)Palm V Handheld. Blackberry 6. 71. Wireless Handheld. Preinstallation Requirements for Oracle Connector for Outlook. A supported Outlook version must be installed on a supported platform. To install Oracle Connector for Outlook on Windows NT, 2. XP, you must have administrative privileges. Outlook 9. 8 and Outlook 2. Corporate/Workgroup mode. Verify the Outlook configuration by selecting Options from the Tools menu, then select Mail. Services, and click Reconfigure. Mail. Support. To avoid losing information, Oracle Corporation recommends that you synchronize your offline folders before upgrading. Installing Oracle Connector for Outlook. In most cases, Oracle Connector for Outlook will be installed and configured for you using a silent installation. If you have not already run this process, visit itweb. Web page for details. If the silent installation process fails on your machine or if your machine has a non- standard or custom build, you will have to manually install and configure Oracle Connector for Outlook. To manually install Oracle Connector for Outlook: Exit all Windows applications before installing Oracle Connector for Outlook. If you are upgrading from a previous version and want to add or change the languages installed, run con_outlook_9. Lang. Otherwise, just double- click the con_outlook_9. Follow the on- screen installation instructions. Note. To avoid conflict between POP3 and IMAP4 protocols, do not set up Microsoft's Internet Mail or Exchange service providers in the same profile as Oracle Connector for Outlook. Disabling Outlook Add- ins. It is recommended that you disable Outlook Add- ins that are specific to Microsoft Exchange to avoid conflicts with Add- ins installed with Oracle Connector for Outlook. For details, see the Configuring Add- ins section of the Oracle Connector for Outlook online help. Upgrading Microsoft Outlook. If you upgrade your Outlook installation, you must reinstall Oracle Connector for Outlook after the upgrade. See Installing Oracle Connector for Outlook for installation instructions. Configuring Oracle Connector for Outlook. This section contains the following topics: Managing your profiles using Outlook 9. This section contains the following topics: Creating a new profile. When creating a new profile using the Oracle Connector for Outlook service, you will need to provide a variety of information to connect to your mail and calendar servers. Close Outlook. From the Windows Start button, select Settings. Select Control Panel from the pop- up list, and double- click the Mail icon. Click Show Profiles. Click Add. Select the Use the following information services option and select the Oracle Connector for Outlook check box. Enter a name for the profile in the Profile Name field and click Next. The Setup Wizard opens: On the first screen of the Oracle Connector for Outlook setup wizard, select the Corporate option to connect to your organization's calendar server over a LAN or VPN connection. Select the ASP option if your calendar and mail services are provided by a third- party reseller. Select the I do not have an Oracle Calendar account yet check box to skip configuring your calendar server connection and move on to your e- mail server connections. Click Next to proceed. If you selected the Corporate option, you will have to provide the network name or address of your server, followed by a comma, followed by the node- ID or alias of your calendar server node, in the Server name field. If you are using a master node configuration, enter the master node server name only. A node- ID is not required. Specify the user name and password of your calendar account in the other boxes of this screen. In a master node configuration, your user name must be your user ID. Consult your system administrator for the necessary information. Click Next to proceed. If you selected the ASP option, you will have to provide the Domain ID used by your service provider to identify your company, as well as the host name or names of your provider's calendar domain service hosts. Your service provider contact should be able to provide you with this information. Enter the user name and password for your calendar account in the other boxes on this screen. Click Next to proceed. Configure your IMAP4 server connection for incoming mail. If you do not have an account or wish to skip this step, select the I do not have an IMAP4 account yet check box. Otherwise, enter the host name of your IMAP4 server in the Server name field. You can select the Use same settings as my Oracle Calendar Server check box if your mail and calendar accounts have the same user name and password. Click Next to proceed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |