Windows XP Home Edition SP2 NL Lite Serial Key
Arnau Cyr
Due to the nature of this organisation, typically BYOD (personal devices) can be limited to browser-only access to SharePoint / OneDrive online through Azure Conditional Access Session Control; however there is an emerging use case for offline access on BYOD (the org already has a precedent of soft-managing BYO devices, so this part isn't a problem), but a requirement to ensure the files are kept securely.
This is where I feel WIP would provide suitable gap-filling capabilities; but there's quite a significant pre-requisite: It requires Windows 10 1607 Pro edition (or higher). The 1607 part of that isn't a big problem, as Intune can cater for version limits within enrolment policies, but there's no Edition filters/requirements.
This means we can set up WIP and MAM, and have all the nice secure controls applied to any BYO devices running Win 10 Pro, however as soon as someone enrols a Win 10 Home device, it simply ignores all of that and allows free-reign over non-encrypted files.
I'm trying to come up with workarounds to this gap, things like attempting to apply a BitLocker compliance policy specifically to Home edition devices, which of course will fail and mark the device as non-compliant (which can subsequently be filtered in Azure Conditional Access), but this isn't an elegant solution.
WIP is appealing for BYO scenarios since it only applies to corporate data / apps, rather than wholesale applying overbearing policies to every part of the device, specifically causing constraints in the context of encryption (requirement for MS accounts; requirement for InstantGo hardware certification etc).
It appears the trade-off of not implementing the overbearing policies is an incomplete picture, if those on a Home edition can simply bypass the policies - and there's no way to conditionally stop them.
Despite there being an "operatingSystemEdition" field within the hardwareInformation properties of managedDevices in Graph, Intune isn't filling this in, so we can't even create dynamic groups based on OS edition.
Where did you find that WIP only supports Windows 10 Pro and higher? For as I know is that WIP also Home Edition supports. With WIP you can manage your corporate data on Home edition. This only with MAM without enrollment. MDM is another story, but WIP and MAM without Enrollment on a Home edition is supported and works the same as a Windows 10 Pro edition.
That is strange. So, the same policy works on Pro but not on a Home edition device? With the same user account? I have here a Home edition test virtual machine. Windows 10 1803 is on this machine installed. If I enable the MAM without enrollment for Windows 10 then WIP will activated on the Home Edition machine. I have allowed IE, Edge, Word, Outlook, Onedrive and OneNote. I have also included these network perimeters: -my.sharepoint.com.sharepoint.comoutlook.office365.com.
The basic polices I setup are pretty much the same as yours. But something is stopping Home from honoring MAM+WIP policies. Or it's plain broken. And nope - no MDM in sight anywhere. And even if there were, that Home just lets me extract work files unencrypted is unacceptable. Under ANY circumstances.
We use Microsoft 365 Business. The WIP policies it comes with include some protected apps by default, among which is the OneDrive STORE app, but not the desktop next-gen sync client. I have no idea why M365B doesn't include ODfB Sync by default, but it mislead me. Again. Because already solved this problem a few months ago. :rolling_on_the_floor_laughing:
And SECOND: The W10 Pro VM I used to test above ^^ is actually AAD-joined - which I didn't know. A colleague of mine was using it for other purposes and joined it. So it was following a different set of policies: For enrolled devices, right? That policy obviously works just fine, so it naturally showed WIP protection active. I just validated my findings with a new, un-enrolled (AAD registered, not joined) W10 Pro VM and was able to get the same, expected (!) behavior on Pro and Home.
So, all is good, WIP on W10 Home DOES work. Which makes this an awesome and low-cost option for any kind of BYOD / work from home requirement. Sorry to bug you but, sometimes you just need a sounding board to validate what you're doing - or not. ;)
@richochet If you're trying to block access from non-compliant devices (ie. ones not following WIP policies), you can use Conditional Access. CA will deny access to company resources at the cloud level - making it independent of the device used. Whether the device is compliant with your policies is only one criterion - there are many more, too. So for an environment where company-owned Windows Pro isn't the global standard, CA is probably the best approach IMHO. CA is included in M365BP, M365E3 and E5.
The company that I work for continuously hires new people, and I'm the one who has to go and purchase new computers. The majority of them, if not all, come pre-installed with Windows Home editions. I'm noticing that the Windows 7/8 Home editions are unable to connect to domains. I'm having to buy the upgrades to the Pro editions. I'm trying to understand as to why the Home edition of the OS is unable to connect to domains?
Microsoft doesn't allow Home editions of Windows to join domains because they figure that home users won't be connecting to any type of domain. Although that does suck, you do have to purchase the professional version of Windows in order to get that feature.
Don't be fooled by some of these answers, while you can't join a domain there are ways you can connect to a domain for running applications that require it if you have a domain account. You can use the runas /netonly command:
You will be prompted to enter a password and if the username and password provided does indeed match a domain user the given program in pathToFile/file.exe will run as if you where on the domain mydomain.
It's basically market segmentation by Microsoft. They have decided that the Home editions cannot connect to the domain so they can price and support different products in a different way. You will continue to have to upgrade the Home editions unless you can find a vendor, such as CDW (just what my employer uses), that will provide the business versions pre-installed. Many of these vendors will ship next day, but for a price. It's up to you and your employer if you want to go that route.
One option you have is to purchasecomputers that come with a Professional Edition of Windows pre-installed. These do exist, and it's likely cheaper to get your license this way than to pay for the upgrade seperately.
An even better option is to start using volume licensing. If you have 5 or more Windows computers at your business, you qualify for the volume licensing program. This can yield a huge saving over the retail pricing.
My brand new XPS-15 arrives today - obtained at short notice with Windows 10 Home edition installed. I only use Windows 10 Pro edition. What is the most straightforward way for me to upgrade to the Pro edition - ideally retaining a Dell installation image (with all the Dell add-ins, drivers etc). I do not intend activating the Home version.
I'm hoping that the current installation already has the pro features present (but locked) and can only be 'unlocked' by a Pro License Key. That would be great - is that way forward feasible. Please comment on whether a Dell(OEM) license key would be required or a Microsoft Sourced one.
To upgrade from Windows 10 Home if you have a Windows 10 product key:
Select the Start button, then select Settings > Update & security > Activation.
Select Change product key, and then enter the 25-character Windows 10 Pro product key.
Select Next to start the upgrade to Windows 10 Pro
@EddieZe Wow that ! Sorry to hear that... Does not look good for me then, that's exactly what I need to do. But "Tech specialist" (or something like that) here told me that it should work no problem.
Clearly there is a problem here. As others have reported it is NOT as easy as entering a Pro License Key. That fails for me as it has failed for others. Dell should have a documented path from home to pro that works and document that on dell.com. OR they should tell us why an upgrade won't work. I ended up in the Windows 10 Enterprise state after a failed update after entering the lic key. Microsoft said only a clean install using a Windows 10 Pro image off a USB bootable drive would work. It didn't as when you boot from the USB drive it cannot see they main drive for some (possible secure boot related) reason.
Here is what worked for me:
After you try to activate from Win 10 Home to Pro and get the error message, try to install windows updates and than restart your PC, than come back to This COmputer, go to change product key and insert your new win 10 pro product key. The activation was successful for me after this. Hope this helps someone - btw, I have Dell G5 - 5500, brand new with win 10 home.
Have a nice day guys.
Step 8 : Install temporarily a generic license key that allows to upgrade to Pro. This will trigger the upgrade, then reboot the computer several times. This generic key but cannot be activated, so you'll need your own Pro license key to setup immediately after the upgrade. Copy and paste the following instructions in the command line prompt and type enter :
I have set up GCPW on a windows 11 home edition device. Log in and everything works as expected. However no policies seem to be applied to the user. I've checked the enrollment token is there. Device management is enabled. The documentation status stats windows 10 Pro is supported. Does this mean windows 11 home edition wouldn't be supported because it's not Pro?
Below are the system requirements for GCPW from the documentation which states you need Windows Pro editions at a minimum or using one of the other editions stated. You can install GCPW on Windows Home editions but the policies and provisions won't be applied properly amongst other issues that may show up.
7fc3f7cf58