Skip to main contentSkip to search
Powered by Zoomin Software. For more details please contactZoomin
Progress DocumentationProgress Documentation
Progress Documentation
  • Home
  • Home
  • EnglishČeštinaDeutsch (Germany)Español (Spain)Français (France)Italiano (Italy)Português (Brasil)日本語Русский (Russia)中文 (简体) (China)中文 (繁體, 台灣) (Taiwan)ar-AR
  • Login

Installation and Configuration Guide

Install Ad Hoc Transfer Plug-in for Outlook on Multiple End User Computers

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
Table of Contents
  • Installing
    • WS_FTP Server Installation
      • Traditional Install on a Single Computer
        • Standard Installation
        • Advanced Installation
        • Activating WS_FTP Manually
      • Silent Install
    • Ad Hoc Transfer Plug-in for Outlook Installation
      • Install Ad Hoc Transfer Plug-in for Outlook on a Single Computer
      • Install Ad Hoc Transfer Plug-in for Outlook on Multiple End User Computers
      • Silent install of the Ad Hoc Transfer Plug-in for Outlook
      • Remote Deployment via Active Directory Group Policy
  • Configuring
    • WS_FTP Server Web Transfer Client Configuration
    • Ad Hoc Transfer Module Configuration
    • Ad Hoc Transfer Plug-in for Outlook Configuration
      • End User Configuration
      • Help Topic Customization
      • User Interface Customization
    • Tuning Ad Hoc Transfer Upload and Download Buffer Sizes
    • Failover Configuration
      • Configuring a Failover Solution Using Microsoft Cluster Services
        • Architecture
        • Requirements
        • Step 1: Configure the MSCS Failover Solution
        • Step 2: Install WS_FTP on Both Nodes
        • Step 3: Edit Progress Registry Settings on Both Nodes
        • Step 4: Configure Progress Services in Microsoft Cluster Services
        • Step 5: Test the Failover Cluster
      • Configuring a Failover Solution Using Microsoft Network Load Balancing
        • Architecture
        • Requirements
        • Step 1: Configure the NLB Failover Solution
          • Configuring a Two-Node Cluster in Windows Server 2012 R2/2016
          • Ensuring Both Nodes Can Access External Resources
        • Step 2: Install WS_FTP on Both Nodes
        • Step 3: Configure Web Transfer and Ad Hoc Transfer Modules on Both Nodes
          • Configuring the Ad Hoc Transfer Module
          • Configuring the Ad Hoc Transfer Outlook Plugin
        • Step 4: Edit Progress Registry Settings on Both Nodes
        • Step 5: Configure Progress Services to Restart on Failure
        • Step 6: Configuring IIS for Log Viewing
        • Step 7: Configure the Logging Server
        • Step 8: Test the Failover Cluster (NLB)
      • Configuring Windows Share Permissions for Failover Clusters
        • Setting Sharing and Security Permissions in Windows Server
      • Migrating WS_FTP to a Failover Cluster
        • Migrating Data from the Standalone Server
        • Installing WS_FTP on Both Nodes
        • Copying Progress Registry Settings to Both Nodes
      • Replacing a Failed Node in a Failover Cluster
  • Uninstalling
  • Using the Products
    • Using WS_FTP Server Manager
    • Ad Hoc Transfer Module Notes
    • WS_FTP Server Web Transfer Client Notes
    • Using the Ad Hoc Transfer Plug-in for Outlook
Table of Contents

Install Ad Hoc Transfer Plug-in for Outlook on Multiple End User Computers

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
  • Last Updated: January 29, 2024
  • 1 minute read
    • WS_FTP Server
    • Version 2025
    • Documentation

Install Ad Hoc Transfer Plug-in for Outlook on Multiple End User Computers

To deploy the Ad Hoc Transfer Plug-in for Outlook to multiple end user computers, or a large workgroup, automate the process by using one of the following options:

  • Silent Install of the Ad Hoc Transfer Plug-in for Outlook
  • Remote Deployment via Active Directory Group Policy
TitleResults for “How to create a CRG?”Also Available inAlert