- AskCody Help Center
- Integrations and Security
- Active Directory Server
-
Implementing AskCody
- 1. Preface
- 2. Plan & Prepare for the implementation of AskCody
- 3. Create your organizational account
- 4. Integrate with Microsoft Exchange
- 5. Establish User Management
- 6. Setting up Bookings
- 7. Setting up Displays
- 8. Setting up Services
- 9. Setting up Visitors
- 10. End-user management
- 11. Final Testing
- 12. Deploy to end-users
- 13. End-user Training and Adoption
- 14. Support after go-live
-
Integrations and Security
-
Troubleshooting
-
Bookings
-
Services
-
Visitors
-
Insights
-
Maps
-
Tips & Tricks, Webinars, and more
-
Data processing and legal
-
Mastering Reports
-
Join the AskCody User Community
Configuration file (config.json) is missing after Active Directory Server Integration
Troubleshoot when the config file for Active Directory Server Integration is missing from the system folder
When you have installed and started the Active Directory Server Integration, the configuration file (config.json) should appear in the folder named:
%USERPROFILE%\AppData\Roaming\AskCody\ActiveDirectory\ForwardingService
If this is not the case, please check the following troubleshooting steps:
1. Please note that %USERPROFILE% is the user that the service will run as, which is not necessarily the same user that installed the service. In that case, the Active Directory Server Integration shortcut folder on the Desktop might point to the wrong folder.
2. Check to see if the service is running
3. Make sure that the Windows server has the following requirements:
Minimum Requirements
The service depends on the following:
- Windows Server 2008 R2 SP1 or later
- .NET Framework 4.6.2
Minimum Server Requirements
- Processor: Minimum 2GHz dual-core
- RAM: 2GB
- Memory: 1.75GB
Info
Please make sure that outbound communication on port 443 (HTTPS) is allowed in the Exchange Server (both for client, and server requests)