- AskCody Help Center
- Integrations and Security
- Outlook and Office 365
-
Implementing AskCody
- 1. Plan & Prepare for the implementation of AskCody
- 2. Identify the meeting journey / business processes
- 3. Sign up to the AskCody Platform
- 4a. Integrate with Microsoft Exchange
- 4b. Establish User Management
- 5. Setting up Bookings
- 6. Setting up Services
- 7. Setting up Visitors
- 10. Setting up Displays
- 11. User management in Entra ID and AD Server
- 12. Platform test and adjustments
- 13. Deploy Add-ins to all end-users
- 14. Training and end-user adoption
- 15. Go-Live
-
Troubleshooting
-
Tips & Tricks, Webinars, and more
-
Central
-
Maps
-
Bookings
-
Services
-
Visitors
-
Insights
-
Integrations and Security
-
Data processing and legal
-
Mastering Reports
-
Join the AskCody User Community
Service requests and pre-registrations not being updated?
Learn how to troubleshoot when requests placed via the Services add-in and pre-registered visitor lists are not following meeting rescheduling and cancellations.
One of the main requirements for using the Services and Visitor Management modules is to have TLS 1.2 enabled and selected both for inbound and outbound traffic (both for client and server requests) in your Exchange Servers. Using older versions of TLS, such as 1.0, or 1.1 will prevent your requests and visitor pre-registrations from following any modifications made to meetings (such as rescheduling and cancellations), thus making the meeting management process more difficult.
In order to make the requests and pre-registered visitor lists to follow changes made to the meetings (re-scheduling or cancellations), please enable and select TLS 1.2 both for inbound and outbound traffic (both for client and server requests) in your Exchange Servers.
The following guidance from Microsoft contains instructions for how to do so, and it goes step-by-step through the process of making sure TLS 1.2 for outbound traffic on HTTPS is enabled.