Logs & Settings Action Plan for Mobile Devices and PC Sign in with Active Directory Credentials
Please follow this action plan in order to collect the logs:
1. Change the LAC Log Level
|
2. Change the Bastion Log Level
|
3. Restart the Bastion Service
|
4. Change the SIP Filter Log Level
|
5. Restart the SIP Filter Service
|
6. Replicate the issue
7. Collect the log LAC_<poolname>_<date>.log and the Dumps folder from the relevant date
8. Collect the log Bastion.<date>.log and the dumps folder from the relevant date
9. Collect the Lync_Access_Control.xml
10. Revert back to the old Lync_Access_Control.xml
11. Collect the log sipfilter-<date>.log and the trace.<date>.log from the relevant date
12. Collect the AgatSfbSIPFilter.yaml file
13. Revert back to the old AgatSfbSIPFilter.yaml
14. Revert back to the old Bastion.xml
15. Restart the Bastion Service
|
16. Export Access Portal Logs
|
17. Send AGAT Software Support the collected logs
The following files are expected to be delivered following this plan:
- Access Portal logs and settings
- LAC_<poolname>_<date>.log from the relevant time frame in Debug mode
- LAC Traffic dumps from the relevant time frame
- Lync_Access_Control.xml
- sipfilter_<date>.log from the relevant date from the Edge
- trace-<date>.log from the relevant date from the Edge
- AgatSfbSIPFilter.yaml from the Edge
- Bastion_<version>_<date>.log folder from the relevant date
- Bastion Traffic dumps folder from the relevant date
- Bastion.xml
- Skype for Business Client logs- see here How to find Skype Client logs
Default file location could be found here.
Please include the following information:
a. Time frames of issue
b. Users involved (SIP Address, AD username, UPN, etc.)
d. Client logs