Logs & Settings Action Plan for MDM Integration Issues with SkypeShield App
Owned by Agat Support
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. Replicate the issue
5. Collect the log LAC_<poolname>_<date>.log and the Dumps folder from the relevant date
6. Collect the log Bastion.<date>.log and the dumps folder from the relevant date
7. Collect the Lync_Access_Control.xml
8. Revert back to the old Lync_Access_Control.xml
9. Revert back to the old Bastion.xml
10. Restart the Bastion Service
|
11. Export Access Portal Logs
|
12. Attach a screen capture of the SkypeShield App settings
|
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 from DMZ Reverse Proxy
- LAC Traffic dumps from the relevant time frame from DMZ Reverse Proxy
- Lync_Access_Control.xml from DMZ Reverse Proxy
- Bastion.<date>.log folder from the relevant date from DMZ Reverse Proxy
- Bastion Traffic dumps folder from the relevant date from DMZ Reverse Proxy
- Screen capture of the application configuration
- Skype for Business 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