Most of the software we tried tended to fit into two categories: too many fields which made basic tasks like entering a ticket too slow, or a high cost per month. In the midst of that, our management was asking for more accurate asset inventory across the company and we decided to take the opportunity to evaluate other ticket and asset software. So a migration was in our future either way. Spiceworks has decided to stop the development of its on-premises software and move to the cloud. We'd been using Spiceworks for our help desk tickets and asset management for several years. I enjoy using automation scripts, mostly PowerShell, whenever I can. My main responsibilities are higher-level troubleshooting, managing the network and servers, and evaluating new systems, like Lansweeper, then implementing, documenting, and training others how to use them. I'm a System Administrator at a company I've been with for 12 years now. Hi Ethan, tell us a bit more about yourself? We reached out to ask him a couple of questions on is work. We are very grateful that Ethan is willing to share his work with the community. After a first version to migrate Spiceworks tickets using ODBC, Excel, and manual labor he has now cooked up a fully automated version! The blog article features a step-by-step tutorial so you can easily follow along, but do keep in mind that this is not an official Lansweeper procedure. We received notice of an interesting blog post by Ethan the Kiwi on how to use a Powershell Script to automatically migrate Spiceworks Tickets to the Lansweeper helpdesk.
0 kommentar(er)
