They log to themselves centrally, and they log to the standard locations on the clients, so you can pull the logs in from there using your standard centralized

They log to themselves centrally, and they log to the standard locations on the clients, so you can pull the logs in from there using your standard centralized logging setup. Conflicting address ranges for subnets isn't especially surprising to me. Making sure your corpnet isn't on 192.168/16 probably is the most helpful thing to do there.