Supportanfrage

FAQ

Licensing

AgendaX licensing is based on the number of mailbox calendars that you display in the AgendaX Web interface. You can freely choose which mailboxes in your company you would like to display and which not. The total number of displayed mailboxes is the number of licenses you require. The AgendaX license is a onetime fee and includes patches and updates within the current version, as well as Standard e-mail support during the first 90 days. Additional Support options are available.


2 people found this faq useful.

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


Be the first person to like this faq.

Only the Software Assurance contract includes free updates to major version updates. All other Support options include updates within the licensed version.


Be the first person to like this faq.

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


Be the first person to like this faq.

Configuration

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.


Be the first person to like this faq.

You will need to uninstall MAPI/CDO (Exchange Server MAPI) and install an Outlook 32bit client on the AgendaX server. Also, the AgendaX mailbox needs to be migrated to Office 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.
  • Run Regedit and make sure that there is no value called MapiHttpDisabled under HKEY_CURRENT_USER\Software\Microsoft\Exchange or that its value is set to 0.
    • Outlook 2010:
      nothing special needs to be done
    • Outlook 2013:
      Run Regedit, go to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Cached Mode and add a value called AllowAutoDiscoverForNonOutlook and set its value to DWORD 1.
      Make sure that KB3114941 for Office 2013 32bit (https://support.microsoft.com/en-us/kb/3114941) is installed.
      Add the following parameter to AgentX.ini:
      [Config]
      ForceIExchangeManageStoreEx=1
    • Outlook 2016:
      Run Regedit, go to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Cached Mode and add a
      value called AllowAutoDiscoverForNonOutlook and set its value to DWORD 1.
  • 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 365 have to be set a bit differently than in an On Site Exchange environment. On Office 365, you will have to set permissions on folder level:

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

The following EMS scripts (or similar) 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 }

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

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

The terms ‘Inbox’ and ‘Calendar’ in the above examples are language- specific and might have to be changed in your environment, depending on the Outlook folder names in your language.

 

Please see also the following document: AgendaX Installation Guide V6.0


Be the first person to like this faq.

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


Be the first person to like this faq.

As AgendaX is working like an Outlook Client, there is nothing to worry about in a cluster environment.  If a cluster member fails, as soon as the other cluster member takes over, it will pick up from this one.


Be the first person to like this faq.

AgendaX provides a web-based configuration console that enables easy set-up of all AgendaX features. AgendaX views are easily tailored to reflect corporate identity and business needs. The ‚out-of-the-box‘ icons and colors used to represent different activities can be changed as desired.

The AgendaX Administration Page is used to configure the most common settings of AgendaX. It can only be accessed by a closed user group of Administrators. The page is divided into the following sections:

  • Global Settings are settings that affect all views (such as time format, language, etc.)
  • Display Settings affect how views are displayed (which colors to use, how many days to display, etc.)
  • Feature Settings lets you enable / disable various AgendaX features.
  • View Settings lets you define which views are enabled and lets you configure various aspects of these views.
  • Categories lets you define which Outlook Categories are color coded in the overviews.
  • Additional Settings lets you configure other not so common AgendaX settings.

Be the first person to like this faq.

AgendaX ships with a series of icons to represent key functions, as well as background colours, date layouts, ruler colours, etc.  It is very easy to change background colors, date layouts, ruler colors, etc., adding your own logo and background tile images as required.

You can also tailor how meetings are shown, for example:  Only show weekdays, only show meetings within normal working hours, hide meetings that are marked as free, display the meeting organiser and attendees in a tooltip, etc.

Furthermore, thanks to the open scripts and access to source code for all of the views, you can program your own customized views or have us program them for you.


Be the first person to like this faq.

AgendaX offers 3 levels of security:  No security, minimal security, and full security.

  • No security - Everybody sees all calendars, but by default, AgendaX does not publish meetings with sensitivity set to ‘Personal’, ‘Private’, or ‘Confidential’.
  • Minimal security - Details such as the subject and location are not published for certain users.
  • Full security - Users will only see calendars of users that have granted them access rights to their Outlook calendar folder, with the option to display just  free/busy data for calendars without permissions.

You can also setup different installations of AgendaX to show separate groups of users if they are not allowed to see each other’s data.


Be the first person to like this faq.

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

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

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


Be the first person to like this faq.

Supported languages are currently English, German, French, Italian, Danish, Norwegian, Swedish, Dutch and Polish.

Note that the language can be either:

  • Administer defined (all users use the same language)

or

  • Automatically set to the 1st browser language that is supported by AgendaX

 

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


Be the first person to like this faq.

Error Messages

Reported Errors in Application Event log of AgendaX Update Service:
Event ID 139: Error creating profile. MAPIAdminProfiles returned 80040605
Event ID 137: AgendaX Debug Log. \ Location: Create TempProfile failed. \ Data 1: %3\ Data 2: %4
Event ID 123: Mailboxes Scanned 0. Mailboxes on other sites (not scanned locally): 0.

Check that the AgendaX user has sufficient rights on the AgendaX server. In case you are using Exchange Server MAPI (not Outlook MAPI), the AgendaX Update Service dynamically creates MAPI profiles to access mailboxes on Exchange Server. These profiles are stored in the registry. Please make sure that this account has administrative privileges on the AgendaX server.
Also check that you have the latest MAPI version installed. MAPI can be downloaded from: http://www.microsoft.com/download/en/details.aspx?id=1004

Check the LogonServer and LogonMailbox parameters in the AgentX.ini file in your AgendaX installation directory. They should point to a valid mailbox (the mailbox associated with the AgendaX account).


Be the first person to like this faq.

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.


Be the first person to like this faq.

(FYDIBOHF23SPDLT)/cn=Recipients/cn=51d64b31d51b42e69a34d0463ce42322-abcd' in Global Address Book.
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.


Be the first person to like this faq.

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.).


Be the first person to like this faq.

If you can browse to the AgendaX Main Menu, but get an HTTP 500 error when you click on any of the views, you should set the following settings to get a detailed error message:

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

This will always show detailed errors instead of a HTTP 500 error, which is  useful to track down problems.


Be the first person to like this faq.

General Questions

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 switches 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).


Be the first person to like this faq.

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
  • Complete support for all Outlook properties (Mileage, Billing, etc.) including user-defined Outlook fields
  • 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 a required field, etc.
  • Easy-to-use administration page simplifies configuration
  • Rationalize multiple sites and time-zones
  • AgendaX reporting can also be used by business and HR managers within your organization to report on activities, chargeable days, sick days 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.

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.


Be the first person to like this faq.

No. AgendaX supports only mailbox calendars, not public folder calendars. Public folders are deprecated and will not be available in the next Exchange Server version. We therefore recommend converting Public Folder Calendars to Mailbox Calendars.


Be the first person to like this faq.

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


Be the first person to like this faq.

Yes, V6 of AgendaX supports hybrid deployments of Office 365. It’s advisable to place the AgendaX mailbox in the cloud.


Be the first person to like this faq.

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.


Be the first person to like this faq.

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 GAL (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 irrelevant. Only the total number of published mailbox calendars determines the licenses needed.


Be the first person to like this faq.

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.


Be the first person to like this faq.

AgendaX runs as a server-based Windows Service which reads appointments of selected users in regular intervals from the Microsoft Exchange Server Message Stores / databases and writes the information into a central database (SQL Server, SQL Express).

The calendar information is then published by Microsoft Internet Information Server (IIS) on the corporate Intranet or Internet / DMZ site using a set of Active Server Pages accessed via a web browser.

how_AgendaX_works_schematic


Be the first person to like this faq.

Components required on the AgendaX Server are:

  • Microsoft Windows Server (all versions supported)
  • Microsoft IIS Server
  • 32bit Outlook client installed on the AgendaX server
  • A SQL Server or SQL Server Express database

Although AgendaX can be installed on the same server as Exchange, we recommend you install it on an existing Microsoft IIS Server with at least 2 GB of RAM, and a Dual Core CPU.

Supported versions of Exchange are:

  • Microsoft Exchange Server (5.5, 2000, 2003, 2007, 2010, 2013, 2016, Office 365 / Hosted Exchange)

Be the first person to like this faq.

Yes.  If configured, all or selected users can make bookings via AgendaX without having to go back into Outlook calendar.

Default booking templates can be created if required that pre-fill start/end times, subjects, categories, All day event = no, etc., making it quicker and easier for end users to complete their booking.

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

It is also possible to:

  • Enable individuals to make bookings on behalf of a co-worker (e.g. off sick)
  • Allow bookings to be made that don’t include that individual (e.g. a PA booking a meeting)

All bookings are automatically synchronized into Outlook calendars and a log of all bookings made via AgendaX is kept.


Be the first person to like this faq.

Yes.  There are several ways to connect different AgendaX sites that don’t share the same Active directory forest, domain, or even if they are totally separate companies.

For example, AgendaX can scan the mailbox calendars on local Exchange Server(s) and write the information to a locally or remotely held database. A data source is configured between all sites (a specific port can be chosen) in order that all AgendaX installations are aware of each other and write to a central database.

For details about the protocols involved, please see also Multiple Organizations Architecture and Protocols


Be the first person to like this faq.

AgendaX offers benefits in several areas:

  • Even with the group schedule view option that ‘stacks’ calendars, Outlook Calendar views become almost unusable with more than 3-5 people’s calendars listed
  • Outlook Calendar can be slow as information is read in real-time from Exchange server
  • With Outlook Calendar it’s impossible for a receptionist to view where any individual is ‘at a glance’
  • AgendaX works across untrusted domains and even across organizations
  • With AgendaX you can easily filter views by categories (e.g. to produce holiday calendars)
  • AgendaX can be made accessible from the internet, for example if an employee is at a customer site and needs to quickly check the availability of his colleagues to set up a follow-up meeting with the customer
  • AgendaX lets you report on calendar activity (e.g. workload, time used for a customer, annual leave, sick leave, etc.)

AgendaX can include Active Directory information and can therefore be used as a company directory


Be the first person to like this faq.

Installation

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 2010 or later instead of the MAPI download.
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') and on the Inbox
  • Editor rights on the Calendar folder

The following EMS scripts (or similar) 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 }

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

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

The terms ‘Inbox’ and ‘Calendar’ in the above examples are language- specific and might have to be changed in your environment, depending on the Outlook folder names in your language.

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.
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.


Be the first person to like this faq.

If AgendaX is installed on a subnet of your Exchange Server Active Directory, AgendaX might have difficulty to connect to the Exchange Servers. You might also not be able to ping the CAS array on Exchange 2010+, while pinging individual mailbox servers works fine.
In this case, it could be that you are using Windows Network Load Balancer (WNLB) and you will need to statically assign the ARP entry in your router. More on this topic can be found here: http://social.technet.microsoft.com/Forums/da-DK/exchangesvravailabilityandisasterrecovery/thread/175551e6-d241-42d0-b8ab-d4d435554923


Be the first person to like this faq.

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

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


Be the first person to like this faq.

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.
Also, make sure to define all Exchange Servers in the 'Servers' configuration of AgendaXCfg.exe


Be the first person to like this faq.

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.


Be the first person to like this faq.

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 datasource (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 datasource (not user datasource), 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 to the web application.


Be the first person to like this faq.

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).

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.


1 people found this faq useful.

Components required on the AgendaX Server are:

  • Microsoft Windows Server (all versions supported)
  • Microsoft IIS Server
  • 32bit Outlook client installed on the AgendaX server
  • A SQL Server or SQL Server Express database

Although AgendaX can be installed on the same server as Exchange, we recommend you install it on an existing Microsoft IIS Server with at least 2 GB of RAM, and a Dual Core CPU.

Supported versions of Exchange are:

  • Microsoft Exchange Server (5.5, 2000, 2003, 2007, 2010, 2013, 2016, Office 365 / Hosted Exchange)

Be the first person to like this faq.

No, AgendaX can be installed on an IIS server; it does not need to be installed on the Exchange Server.  No component installation is needed on the Exchange Server.


Be the first person to like this faq.

As AgendaX is working like an Outlook Client, there is nothing to worry about in a cluster environment.  If a cluster member fails, as soon as the other cluster member takes over, it will pick up from this one.


Be the first person to like this faq.

Patches and Updates

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.


2 people found this faq useful.