u/Large-Special-4530

I recently switched my plex server from Windows to unRaid. All I cared about retaining was watch history. I don't have outside users so I didn't try to bring app data over. The initial library scan was taking forever and I wanted to create my parity so I stopped the container to allow full CPU and disk use for parity building. Everything was fine afterwards and plex worked normally. However after a week or two I noticed that every episode or movie I watched the option to skip intros and credits was missing. I tried getting plex to do manual scans, analyze etc.. I started using CLI commands to get it to analyze, but it would not get all the files. I would go into the XML and the voice detection markers were missing, along with intros and credits. Anyway your experience may vary but eventually I just went into appdata and deleted the DB folder and then readded the library and let it go for 2 days until it was finished and all is well now.

I do IT support for a Treasurers office in county government. We have to get rid of QB pro 2019 because it is no longer supported and the main IT for county/city doesn't want to host QB server anymore and wants us to move to the cloud. A few years ago, the accounting team had me work on importing files into QuickBooks. I don't remember the limitation of QB 2019 or the reason, but we had to get a 3rd party import product, Transaction Pro, which has worked great. Essentially we just import bank transactions and use QB for reconciliation. Does QBO have a pretty robust importing process that may eliminate the need for us to move to the Transaction Pro QBO product? I believe the newer version of Transaction Pro requires a subscription whereas the old importer was a perpetual license.

I’ll start by saying this is my first step into using a non-consumer router. I recently purchased an ER707-M2; previously, I was used to a standard router (or my own DNS server) handling local DNS automatically, where "things just worked."

After setting up the ER707-M2 at home and adding an IoT VLAN, I noticed I couldn't reach devices by their hostnames. I went into the VLAN configuration, set home.lan as the domain, and added the entries to LAN DNS. Everything worked perfectly.

I then read that the current standard for private networks is to use the .home.arpa domain. Making this switch led to an hour of frustration. I discovered that while I can change my domain to home.bob, .jim, or .pizza it works fine, home.arpa fails completely. I simply cannot ping or connect to my devices via their FQDN when using that specific suffix.