Securely Running Teamspeak 3 Server 2018 as a Service on Windows 2012 Server or later

[d4rk0n3]

Hi,

I was recently forced to upgrade and i ran into problems running the new teamspeak server as a service using the old tricks that have previously worked so i figured out a new solution i though i could share for others with this problem.

I personally have a windows 2012 server but this probably works for previous versions of windows as well.

Download: https://coreserver.net/stuff/Teamspe...ervice2018.zip and extract the content directly into your teamspeak 3 server folder.

Simply edit the included xml configuration (teamspeak3service.xml) file to suit your needs.

After you have finished editing the configuration file you simply open CMD with admin rights, go to the root directory of your teamspeak 3 server setup

example cd c:/Teamspeak3Server

Then run command

teamspeak3service.exe install

Service will now be installed as "Teamspeak3" in your service.mgr, if all went good your service won't have a problem starting.

Remember to always use a service account without administrative privileges, and when you do make sure you set the rights for the service account to have privileges on the teamspeak3 server folder otherwise the service cannot run as it lacks permission to access the files.

Now you can run your new Teamspeak 3 server 2018 securely as a service on windows without having to give administrative rights to the account running the server and avoid the security risks that comes with doing that.

[dglandorf]

The link doesn't work

Anyone have a solution to run as a service?

[Shivex]

Hi Guys, I am running into the issue that TS3server is shutdown when logging of.

Since this DL link is dead I run into the issue that the service account has to be logged in all the time. Weirdly, when having the task scheduler start ts3 automatically when not logged in, clients are not able to connect but I could confirm the server running in task manager (not in notification area) when started through the Task scheduler.

The other solution on the forum was the one which says "[Not Supported] Guide easy TS3 Server as Service in 3 clicks"
That kinda puts me off.

Basically everything else is too old to consider chasing (right?).

I run a Windows Server 2016 VPS. Why not Linux? Well, Windows is just easier to grasp for my less tech savvy buddy who is paying for the VPS. I thought about pressing reset and get some Linux distro but we are stuck in a year contract

BTW, if for some reason I need to delete Teamspeak and for example start over from CMD or something that would be no issue. I would however like a quick pointer in the right direction when or if that's the case. Not being able to logoff an account when leaving the server annoys the hell out of me.

[.Fake.]

There are several ways to run TeamSpeak in the background.

Use the Windows task scheduler for example to create a task which
doesn't require any user to be logged in. [cmd: taskschd]

the issue that TS3server is shutdown when logging of

A even more easier solution is to not log off.
Use "Lock computer" instead of logging off from your user account.

[Shivex]

There are several ways to run TeamSpeak in the background.

Use the Windows task scheduler for example to create a task which
doesn't require any user to be logged in. [cmd: taskschd]

As I said, this does not work correctly. I want this to work though, have not yet found a reason why this happens or solution.

A even more easier solution is to not log off.
Use "Lock computer" instead of logging off from your user account.

This is what I have right now. We are talking about an actual server here, not my regular desktop. Staying logged is not 'best practice' and just plain annoys me. I might use it as a Terminal server in the future as well with multiple users.

[Air SeaTac]

I set up Teamspeak server and other software as services using Microsoft's own tools years ago. Can't remember how I did it but try this link

https://stackoverflow.com/questions/...ws-2012-server