Standardising layouts have three advantages:


You can reuse slides across presentation without changing the styling.  
When you create presentations, you don't need to think about styling; the templates are already set up for you.
Creating templates and styling can be delegated to someone with design skills, and everyone else gets to use them.


The first two points are applicable whether you have your own signature style, or you follow a team or corporate style.

The last point is different. In theory, having a corporate style is a really good idea because everyone gets the benefit of using templates created by the design genius in the marketing department.  In practice, corporate templates are almost universally awful.

So, if a corporate template exists, and you are lucky enough to like it, then use that.  There's no point in reinventing the wheel.

If there is no template, or it is dreadful, then create one for yourself and stick to that.  

Either way, you don't want to have to keep deciding on new fonts to use for every presentation that you make.

Is there added value in having your own presentation layout and using it consistently?
I have an ASA5520 that is set up to send logs to a splunk syslog server.  the setup works for a while, usually around 24 hours or so, but then stops until either the logging is reconfigured (twiddling the ports) or the ASA is restarted.

what should i be looking at to resolve this issue?  im not sure if its the splunk syslog daemon ignoring connections or the ASA that gets messed up and stops sending.

id like to enable the 'dont pass traffic without logging working' option, but without a stable connection to syslog, thats a non starter.

tried so far:
TCP and UDP, different ports, changing the logging level
