The remark about 'Enterprise Android' was an attempt at sarcasm. Google is a marketing machine and access to anonymous and /or personal info is easy for them to get if you're not aware of it. Enterprise Android would make Google a part of the enterprise using it, hypothetically. With Win10 emulating Google as a miner of user oriented data, I took a leap of logic and wondered if Win Server, by comparison, might start resembling Google Android in some ways. Thus my concern about companies now having to expend time and money just to keep MS out of their business where it wasn't specifically invited. BTW, Win10 Pro can join a domain and a lot of companies don't use Enterprise level releases. It's also more likely that Win10 Enterprise will have additional features such as DirectAcccess or BranchCache, rather than edited features.
MS office is a cash cow. But more so, MS Server and the total crapware called Sharepoint. Gawd Sharepoint is awful.
That's ok... sarcasm noted, but at the same time, folks are wondering about this, and there are those in the android ecosystem that would like to break into the enterprise market - lockin is a strong incentive, and the path to good recurring revenue - to whit - Blackberry...
Android is - as it's closely related to Linux - folks do watch what's happening there...
But Android isn't Linux, and there are those in the Linux community that totally reject Android - what's funny is that many of those that I've talked to have an iFondleSlab in their pocket, or writing code on a shiny aluminum laptop forged in the spirit of Steve Jobs...
Oh well...
FWIW - Over the last couple of year, and more importantly, in the last 12 months - I can appreciate that MSFT has refocused on what is important - and we're seeing some great software and services as a result - and Win10/Windows in general is not my primary platform...
Don't get me wrong, I generally like my kid's Asus android 7" tablets. Especially as a budget device they are very good. As a high end device, not so much. I mostly like Android OS how it is setup, for a touch device. However, the fact that bug fixes and critical security flaws are going to continue to be back burnered until something radical changes in the Android paradigm, never for a phone for me.
Your best bet, if you can, is to get an unlocked bootloader phone and load an alt Android on it that probably will be much better supported by the developers. That covers maybe .5% of all Android users.
That's the root of the problem: Microsoft introduced a fairly scary setting, and even their FAQ doesn't do a very good job at explaining how it works (and that's assuming someone even knows about its existence).
A lot of people will blindly connect to their home network and fail to notice the sharing checkbox that is new on the passkey UI, and is unfortunately checked by default. This is a feature that should be opt-in, not opt-out.
As a consultant, how do / will you reply to business managers who wonder if their employees who use Win10 will impact corporate information / security / trade secrets just by not being computer experts? What will be your informed reply to a question you will certainly be asked many times?
My stance over the past many years is to not ever let employees access a business network with anything other than a paid for and internally supported device and OS that has been tested and setup by a trusted process.
When I am suspicious of a new setting, I do not consult the manufacturer (MS in this case), as I assume they will lie.
I can't speak to anyone else's customers, but my customers just wouldn't stand for that approach. They're trying to recruit Fortune 100 talent and Fortune 100 talent has a certain level of expectation about the work environment. You can't ban BYOD and disable dozens of features on their devices and expect them to be happy - they'll just go work for your competitor across the street.
In what other industry would you hear someone say this and still buy the product? I certainly can't think of any.
At least with enterprise, one thing to keep in mind, unless I have completely missed something, the wifisense thing does NOT work with WPA2 enterprise. IE if you are using RADIUS, wifisense isn't going to work.
The company that assumed Win 8 charms, no start menu, and more need to be shoved down user's throats will never show even simple sensitivity towards this issue. Lots of windows evangelists who have livelihoods that depend on MS good graces will patronize those with concerns. Complaints such as mine are pi**ing in the wind, but these things need to be said. I do not expect MS to lighten up even a little. They have no need. It's Win10, eventually, or don't use your computer. By then, easy privacy apps will be common. Classic Shell for Win 8 is a parallel.
Thread starter | Title | Forum | Replies | Date |
---|---|---|---|---|
J | Windows HP laptop takes a long time to connect to Wi-Fi | General Wi-Fi Discussion | 14 |
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!