Joining 2 Windows 10 Machines
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
How would he even license this?
But a simple question, why not just install the other computers hdd into this system and select the boot device?
That or run it as a VM.
-
@wrx7m said in Joining 2 Windows 10 Machines:
That or run it as a VM.
That is also an option, but based on the absurd question I assumed this client wasn't willing to pay for anything beyond the .5 hours it would take to install this drive into that computer and show said client how to select the boot disk.
-
Also we don't know if this is Windows 10 Professional (or home) or some other version, so setting up Hyper-V on one installation may not be an option while keeping the system intact .
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
Also we don't know if this is Windows 10 Professional (or home) or some other version, so setting up Hyper-V on one installation may not be an option while keeping the system intact .
Could go virtual box too
-
@wrx7m said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
Also we don't know if this is Windows 10 Professional (or home) or some other version, so setting up Hyper-V on one installation may not be an option while keeping the system intact .
Could go virtual box too
Still would have issues legally with it, but yeah. . . .
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
@wrx7m said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
Also we don't know if this is Windows 10 Professional (or home) or some other version, so setting up Hyper-V on one installation may not be an option while keeping the system intact .
Could go virtual box too
Still would have issues legally with it, but yeah. . . .
Yeah. He would definitely need a license for both.
-
@wrx7m said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
@wrx7m said in Joining 2 Windows 10 Machines:
@DustinB3403 said in Joining 2 Windows 10 Machines:
Also we don't know if this is Windows 10 Professional (or home) or some other version, so setting up Hyper-V on one installation may not be an option while keeping the system intact .
Could go virtual box too
Still would have issues legally with it, but yeah. . . .
Even if the client went with the vBox route, it might cost more in money to convert 1 system and import it than it would be to just connect the other disk into the system and teach the client how to select the boot device. .
-
Yeah. Probably. I guess it just depends on if they need both accessible at the same time or just one or the other.
-
@wrx7m said in Joining 2 Windows 10 Machines:
Yeah. Probably. I guess it just depends on if they need both accessible at the same time or just one or the other.
By the very first post in this topic, the client is okay with dual booting. That would mean that they don't need access to both systems at the same time. . .
-
If he truly want to be able to run either one or the other, I suggest a hotswap drive enclosure. Insert the drive for the installation you wish to use.
If he wants access to his old PC from his new PC, I suggest virtualbox. There are of course other reasons to dual boot but I find this to be a common one. Virtualbox works extremely well for this.
-
Yeah there are plenty of reasons to want to keep a system around, but none of that matters in this case.
The simple solution, plug the one disk into the other chasis, show the client how to select the boot disk.
It's quick and it cost them near to nothing to have done. They get what they want from the system and @CCWTech can move on with his day.
If the client wants to spend more money on this, than other options can be considered, but I believe he was simply over thinking this one.
-
Also don't forget that some clients can't have two computers on their desk, but if you show them how to remote desktop into their second PC, that might be all it takes to make them happy.
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
Yeah there are plenty of reasons to want to keep a system around, but none of that matters in this case.
The simple solution, plug the one disk into the other chasis, show the client how to select the boot disk.
It's quick and it cost them near to nothing to have done. They get what they want from the system and @CCWTech can move on with his day.
If the client wants to spend more money on this, than other options can be considered, but I believe he was simply over thinking this one.
Too complicated in my experience. For the user that is.
-
@Pete-S said in Joining 2 Windows 10 Machines:
Too complicated in my experience. For the user that is.
More complicated than a boot loader?
-
Why not just create a new user on his pc, then copy the "2nd" pc's user to that new user folder. Then install anything he actually needs.
-
Dual boot and virtualization seem kinda pointless when you running the exact same OS. It might make sense if you were testing and wanted to blow things up. But that doesn't seem to be the case here
-
@IRJ said in Joining 2 Windows 10 Machines:
Why not just create a new user on his pc, then copy the "2nd" pc's user to that new user folder. Then install anything he actually needs.
This would only pull the user files over and not the entire environment.
(I was under the impression that the user simply wants to run two distinct OS's because of some applications that are configured on each system)
-
@DustinB3403 said in Joining 2 Windows 10 Machines:
@IRJ said in Joining 2 Windows 10 Machines:
Why not just create a new user on his pc, then copy the "2nd" pc's user to that new user folder. Then install anything he actually needs.
This would only pull the user files over and not the entire environment.
(I was under the impression that the user simply wants to run two distinct OS's because of some applications that are configured on each system)
Is there any real reason for this? OP doesn't mention it either
-
@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.
-
Installing a boot loader (like grub) could probably work, but BIOS already has a boot loader built in. Adding the complexity of installing another boot loader on top of an existing installation, and then converting a physical installation from one host to a physical installation on another host, under a custom boot loader.
Is way more complex, and likely would cause all sorts of issues.
I would stick with using the existing BIOS to manage the boot device and simply train the customer how to hit F12 or Delete or whatever the boot selection key is at startup.
You can name the boot devices from within the OS.
