@Dashrender said in Pre-Planning new domain and environment:

It's the whole ZT/DNS

@Dashrender said in Pre-Planning new domain and environment:

and when I tested ZT in the past,

It is just DNS. You have to have it on EVERYTHING if you go that route.

Or, you make the ZT network the same subnet and not different.

Just take your 10.0.0.0/24 and make it a 10.0.0.0/23 instead.
have the local DHCP server hand out 10.0.0.101-254
have ZT DHCP hand out 10.0.1.101-254

or use ZT Bridging
Lots of ways to skin the cat.

@wrx7m happy to help!

@phlipelder said in Website hosting: Which direction to go:

I'm in the process of figuring out how to set up Wiki.js on Ubuntu running in Azure with a MongoDB backend and Apache fronting for SSL.

MongoDB will be phased out in Wiki.js 2.0.0
https://github.com/Requarks/wiki
0_1532199283945_03dba03f-a33e-4ce2-a8a5-d95a0c45e1b3-image.png

Sorry, he posted that for me and no I did not see that. I think that is a good answer on what to do and will go forward from there. Thanks.

@JasGot said in Exchange 2010 (On-prem) Migration to Hosted Exchange/Office 365 Planning:

@wrx7m How did your migration go? Have you done any more? Just curious what tools (if any) you used......

I'm about to start a migration and need to decide if I am going to do it as a pst import, or a migration from on premise exchange to cloud, and if so, do I use the built-in migration tool at admin.exchange.microsoft.com or a third party tool.

I am interested in what you did and what the pros and cons were.

Thanks!

Ended up doing a migration using the standard MS tools. Been a few years now and am glad I did it.

Data prisoning is a big deal. You need companies with clear paths to data migration. Something very important to ask when getting into a situation where a vendor holds your critical data.

@FiyaFly said:

Well, they send the notification as though they are getting a channel unavailable response from the PBX. I'm looking to call them tomorrow but wanted to see if anyone had seen this before. I do not think it is the PBX either.

Everything about this screams "hiccup in Vitelity" but of course, they'll pass it off as a PBX problem unless you can prove definitively otherwise.