I have many databases restored from various other database servers on a shiny new server. I want to unify the log file size limits and allocation percentages. However, I'd like to not do this by hand so we can conform things as time passes.
You don't want to set size limits on the transaction log files. If you do and a log file fills the users won't be able to use the application any more until to resolve the issue. Set all the transaction logs to grow to what ever size that they need, and don't shrink them unless a rogue transaction comes through and grows the log larger than is normally needed.
If space becomes an issue, buy more drive space.
You want to read up on this more before sizing your TLogs. Check out Kim and Paul's articles on SQLSkills.com.
You're almost always better off with a growth size that isn't a percentage. And unless you have a dedicated drive for the only important Tlog in your system a limit may save you from a wider outage. More importantly, after killing a rogue process having a bit more TLog space to allow may let you get the rollback started or an emergency TLog backup completed without out having to go down to do it.