After checking that, run the installer with the default options. I always check files from less familiar sites by uploading them to Virus Total. Go to and download the current version 64bit, sqliteodbc_w64.exe.
Install spiceworks agent install#
Next we need to install a driver so that Windows can talk to SQLite. Unzip the file and rename it to remove the square brackets “” from the file name. For me that address was \\spiceworks\c$\Program Files (x86)\Spiceworks\Backup Copy that file from the server to a folder on your computer using either Remote Desktop copy paste or a UNC path in file explorer which seems to be a bit faster. If it looks odd or the file size is 0 or growing, Spiceworks may not be finished backing up yet. Note that once you do this export, any new tickets or updates that come into Spiceworks will not be imported into LanSweeper. It may take several minutes for the backup to complete. Click Backup Now and note the Backup Location folder. Go to Settings > Global Settings > Backup Configuration. We could access the production database that Spiceworks uses, but to be a bit safer, we’re going to make a copy instead. It may be possible to run the Help Desk Export from the cloud version, install the on premises version of Spiceworks, import the JSON file, then follow this tutorial from there. Note: In this tutorial we are dealing with the on premises version of Spiceworks not the cloud version.
Install spiceworks agent how to#
If you want to do this faster, read my newer article on How to Migrate from Spiceworks to Lansweeper using a Script. This article describes how to manually migrate tickets using ODBC and Excel. I briefly tried to convert the file, but gave up when I found a better way to get at the data by accessing Spicework’s SQLite database. There is a Help Desk Import/Export page in settings, but this exports tickets in JSON and LanSweeper imports via CSV. If you want to migrate from Spiceworks to Lansweeper, the first thing we need to do is get the tickets out of Spiceworks.
0 kommentar(er)
