I have Designer for macOS and also want to purchase Publisher - i will soon have to use them on Windows, though, and so i am not sure, what to do - doesn't make sense if i purchase it now for the mac and having to purchase it again in a few month for Windows. Especially as i am Hobbyist and don't use it for commercial purpose.
It doesn't help to always only cite the FAQs - it can always happen, that they change licensing details ... so asking questions about must be allowed, especially when others spread untruth eg. at reddit. I also don't understand Serif in regards to this - as much as i love their software - what's the problem in asking about licensing details?
It sounds like so "... First and foremost, these are definitive, and you should not post questions about these ..." - but maybe it's a misunderstanding from my side. Btw. Licencing details should be more prominent on the main website - i've had a hard time finding them when looking at the product pages. Anyway, it is as it is - i'll probably wait until blackfriday-deals or so to purchase a windows license for designer and probably will wait to also purchase a publisher license for windows ... i didn't want to sound harsh, or so i just wondered if anything changed after reading the reddit thread and it could always be, that they changed it and forgot to update the FAQs.
Just to give you the background, I run an MSP and we mostly deal with cloud apps and support. But if I were to sell 25 computers to a customer, and I wanted to build the computers myself, would it be possible to:
My main concern is about step 3. Can those other computers be activated with their own OEM license keys, or is it an issue as all the imaged computers would have the same product ID but being activated at different times using different keys?
Basically each machine has to be activated with its unique OEM key. (Other option is to use Volume Licensing but that has to be purchased by your customer - you only need one VL license but you still need to sell them an OEM license of Pro for each machine)
@Da_Schmoo, So I was planning on using Sysprep so the end user would accept the eula. They would also be provided with an unused OEM product key to input at that time. But is it ok that all these users would be activating an image made from the same OEM copy of Windows, in other words they would all have the same product id? And is there a limit to the number of the times the same product it can be activated, or do I have it wrong? Also thank you I will look up those system builder guidelines, why do they make everything so difficult to find and navigate!
You can simplify matters here by using a Volume License key but as mentioned before, your customer has to purchase it. Once they are have that license you can use the same key on all of their builds but you still need to sell and affix the OEM sticker to the chassis. (This is what I do for the machines I build for my customers.)
Get step-by-step guidance for OEMs to deploy Windows 10 to desktop computers, laptops, and 2-in-1s. Find information about how to enable imageless, push-button reset recovery and more. (oem-deployment-of-windows-10-for-desktop-editions)
In short, if you want to be able to deploy OEM licenses in an efficient manner, you likely need to be a device partner (second link) and follow the directions in the first link for preparing to build, building, and distributing the machines.
On a related note, when I go to the link posted by MultiverseIT, it says that you first have to download all the tools required from which includes the ADK etc. However when I go to that URL, it asks me to sign in with my Microsoft account. I tried signing in with my Microsoft account which is associated with my Microsoft Partner number, but it takes me to a page that says access denied, and that page talks about some kind of invitation.
I also bought the mac version but the display on my mac is to small to fit the view I like so I have installed on my touch screen HP Pc that I had to upgrade to windows 10 (was free). Now I have a huge touch screen but yes sucks I had to buy another copy. Also liked djpro so much looking at upgrading my Dj controller to an actual one built for DJ Pro and guess what they come with the software so had to buy it again. How many times do you need to buy the same software?
I am looking at purchasing a used Z440 workstation from ebay and I would like to make sure that I recieve a valid Windows 10 OEM License. If I understand correctly the windows 10 OEM license is paired to the hardware and it cannot be transfered or deactivated. So assuming the computer I purchase came origionally configured with windows 10 and the origional motherboard has not been replaced I should be able to do a fresh W10 install and automatically activate the OEM lisence. Is this a correct assumption? I ask because sellers sometimes write misleading statements such as "windows 10 key included" or "No OS COA" which dont apply to windows 10 systems if I understand correctly.
... Is this a correct assumption? I ask because sellers sometimes write misleading statements such as "windows 10 key included" or "No OS COA" which dont apply to windows 10 systems if I understand correctly.
From my understanding that is correct given Windows 10 was pre-inalled OR old owner installed or upgraded the machine legally. Legally installed or upgraded to Windows 10, the key will be embedded in BIOS of the motherboard.
1. If the computer was originally factory-loaded with Windows 7, there will not be a product-key embedded in the motherboard. However, if the computer was upgraded to Windows 10, and Windows 10 was successfully "activated", then a "digital entitlement" has been granted, to allow a re-install of the "retail" version of Windows 10, at any time, at no cost, onto the "same" computer. Changing the disk-drive does not seem to violate that "same" requirement. Presumably, the seller has not changed/removed any other hardware components since activating (or has re-activated with the changed hardware).
2. If the computer was originally factory-loaded with Windows 8 or Windows 10, there will be a product-key embedded in the motherboard. Then, using the HP-modified OEM version of the original operating system will use that product-key to successfully activate. Hopefully, that software can be downloaded or purchased from HP, or purchased from www.ComputerSurgeons.com or from www.RestoreDisks.com (although this latter web-site seems to currently be offline).
Updating to Windows 10 creates a digital license which is stored on Microsoft W 10 servers. It (W 10) does not create a digital license on the local PC. Any digital license on the local PC relates to the HP factory installed operating system.
I don't know if this is still happening but I have updated to W 10 using W 7 and W 8.x product keys as recently as February of this year. I have not done this lately. Microsoft may have shut down this option.
You will have to install the HP factory operating system, FREE, using the Heidoc link provided above if you buy the PC with no operating system to get the possible update to W 10. Download the OEM version to match the HP BIOS imbedded product key.
Maybe the seller has updated to W 10. This means you will have the digital license to use W 10 Pro. You can then, under this circumstance, do a clean install of W 10 and get activation without any problems and will not have to install the HP supported operating systems (W 7 or W 8.1).
When I look in the HP quickspecs for the Z440 I do see Windows 10 Pro listed as a OS configuration so I am confident it was posssible to order a Z440 with a W10 oem lisence. As far as upgrades go I have read that after the W10 anniversary update microsoft made it possible to pair your windows 10 license with your microsoft account. This even allows you to transfer a retail license to new hardware at least one time which makes it all much less straight foreward. My current understanding is as follows:
BUT if the user purchased W10 retail and performed a clean install not an upgrade that hardware would be given a retail license of W10 and it would be possible to transfer to new hardware using a micosoft account. In this scenario it seems possible that the previous owner could transfer the license to another computer after the sale which I presume would deactivate the license on the old hardware.
But you may stll be able to run W10 using the possible upgrade option in my previous post by using the HP factory W7 or W8.1 OEM operating system product keys. This article by Ed Bott was referenced to successfuly upgrade to W10 using W7 Home and W8.1 Pro unused OEM product keys. It may not work anymore.
For example, in early 2018 I upgraded a recently built system using an unused W7 Home premium product key to W10 Home. I then realized I had an unused copy of W8.1 Pro. So I used this W8.x product key to upgrade the system to W10 Pro. The upgrade was done using "Settings", Update and Security, Activation, Change product key.
As I have said, you still have possible operating system upgrade options using HP OEM Windows and possible upgrade rights to W10 using the HP W7 or W8.1 OEM product keys. Microsoft may have now disabled this specific upgrade process.
d3342ee215