That link contains all the documentation you need to accomplish your task. It hasn't changed in years.
I have just one question, with Windows Server 2012 being just 10 days shy of 1 year old, how has this method been the solution unchanged for years?
Furthermore, i too am looking for this solution, and the above linked solution is not it, i am looking to set Teamspeak 3 Server x64 as a startup (without logging in) program so i can let Windows Server 2012 do its thing with updates with no fear of drawn out down times.
I hope this thread gets bumped until a solution presents itself.