Rebooting of SQL Server causes "sequencing issues"

We have an app that has "application numbers"
every time we reboot the sql server, the next submitted application breaks the previous sequence by 1000.

the support people have identified the problem as an identity column issue and say that sql server is acting the way it should.
they say that identity columns reserve a pool of 1000  numbers and when it reboots, it jumps the sequencing by a thousand.
I reboot this server monthly and this is causing a problem.
Their recommended fix sounds to cumbersome to me which was running about 7 scripts to reset the pool identity everytime the sql restarts.

They also pointed out this article that sounds pretty reasonable but I would like someone to confirm the logic in the article posted before I try either one of the suggested solutions.
http://www.dfarber.com/computer-consulting-blog/2014/2/13/how-to-solve-identity-problem-in-sql-2012.aspx

can someone verify?
Does anyone else have a better solution?