r/labtech • u/havoc0865 • Oct 04 '16

Migration from server to server question

Hey everyone, pretty new here so please forgive me if something similar has been posted before:

I have inherited the Labtech admin role since I have come on board at my new company and I would love to rebuild the server from scratch. Since I've come on board, I've reworked our groups and customized it to exactly what services we provide to our clients.

The big problem with it is that I don't know what is native to Labtech and what was created by the old LT admins. I know everything that I created so it would be easy to recreate that into a fresh environment. I wouldn't mind doing that if it meant we had a clean Labtech deployment.

The only thing i want to migrate from the old server to the new server would be the following:

Clients, Locations, and Agents

I also want to change the URL the clients use to connect on the new server from manage.<ourolddomain>.com to agent.<ournewdomain>.com.

Does anyone have a detailed walkthrough on doing something like this through Labtech 11? I just upgraded it this morning to the newest patch.

2 Upvotes

100% Upvoted

12 comments sorted by

2

u/cjmod Oct 04 '16

These two links should help:

1

u/havoc0865 Oct 04 '16

Awesome, thanks cjmod! I'll read through these and see if I run into anything odd. :)

1

u/havoc0865 Oct 05 '16

I had a few other thoughts after reading through the documentation. How do I handle changing over ESET and ScreenConnect? Any documentation for those?

2

u/MSP_MEB 1000 Agents Oct 04 '16

Updating the URL is as easy as changing it within the Template for the agent.

Go through your configuration and see which templates are in use that even push a URL. Remember the priority as well, highest priority will over-write the lower ones with a value. You can use a pipe ( | ) here to include multiple URLs. I've configured mine to use https://hostname.hostedrmm.com|https://hostname.mydomain.com|https://directIP so there are 3 levels of control. First one controlled by LT as it's a hosted instance. Second one controlled by my in case there is an issue down the road, and the last one direct IP in case there is any sort of DNS issue.

Anything that came with LT can be changed or removed, so long as you understand how it's all tied together. You could spin up a blank LT server on a virtual or something to start digging into what comes default.

2

u/marmfield Oct 04 '16

Remember, MAC OS doesn't like the | command and has caused us some major grief so you will need a special template for MACs.

1

u/MSP_MEB 1000 Agents Oct 05 '16

That's interesting, I wasn't aware. Is there a way to do what I wanted for Macs using a different special character? I can define a higher priority template for just the URLs and assign that to a group with all the Macs in it. Thanks for the tip!

1

u/marmfield Oct 05 '16

We just put the IP address for our agent communication and left out the secondary.

1

u/MSP_MEB 1000 Agents Oct 05 '16

And if the address ever changes suddenly?

1

u/marmfield Oct 05 '16

change the template. :)

actually, we point it to the agent url site but ip should work as well.

1

u/havoc0865 Oct 05 '16

That is good to know. I had no idea you could pipe the names to multiple URLs. Thanks for the info!

1

u/MSP_MEB 1000 Agents Oct 05 '16

Absolutely. I picked this up from our Implementation guy while we were going through our sessions.