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.
Therefore this site is blank.