![]() This is because legacy DOS or Windows 95 & 98 programs expect your printer to be connected to a LPT1 port, which is usually not the case anymore nowadays. Have you ever faced the problem where a legacy DOS or Windows 95 & 98 runs perfectly on Windows XP/Vista/7/8, with or without compatibility mode, but refuses to print? How to: Enable printing to USB/Network printers for legacy DOS/Windows 95 & 98 programs 32-bit or 64-bit from: ģ) Unzip the contents to a folder of your choice, for example C:\teamspeak3-server_win64Ĥ) Paste the files you’ve copied earlier from your TeamSpeak 3 Linux server to the folder you used in step 3.ĥ) Start your TeamSpeak 3 Server by running the ts3_server.exe file.Ħ) Done! Your TeamSpeak 3 Server should now be reachable at the new IP address of your Windows machine and all settings should be exactly the same! flash-disk etc, to a temporary directory, for example C:\TS3MigrationĢ) Login to your Windows machine and download the latest available TeamSpeak 3 server version for your platform, i.e. Also note that the default character set for the database is now ‘utf8mb4’, which means the server needs to be at least MySQL 5.5.3 or MariaDB 5.5.ġ) Login to your Linux server, navigate to your TeamSpeak 3 installation folder and copy the files listed above to your new Windows machine using your favorite method, i.e. Here’s a free hint though: Read doc/update_mysql_to_mariadb.txt for instructions on how to update. Which means that if you were using a MySQL database for your TeamSpeak server, you need to migrate it to MariaDB, else your database will be incompatible with the latest TeamSpeak Server version.Īs SQLite is used by default, this is outside the scope of my tutorial and thus I will not be covering this. ![]() This is because as of TeamSpeak Server 3.0.11, the MySQL database plugin has been replaced by a MariaDB plugin. However, this *only* holds if you’re using a SQLite database, which is the case by default. In my introduction above, I mentioned that you can migrate between TeamSpeak versions withouth having to do an in-place update before. All Settings of the server instance and its virtual servers are contained in this file. ![]() Ts3server.sqlitedb – The database, this file is the most important one and contains all the information about virtual servers, users, permissions, channels, groups etc. Be sure to copy the entire folder including any subfolders and files inside. Query_ip_blacklist.txt – Blacklisted IPs for the query interfaceįiles/ – Any Icons, Avatars and files that were uploaded to the server. Query_ip_whitelist.txt – Whitelisted IPs for the query interface Licensekey.dat – Only applicable if you own a TeamSpeak 3 license. Now, let’s get going!įirst, we need to copy the following files from our TeamSpeak 3 Linux server to our new Windows machine: That’s right, there’s no need to do an in-place update before you can migrate…. You can even migrate between versions, i.e. In this particular tutorial, I will be moving TeamSpeak 3.0.10.3 on Ubuntu Server 12.04.5 LTS to TeamSpeak 3.0.11 on Windows Server 2008 R2. The process is no rocket science, so don’t worry. However, since most of them are outdated, for example most guides let you execute SQL queries to replace all the linux directory standards with windows standard which is no longer needed, I felt the need to write this up-to-date tutorial, in which I will explain how to move a Teamspeak 3 server from Linux to Windows. One could say that this process is simply the same, only executed backwards. There are lots of tutorials online that show you how to move, or migrate if you will, your TeamSpeak 3 server from Windows to Linux, but there’s no guide that shows the other way around.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |