Joining 2 Windows 10 Machines
-
@scottalanmiller said in Joining 2 Windows 10 Machines:
Another option.... avoid licensing issues by using a single OS install and making two user profiles instead.
As @IRJ said. . .
@IRJ said in Joining 2 Windows 10 Machines:
@scottalanmiller said in Joining 2 Windows 10 Machines:
Another option.... avoid licensing issues by using a single OS install and making two user profiles instead.
I already said that
And this would likely only work in the case that the Client simply wants to consolidate their hardware and doesn't have a bunch of software that needs to come with it. As I mentioned above.
We need more details from @CCWTech to figure this out.
-
@scottalanmiller said in Joining 2 Windows 10 Machines:
Another option.... avoid licensing issues by using a single OS install and making two user profiles instead.
I cant think of many scenarios where this isnt the answer.
If they had some valid reason why they couldnt just install the tools the need on one installation, then I think virtualization is the only try solution. Dual boot causes so many issues, because it isnt manageable on the network. Another huge disadvantage of dual boot is a loss in productivity. You have to run updates on two devices and dual booted system cannot run updates when it isnt booted.
-
@IRJ said in Joining 2 Windows 10 Machines:
If they had some valid reason why they couldnt just install the tools the need on one installation,
I've dealt with software that is bound of the serial of the CPU it's originally installed with/on in the past which would make this nearly impossible to move without involving the software vendor (but maybe you could go the other way with it).
In any case, there are valid reasons to need multiple installations accessible from a single footprint. (it's a benefit of virtualization and or dual-booting today).
But we're just speculating at this point.
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
@IRJ said in Joining 2 Windows 10 Machines:
If they had some valid reason why they couldnt just install the tools the need on one installation,
I've dealt with software that is bound of the serial of the CPU it's originally installed with/on in the past which would make this nearly impossible to move without involving the software vendor (but maybe you could go the other way with it).
In any case, there are valid reasons to need multiple installations accessible from a single footprint. (it's a benefit of virtualization and or dual-booting today).
But we're just speculating at this point.
Yeah I agree about virtualization, but I can't see a valid use case for dual boot with all the negatives it provides
-
@IRJ Yeah I would agree, virtualizing one installation and running it as a VM on the other's hardware would likely make the most sense.
But it will take more time to complete and setup, compared to the alternative(s).
It's just a matter of what the client is really looking for and how much they are willing to spend.
-
@IRJ said in Joining 2 Windows 10 Machines:
but I can't see a valid use case for dual boot with all the negatives it provides
The use case is almost moot at this point.
All we know is the client wants to run two existing installations of Windows 10 on a single workstation and apparently is comfortable enough to use a Boot loader to dual boot.
What's the most cost efficient means to completing this?
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
You're still wrong, the only way to do this legitimately would be to purchase a RETAIL key and apply that additional key to ANY Key that is already assigned to an individual computer.
I'm not aware of there being a limitation to having many OEMs purchased for a single motherboard. Because OEM can be purchased for any piece of hardware, you can get one for a drive, one for RAM, one for CPU, etc. So you can have one copy for each piece of purchased hardware. But this requires you to be the whitebox builder and purchase each OEM license at the time that you purchase each system component.
-
@scottalanmiller said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
You're still wrong, the only way to do this legitimately would be to purchase a RETAIL key and apply that additional key to ANY Key that is already assigned to an individual computer.
I'm not aware of there being a limitation to having many OEMs purchased for a single motherboard. Because OEM can be purchased for any piece of hardware, you can get one for a drive, one for RAM, one for CPU, etc. So you can have one copy for each piece of purchased hardware. But this requires you to be the whitebox builder and purchase each OEM license at the time that you purchase each system component.
Right, but since this box isn't a whitebox (they are existing systems) OEM keys aren't legally an option for purchase according to the license from MS.
Retail product keys are the only option to do this with the hardware that exists today.
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
Right, but since this box isn't a whitebox (they are existing systems) OEM keys aren't legally an option for purchase according to the license from MS.
It's not a white box? I don't know that the NEW box isn't a white box. Did I miss that it is pre-built?
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
Retail product keys are the only option to do this with the hardware that exists today.
If it is existing hardware, then yes, OEM is already out of the question.
-
@scottalanmiller said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
Right, but since this box isn't a whitebox (they are existing systems) OEM keys aren't legally an option for purchase according to the license from MS.
It's not a white box? I don't know that the NEW box isn't a white box. Did I miss that it is pre-built?
All of the equipment is existing, the client wants to consolidate as far as the OP has described.
That would mean the boxes are used, and not white. An additional retail license would be required in any scenario we could propose.
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
@scottalanmiller said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
Right, but since this box isn't a whitebox (they are existing systems) OEM keys aren't legally an option for purchase according to the license from MS.
It's not a white box? I don't know that the NEW box isn't a white box. Did I miss that it is pre-built?
All of the equipment is existing, the client wants to consolidate as far as the OP has described.
That would mean the boxes are used, and not white. An additional retail license would be required in any scenario we could propose.
OIC, I was thinking wrongly that they had one PC and were going to deal with a second one that might not exist yet. Yeah, if they already have it, no OEM.
The bigger issue is that the old one is almost certainly already OEM'd and can't be moved.
-
@scottalanmiller said in Joining 2 Windows 10 Machines:
The bigger issue is that the old one is almost certainly already OEM'd and can't be moved
This is the part that I have questions with. If you purchase a Retail key and "build a new system" and reactivate Windows, would microsoft really lock that installation to that original equipment?
I think it would be allowed to move, since you are moving from an OEM key to a Retail key in good faith and following through with the activation process.
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
This is the part that I have questions with. If you purchase a Retail key and "build a new system" and reactivate Windows, would microsoft really lock that installation to that original equipment?
You mean if you buy a "second" license for the original install so that the OEM license is replaced by a Retail license? I'm 90% sure that MS would be perfectly happy with that arrangement (as they make a shit ton on that one install.)
-
Re: Joining 2 Windows 10 Machines
I'd go about this very differently.
Get him a USB KVM and forget about the hassles of licensing or dealing with both Windows screwing up the UEFI boot order.
It'll be nearly the same user experience as dual booting, with having both iterations of Windows instantly available.
-
@scottalanmiller said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
This is the part that I have questions with. If you purchase a Retail key and "build a new system" and reactivate Windows, would microsoft really lock that installation to that original equipment?
You mean if you buy a "second" license for the original install so that the OEM license is replaced by a Retail license? I'm 90% sure that MS would be perfectly happy with that arrangement (as they make a shit ton on that one install.)
I was thinking as a means of converting (whichever installation was moving) from OEM to Retail and activating that new product key on the Target workstation.
-
@batman said in Joining 2 Windows 10 Machines:
Re: Joining 2 Windows 10 Machines
I'd go about this very differently.
Get him a USB KVM and forget about the hassles of licensing or dealing with both Windows screwing up the UEFI boot order.
It'll be nearly the same user experience as dual booting, with having both iterations of Windows instantly available.
That is also another perfectly valid option, but it's not what the client is asking for.
-
@batman The client may have an older system that they want to keep around for purposes that's near death, so moving it might make sense.
Compared to backing it up and having to go to disk to pull files or whatever.
So many unknowns about this topic to dig much further.
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
@Obsolesce said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
@IRJ said in Joining 2 Windows 10 Machines:
Is there any real reason for this? OP doesn't mention it either
IDK, I thought the same thing as well, but I didn't not want to provide a potentially useful answer.
When the objective or goal itself is useless, any answer you feel is useful would then default to useless anyways.
So, the only potentially useful answer would be to get the OP to re-evaluate the situation and perhaps approach it differently altogether.My response is to get more detail from @CCWTech as to the reason the client wants this. I don't know why the client wants to do this as it's not explained anywhere in this topic.
@CCWTech why just post and disappear? Give us some more details.
Sorry, I've been crazy busy. He doesn't want to have to reinstall programs. I think the F12 boot option may work the best. As long as the hardware isn't too different and it will actually boot.
-
@CCWTech said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
@Obsolesce said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
@IRJ said in Joining 2 Windows 10 Machines:
Is there any real reason for this? OP doesn't mention it either
IDK, I thought the same thing as well, but I didn't not want to provide a potentially useful answer.
When the objective or goal itself is useless, any answer you feel is useful would then default to useless anyways.
So, the only potentially useful answer would be to get the OP to re-evaluate the situation and perhaps approach it differently altogether.My response is to get more detail from @CCWTech as to the reason the client wants this. I don't know why the client wants to do this as it's not explained anywhere in this topic.
@CCWTech why just post and disappear? Give us some more details.
Sorry, I've been crazy busy. He doesn't want to have to reinstall programs. I think the F12 boot option may work the best. As long as the hardware isn't too different and it will actually boot.
Don't forget you would need to purchase an additional license.
