Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Google Apps for Education: Mail Merge

Note: This is not a public or community-wide article, and is not available to all Bethel community members.

Bethel Community members who wish to run mail merges in Google Mail will need to use a tool called Google Apps Sync for Microsoft Outlook. Bethel University ITS supports the use of this program exclusively for Bethel staff and faculty sending mail from a Bethel owned computer. If you would like to send mail merges through your Bethel Google Apps account, please take the following steps:

Requesting Google Apps Sync for Microsoft Outlook

  1. To have Google Apps Sync for Microsoft Outlook installed on a Bethel owned computer, the user will need to request the program through the Bethel ITS Helpdesk.


      • You must have the tag number that identifies your particular Bethel machine, and include this information in their request for the Google Apps Sync tool.

    • *Example Request: "I would like Google Apps Sync for Microsoft Outlook to be an installed on PC #1234."
  2. After a request has been approved, the program will be remotely installed on your Bethel owned computer. This installation will occur automatically after approval, the first time you connect to Bethel University's network (via an on campus ethernet or wireless connection).

Setting Up Google Apps Sync For Microsoft Outlook

After Google Apps Sync for Microsoft Outlook has been installed on your machine, you need to set up the tool to interact with your Google Mail Account.

    1. First, select the start menu and type Google into the search bar.

    1. From the list of applications that appears, select Set up a Google Apps Sync user. If this link does not appear, go to the Google Apps Sync folder shown in the Programs list. You will find the link inside that folder.

      Note: If you still do not see this option listed (i.e. "Setting Up A Google Apps Sync User" does not appear in your application list), it means that the program has not been installed on your machine. If this is the case, please contact the ITS Helpdesk and inquire about the status of your case.
      Typing Google into search box
  1. Once you open Google Apps Sync For Microsoft Outlook, sign in to your Bethel Google Apps account.


      • Select the Yes, I have a password option.

    • For the password field, use your Google Sync Password. Do not use your Bethel Community Account password. This Google Sync password is unique from your Bethel Community Account password, and is not what you would use to access BLink, Moodle or other Bethel internet applications. It is specific to Google Sync, and would be the same password you use to sync mobile devices. To generate a Google Sync password (or to view your existing Google Sync password), please see:   https://iam.bethel.edu/googlepasswd/googlepasswd.cgi

  2. On the next screen, simply click Create profile. Do not check either of the boxes (import data or send crash reports).
    Clicking Create Profile button
  3. You should be taken to a screen confirming that "Google Apps Sync setup is complete." On this screen, click Start Microsoft Outlook.
    Clicking Start Microsoft Outlook
  4. At this point, Outlook will open and begin automatically syncing with your Bethel Google Mail account. This initial syncing process may take up to an hour, but typically lasts around 15 minutes. Please do not close Outlook while syncing. Once the sync is complete, you may run a standard mail merge in Outlook. Your content will be sent out using your Bethel Google Mail account. From this point forward, you will be able to use Outlook for the purpose of mail merges.

*IMPORTANT NOTE: Outlook may only be used for executing mail merges. All other mail activity should occur in the online Google Mail environment. Using Google Apps Sync for Microsoft Outlook for any purpose other than running mail merges will be considered a misuse of the resource, and could result in a loss of access to the tool.

  • No labels