Please make sure that you enter the Company name exactly as provided on the license document or in the email you received from us (capitalization, spacing, etc.).

If you can navigate to the AgendaX main menu but get an HTTP 500 error when you click on one of the views, you should adjust the following settings to get a detailed error message:

• Disable ‘Show friendly HTTP errors’ in Internet Explorer / Tools / Internet Options / Advanced / Browsing.
• On IIS, in the virtual directory of AgendaX, under Error pages, 500, Edit feature settings, set the Error responses option to ‘Detailed errors’.

This always displays detailed errors instead of an HTTP 500 error, which is useful for detecting problems.

Server object error ‘ASP 0177 : 800700c1’
Server.CreateObject Failed
/agendax/agenda/agxlib.inc, line xyz
800700c1

If you get the above error, it means that the file AEPwDc.DLL was not correctly registered with the system.
On a 64bit Windows system, copy AEPwDc64.DLL to AEPwDc.DLL, on a 32bit Windows system leave the original copy of AEPwDc.DLL.
Then, register the DLL with regsvr32 on the command line:

Run CMD.EXE with ‘Run as Administrator’
C:
CD \Inetpub\AgendaX
regsvr32 AEPwDc.DLL

When accessing any of the AgendaX views the following error appears:
Microsoft VBScript runtime error ‘800a000d’ Type Mismatch ‘UBound’
One of the AgendaX groups doesn’t contain any members, or contains an empty distribution list.
Check that all of the AgendaX groups contain members and / or non-empty distribution lists.

Most probably Exchange Cache Mode is turned on in the Outlook profile of the AgendaX account. Please do the following:

• Log in with the AgendaX user on the AgendaX server
• Edit the Outlook profile that is configured for the AgendaX service (AgendaXCfg.exe / MSX Version) and make sure that Exchange Cache mode is turned OFF.

If you get the following error in the Application Event log:

The AgendaX Update Service reported the following error:
General Error – Output: Error while opening address book.
Error Code: 0x00040380 (MAPI_W_ERRORS_RETURNED)
Description: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
MAPI was unable to load the information service EMSMDB.DLL. Be sure the service is correctly installed and configured..

and you are connecting to Office 365, please follow the steps below to solve this problem:

Add the following keys to the registry, logged-in with the user that is used to run the AgendaX Update Service:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity

EnableADAL (DWORD) 1
DisableAADWAM (DWORD) 1
DisableADALatopWAMOverride (DWORD) 1

16.0 is for Outlook 2016, 2019 and Outlook 365. If you use Outlook 2013, you have to update to Outlook 2016 or above as Microsoft does not support connections to O365 with earlier clients anymore.

Go to Control Panel / Credentials Manager / Windows Credentials and delete all credentials starting with MicrosoftOffice16_Data.

Reboot the server (not always necessary), recreate the Outlook profile that you have configured AgendaX to use, turn off Exchange Cache Mode in the profile, start Outlook with this profile, close Outlook again.

If you are prompted for username / password, please activate the checkbox ‘Save password’.

After these steps, the error logged to the Application eventlog should go away.

If you continue to get this error, or if it reappears after 24 – 26 hours, your Outlook version is not capable of renewing the OAuth access token for Microsoft 365 automatically without running Outlook once per day.

We are currently looking into this problem with Microsoft, and until we have a permanent solution, downgrade to the latest version of Outlook (Version 2403, Build 17425.20146 from March 29,2024) that works and disable Outlook updates.

To do so, please do the following:

• Stop the AgendaX Update Service
• Download the Office deployment tool and install it in a temp folder: https://www.microsoft.com/en-us/download/details.aspx?id=49117
• Note: To install Build 17425.20146, you have to be subscribed in Current Chanel, but any other version in the other channels prior to 17425.20146 will also work.
• Create a file “config.xml” in the same folder that contains the following:

• Start an elevated CMD.exe (Run as Administrator), change to the folder of the Office deployment tool and run:
  setup /configure config.xml
• Run Outlook and click on File / Office account / Update options / Update now and let the installer setup the previous version of Outlook. You can close Outlook while installing.
• Once it’s finished installing, run Outlook, click Update options / Disable updates. This section will become yellow. Close Outlook
• Start the AgendaX Update Service and check the Application event log.

If it doesn’t work right away, stop the service, create a new Outlook profile logged-in as the user that is used to run the AgendaX Update Service, turn off Exchange Cache Mode in the profile, set the new Outlook profile name in AgendaXCfg.exe / MSX Version / Outlook profile, start Outlook with this profile and close it again, and start the AgendaX Update Service again.

This should get it back working without user intervention.

Yes, AgendaX allows users to set the time zone they are in (this can change when employees move or travel between locations). This allows all meeting times to be displayed in the respective time zone.

Yes, you can install AgendaX on multiple servers, as long as the total number of different published mailbox calendars on all installations is not higher than the total number of licenses purchased.

There are no additional costs associated with installing AgendaX on multiple servers.

Since AgendaX behaves like an Outlook client, nothing special needs to be considered in a cluster server environment. If a cluster member server goes down, AgendaX automatically connects to another member server as soon as it takes over.

No, AgendaX can be installed on any IIS server.

An installation on Exchange Server is not required.

Also, no components need to be installed on the Exchange server.

AgendaX runs as a server-based Windows service that periodically reads appointments of selected users from the Microsoft Exchange Server / Microsoft 365 and writes this information to a central database (SQL Server, SQL Server Express).

The calendar information is then published by the Microsoft Internet Information Server (IIS) on the Intranet or Internet / DMZ site of the company. AgendaX uses Active Server Pages, which are accessed via a web browser.

Yes, there are several ways to connect different AgendaX sites that do not share the same Active Directory Forest or domain, or are even in completely separate companies or Microsoft 365 tenants.

For example, AgendaX can scan the mailbox calendars on local Exchange servers and write the information to a local or remote database. A data source is configured between all locations (a specific port can be freely selected) so that all AgendaX installations know each other and write to a central database.

Details about the protocols in use can be found in the document Multiple Organizations Architecture and Protocols

Yes, if configured, all or selected users can make bookings via AgendaX without having to return to the Outlook calendar.

Standard booking templates can be created as needed, pre-filled with start/end times, subjects, categories, all-day events, etc., making it quicker and easier for the end user to complete his or her booking.

If configured as an option, all or selected users can also change existing meetings.

It’s also possible to:

• enable selected employees to book meetings on behalf of others (delegate), e.g. to show to others that a person is off sick.
• enable bookings where the organizer does not take part in the meeting as an attendee (e.g. a personal assistant that books meetings for his / her supervisor)

All bookings are automatically synchronized with the Outlook calendar. A log of all bookings recorded via AgendaX is kept.

You can

• run the Online demo of AgendaX on our website,
• watch a Feature video,
• download a free trial version and install it on your own web site.

AgendaX complements Outlook and offers advantages in several areas:

• The group calendar view of Outlook, which “stacks” calendars becomes almost unusable when looking at more than 3-5 calendars
• Outlook calendar can be slow because information is read from the Exchange server / Microsoft 365 in real time.
• With Outlook Calendar, it is impossible for a receptionist to see at a glance where a person is.
• AgendaX can be used across untrusted domains and even across organizations, across Microsoft 365 tenants
• With AgendaX you can easily filter views by categories (e.g. to create holiday calendars).
• AgendaX can be made accessible through the Internet, e.g. when an employee is at a customer site and needs to quickly check the availability of his colleagues in order to arrange a follow-up meeting with the customer.
• With AgendaX you can create reports on calendar activities (e.g. workload, time spent on a customer, annual leave, sick leave, etc.).
• AgendaX can include Active Directory information and can therefore be used as a company directory.
• AgendaX includes easy to define and use meeting templates for quickly booking meetings with the same characteristics (subject, time, location, etc.)
• AgendaX lets you define custom fields to store additional information about a meeting (e.g. project affiliation, flight information, car hire information, etc.). These fields can also be filtered and statistically analyzed.

AgendaX needs the following components:

• Microsoft Windows Server (all versions are supported)
• Microsoft IIS Server (included in Windows Server)
• 32bit Outlook Client installed on the AgendaX Server
• A SQL Server or SQL Server Express

Even though AgendaX can be installed on the same server like Exchange Server, we recommend to install AgendaX on an existing IIS Server with a minimum of 2 GB of RAM and a Dual-Core-CPU.

Supported Versions of Exchange are:

• Microsoft Exchange Server 5.5
• Microsoft Exchange Server 2000
• Microsoft Exchange Server 2003
• Microsoft Exchange Server 2007
• Microsoft Exchange Server 2010
• Microsoft Exchange Server 2013
• Microsoft Exchange Server 2016
• Microsoft Exchange Server 2019
• Office 365, Microsoft 365
• Hosted Exchange

Pricing is calculated based on the number of mailbox calendars you want to publish. The minimum number of licenses is 10, and you can get any number of licenses from there.

You can select the calendars you wish to read / publish; you don’t need to license the whole global address list.

In AgendaX you create groups (e.g. Sales, Marketing, etc. or Location 1, Location 2, etc.) and for each group you select members from the Global Address List (GAL). You can use distribution lists or individual mailboxes.
A mailbox can be part of multiple groups and is only calculated as one license. The total number of all members of these groups determines the number of licenses you need.

The number of AgendaX web application users is unlimited. Only the total number of published mailbox calendars determines the licenses needed.

Yes, V6 of AgendaX supports hybrid deployments of Office 365. You will need an AgendaX mailbox for the on-premise AgendaX installation and an AgendaX mailbox for the Office / Microsoft 365 AgendaX installation (cloud mailbox).

Does AgendaX support hosted Exchange environments / Exchange Online / Office 365 / Microsoft 365?
Yes. AgendaX supports all hosted Exchange environments.

No. AgendaX supports only mailbox calendars, not public folder calendars.

Public folders are deprecated and will not be available in upcoming Exchange Server versions.

We therefore recommend converting Public Folder Calendars to Mailbox Calendars.

Why do you think AgendaX is better than its competitors?
The main points where our software stands out are the following:

• Very easy to use user interface, and therefore no training necessary
• Customizable to reflect corporate identity and business needs
• Who is where? view – great for receptionists and telephone operators – gives them an instantaneous view of all the company employees to know if they’re currently free, busy, or out of office.
• Complete support for all Outlook properties (Mileage, Billing, etc.) including user-defined Outlook fields, which let you store additional information about a meeting (e.g. project affiliation, flight information, car hire information, etc.). These fields can also be filtered and statistically analyzed.
• Optionally displays phone, fax, mobile, department, picture/photo etc. for each user
• Allows meetings to be scheduled via the web interface without Outlook, with the option to restrict bookings to free time only, make location or category a required field, etc.
• Easy-to-use administration page simplifies configuration
• Rationalize multiple sites and time-zones, multiple organizations and Microsoft 365 tenants
• AgendaX reporting can also be used by business and HR managers within your organization to report on activities, chargeable days, sick days etc.
• AgendaX includes easy to define and use meeting templates for quickly booking meetings with the same characteristics (subject, time, location, etc.)
• Flexible security models
• You can chose which mailbox calendars are shown with AgendaX. Test mailboxes or administrative mailboxes (e.g. Administrator) do not count as licenses and are therefore not charged.
• Licenses can be added to the base license at any time and for any number of mailboxes (minimum 10). No need to buy packages of 50 if you really just need 12 additional licenses.
• The increased visibility and usability AgendaX gives to the contents of the Outlook calendars will encourage more active and accurate use of this facility.
• Web based, no client software required

These are just a few of the many points which make AgendaX one of the best-selling group calendaring solutions available today on the market.

The AgendaX Update Service has a negligible impact on the Exchange Servers.
When it scans the Exchange mailbox calendars, it does so by scanning each configured mailbox individually one at a time. You can therefore compare the bandwidth and processor usage of the AgendaX Update Service with a (very fast working) user that opens each mailbox one at a time and reads every calendar entry that takes place in the interval specified by the Administrator (days past, days ahead parameters in AgendaXCfg.exe).
Scanning a calendar takes anywhere between a few milliseconds to a few seconds, depending mostly on the speed of the Exchange Servers and network throughput between the AgendaX Server and the Exchange Servers.
The above applies to a single AgendaX Update Service configured to scan all the mailboxes into 1 database.
You can also install several AgendaX Update Services working in parallel on a single machine, each scanning different mailboxes either into the same database (to cut down time) or into several databases (to handle access permissions or visibility requirements, e.g. maybe some groups should not see other groups’ calendars).

Development of V5 has ceased. The latest patch available for this version is patch 38. You can download this patch, or the V5 setup that includes this patch (in case you need to install it on another server) from our homepage in the Downloads section.

We recommend all users of V5 to upgrade to V6 or the latest version.

AgendaX offers you 3 security levels: no security, minimal security, and full security.

• No security – Everyone sees all calendars, but by default AgendaX does not publish meeting details of meetings with the sensitivity ‘Personal’, ‘Private’ or ‘Confidential’.
• Minimal Security – Details of meetings (subject, location, attendees) for selected people (e.g. board of directors, HR, etc.) are not published
• Full Security – Users only see calendars of users who have granted them access rights to their Outlook calendar folder, with the option to display only Free/Busy data for calendars without permissions.

You can also set up different installations of AgendaX to display separate groups of users if they are not allowed to view the data of the other groups.

AgendaX comes with a customizable stylesheet. It is very easy to change background colors, date layouts, ruler colors, etc., and add your own logo and background images if needed through the web-based administration interface of AgendaX.

You can also specify how meetings are displayed:  For example, show only weekdays (without Saturday / Sunday), show only meetings within the specified working hours, hide meetings that are marked as free, show the organizer and participants in a tooltip, and so on.

Furthermore, thanks to access to the source code of all views, you can program your own custom views or let us program them for you.

AgendaX provides a web-based configuration interface that allows easy setup of all AgendaX features. AgendaX views can be easily customized to match corporate identity and business requirements. The supplied icons and colors used to represent various activities can be changed to suit your needs.

The AgendaX administration page is used to configure the most common AgendaX settings. Only a closed user group of administrators can access it. The page is divided into the following sections:

• Global settings
  Settings that affect all views (e.g. time format, language, etc.)
• Display settings
  Settings that affect how the views are displayed (which colors to use, how many days to display, etc.)
• Feature settings
  allow you to enable / disable various AgendaX features.
• View settings
  let you determine which views are available and configure various aspects of those views.
• Categories
  With Categories you can define which Outlook categories are highlighted / color coded in the overviews.
• Additional settings
  Allows you to configure other, less commonly used AgendaX settings.

Currently supported languages are:

• English
• German
• French
• Italian
• Danish
• Norwegian
• Finnish
• Swedish
• Dutch
• Polish

The language used by AgendaX can either be:

• defined by the Administrator (all users use the same language)

or

• AgendaX automatically adapts to the first browser language supported by AgendaX.

Additional languages can  be added easily.
Upon request, we can send you a language file for translation to your local language, which we can integrate into the product within just a few days.

AgendaX uses MAPI / Outlook MAPI to connect to the Exchange Servers. MAPI is a standard Microsoft protocol that uses RPC/MAPI connections to / from the Exchange Servers. When using Outlook MAPI, the RPC/MAPI packets may be encapsulated in HTTP packets, especially when reading Microsoft 365 mailbox calendars.

AgendaX uses standard TCP/IP connections to access SQL servers / SQL Express.

Yes, you can install AgendaX on multiple servers, as long as the total number of different published mailbox calendars on all installations is not higher than the total number of licenses purchased.

There are no additional costs associated with installing AgendaX on multiple servers.

Only the Software Assurance contract includes free updates to major version updates.

All other Support options include updates within the licensed version.

We offer a 30% discount to accredited schools and universities, but no discount to non-profit organizations.

Pricing is calculated based on the number of mailbox calendars you want to publish. The minimum number of licenses is 10, and you can get any number of licenses from there.

You can select the calendars you wish to read / publish; you don’t need to license the whole global address list.

In AgendaX you create groups (e.g. Sales, Marketing, etc. or Location 1, Location 2, etc.) and for each group you select members from the Global Address List (GAL). You can use distribution lists or individual mailboxes.
A mailbox can be part of multiple groups and is only calculated as one license. The total number of all members of these groups determines the number of licenses you need.

The number of AgendaX web application users is unlimited. Only the total number of published mailbox calendars determines the licenses needed.

No, you can only purchase a Software Assurance contract during the first 30 days after a license purchase or while purchasing a regular update.

If you want to move your AgendaX database to a new SQL server, please proceed as follows:

• Stop the AgendaX Update Service
• Transfer the database to the new database server either by Backup / Restore or with the Import / Export Wizard in SQL Management Studio
• On the new database, check under Options that the ‘Simple Recovery Model’ is selected
• Create and authorize the SQL user used for AgendaX (AgendaXCfg.exe / DB User) on the new database (db_owner rights on the new database)
• In AgendaXCfg.exe, under Config / Edit, adjust the SQL data source to the new database
• Possibly adjust under AgendaXCfg.exe / DB user if the database user on the new database has a different name
• In AgendaXCfg.exe under Servers, select the first entry under ‘Available Servers’, click on ‘…’ under Datasource, then Edit and go through the SQL data source wizard again until the end. Adjust DB Username and DB Password here if necessary, then click ‘modify’ and OK, click Update and ‘No’ when asked to restart the service
• Check AgentX.ini and AgendaX.inc to see if there are no more references to the old database server (just to be on the safe side)
• Restart the AgendaX Update Service

After starting the service, please check the Windows Application Eventlog for any errors / warnings.

Since AgendaX behaves like an Outlook client, nothing special needs to be considered in a cluster server environment. If a cluster member server goes down, AgendaX automatically connects to another member server as soon as it takes over.

No, you will need to upgrade to V6 of AgendaX, as V5.1 is not compatible with the above Exchange Server versions.

You can get a quote for the Upgrade from our Sales team.

Please fill out the inquiry form on our homepage and a member of our Sales team will get in touch with you asap.

AgendaX comes with a customizable stylesheet. It is very easy to change background colors, date layouts, ruler colors, etc., and add your own logo and background images if needed through the web-based administration interface of AgendaX.

You can also specify how meetings are displayed:  For example, show only weekdays (without Saturday / Sunday), show only meetings within the specified working hours, hide meetings that are marked as free, show the organizer and participants in a tooltip, and so on.

Furthermore, thanks to access to the source code of all views, you can program your own custom views or let us program them for you.

AgendaX provides a web-based configuration interface that allows easy setup of all AgendaX features. AgendaX views can be easily customized to match corporate identity and business requirements. The supplied icons and colors used to represent various activities can be changed to suit your needs.

The AgendaX administration page is used to configure the most common AgendaX settings. Only a closed user group of administrators can access it. The page is divided into the following sections:

• Global settings
  Settings that affect all views (e.g. time format, language, etc.)
• Display settings
  Settings that affect how the views are displayed (which colors to use, how many days to display, etc.)
• Feature settings
  allow you to enable / disable various AgendaX features.
• View settings
  let you determine which views are available and configure various aspects of those views.
• Categories
  With Categories you can define which Outlook categories are highlighted / color coded in the overviews.
• Additional settings
  Allows you to configure other, less commonly used AgendaX settings.

Calendar views showing different groups of people and/or resources can be created by the administrator or end users.

The administrator can configure an unlimited number of individual groups consisting of Exchange distribution lists and individual users. The members of these groups are the users whose calendars are displayed by the AgendaX web application.

Each AgendaX end user has the possibility to define up to 9 personal groups, which are only available to him / her. Personal groups are defined in the AgendaX web interface.

Currently supported languages are:

• English
• German
• French
• Italian
• Danish
• Norwegian
• Finnish
• Swedish
• Dutch
• Polish

The language used by AgendaX can either be:

• defined by the Administrator (all users use the same language)

or

• AgendaX automatically adapts to the first browser language supported by AgendaX.

Additional languages can  be added easily.
Upon request, we can send you a language file for translation to your local language, which we can integrate into the product within just a few days.

Can I add Exchange distribution lists to AgendaX groups instead of individual mailboxes?
Yes. AgendaX groups can contain individual mailboxes and / or Exchange Distribution Lists.

Exchange Distribution Lists are resolved to their members each time the AgendaX Update Service scans calendars, so new members of an Exchange Distribution List are automatically added to AgendaX groups.

Likewise, members that are deleted from an Exchange distribution list also get deleted from AgendaX groups. Therefore, you only need to update group membership in Exchange distribution lists, and AgendaX automatically updates its groups.

Does AgendaX support Windows Authentication on the AgendaX database?
Yes, but we recommend using SQL authentication, as it’s easier to manage.

If your company policies don’t allow usage of SQL authentication, you can use Windows authentication, but you will need to grant all AgendaX web application users permissions on the SQL database.

When using Windows authentication, do not enter a SQL username and password during Setup or in AgendaXCfg.exe / DB User and Servers / DB Username.

Yes, AgendaX can scan mailbox calendars of any Exchange Server version with a single AgendaX Update Service.

Make sure that you setup the AgendaX Service account mailbox on the Exchange server with the latest version, and specify that Exchange server version during Setup / in AgendaXCfg.exe.

AgendaX does NOT use Log4j and / or Java in general and is therefore not affected by the Log4j security gap.

If the move to Office / Microsoft 365 takes some time and you migrate mailboxes with several batches, we suggest to install a second instance of AgendaX during the transition.

The first (existing) instance will read on-premise mailboxes and the second (new) instance will read migrated (Microsoft 365) mailboxes.

During the transition, you will still see all calendars of both on-premise and migrated mailboxes in the AgendaX web application.

Installing a second AgendaX Setup on the AgendaX server to access the Microsoft 365 mailboxes

• Create a new AgendaX user on Office / Microsoft 365 (including mailbox)
• Copy the AgendaX installation folder to a second location, e.g. AgendaXM365
• Install the second service with the AgendaX Multi service configuration tool. The service account you enter will be the account used to run the AgendaX Update Service. This should ideally be the new AgendaX user on Office 365. If this is not possible, select a local user with Administrative privileges on the AgendaX Server.
• Install or update to Outlook 2016 (or later) on the AgendaX Server, if not already present
• Log on with the new AgendaX user (or the local user you specified while installing the second service) to the AgendaX server
• Set the appropriate registry flags for the Outlook version used and AgentX.ini settings (pages 5/6 in the Installation Guide)
• Create an Outlook profile with this user, accessing its mailbox on Microsoft 365, and disabling Exchange Cache Mode in the Outlook profile. If you are prompted for a username / password, check the ‘Remember Password’ option before entering the credentials. Note the name of the Outlook profile you created (default: Outlook)
• Run the AgendaX Configuration in the AgendaX M365 installation (AgendaXCfg.exe), click MSX Version, select Office 365 and enter the name of the Outlook profile you created, logged-in with the Microsoft 365 AgendaX user (or the local user).
• Set the Mailbox folder permissions for the users already migrated to Microsoft 365 with the following script.
  Replace “agendax” on the 4th and 5th line in the script with the name of your Microsoft 365 AgendaX account:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-EXOMailbox -OrganizationalUnit abc -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

"-OrganizationalUnit abc" limits the users to a specific OU (here "abc"). This can be omitted if you would like
to grant the permissions on every account in your organization.

If, instead, you would like to limit the users to users that have a specific SMTP- address, you can use the
following script:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-Mailbox -ResultSize Unlimited | where-Object {($_.PrimarySMTPAddress -like "*@agendax.net")}))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

Or, if you would like to limit the users to members of a specific distribution list, you can use the following:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-DistributionGroupMember -Identity "NameOfDistributionList" -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

• Stop the AgendaX Update service of the old AgendaX installation
• Run the AgendaX Configuration of both the old and the new installation (AgendaXCfg.exe) and tick the “Multiple services write to this database” option and drop the database tables (only once) under Config / Drop tables.
• Click “Update” in both AgendaX Configuations and “Yes” to restart the Services
• Check the Windows Application Eventlog for possible warnings / errors. Each of the services will add warnings to the Application Event log for the mailboxes that are not on their system. This is normal. The on-premise Setup will create warnings for the Microsoft 365 mailboxes and the Microsoft 365 Setup will create warnings for the on-premise mailboxes. If you get warnings on the Microsoft 365 installation about mailboxes that cannot be found in the global address book and these mailboxes have already been migrated to Microsoft 365, you will have to re-select them from the address book in the AgendaX group definition (AgendaXCfg.exe / Groups).
• After both AgendaX Update Services have finished scanning through the mailboxes, you will see both on-premise and Microsoft 365 mailbox calendars in the AgendaX web application.
• While you are moving users from the on-premise Exchange servers to Microsoft 365, you will need to re-run the above Powershell script to set permissions on the newly moved mailboxes.

Removing the old AgendaX Setup after all mailboxes are moved to Microsoft 365

When all mailboxes are moved to Microsoft 365, you can uninstall the old AgendaX setup by following the steps below. As the web-application of AgendaX is still running under your old AgendaX setup, you will first need to move this to the location of the new (M365) installation:

Run Internet Information Services (IIS) Manager, navigate to Sites / Default Web Site / AgendaX, click “Basic settings” and change the location of the “Physical path” to the folder of your new AgendaX M365 installation.

If you have made any configuration changes on the AgendaX Administration page (in the AgendaX web application) since you installed the Microsoft 365 installation of AgendaX, or if you have made changes to the collapsible group menu in the multmenu.txt file, copy config.inc and multmenu.txt (both are located in the AGENDA subfolder of your AgendaX installation folder) from the old Setup to the Microsoft 365 setup.

To uninstall the old AgendaX Setup, follow the steps below:

• Stop the AgendaX Update Service of the old installation
• Close any instances of MMC (Microsoft Management Console), e.g. Services, Event Viewer
• Open an elevated command prompt (Run as Administrator) and change to the AgendaX installation folder of your old AgendaX installation, e.g. CD C:\Inetpub\AgendaX
• Enter the following command:
  AgendaXSrv.exe -u (this will uninstall the AgendaX Update Service)
• Delete the old AgendaX installation folder

The final step is to tell the AgendaX Update service that no longer other services are using the same database. Run the AgendaX Configuration (AgendaXCfg.exe) in your new Microsoft 365 setup folder and untick the “Multiple services write to this database” option and drop the database tables under Config / Drop tables, then click “Update” and “Yes” to restart the service.

You will need to uninstall MAPI/CDO (Exchange Server MAPI, if installed) and install an Outlook 32bit client on the AgendaX server (Outlook 2016 or later). Also, the AgendaX mailbox needs to be migrated to Microsoft 365 first, before you start migrating user mailboxes.

Then,

• Log in on the AgendaX Server with the AgendaX user. This is VERY important because Outlook profiles are user specific.
• Set the appropriate registry flags for the Outlook version used and AgentX.ini settings (pages 5/6 in the Installation Guide)
• Then, create the Outlook profile and make sure that Exchange Cache mode is disabled in the Outlook profile. Enter the Outlook profile name (either in AgendaX Setup if you are setting up a new instance of AgendaX or in AgendaXCfg.exe if AgendaX is already installed under MSX Version / Outlook MAPI Client / Outlook Profile Name). The Standard- Name for the first Outlook- Profile that is configured is ‘Outlook’.
• Start Outlook with that profile and make sure that the profile works. When you are prompted for a password, make sure to check the ‘Remember password’ checkbox.
• Finally, close Outlook and restart the AgendaX Update Service

The permissions on Office / Microsoft 365 have to be set a bit differently than in an On Site Exchange environment. On Microsoft 365, you will have to set permissions on folder level:

Please give the AgendaX user Reviewer rights on the top of the mailbox and Editor rights on the Calendar folders.

The following powershell scripts (or similar) might be helpful for doing this for all or a subset of mailboxes:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-EXOMailbox -OrganizationalUnit abc -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

"-OrganizationalUnit abc" limits the users to a specific OU (here "abc"). This can be omitted if you would like
to grant the permissions on every account in your organization.

If, instead, you would like to limit the users to users that have a specific SMTP- address, you can use the
following script:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-Mailbox -ResultSize Unlimited | where-Object {($_.PrimarySMTPAddress -like "*@agendax.net")}))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

Or, if you would like to limit the users to members of a specific distribution list, you can use the following:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-DistributionGroupMember -Identity "NameOfDistributionList" -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

Permissions that need to be set for the AgendaX account on Exchange Server 2013, 2016, 2019, and Office 365 / Microsoft 365 are Outlook folder level permissions.

Since folder names in Outlook differ depending on the language used when the mailbox is first opened with Outlook, you have to know which employee uses which language to assign permissions to the correct folders. In addition to that, you have to know what the folders are called in these languages.

If you have mailboxes in multiple languages in your company, you can easily set the required permissions for the AgendaX account using the following script.

Please make sure you replace “agendax@company.com” on the 3rd line with the name of your AgendaX account:

foreach ($Mailbox in (Get-Mailbox -ResultSize Unlimited))
{
  $AgendaXAccount = "agendax@company.com"

  $CalendarStat = Get-MailboxFolderStatistics -Identity $Mailbox -FolderScope Calendar | Where {$_.FolderType -eq "Calendar"}
  $CalendarName = "$($Mailbox.Name)" + ":\" + "$($CalendarStat.Name)"

  Write-Host "Applying permissions to mailbox: $($Mailbox.Name) (TOIS/$($CalendarStat.Name))"
 
  $AccRightTOIS = Get-MailboxFolderPermission -identity $Mailbox.Name -user $AgendaXAccount >$null 2>&1
  $AccRightCalendar = Get-MailboxFolderPermission -identity $CalendarName -user $AgendaXAccount >$null 2>&1

  If ($AccRightTOIS.AccessRights -ne "Reviewer")
  {
    Remove-MailboxFolderPermission -Identity $Mailbox.Name -User $AgendaXAccount -Confirm:$false >$null 2>&1
    Add-MailboxFolderPermission -identity $Mailbox.Name -AccessRights Reviewer -User $AgendaXAccount >$null 2>&1
  }
  If ($AccRightCalendar.AccessRights -ne "Editor")
  {
    Remove-MailboxFolderPermission -Identity $CalendarName -User $AgendaXAccount -Confirm:$false >$null 2>&1
    Add-MailboxFolderPermission -identity $CalendarName -AccessRights Editor -User $AgendaXAccount >$null 2>&1
  }
}

Just copy and paste the above script into Powershell. It will assign Reviewer rights on the top of the mailbox as well as Editor rights on the Calendar folder.

AgendaX works installed on a server of your Exchange provider, or installed on your local network.
Most probably, your Exchange Hosting provider will not let you install anything on his servers. In this case, you can install AgendaX on your local network.

On the AgendaX Server computer, install Outlook 32bit (Outlook 2016 or later for Exchange Server 2016 or later, or hosted Exchange).
Then, create a mailbox (e.g. ‘AgendaX’), and give this mailbox the following permissions on every mailbox that you want to read and publish with AgendaX:

Rewiewer rights on the top of the mailbox (in some Outlook versions called ‘Outlook Today’)
Editor rights on the Calendar folder

The following Powershell scripts might be helpful for doing this for all or a subset of mailboxes:

foreach ($Mailbox in (Get-Mailbox -OrganizationalUnit abc -ResultSize Unlimited))
{
  Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
  Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}

The term ‘Calendar’ in the above example is language specific and might have to be changed in your environment, depending on the Outlook folder names in your language.

The term “-OrganizationalUnit abc” limits the mailboxes to those of a specifig OU. If you want to assign rights to all mailboxes, remove this parameter.

Create a user account (‘AgendaX’) in your local Active Directory and log in with that account on the AgendaX server.

Start Outlook and create a profile that accesses the mailbox of the AgendaX user. Turn OFF Exchange Cache mode.

Finally, install AgendaX and when prompted for the Exchange Server version, check the checkbox labeled ‘Exchange is hosted by a hosting provider in an untrusted domain’ and enter the name of the profile you created above.

If you wish to hide meeting details, you’ll have to use the ‚Minimal Security‘ model of AgendaX. This model implies that you set a Custom Mailbox attribute to the value “1” for each mailbox that should not publish details.

If you would like to use this feature for all users without setting this Custom Mailbox attribute for every user, you can ‚reverse’ the security logic by specifying a Custom Mailbox attribute in AgendaXCfg.exe / Security that is NOT set to “1” for any user and by adding the following switch to AgentX.ini:

[Config]
ReverseSecurityLogic=1

How do I setup a second copy (installation) of AgendaX on the same server?

If you want to setup a new copy (installation) of AgendaX on the same server, you have to do this with the AgendaX Multiple Services Configuration Utility provided on our homepage in the Downloads section.

First copy your current setup to another location on the hard disk, and then register the new service with the utility provided.

Then, make the configuration changes on the new installation (delete / add groups, users), etc., and setup a second virtual directory on IIS (if needed):

AECrVDir.exe path_to_AgendaX_setup virtual_directory_name

e.g. AECrVDir c:\inetpub\agendax2ndgroup agendax2

More information on how to setup a virtual directory can be found in the Administrator Guide.

The latest patch for V6 is V6.5. You can download the patch in the Downloads section or directly from here: http://www.drollingertechnologies.com/download/agx65update.zip

Please note that the current trial version download already includes the latest patch.

Development of V5 has ceased. The latest patch available for this version is patch 38. You can download this patch, or the V5 setup that includes this patch (in case you need to install it on another server) from our homepage in the Downloads section.

We recommend all users of V5 to upgrade to V6 or the latest version.

Please make sure that you enter the Company name exactly as provided on the license document or in the email you received from us (capitalization, spacing, etc.).

Yes, you can install AgendaX on multiple servers, as long as the total number of different published mailbox calendars on all installations is not higher than the total number of licenses purchased.

There are no additional costs associated with installing AgendaX on multiple servers.

No, AgendaX can be installed on any IIS server.

An installation on Exchange Server is not required.

Also, no components need to be installed on the Exchange server.

AgendaX needs the following components:

• Microsoft Windows Server (all versions are supported)
• Microsoft IIS Server (included in Windows Server)
• 32bit Outlook Client installed on the AgendaX Server
• A SQL Server or SQL Server Express

Even though AgendaX can be installed on the same server like Exchange Server, we recommend to install AgendaX on an existing IIS Server with a minimum of 2 GB of RAM and a Dual-Core-CPU.

Supported Versions of Exchange are:

• Microsoft Exchange Server 5.5
• Microsoft Exchange Server 2000
• Microsoft Exchange Server 2003
• Microsoft Exchange Server 2007
• Microsoft Exchange Server 2010
• Microsoft Exchange Server 2013
• Microsoft Exchange Server 2016
• Microsoft Exchange Server 2019
• Office 365, Microsoft 365
• Hosted Exchange

No, you will need to upgrade to V6 of AgendaX, as V5.1 is not compatible with the above Exchange Server versions.

You can get a quote for the Upgrade from our Sales team.

Please fill out the inquiry form on our homepage and a member of our Sales team will get in touch with you asap.

Yes, V6 of AgendaX supports hybrid deployments of Office 365. You will need an AgendaX mailbox for the on-premise AgendaX installation and an AgendaX mailbox for the Office / Microsoft 365 AgendaX installation (cloud mailbox).

Does AgendaX support hosted Exchange environments / Exchange Online / Office 365 / Microsoft 365?
Yes. AgendaX supports all hosted Exchange environments.

I would like to install the AgendaX Update Service (that reads calendars from Exchange) and the AgendaX web application on 2 different servers. Is this possible?

Yes, perform a full Setup on the server that will host the AgendaX Update Service, Then, copy the Inetpub/AgendaX folder to the server that will host the AgendaX web application, set up the virtual directory, and register AEPwDC.DLL with regsvr32. This DLL is required to decrypt the SQL password.

Also, you have to create a data source (preferably with the same name) on the web server, pointing to the SQL server database. If you name it differently, you will have to also change it in AgendaXCfg.exe under ‘Config’ and ‘Servers’. Please note that you have to create a system data source (not user data source), to be accessible by all users.

Please note that when you make changes to the AgendaX Configuration using AgendaXCfg.exe, you have to copy the file AgendaX.inc to the AgendaX installation directory on the web server to reflect those changes in the web application.

Does AgendaX support Windows Authentication on the AgendaX database?
Yes, but we recommend using SQL authentication, as it’s easier to manage.

If your company policies don’t allow usage of SQL authentication, you can use Windows authentication, but you will need to grant all AgendaX web application users permissions on the SQL database.

When using Windows authentication, do not enter a SQL username and password during Setup or in AgendaXCfg.exe / DB User and Servers / DB Username.

Yes, AgendaX can scan mailbox calendars of any Exchange Server version with a single AgendaX Update Service.

Make sure that you setup the AgendaX Service account mailbox on the Exchange server with the latest version, and specify that Exchange server version during Setup / in AgendaXCfg.exe.

AgendaX uses MAPI / Outlook MAPI to connect to the Exchange Servers. MAPI is a standard Microsoft protocol that uses RPC/MAPI connections to / from the Exchange Servers. When using Outlook MAPI, the RPC/MAPI packets may be encapsulated in HTTP packets, especially when reading Microsoft 365 mailbox calendars.

AgendaX uses standard TCP/IP connections to access SQL servers / SQL Express.

AgendaX does NOT use Log4j and / or Java in general and is therefore not affected by the Log4j security gap.

If the move to Office / Microsoft 365 takes some time and you migrate mailboxes with several batches, we suggest to install a second instance of AgendaX during the transition.

The first (existing) instance will read on-premise mailboxes and the second (new) instance will read migrated (Microsoft 365) mailboxes.

During the transition, you will still see all calendars of both on-premise and migrated mailboxes in the AgendaX web application.

Installing a second AgendaX Setup on the AgendaX server to access the Microsoft 365 mailboxes

• Create a new AgendaX user on Office / Microsoft 365 (including mailbox)
• Copy the AgendaX installation folder to a second location, e.g. AgendaXM365
• Install the second service with the AgendaX Multi service configuration tool. The service account you enter will be the account used to run the AgendaX Update Service. This should ideally be the new AgendaX user on Office 365. If this is not possible, select a local user with Administrative privileges on the AgendaX Server.
• Install or update to Outlook 2016 (or later) on the AgendaX Server, if not already present
• Log on with the new AgendaX user (or the local user you specified while installing the second service) to the AgendaX server
• Set the appropriate registry flags for the Outlook version used and AgentX.ini settings (pages 5/6 in the Installation Guide)
• Create an Outlook profile with this user, accessing its mailbox on Microsoft 365, and disabling Exchange Cache Mode in the Outlook profile. If you are prompted for a username / password, check the ‘Remember Password’ option before entering the credentials. Note the name of the Outlook profile you created (default: Outlook)
• Run the AgendaX Configuration in the AgendaX M365 installation (AgendaXCfg.exe), click MSX Version, select Office 365 and enter the name of the Outlook profile you created, logged-in with the Microsoft 365 AgendaX user (or the local user).
• Set the Mailbox folder permissions for the users already migrated to Microsoft 365 with the following script.
  Replace “agendax” on the 4th and 5th line in the script with the name of your Microsoft 365 AgendaX account:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-EXOMailbox -OrganizationalUnit abc -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

"-OrganizationalUnit abc" limits the users to a specific OU (here "abc"). This can be omitted if you would like
to grant the permissions on every account in your organization.

If, instead, you would like to limit the users to users that have a specific SMTP- address, you can use the
following script:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-Mailbox -ResultSize Unlimited | where-Object {($_.PrimarySMTPAddress -like "*@agendax.net")}))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

Or, if you would like to limit the users to members of a specific distribution list, you can use the following:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-DistributionGroupMember -Identity "NameOfDistributionList" -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

• Stop the AgendaX Update service of the old AgendaX installation
• Run the AgendaX Configuration of both the old and the new installation (AgendaXCfg.exe) and tick the “Multiple services write to this database” option and drop the database tables (only once) under Config / Drop tables.
• Click “Update” in both AgendaX Configuations and “Yes” to restart the Services
• Check the Windows Application Eventlog for possible warnings / errors. Each of the services will add warnings to the Application Event log for the mailboxes that are not on their system. This is normal. The on-premise Setup will create warnings for the Microsoft 365 mailboxes and the Microsoft 365 Setup will create warnings for the on-premise mailboxes. If you get warnings on the Microsoft 365 installation about mailboxes that cannot be found in the global address book and these mailboxes have already been migrated to Microsoft 365, you will have to re-select them from the address book in the AgendaX group definition (AgendaXCfg.exe / Groups).
• After both AgendaX Update Services have finished scanning through the mailboxes, you will see both on-premise and Microsoft 365 mailbox calendars in the AgendaX web application.
• While you are moving users from the on-premise Exchange servers to Microsoft 365, you will need to re-run the above Powershell script to set permissions on the newly moved mailboxes.

Removing the old AgendaX Setup after all mailboxes are moved to Microsoft 365

When all mailboxes are moved to Microsoft 365, you can uninstall the old AgendaX setup by following the steps below. As the web-application of AgendaX is still running under your old AgendaX setup, you will first need to move this to the location of the new (M365) installation:

Run Internet Information Services (IIS) Manager, navigate to Sites / Default Web Site / AgendaX, click “Basic settings” and change the location of the “Physical path” to the folder of your new AgendaX M365 installation.

If you have made any configuration changes on the AgendaX Administration page (in the AgendaX web application) since you installed the Microsoft 365 installation of AgendaX, or if you have made changes to the collapsible group menu in the multmenu.txt file, copy config.inc and multmenu.txt (both are located in the AGENDA subfolder of your AgendaX installation folder) from the old Setup to the Microsoft 365 setup.

To uninstall the old AgendaX Setup, follow the steps below:

• Stop the AgendaX Update Service of the old installation
• Close any instances of MMC (Microsoft Management Console), e.g. Services, Event Viewer
• Open an elevated command prompt (Run as Administrator) and change to the AgendaX installation folder of your old AgendaX installation, e.g. CD C:\Inetpub\AgendaX
• Enter the following command:
  AgendaXSrv.exe -u (this will uninstall the AgendaX Update Service)
• Delete the old AgendaX installation folder

The final step is to tell the AgendaX Update service that no longer other services are using the same database. Run the AgendaX Configuration (AgendaXCfg.exe) in your new Microsoft 365 setup folder and untick the “Multiple services write to this database” option and drop the database tables under Config / Drop tables, then click “Update” and “Yes” to restart the service.

You will need to uninstall MAPI/CDO (Exchange Server MAPI, if installed) and install an Outlook 32bit client on the AgendaX server (Outlook 2016 or later). Also, the AgendaX mailbox needs to be migrated to Microsoft 365 first, before you start migrating user mailboxes.

Then,

• Log in on the AgendaX Server with the AgendaX user. This is VERY important because Outlook profiles are user specific.
• Set the appropriate registry flags for the Outlook version used and AgentX.ini settings (pages 5/6 in the Installation Guide)
• Then, create the Outlook profile and make sure that Exchange Cache mode is disabled in the Outlook profile. Enter the Outlook profile name (either in AgendaX Setup if you are setting up a new instance of AgendaX or in AgendaXCfg.exe if AgendaX is already installed under MSX Version / Outlook MAPI Client / Outlook Profile Name). The Standard- Name for the first Outlook- Profile that is configured is ‘Outlook’.
• Start Outlook with that profile and make sure that the profile works. When you are prompted for a password, make sure to check the ‘Remember password’ checkbox.
• Finally, close Outlook and restart the AgendaX Update Service

The permissions on Office / Microsoft 365 have to be set a bit differently than in an On Site Exchange environment. On Microsoft 365, you will have to set permissions on folder level:

Please give the AgendaX user Reviewer rights on the top of the mailbox and Editor rights on the Calendar folders.

The following powershell scripts (or similar) might be helpful for doing this for all or a subset of mailboxes:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-EXOMailbox -OrganizationalUnit abc -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

"-OrganizationalUnit abc" limits the users to a specific OU (here "abc"). This can be omitted if you would like
to grant the permissions on every account in your organization.

If, instead, you would like to limit the users to users that have a specific SMTP- address, you can use the
following script:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-Mailbox -ResultSize Unlimited | where-Object {($_.PrimarySMTPAddress -like "*@agendax.net")}))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

Or, if you would like to limit the users to members of a specific distribution list, you can use the following:

Connect-ExchangeOnline
foreach ($Mailbox in (Get-DistributionGroupMember -Identity "NameOfDistributionList" -ResultSize Unlimited))
{
Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}
Disconnect-ExchangeOnline

Permissions that need to be set for the AgendaX account on Exchange Server 2013, 2016, 2019, and Office 365 / Microsoft 365 are Outlook folder level permissions.

Since folder names in Outlook differ depending on the language used when the mailbox is first opened with Outlook, you have to know which employee uses which language to assign permissions to the correct folders. In addition to that, you have to know what the folders are called in these languages.

If you have mailboxes in multiple languages in your company, you can easily set the required permissions for the AgendaX account using the following script.

Please make sure you replace “agendax@company.com” on the 3rd line with the name of your AgendaX account:

foreach ($Mailbox in (Get-Mailbox -ResultSize Unlimited))
{
  $AgendaXAccount = "agendax@company.com"

  $CalendarStat = Get-MailboxFolderStatistics -Identity $Mailbox -FolderScope Calendar | Where {$_.FolderType -eq "Calendar"}
  $CalendarName = "$($Mailbox.Name)" + ":\" + "$($CalendarStat.Name)"

  Write-Host "Applying permissions to mailbox: $($Mailbox.Name) (TOIS/$($CalendarStat.Name))"
 
  $AccRightTOIS = Get-MailboxFolderPermission -identity $Mailbox.Name -user $AgendaXAccount >$null 2>&1
  $AccRightCalendar = Get-MailboxFolderPermission -identity $CalendarName -user $AgendaXAccount >$null 2>&1

  If ($AccRightTOIS.AccessRights -ne "Reviewer")
  {
    Remove-MailboxFolderPermission -Identity $Mailbox.Name -User $AgendaXAccount -Confirm:$false >$null 2>&1
    Add-MailboxFolderPermission -identity $Mailbox.Name -AccessRights Reviewer -User $AgendaXAccount >$null 2>&1
  }
  If ($AccRightCalendar.AccessRights -ne "Editor")
  {
    Remove-MailboxFolderPermission -Identity $CalendarName -User $AgendaXAccount -Confirm:$false >$null 2>&1
    Add-MailboxFolderPermission -identity $CalendarName -AccessRights Editor -User $AgendaXAccount >$null 2>&1
  }
}

Just copy and paste the above script into Powershell. It will assign Reviewer rights on the top of the mailbox as well as Editor rights on the Calendar folder.

AgendaX works installed on a server of your Exchange provider, or installed on your local network.
Most probably, your Exchange Hosting provider will not let you install anything on his servers. In this case, you can install AgendaX on your local network.

On the AgendaX Server computer, install Outlook 32bit (Outlook 2016 or later for Exchange Server 2016 or later, or hosted Exchange).
Then, create a mailbox (e.g. ‘AgendaX’), and give this mailbox the following permissions on every mailbox that you want to read and publish with AgendaX:

Rewiewer rights on the top of the mailbox (in some Outlook versions called ‘Outlook Today’)
Editor rights on the Calendar folder

The following Powershell scripts might be helpful for doing this for all or a subset of mailboxes:

foreach ($Mailbox in (Get-Mailbox -OrganizationalUnit abc -ResultSize Unlimited))
{
  Add-MailboxFolderPermission -identity "$($Mailbox.Name)" -AccessRights Reviewer -User agendax
  Add-MailboxFolderPermission -identity "$($Mailbox.Name):\Calendar" -AccessRights Editor -User agendax
}

The term ‘Calendar’ in the above example is language specific and might have to be changed in your environment, depending on the Outlook folder names in your language.

The term “-OrganizationalUnit abc” limits the mailboxes to those of a specifig OU. If you want to assign rights to all mailboxes, remove this parameter.

Create a user account (‘AgendaX’) in your local Active Directory and log in with that account on the AgendaX server.

Start Outlook and create a profile that accesses the mailbox of the AgendaX user. Turn OFF Exchange Cache mode.

Finally, install AgendaX and when prompted for the Exchange Server version, check the checkbox labeled ‘Exchange is hosted by a hosting provider in an untrusted domain’ and enter the name of the profile you created above.

If you wish to hide meeting details, you’ll have to use the ‚Minimal Security‘ model of AgendaX. This model implies that you set a Custom Mailbox attribute to the value “1” for each mailbox that should not publish details.

If you would like to use this feature for all users without setting this Custom Mailbox attribute for every user, you can ‚reverse’ the security logic by specifying a Custom Mailbox attribute in AgendaXCfg.exe / Security that is NOT set to “1” for any user and by adding the following switch to AgentX.ini:

[Config]
ReverseSecurityLogic=1

How do I setup a second copy (installation) of AgendaX on the same server?

If you want to setup a new copy (installation) of AgendaX on the same server, you have to do this with the AgendaX Multiple Services Configuration Utility provided on our homepage in the Downloads section.

First copy your current setup to another location on the hard disk, and then register the new service with the utility provided.

Then, make the configuration changes on the new installation (delete / add groups, users), etc., and setup a second virtual directory on IIS (if needed):

AECrVDir.exe path_to_AgendaX_setup virtual_directory_name

e.g. AECrVDir c:\inetpub\agendax2ndgroup agendax2

More information on how to setup a virtual directory can be found in the Administrator Guide.