Logs & Settings Action Plan for EWS issues with SkypeShield Credentials
Please follow this action plan in order to collect the logs:
1.Change log levels
I. Change the LAC Log Level
|
II. Change the EWS Log Level
|
III. Change the DMZ Bastion and Authentication Extender Log Level
|
IV. Restart the Bastion Service on the DMZ Bastion and Authentication Extender
|
2. Replicate the issue
3. Collect files
I. Collect the log LAC_<poolname>_<date>.log and the Dumps folder from the relevant date
II. Collect the log KCD.<poolname>.<date>.log and the AuthConsumer.<poolname>.<date>.log from the relevant date
III. Collect the log Bastion.<date>.log and the dumps folder from the relevant date
IV. Collect the Lync_Access_Control.xml
V. Collect the log EWS_<poolname>_<date>.log and the Dumps folder from the relevant date
VI. Collect the EWS_Protector.xml
VII. Export Access Portal Logs
|
4. Revert Changes
I. Revert back to the old Lync_Access_Control.xml
II. Revert back to the old Bastion.xml
III. Revert back to the old EWS_Protector.xml
IV. Restart the Bastion Service
|
The following files are expected to be delivered following this plan:
- Access Portal logs and settings
- EWS_<poolname>_<date>.log from the relevant date
- EWS Traffic Dumps folder from the relevant date
- EWS_Protector.xml
- Bastion.<date>.log folder from the relevant date from DMZ Reverse Proxy
- Bastion Traffic dumps folder from the relevant date from DMZ Reverse Proxy
- Bastion.<date>.log folder from the relevant date from Authentication Extender
- Bastion Traffic dumps folder from the relevant date Authentication Extender
- KCD.<poolname>.<date>.log from the relevant date from Authentication Extender
- the AuthConsumer.<poolname>.<date>.log from the relevant date from Authentication Extender
- 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