5 ms·
OK they messed it up, again? Anyone with a laptop preloaded with the crippled Home edition (meaning most laptops) will not be able to take it to the work place
by jeswin 11y ago
OK they messed it up, again? Anyone with a laptop preloaded with the crippled Home edition (meaning most laptops) will not be able to take it to the work place and connect it to the domain. Then there's Pro and Enterprise, and most people don't know why they need Enterprise.
- wvenable 11y agoYou just pay for the upgrade to Pro which you can do from within the OS.
- cp9 11y agowhy would you take your home computer and connect it to the workplace?
- mkr-hn 11y ago"why would you take your home computer and connect it to the workplace?" - Blackberry
- jeswin 11y agoYou should Google up and see how common this problem really is. My example, I am a consultant. But I do have domain accounts in companies I consult. The OS that came with the machine (windows 7 home) had to be written over since it won't let me log in. The point being, it's such an artificial restriction. Most PCs are laptops, and this really restricts mobility.
- scott_karana 11y agoFor clarity, are you talking about joining your laptop to the domain, or merely logging into domain accounts using a non-domain-joined laptop?
- keithpeter 11y agoA remote desktop session into the my employer's network from guest wifi works fine within their building. My laptop running the rdp client is faster than the thin client they issued me with!
- ZoFreX 11y agoI think a consultant using their machine for work purposes can fork out for Windows Pro instead of using Home edition...
- 0xffff2 11y agoAnd where do you work that this is even allowed? Maybe it's only because I work for the Federal government, but there is not a snowball's chance in hell that I would be allowed to attach my personal machine to the non-guest network in any way.
- adamkochanowicz 11y agoI do this all the time.
- jameshart 11y agoBYOD (bring your own device) is the big noise in corporate IT, has been for a while. Now, it started with iPhones and macs and iPads, but if your staff have, for example, a Surface Pro 3 they like to use, you want some way for them to be able to use it in the corporate network environment, right? Now, I'd question whether the right way to handle that is to join it to the Windows domain (I'd question whether having a Windows domain is the right way to handle ANYTHING in fact), but it's definitely a part of the corporate IT landscape nowadays, and MS should have some sort of a story for how you can do it.
- worklogin 11y agoThis is against so many IT security best practices, you're probably breaking a regulation if you're in an industry not dealing with selling jewelry on Etsy.
- fragmede 11y agoWhile you're right, BYOD has been an on-going headache in IT for several years now. It's one thing to say unapproved devices are completely not allowed, but reality is when the CEO brings in their shiny new iPad and demands it get on the office wifi, the iPad gets onto the network (however heavily segmented and firewalled).
- worklogin 11y agoBYOD for mobile isn't entirely new, but most people doing that have MDM software that MITM's secure connections (potentially) and keeps all office-related software in a sandbox. Attaching a desktop to an office network rarely has those same mechanisms.
- bpye 11y agoSome devices include Windows 8.1 Pro, see for example the Surface Pro 3.