Again, a simple problem is fixed by just checking the Event Viewer. There are two servers on different subnets connected via VPN. Replication has not happened for a while simply because it was not a pressing issue. I vaguely remembered that I had this problem with AD replication so I went into Event Viewer of both sides and checked the Application and Services Logs > DFS Replication events. Clear as day you can see Event ID 2213 that reports that the database was “not shut down cleanly” and Auto Recovery is disabled (I should check into that later). But the important part is that it shows how to fix the issue. I have highlighted it in the screen snip below.
Almost immediately after running the command I can see that replication is occurring in the background trying to catch up with the changes.
Unfortunately the first problem has occurred in my usage of the Pebble smartwatch family. My Kickstarter Edition Pebble Time has stopped working when it got wet from minimal submergence in water. I’m talking about 1-2 feet maximum. I looked closer and found the bezel came unstuck from its adhesive. I have emailed Pebble support and hope for the best. We shall see how much loyalty says for Pebble.
After much work (see previous post), I now have a fully functional ticketing system utilizing osTicket. I have used this system in years past and was very happy with its features and pricing (free). It is being actively developed and is not ad-supported.
I just wasted about an hour because Google failed. I just extracted the contents of osTicket to the desired folder and attempted to browse to the setup folder. It generated an HTTP 500 error and I could not figure out why.
“osTicket does not support PHP7 at this time. It will once 1.10 is released.”
Make sure you use the PHP Manager for IIS to change the PHP version being used to version 5 on the site you are using. Restart IIS services after doing this.
First of all, don’t let me agree to perform a screen replacement again, except on an Apple iPhone 4 or 4S. Second, if I do agree to it, make sure the glass, if glued to the screen, is not in a hundred pieces. Third of all, I hate Samsung. So much I hate this company.
Every year the same thing happens. Most (if not all) smartphone manufacturers announce new models, just like new automobile manufacturers. The technology sites are accustomed to it, and there are very few exceptions. Google has I/O, Apple has WDC, Samsung has Developer Conference, and ASUS has Computex. Each and every year we get a new phone model lineup from all the big players.
Which brings me to my issue. Every year the models get more and more confusing. This first came to light when HTC released the “One”. How do you top that name? “HTC One 2”? “HTC One Next”? Ultimately we received the worst model name in my opinion: “HTC The New One”.
Maybe people just don’t care as much as I do, but I envision a world where smartphone models mimic automobile models. Every year we get a new revision, and whether or not the manufacturer decides to make an entirely new model, the consumer can pretty much assume the 2016 model is generally better than the 2015 model, but still be the same form factor, similar (or same) size, and same price point.
Moto X (2nd generation)
Moto X Play
2013 Moto X
2014 Moto X
2015 Moto X
Without having any technology knowledge, if you were shopping for a phone whether new or used, just by looking at the model you would know how old (or new) the phone is. In technology, this matters greatly. Consumers cannot be bothered to know the age of the smartphone just by the model name (can you imaging the Samsung Galaxy S12)?
First post from WordPress for Android!
Speaking of Android, can you believe how many different flavors of Android are in the wild right now? I’m glad I didn’t take that developer job offer!
Last night I decided to tackle the task of enabling the SonicWALL CFS service on my new TZ 500 NFR model. I had done this with my NSA 240 years ago (circa 2009) and was very impressed with the end results. Now with another 365 days of free CFS service, better use it, right?
Not using any KB articles, I was able to complete the whole thing without much difficulty. The TZ 500 paired with LDAP (unsecured) using a non-admin service account and I installed the SonicWALL SSO Agent program on the DC and configured to run as a service. I tested the functionality pretty thoroughly and wherever I logged in as my account, the SonicWALL figured it out and adjusted the CFS automatically and perfectly.
The only issue is that I could not figure out how to manually log in as a user to authenticate via AD (and get special CFS policy) on non-Windows (or domain joined) devices such as guest systems and handheld devices. Hopefully I will post about that soon.
Unceremoniously, I have decided that for all those times I have figured something out, or learned something new, or found something deep in Google, I will remember it here!
Too frequently is something forgotten without documentation. That ends today on June 2, 2016.
…or at least I hope.