I have a number of computers. What I need to know is, can I take my hard drive that contains my Windows 7 OS, and move it from one computer to another so I don't need to buy an OS for each computer? I know I can't just download the OS onto a disk and install it on another computer. The reason I ask this is that I build computers and I like to give them a test run after completion without having to buy an OS for each build and some of the people I build for prefer a different OS than Windows 7. Thanks for any info!
Can I move a hard drive with Windows 7 from one computer to another?
- Thread starter sheriff12
- Start date
Solution
jitpublisher
Splendid
- May 16, 2006
- 8,747
- 2
- 31,960
No, you cannot take a hard drive with an installed Win 7 OS and move it from computer to computer. If you are a builder as you say you are, one would think you should know the reasons why.
- Aug 24, 2012
- 16,247
- 1,516
- 87,240
Simple answer: No
Not so simple answer: No, not without reinstalling each time, unless the hardware is identical. Either way you will have to reactivate each time. If you want to do a burn in then just use a Linux LiveDVD.
Not so simple answer: No, not without reinstalling each time, unless the hardware is identical. Either way you will have to reactivate each time. If you want to do a burn in then just use a Linux LiveDVD.
- Aug 24, 2012
- 16,247
- 1,516
- 87,240
And here's why you can't use Sysprep to move a drive from one system to another:
https://support.microsoft.com/en-us/kb/828287
You will, eventually, encounter problems if you move a drive that has been in production for a period of time. Sysprep is intended only for use on newly imaged systems.
https://support.microsoft.com/en-us/kb/828287
You will, eventually, encounter problems if you move a drive that has been in production for a period of time. Sysprep is intended only for use on newly imaged systems.
FALC0N
Splendid
- Apr 5, 2010
- 3,881
- 60
- 23,240
Why? All because Microsoft says it's an unsupported scenario? You do realize how many things are "unsupported" scenarios according to Microsoft, but still work perfectly well?
If your concerned about long term stability, just do a repair install after the move.
If your concerned about long term stability, just do a repair install after the move.
jitpublisher
Splendid
- May 16, 2006
- 8,747
- 2
- 31,960
And just because you can do it does not mean its brightest idea in the world either. There is no simple way to move a drive with an installed Windows OS from PC to PC all the time, it's simply going to be a pain. If you want to spend hours doing repair installs, reinstalling the correct drivers and setting up the OS each time you move the drive, all the while with the possibility that each move could end up needing a complete new install to get everything working right again. Not to mention reactivating the OS each time. Even a retail OS version will only allow so many activations before you have to call Microsoft and get a new activation string. Its just not a great idea.
WinOutreach2
Distinguished
- Mar 3, 2011
- 413
- 0
- 19,160
In your scenario I would recommend preparing a deployment environment with the evaluation version of Windows that allows you to image the new systems quickly with your test environment.
For example on your server or workstation you could install the Microsoft Deployment Toolkit (MDT) and then import the Windows 8.1 Enterprise Evaluation from the TechNet Evaluation Center. Depending on the test environment you are looking to implement, you could use MDT to install your test software or create a custom image with the software installed. You could then create USB installation media that would install this image on each new computer.
Some notes worth considering:
• If you create a custom image, you will want to use a virtual machine for the reference system. A virtual machine with minimal drivers is the surest way to ensure maximum compatibility with various hardware configurations.
• Your installation media can include the image, a.k.a. offline media, or can be a minimal environment that installs the image over the network.
• If you import your applications into MDT rather than creating a custom image, the installation process can be granular. You can be prompted with a list of applications to install each time and pick and choose the ones you need.
• While the deployment will include all of the drivers of a native installation out of the box, you may need to import specific drivers into MDT to enable certain devices on the resulting computer. You could also just install those drivers manually on the computer after deployment. While this is an extra step, it addresses the possibility of the environment crashing or refusing to work on each new computer.
For example on your server or workstation you could install the Microsoft Deployment Toolkit (MDT) and then import the Windows 8.1 Enterprise Evaluation from the TechNet Evaluation Center. Depending on the test environment you are looking to implement, you could use MDT to install your test software or create a custom image with the software installed. You could then create USB installation media that would install this image on each new computer.
Some notes worth considering:
• If you create a custom image, you will want to use a virtual machine for the reference system. A virtual machine with minimal drivers is the surest way to ensure maximum compatibility with various hardware configurations.
• Your installation media can include the image, a.k.a. offline media, or can be a minimal environment that installs the image over the network.
• If you import your applications into MDT rather than creating a custom image, the installation process can be granular. You can be prompted with a list of applications to install each time and pick and choose the ones you need.
• While the deployment will include all of the drivers of a native installation out of the box, you may need to import specific drivers into MDT to enable certain devices on the resulting computer. You could also just install those drivers manually on the computer after deployment. While this is an extra step, it addresses the possibility of the environment crashing or refusing to work on each new computer.
TRENDING THREADS
-
-
Question Half the time, my new PC has high input lag/sticking, terrible frames, and stuttering
- Started by aFishIntheSea
- Replies: 1
-
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 3K
-
Question Looking to pay around $500 for a desktop computer, what brands are recommended and is Newegg safe to buy from?
- Started by arnoldhwang
- Replies: 14
-
Question Is this fanless RTX 4090 amazon listing legit?
- Started by kristianp
- Replies: 7
Facebook
Twitter
Instagram