A published change with an uncorrected target
A branch-access change is entered in SmartConsole and published. The operator installs a policy on two gateways, and the task succeeds on one but fails on the branch gateway used by the affected employees. A screenshot of the new rule is presented as proof that the incident is fixed. The branch gateway still reports an older installed policy. The operator also searches for test logs on a Log Server that no longer receives that gateway’s events after a recent migration. Management trust is healthy, but a colleague suggests resetting SIC because the application remains unavailable. The team can review task details, actual logging destinations, and the gateway’s policy status before making further changes.
1. What should policy-delivery troubleshooting establish?
Read the worked answer
Separate the published management change from target installation. Check the selected package and branch target, inspect that task’s exact failure, and verify the gateway’s installed policy. Success on the other gateway and a management screenshot do not prove branch enforcement.
2. How should missing logs and the proposed reset be handled?
Read the worked answer
Reconcile the actual logging destination, receipt, timestamps and query filters for the test. Healthy trust and a target installation failure do not justify an unsupported SIC reset. After the targeted correction, retest the application and log visibility independently.